7.1 Introduction

7.1.1 Table of contents

7.1.2 Objectives

The primary objectives of the specifications in this clause are:

1. to promote interoperability by eliminating arbitrary subsets of, or extensions to, ISO/IEC 14772;
2. to promote uniformity in the development of conformance tests;
3. to promote consistent results across VRML browsers;
4. to facilitate automated test generation.

7.1.3 Scope

Due to the nature of this Part, it is not possible to specify the conformance tests of an individual language bindings to the specification. Separate Conformance sections shall be provided within each language that provide the necessary information to implement language specific binding conformance tests.

A concept of base profile conformance is defined to ensure interoperability of VRML applications and VRML browsers. Base profile conformance is based on a set of limits and minimal requirements. Base profile conformance is intended to provide a functional level of reasonable utility for VRML language bindings while limiting the complexity and resource requirements of VRML browsers. Base profile conformance may not be adequate for all uses of the SAI.

7.2 Conformance

7.2.1 Conformance to ISO/IEC 14772-1

1. Requests of the Browser services shall conform exactly to the behaviour as specified in ISO/IEC 14772-1 4.12 Scripting.Where there are differences, the provisions of 6.3, Browser Services shall take precedence over ISO/IEC 14772-1 4.12.
2. Where a browser is required to read and parse VRML content, it shall be able to handle any VRML file that conforms to the base profile defined in ISO/IEC 14772-1 7.3.3 VRML requirements for conforming to the base profile.
3. Only nodes in the top level world (the file defined by the getWorldURL service) that are named with the DEF construct shall be visible to the getNode browser service request.
4. There shall be no difference in treatment of events that result from an external service request compared to events generated within the VRML browser environment. That is, externally generated event cascades shall have no favoured treatment.

7.2.2 Language bindings

1. It implements the services defined in this specification including return values, error conditions and asychronous events.
2. The services implemented conform to the base profile of required services.
3. It provides sections outlining conformance and minimum requirements of implementations of that binding.

7.3 Minimum Requirements

7.3.1 Requirements for implementations

A language binding must at a minimum implement the service requirements outlined in 7.3.2 Base Profile. It may also define its own optional set of minimum requirements that are no less than the requirements of this section. A browser implementation must, in addition to the base support profile, also support the minimum capabilities defined in 7.3.2 Base Profile. In general, the browser requirements are specified as more general requirements with the underlying representation that specific language issues.

Where a browser implements two or more langauge bindings with different levels of minimum requirements, the browser must support the minimum requirements for each language separately. Therefore, if one language has higher requirements, the lower requirements of the other shall not be used.

7.3.2 Base Profile

For all these requirements it shall be assumed that the language binding shall provide complete implementation of all the parameters required for the individual services. Language bindings of data types may be implemented as primitive types in the target language rather than separate data types. Table 7.2 indicates where this may be permitted.
 

http://www.vrml.org/Specifications/VRML97/part2/conformance.html