Legacy Issue Number: 18781
Source: THALES ( Hugues Vincent)
Checked with Xerces, the XSD file has many errors which come from the lack of use of namespace.
Lines: 37, 57, 60, 108, 111, 114, 136, 139, 143, 146, 241, 248, 267, 270, 277, 294, 370, 373, 435, 439, 442, 445, 448, 465, 495, 520, 523, 557, 560, 578, 581, 640
Xerces error (for the first one: "filename"): "E [Xerces] src-resolve.4.1: Error resolving component 'fileName'. It was detected that 'fileName' has no namespace, but components with no target namespace are not referenceable from schema document 'http://www.omg.org/spec/DDS-XTypes/20120202/dds-xtypes_type_definition.xsd'. If 'fileName' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'fileName' has no namespace, then an 'import' without a "namespace" attribute should be added to 'http://www.omg.org/spec/DDS-XTypes/20120202/dds-xtypes_type_definition.xsd'."
Reported: DDS-XTypes 1.1 — Mon, 17 Jun 2013 04:00 GMT
Disposition: Resolved — DDS-XTypes 1.2
Fixing Namespace in XSD files
The original XSD schemas had multiple problems related to namespaces.
To address these issues and make it simpler for other specifications to refer to the types define in the schema included in the specification, we are applying the so-called Chameleon Namespace Design, dividing the original schema into two different XSD files:
1. dds_types.xsd, which can be used by applications to validate the types defined in an XML file. This file sets targetNamespace="http://www.omg.org/dds/".
2. dds_types_definition.xsd, which includes all the type definitions without specifying a targetNamespace.
Accompanying these two XSD files we include a non-normative XML file that demonstrate how to load dds_types.xsd with the right namespace to define a set of data types.
Updated: Thu, 22 Jun 2017 16:42 GMT