Re: [ubl-dev] cct Definition missing in multiple locations inUBL-UnspecializedDatatypes-1.0.xsd?

["Stephen Green" <stephen_green@bristol-city.gov.uk>]

Bryan

Yes, there has been discussion in UBL TC of this issue a few times since UBL 1.0 beta so
it is a known issue which will probably be part of a UBL 1.0 FAQ document.

There is no need for definitions of datatypes in the UnspecializedDatatypes Schema since these are
defined not by UBL but by the CCTS (though not in Schema format). The issue is then
should ccts:Definition be defined in theCoreComponentParameters Schema as minOccurs="1"?
The problem occurs because the ccts:Definition was primarily designed for the document and reusable
model BIEs. Using the CoreComponentParameters Schema and the model spreadsheets to model
and generate Schemas for the UnspecializedDatatypes, etc was a later move.

It was agreed that the CoreComponentParameters Schema be left like this for UBL 1.0 since validation of elements within 
xsd:annotation/xsd:documentation is not mandatory and most validators leave it alone.
It seems that XSV is the main validator which does throw errors for this. 

I expect the CoreComponentParameters Schema will be improved for UBL 1.1 with the change from 
minOccurs="1" for some of the relevant elements to minOccurs="0".

All the best

Stephen Green


>>> Bryan Rasmussen <brs@itst.dk> 15/09/04 11:29:01 >>>
Hey,
In various locations in the unspecializedDatatypes schema, for example:   
<xsd:complexType name="MeasureType">
    <xsd:annotation>
      <xsd:documentation>
        <ccts:Component>
          <ccts:ComponentType>DT</ccts:ComponentType>
          <ccts:DictionaryEntryName>Measure. Type</ccts:DictionaryEntryName>
          <ccts:RepresentationTerm>Measure</ccts:RepresentationTerm>
        </ccts:Component>
...
there is no ccts:Definition, according to
UBL-CoreComponentParameters-1.0.xsd 

 <xsd:complexType name="ComponentType">
        <xsd:sequence>
            <xsd:element ref="ComponentType" minOccurs="1" maxOccurs="1"/>
            <xsd:element ref="DictionaryEntryName" minOccurs="1"
maxOccurs="1"/>
            <xsd:element ref="Version" minOccurs="0" maxOccurs="1"/>
            <xsd:element ref="Definition" minOccurs="1" maxOccurs="1"/>
            <xsd:element ref="Cardinality" minOccurs="0" maxOccurs="1"/>
            <xsd:element ref="ObjectClassQualifier" minOccurs="0"
maxOccurs="1"/>
            <xsd:element ref="ObjectClass" minOccurs="0" maxOccurs="1"/>
            <xsd:element ref="PropertyTermQualifier" minOccurs="0"
maxOccurs="1"/>
            <xsd:element ref="PropertyTermPossessiveNoun" minOccurs="0"
maxOccurs="1"/>
            <xsd:element ref="PropertyTermPrimaryNoun" minOccurs="0"
maxOccurs="1"/>
            <xsd:element ref="PropertyTerm" minOccurs="0" maxOccurs="1"/>
            <xsd:element ref="RepresentationTerm" minOccurs="0"
maxOccurs="1"/>
            <xsd:element ref="DataTypeQualifier" minOccurs="0"
maxOccurs="1"/>
            <xsd:element ref="DataType" minOccurs="0" maxOccurs="1"/>
            <xsd:element ref="AssociatedObjectClassQualifier" minOccurs="0"
maxOccurs="1"/>
            <xsd:element ref="AssociatedObjectClass" minOccurs="0"
maxOccurs="1"/>
            <xsd:element ref="AlternativeBusinessTerms" minOccurs="0"
maxOccurs="1"/>
            <xsd:element ref="Examples" minOccurs="0" maxOccurs="1"/>
        </xsd:sequence>
    </xsd:complexType>

this would seem to be wrong, am I mistaken in my interpretation of missing
definition? XSV seems to consider the lack of definition to be an error.