OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-ndrsc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [ubl-ndrsc] Handcrafted Schema for Core Component Types


Hello all,

I attached a zip-file with four different versions of handcrafted core component types.

1st Version
========
I defined in the first version (CoreComponentTypes_1.xsd) for every CCTs a tuple existing of a simpleType and contentType. Example:

	<xsd:simpleType name="AmountContent" id="000106">
		<xsd:restriction base="xsd:decimal"/>
	</xsd:simpleType>
	<xsd:complexType name="AmountType" id="000105">
		<xsd:simpleContent>
			<xsd:extension base="cct:AmountContent">
				<xsd:attribute name="currencyID" type="xsd:token" use="required" id="000107"/>
				<xsd:attribute name="codeListVersionID" type="xsd:token" use="optional" default="2002"/>
				<xsd:attributeGroup ref="cct:commonAttributes"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>

Additionally, it using the standardized namespaces for language and linking. It will be used the attribute xml:lang instead of languageID and xlink:href, xlink:role and xlink:type for the linking to another locations. 

2nd Version
=========
In the second version do the CCTs based on the built-in datatypes directly. Therefore, they do not have a tuple of simpleType for the Content and complexType for the CCTs itself.
Example:

	<xsd:complexType name="AmountType" id="000105">
		<xsd:simpleContent>
			<xsd:extension base="xsd:decimal">
				<xsd:attribute name="currencyID" type="xsd:token" use="required" id="000107"/>
				<xsd:attribute name="codeListVersionID" type="xsd:token" use="optional" default="2002"/>
				<xsd:attributeGroup ref="cct:commonAttributes"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>

This version does have the (W3C) standardized definitions for language and linking in a different namespace, too. 

3rd Version
=========
The third version is the same as the 1st version but do not have standardized definitions for language and linking.

4th Version
=========
The fourth version is the same as the 2nd version but do not have standardized definitions for language and linking.

We should discuss, which kind of handcrafted xml schema for CCTs should be the best one. 

Kind regards,

	Gunther


 <<CoreComponents.zip>> 

Attachment: CoreComponents.zip
Description: Binary data



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC