Extensible 3D (X3D)
Part 1: Architecture and base components
This clause addresses conformance of X3D files, X3D generators and X3D browsers.
The topics covered in this clause are shown in Table 6.1.
The primary objectives of the specifications in this clause are:
Conformance is defined for X3D files and for X3D browsers. For X3D generators, conformance guidelines are presented for enhancing the likelihood of successful interoperability.
A concept of base profile conformance is defined to ensure interoperability of X3D generators and X3D 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 X3D generators while limiting the complexity and resource requirements of X3D browsers. Base profile conformance may not be adequate for all uses of X3D.
This clause addresses the X3D data stream and implementation requirements. Implementation requirements include the latitude allowed for X3D generators and X3D browsers. This clause does not directly address the environmental, performance, or resource requirements of the generator or browser.
This clause does not define the application requirements or dictate application functional content within a X3D file.
The scope of this clause is limited to rules for the open interchange of X3D content.
An X3D file is syntactically correct according to this part of ISO/IEC 19775 if the following conditions are met:
A X3D generator is conforming to ISO/IEC 19775 if all X3D files that are generated are syntactically correct and meet the requirements state in 6.2.1 Conformance of X3D files.
A X3D generator conforms to a profile if it can be configured such that all X3D files generated conform to that profile.
An X3D browser is conforming if:
There is no minimum complexity which is required of (or appropriate for) X3D generators. Any compliant set of nodes of arbitrary complexity may be generated, as appropriate to represent application content, and which produce only the nodes allowed by the applicable profile.
Each profile defines the minimum complexity which shall be supported by an X3D browser in support of that profile. Browser implementations may choose to support greater limits but may not reduce the limits described for the applicable profile. When the X3D file contains nodes which exceed the limits implemented by the browser, the results are undefined. The words "optionally supported" in the minimum browser support column refers only to the display of the item; in particular, set_ events to ignored inputOutput fields shall still generate corresponding _changed events. Where latitude is specified in a table of minimum support requirements for a particular node, full support is required for other aspects of that node.