← Prev in month ← Prev in thread

errors in RepresentationTerms schema, and suggested change in schemaLocation

From
Dave Carlson <>
Date
2003-11-09T21:39:46+00:00
ID
08a801c3a70a$9d82ea60$0100a8c0@Beethoven
Thread
errors in RepresentationTerms schema, and suggested change in schemaLocation
Using the 1.0 beta schemas sent to me yesterday, I validated the test documents
using Xerces 2.5.0 and discovered 3 errors in the RepresentationTerms schema.
Also, a potential problem with xsi:schemaLocation value in examples.

The error messages are shown below.  In XSD, a restricted type must use element
types that are equal or narrower than the same elements from the base type.
The types in these three elements are incompatible with their base types.  I
modified the RepresentationTerms schema to be valid.  See attached.

(line: 435 in: UBL-RepresentationTerms-1.0-beta.xsd):
derivation-ok-restriction.2.1.2: Error for type 'TextType'. The attribute use
'languageID' in this type has type 'token', which is not validly derived from
'language', the type of the matching attribute use in the base type.

(line: 457 in: UBL-RepresentationTerms-1.0-beta.xsd):
derivation-ok-restriction.2.1.2: Error for type 'NameType'. The attribute use
'languageID' in this type has type 'token', which is not validly derived from
'language', the type of the matching attribute use in the base type.

(line: 94 in: UBL-RepresentationTerms-1.0-beta.xsd):
derivation-ok-restriction.2.1.2: Error for type 'BinaryObjectType'. The
attribute use 'mimeCode' in this type has type 'string', which is not validly
derived from 'token', the type of the matching attribute use in the base type.

--------------------------------
I also get a Xerces error from the xsi:schemaLocation value in the sample
instances.  At first I thought it was due to the way I was calling Xerces, but
realized it is due to the use of "\" instead of "/" in the xsi:schemaLocation
attribute value.  I strongly suggest replacing use of "\" with "/" in the
relative path location for schemas in the sample docs.  Making this change
eliminates the Xerces error message.

Errors from schemaLocation:

(line: 2 in: UBL-Invoice-1.0-beta-Joinery-Example.xml):
cvc-datatype-valid.1.2.1: '..\xsd\maindoc\UBL-Invoice-1.0-beta.xsd' is not a
valid value for 'anyURI'.

(line: 2 in: UBL-Invoice-1.0-beta-Joinery-Example.xml): cvc-attribute.3: The
value 'urn:oasis:names:tc:ubl:Invoice:1:0-beta
..\xsd\maindoc\UBL-Invoice-1.0-beta.xsd' of attribute 'xsi:schemaLocation' on
element 'Invoice' is not valid with respect to its type, 'null'.
← Prev in month ← Prev in thread