December 2014  
Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      

  2009/05/15

ATG and TMG have planned a joint Core Components Working Group and ATG meeting for the week of 22 June 2009 at the SAP offices in the Ronald Reagan International Trade Center in Washington D.C.  Principal focus of this work will be to finalize the CCTS and NDR specifications, promote the Data Type Catalogue to ODP Implementation Verification, and significantly progress the Context Methodology Specification.  Meeting details can be found here.

Posted at 15 May @ 10:28 AM by Mark Crawford | 0 comments
  2009/04/17
Labels: atg_news

ATG1 is happy to inform you that the databases for the April 2009 DMR review in Rome have been uploaded.

They are available from ATG1 - Documents for 14th Forum Meeting (April 2009).

Posted at 17 Apr @ 2:41 AM by gait.boxman@tie.nl | 0 comments
  2008/11/06
Last changed: Nov 06, 2008 09:17 by decala
Labels: agenda, atg_news

Title ATG
Topic Full meeting
Location Saly,Senegal
Date 10-14 November 2008
Start Time 09:00 – Timezone: GMT
End Time 16:00 – Timezone: GMT

Agenda

  1. – Welcome
  2. – Agree on agenda
  3. – Select note taker
  4. – Review Open Action Items
  5. – Other business
  6. – Next meeting

Information

Meeting information.


Posted at 06 Nov @ 9:08 AM by decala | 0 comments
  2008/09/05
Last changed: Sep 05, 2008 10:00 by decala
Labels: atg_news, agenda

Title ATG
Topic Interim meeting
Location Pearl River, New York, USA
Date 22-26 September 2008
Start Time 09:00 – Timezone: EDT
End Time 16:00 – Timezone: EDT

Agenda

  1. – Welcome
  2. – Agree on agenda
  3. – Select note taker
  4. – Review Open Action Items
  5. – Other business
  6. – Next meeting

Information

Meeting information.


Posted at 05 Sep @ 9:15 AM by decala | 0 comments
  2008/08/06

The September F2F will be in Pearl River NY from 22 - 26 September.

Posted at 06 Aug @ 7:01 AM by Mark Crawford | 0 comments
  2008/07/23

Minutes from the ATG face to face meeting in Roros, Norway are available here\.

Posted at 23 Jul @ 3:14 PM by Michael Rowell | 0 comments
  2008/07/14
Last changed: Jul 14, 2008 01:31 by gunther.stuhec

Three options are possible: 

  1. Option 1 - xsd:documentation refers to element group
  2. Option 2 - xsd:documentation refers to specific group element such as ABIEDocumentation
  3. Option 3 - xsd:documentation refers to a single root element

Option 1

Option 1 is a mixture of XML Schema and CCTS annotation/documentation schema. The xsd:documentation refers to the specific element group such as doc:ABIE_Documentation, directly. Each element group must be selected in accordance with the defined artefact type at XML Schema level. The following figure shows the reference between xsd:documentation and the specific element groups.

Advantages:

  • No interim level and redundancy
  • Efficient representation of documentation as it required

Disadvantages:

  • The reference between xsd:documentation and the specific element groups does not exactly follow the XML Schema conventions
  • The selection of specific element groups requires additional tool support

Option 2 

In option 2 the xsd:documentation refers to a root element, which considers specific element group. Every CCTS specific artefact requires a root element, which must be spearately named such as ABIEDocumentation etc. The following figure shows the reference between xsd:documentation and the root elements.

Advantages:

  • Follows XML Schema conventions
  • Separates XML Schema and the documentation schema

Disadvantages:

  • Has an (unnecessary) additional hierachical level, because of XML Schema restrictions
  • The root element names considers redundant information such as "Documentation" and the acronym type.
  • Needs tool support, anyway.

Option 3 

In option 2 the xsd:documentation refers to a single root element, which is named as CCTSDocumentation. The CCTSDocumentation has a choice of the documentation of the CCTS specific. Each specific documentation must be separately named such as ABIEDocumentation etc. The following figure shows the reference between xsd:documentation and the single root element.

Advantages:

  • It is the preference of XML Schema, having a single root element within a schema

Disadvantages:

  • Has two (unnecessary) additional hierachical levels, because of XML Schema restrictions + preferemce
  • The two additional elements considers redundant information such as "CCTS Documentation", and acronym type + "Documentation".
  • Needs tool support, anyway.
Posted at 14 Jul @ 1:12 AM by gunther.stuhec | 0 comments
  2008/07/11
Last changed: Jul 11, 2008 10:29 by gunther.stuhec

Introduction

The schema of annotation/documentation is in the file: CCTS_Documentation_in_XMLSchema_0p1.zip.
It is located within the following path sructure: www.unece.org/uncefact/documentation/standard/
The file name is: XMLNDR_Documentation_3p0.xsd

Some Conventions/Suggestions and Change Requests

There are some recommendations, which are considered at the provided schema so far:

  1. Each annotation/document artefact follows the CCTS and XMLNDR convention itself. The reason, why I did this significant change is the question regarding the self-usage of CCTS. Many customers asked me, why is all the CCTS stuff is not CCTS compliant itself. This is comparable, if a software vendor of office or business solutions will not use his own software. But I guess, we're still in this kind of stage, in where we can do this shift.
    This means in detail:
    • The element names are aligned to the CCTS and XMLNDR naming conventions
    • Each element is based on the appropriate BDT type
    • If a element represents a coded information, this element is based on a code BDT type.
    • Each code BDT type refers to a specific code list according the XMLNDR code list conventions
  2. Additionally, each element that represents an identifier is based on an identifier BDT type. This identifier BDT type refers to a specific identifier scheme, which provides the specific pattern of the identifier scheme. Therefore I recommend
    • The pattern definition should be a part of the additional code list / identifier scheme meta model
    • The XMLNDR should consider an "Identifier Scheme Schema Module", file naming conventions, prefix conventions, the structure of the "Identifier Scheme Schema Modeule", and the way of reference within the BDT schema module.
    • You'll find some examples in the attached zip-file.
  3. The usage rule is a complex element group, because it considers several information that may repeated. The current usage rule is aligned to the CCTS V3.0 meta model.
  4. Each specific element group should be of the annotation/documentation of the appropriate artefact.
  5. The business context part is not a part of annotation/documentation. It follows the resoluition 14 of the Roros-meeting notes - see:
    "The proposal is to define the context in its own xml schema that is used to define its content and structure. It is further proposed that this should be carried within xsd:appInfo."
  6. The documentation should have another prefix (such as "doc"), in order to be more aligned to the documentation and to be a differentiator to the business context prefix, which could be "bc".
  7. The documentation is located in www.unece.org/uncefact/documentation/standard

Issues / Next Steps

  • Adjust minor corrections/changes (such as correct the types)
  • Correct the annotation/documentation of the BDTs, and code lists

Documentation XML Schema Structure:

The XMLNDR annotation/documentation structure is as follows:

<xsd:schema
   xmlns:doc="urn:un:unece:uncefact:documentation:standard:XMLNDRDocumentation:3"
   xmlns:xsd="http://www.w3.org/2001/XMLSchema"
   xmlns:bdt="urn:un:unece:uncefact:data:standard:BusinessDataType:3
   targetNamespace="urn:un:unece:uncefact:documentation:standard:XMLNDRDocumentation:3"
   elementFormDefault="qualified" attributeFormDefault="unqualified">
   <xsd:import namespace="urn:un:unece:uncefact:data:standard:BusinessDataType:3"
      schemaLocation="http://www.unece.org/uncefact/data/standard/BusinessDataType_3p0.xsd"/>
   <xsd:group name="RootSchema_Documentation">
      <xsd:sequence>
         ....
      </xsd:sequence>
   </xsd:group>
   <xsd:group name="ABIE_Documentation">
      <xsd:sequence>
         ....
      </xsd:sequence>
   </xsd:group>
   <xsd:group name="BBIE_Documentation">
      <xsd:sequence>
         ....
      </xsd:sequence>
   </xsd:group>
   <xsd:group name="ASBIE_Documentation">
      <xsd:sequence>
         ....
      </xsd:sequence>
   </xsd:group>
   <xsd:group name="BDT_Documentation">
      <xsd:sequence>
         ....
      </xsd:sequence>
   </xsd:group>
   <xsd:group name="BDT_SC_Documentation">
      <xsd:sequence>
         ....
      </xsd:sequence>
   </xsd:group>
   <xsd:group name="CodeList_Documentation">
      <xsd:sequence>
         ....
      </xsd:sequence>
   </xsd:group>
   <xsd:group name="CodeValue_Documentation">
      <xsd:sequence>
         ....
      </xsd:sequence>
   </xsd:group>
   <xsd:group name="IdentifierScheme_Documentation">
      <xsd:sequence>
         ....
      </xsd:sequence>
   </xsd:group>
   <xsd:complexType name="UsageRuleType">
      <xsd:sequence>
         <xsd:element name="UniqueID" type="bdt:IDType" minOccurs="0"/>
         <xsd:element name="Name" type="bdt:NameType" minOccurs="0"/>
         <xsd:element name="Description" type="bdt:TextType"/>
         <xsd:element name="FormalConstraint" type="bdt:TextType"/>
         <xsd:element name="FormalConstraintTypeCode" type="bdt:FormalConstraintTypeCodeType" minOccurs="0"/>
         <xsd:element name="ConditionTypeCode" type="bdt:ConditionTypeCodeType" minOccurs="0"/>
      </xsd:sequence>
   </xsd:complexType>
</xsd:schema>

Each group provides the specific data as defined in table 6-1, and is shown below.

Element Group Structures

Now to the structures of each part in detail:

Documentation of RootSchema

<xsd:group name="RootSchema_Documentation">
		<xsd:sequence>
			<xsd:element name="UniqueID" type="bdt:EntityUniqueIdentifierType"/>
			<xsd:element name="VersionID" type="bdt:VersionIdentifierType"/>
			<xsd:element name="AcronymCode" type="bdt:DocumentationAcronymCodeType" fixed="RootSchema"/>
			<xsd:element name="Name" type="bdt:NameType"/>
			<xsd:element name="Definition" type="bdt:TextType"/>
			<xsd:element name="BusinessTermName" type="bdt:NameType" minOccurs="0" maxOccurs="unbounded"/>
		</xsd:sequence>
	</xsd:group>

Proposed adoptions according CCTS conventions:

  • The UniqueID is based on EntityUniqueIdentifierType, which refers to the schema module "CCIS1 Entity Unique Identification Scheme" that provides the suggested schema pattern: "UNBE[0-9]{6}"
  • The VersionID is based on VersionIdentifierType, which refers to the scheme module "CCTS4 Versioning Identification Scheme" that provides the suggested schema pattern: [0-9]{1,2}\.[0-9]{2}
  • The AcronymCode is based on DocumentationAcronymCodeType, which refers to the code list "CCTS1 Documentation Acronym Code List", whereby only the code "RootSchema" is used.
  • The "Name" should be based on the BDT "NameType". It is not required to use "languageCode". The language can be globally expressed by the construct <xsd:documentation xml:lang="en-US">.
  • The "Definition" is based on BDT "TextType". The language representation should follow the same approach as described for name.
  • BusinessTermName should be used instead of "BusinessTerm", because of the CCTS naming conventions.

Documentation of ABIE

<xsd:group name="ABIE_Documentation">
		<xsd:sequence>
			<xsd:element name="UniqueID" type="bdt:EntityUniqueIdentifierType"/>
			<xsd:element name="VersionID" type="bdt:VersionIdentifierType"/>
			<xsd:element name="AcronymCode" type="bdt:DocumentationAcronymCodeType" fixed="ABIE"/>
			<xsd:element name="DictionaryEntryName" type="bdt:NameType"/>
			<xsd:element name="Definition" type="bdt:TextType"/>
			<xsd:element name="ObjectClassQualifierName" minOccurs="0" maxOccurs="unbounded">
				<xsd:complexType>
					<xsd:complexContent>
						<xsd:extension base="bdt:TextType">
							<xsd:attribute name="orderKey" type="xsd:positiveInteger" use="required"/>
						</xsd:extension>
					</xsd:complexContent>
				</xsd:complexType>
			</xsd:element>
			<xsd:element name="ObjectClassName" type="bdt:NameType"/>
			<xsd:element name="UsageRule" type="doc:UsageRuleType" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="BusinessTermName" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="Example" type="bdt:TextType" minOccurs="0" maxOccurs="unbounded"/>
		</xsd:sequence>
	</xsd:group>

Proposed adoptions according CCTS conventions:

  • The UniqueID is based on EntityUniqueIdentifierType, which refers to the schema module "CCIS1 Entity Unique Identification Scheme" that provides the suggested schema pattern: "UNBE[0-9]{6}"
  • The VersionID is based on VersionIdentifierType, which refers to the scheme module "CCTS4 Versioning Identification Scheme" that provides the suggested schema pattern: [0-9]{1,2}\.[0-9]{2}
  • The AcronymCode is based on DocumentationAcronymCodeType, which refers to the code list "CCTS1 Documentation Acronym Code List", whereby the fixed value "ABIE" is used.
  • The "DictionaryEntryName" should be based on the BDT "NameType". It is not required to use "languageCode". The language can be globally expressed by the construct <xsd:documentation xml:lang="en-US">.
  • The "Definition" is based on BDT "TextType". The language representation should follow the same approach as described for name.
  • The "ObjectClassQualifierName" has an attribute "orderKey" for the consitent representation of the ordered structure. This attribute is based on positiveInteger.
  • ObjectClassName should be used instead of "ObjectClass", because of the CCTS naming conventions.
  • The *UsageRule" is based on the complexType "UsageRuleType", which provides the complex element structure according the CCTS V3.0 meta model.
  • BusinessTermName should be used instead of "BusinessTerm", because of the CCTS naming conventions.

Documentation of BBIE

<xsd:group name="BBIE_Documentation">
		<xsd:sequence>
			<xsd:element name="UniqueID" type="bdt:EntityUniqueIdentifierType"/>
			<xsd:element name="VersionID" type="bdt:VersionIdentifierType"/>
			<xsd:element name="SequencingKeyID" type="bdt:SequencingKeyIdentifierType"/>
			<xsd:element name="AcronymCode" type="bdt:DocumentationAcronymCodeType" fixed="BBIE"/>
			<xsd:element name="DictionaryEntryName" type="bdt:NameType"/>
			<xsd:element name="Definition" type="bdt:TextType"/>
			<xsd:element name="Cardinality" type="bdt:TextType"/>
			<xsd:element name="ObjectClassQualifierName" minOccurs="0" maxOccurs="unbounded">
				<xsd:complexType>
					<xsd:complexContent>
						<xsd:extension base="bdt:TextType">
							<xsd:attribute name="orderKey" type="xsd:positiveInteger" use="required"/>
						</xsd:extension>
					</xsd:complexContent>
				</xsd:complexType>
			</xsd:element>
			<xsd:element name="ObjectClassName" type="bdt:NameType"/>
			<xsd:element name="PropertyQualifierName" minOccurs="0" maxOccurs="unbounded">
				<xsd:complexType>
					<xsd:complexContent>
						<xsd:extension base="bdt:NameType">
							<xsd:attribute name="orderKey" type="xsd:positiveInteger" use="required"/>
						</xsd:extension>
					</xsd:complexContent>
				</xsd:complexType>
			</xsd:element>
			<xsd:element name="PropertyTermName" type="bdt:NameType"/>
			<xsd:element name="RepresentationTermName" type="bdt:NameType"/>
			<xsd:element name="UsageRule" type="doc:UsageRuleType" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="BusinessTermName" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="Example" type="bdt:TextType" minOccurs="0" maxOccurs="unbounded"/>
		</xsd:sequence>
	</xsd:group>

Documentation of ASBIE

<xsd:group name="ASBIE_Documentation">
		<xsd:sequence>
			<xsd:element name="UniqueID" type="bdt:EntityUniqueIdentifierType"/>
			<xsd:element name="VersionID" type="bdt:VersionIdentifierType"/>
			<xsd:element name="SequencingKeyID" type="bdt:SequencingKeyIdentifierType"/>
			<xsd:element name="AcronymCode" type="bdt:DocumentationAcronymCodeType" fixed="ASBIE"/>
			<xsd:element name="DictionaryEntryName" type="bdt:NameType"/>
			<xsd:element name="Definition" type="bdt:TextType"/>
			<xsd:element name="Cardinality" type="bdt:TextType"/>
			<xsd:element name="ObjectClassQualifierName" minOccurs="0" maxOccurs="unbounded">
				<xsd:complexType>
					<xsd:complexContent>
						<xsd:extension base="bdt:TextType">
							<xsd:attribute name="orderKey" type="xsd:positiveInteger" use="required"/>
						</xsd:extension>
					</xsd:complexContent>
				</xsd:complexType>
			</xsd:element>
			<xsd:element name="ObjectClassName" type="bdt:NameType"/>
			<xsd:element name="AssociatedObjectClassQualifierName" minOccurs="0" maxOccurs="unbounded">
				<xsd:complexType>
					<xsd:complexContent>
						<xsd:extension base="bdt:NameType">
							<xsd:attribute name="orderKey" type="xsd:positiveInteger" use="required"/>
						</xsd:extension>
					</xsd:complexContent>
				</xsd:complexType>
			</xsd:element>
			<xsd:element name="AssociatedObjectClassTermName" type="bdt:NameType"/>
			<xsd:element name="AssociationTypeCode" type="bdt:AssociationTypeCodeType"/>
			<xsd:element name="UsageRule" type="doc:UsageRuleType" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="BusinessTermName" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="Example" type="bdt:TextType" minOccurs="0" maxOccurs="unbounded"/>
		</xsd:sequence>
	</xsd:group>

Documentation of BDT

<xsd:group name="BDT_Documentation">
		<xsd:sequence>
			<xsd:element name="UniqueID" type="bdt:DataTypeUniqueIdentifierType"/>
			<xsd:element name="VersionID" type="bdt:VersionIdentifierType"/>
			<xsd:element name="AcronymCode" type="bdt:DocumentationAcronymCodeType" fixed="BDT"/>
			<xsd:element name="DictionaryEntryName" type="bdt:NameType"/>
			<xsd:element name="Definition" type="bdt:TextType"/>
			<xsd:element name="DataTypeQualifierName" minOccurs="0" maxOccurs="unbounded">
				<xsd:complexType>
					<xsd:complexContent>
						<xsd:extension base="bdt:TextType">
							<xsd:attribute name="orderKey" type="xsd:positiveInteger" use="required"/>
						</xsd:extension>
					</xsd:complexContent>
				</xsd:complexType>
			</xsd:element>
			<xsd:element name="DataTypeName" type="bdt:NameType"/>
			<xsd:element name="PrimitiveTypeCode" type="bdt:PrimitiveTypeCodeType" maxOccurs="unbounded"/>
			<xsd:element name="UsageRule" type="doc:UsageRuleType" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="BusinessTermName" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="Example" type="bdt:TextType" minOccurs="0" maxOccurs="unbounded"/>
		</xsd:sequence>
	</xsd:group>

Documentation of BDT Supplemenatary Components

<xsd:group name="BDT_SC_Documentation">
		<xsd:sequence>
			<xsd:element name="UniqueID" type="bdt:DataTypeUniqueIdentifierType"/>
			<xsd:element name="VersionID" type="bdt:VersionIdentifierType"/>
			<xsd:element name="SequencingKeyID" type="bdt:SequencingKeyIdentifierType"/>
			<xsd:element name="AcronymCode" type="bdt:DocumentationAcronymCodeType" fixed="BDT_SC"/>
			<xsd:element name="DictionaryEntryName" type="bdt:NameType"/>
			<xsd:element name="Definition" type="bdt:TextType"/>
			<xsd:element name="DataTypeQualifierName" minOccurs="0" maxOccurs="unbounded">
				<xsd:complexType>
					<xsd:complexContent>
						<xsd:extension base="bdt:TextType">
							<xsd:attribute name="orderKey" type="xsd:positiveInteger" use="required"/>
						</xsd:extension>
					</xsd:complexContent>
				</xsd:complexType>
			</xsd:element>
			<xsd:element name="DataTypeName" type="bdt:NameType"/>
			<xsd:element name="PropertyTermName" type="bdt:NameType"/>
			<xsd:element name="RepresentationTermName" type="bdt:NameType"/>
			<xsd:element name="PrimitiveTypeCode" type="bdt:PrimitiveTypeCodeType" maxOccurs="unbounded"/>
			<xsd:element name="UsageRule" type="doc:UsageRuleType" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="BusinessTermName" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="Example" type="bdt:TextType" minOccurs="0" maxOccurs="unbounded"/>
		</xsd:sequence>
	</xsd:group>

Documentation of Code list

<xsd:group name="CodeList_Documentation">
		<xsd:sequence>
			<xsd:element name="ID" type="bdt:IDType"/>
			<xsd:element name="VersionID" type="bdt:IDType"/>
			<xsd:element name="Name" type="bdt:NameType" minOccurs="0"/>
			<xsd:element name="AgencyID" type="bdt:IDType"/>
			<xsd:element name="AgencyName" type="bdt:NameType" minOccurs="0"/>
			<xsd:element name="AcronymCode" type="bdt:DocumentationAcronymCodeType" fixed="CodeList"/>
			<xsd:element name="Description" type="bdt:TextType"/>
			<xsd:element name="PrimitiveTypeCode" type="bdt:PrimitiveTypeCodeType"/>
			<xsd:element name="ModificationAllowedIndicator" type="bdt:IndicatorType" minOccurs="0"/>
			<xsd:element name="DefaultIndicator" type="bdt:IndicatorType" minOccurs="0"/>
			<xsd:element name="UsageRule" type="doc:UsageRuleType" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="BusinessTermName" minOccurs="0" maxOccurs="unbounded"/>
		</xsd:sequence>
	</xsd:group>

Documentation of Code Value

<xsd:group name="CodeValue_Documentation">
		<xsd:sequence>
			<xsd:element name="AcronymCode" type="bdt:DocumentationAcronymCodeType" fixed="CodeValue"/>
			<xsd:element name="Content" type="xsd:string" minOccurs="0"/>
			<xsd:element name="Name" type="bdt:NameType" minOccurs="0"/>
			<xsd:element name="Description" type="bdt:TextType"/>
			<xsd:element name="UsageRule" type="doc:UsageRuleType" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="BusinessTermName" minOccurs="0" maxOccurs="unbounded"/>
		</xsd:sequence>
	</xsd:group>

Documentation of Identifier Scheme

<xsd:group name="IdentifierScheme_Documentation">
		<xsd:sequence>
			<xsd:element name="ID" type="bdt:IDType"/>
			<xsd:element name="VersionID" type="bdt:IDType"/>
			<xsd:element name="Name" type="bdt:NameType" minOccurs="0"/>
			<xsd:element name="AgencyID" type="bdt:IDType"/>
			<xsd:element name="AgencyName" type="bdt:NameType" minOccurs="0"/>
			<xsd:element name="AcronymCode" type="bdt:DocumentationAcronymCodeType" fixed="IdentifierScheme"/>
			<xsd:element name="Description" type="bdt:TextType"/>
			<xsd:element name="PrimitiveTypeCode" type="bdt:PrimitiveTypeCodeType"/>
			<xsd:element name="ModificationAllowedIndicator" type="bdt:IndicatorType" minOccurs="0"/>
			<xsd:element name="DefaultIndicator" minOccurs="0"/>
			<xsd:element name="UsageRule" type="doc:UsageRuleType" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="BusinessTermName" minOccurs="0" maxOccurs="unbounded"/>
		</xsd:sequence>
	</xsd:group>

Usage Rule Type

<xsd:complexType name="UsageRuleType">
		<xsd:sequence>
			<xsd:element name="UniqueID" type="bdt:IDType" minOccurs="0"/>
			<xsd:element name="Name" type="bdt:NameType" minOccurs="0"/>
			<xsd:element name="Description" type="bdt:TextType"/>
			<xsd:element name="FormalConstraint" type="bdt:TextType"/>
			<xsd:element name="FormalConstraintTypeCode" type="bdt:FormalConstraintTypeCodeType" minOccurs="0"/>
			<xsd:element name="ConditionTypeCode" type="bdt:ConditionTypeCodeType" minOccurs="0"/>
		</xsd:sequence>
	</xsd:complexType>

Instance Examples

The following examples show the instances of annotation/documentation of each part:

Documentation for an ABIE

<xsd:annotation>
   <xsd:documentation xml:lang="en-US">
		<doc:UniqueID>UNBE000000</doc:UniqueID>
		<doc:VersionID>0.00</doc:VersionID>
		<doc:AcronymCode>ABIE</doc:AcronymCode>
		<doc:DictionaryEntryName>String</doc:DictionaryEntryName>
		<doc:Definition>String</doc:Definition>
		<doc:ObjectClassName>String</doc:ObjectClassName>
	</xsd:documentation>
</xsd:annotation>

Documentation for an BBIE

<xsd:annotation>
	<xsd:documentation xml:lang="en-US">
		<doc:UniqueID>UNBE000000</doc:UniqueID>
		<doc:VersionID>0.00</doc:VersionID>
		<doc:SequencingKeyID>1</doc:SequencingKeyID>
		<doc:AcronymCode>BBIE</doc:AcronymCode>
		<doc:DictionaryEntryName>String</doc:DictionaryEntryName>
		<doc:Definition>String</doc:Definition>
		<doc:Cardinality>String</doc:Cardinality>
		<doc:ObjectClassName>String</doc:ObjectClassName>
		<doc:PropertyTermName>String</doc:PropertyTermName>
		<doc:RepresentationTermName>String</doc:RepresentationTermName>
	</xsd:documentation>
</xsd:annotation>

Documentation for an ASBIE

<xsd:annotation>
	<xsd:documentation xml:lang="en-US">
		<doc:UniqueID>UNBE000000</doc:UniqueID>
		<doc:VersionID>0.00</doc:VersionID>
		<doc:SequencingKeyID>1</doc:SequencingKeyID>
		<doc:AcronymCode>ASBIE</doc:AcronymCode>
		<doc:DictionaryEntryName>String</doc:DictionaryEntryName>
		<doc:Definition>String</doc:Definition>
		<doc:Cardinality>String</doc:Cardinality>
		<doc:ObjectClassName>String</doc:ObjectClassName>
		<doc:AssociatedObjectClassTermName>String</doc:AssociatedObjectClassTermName>
		<doc:AssociationTypeCode>shared</doc:AssociationTypeCode>
	</xsd:documentation>
</xsd:annotation>

Documentation for a BDT

<xsd:annotation>
	<xsd:documentation xml:lang="en-US">
		<doc:UniqueID>UNDT000000-000</doc:UniqueID>
		<doc:VersionID>0.00</doc:VersionID>
		<doc:AcronymCode>BDT</doc:AcronymCode>
		<doc:DictionaryEntryName>String</doc:DictionaryEntryName>
		<doc:Definition>String</doc:Definition>
		<doc:DataTypeName>String</doc:DataTypeName>
		<doc:PrimitiveTypeCode>Binary</doc:PrimitiveTypeCode>
	</xsd:documentation>
</xsd:annotation>

Documentation for a BDT Supplementary Component

<xsd:annotation>
	<xsd:documentation xml:lang="en-US">
		<doc:UniqueID>UNDT000000-000</doc:UniqueID>
		<doc:VersionID>0.00</doc:VersionID>
		<doc:SequencingKeyID>1</doc:SequencingKeyID>
		<doc:AcronymCode>BDT_SC</doc:AcronymCode>
		<doc:DictionaryEntryName>String</doc:DictionaryEntryName>
		<doc:Definition>String</doc:Definition>
		<doc:DataTypeName>String</doc:DataTypeName>
		<doc:PropertyTermName>String</doc:PropertyTermName>
		<doc:RepresentationTermName>String</doc:RepresentationTermName>
		<doc:PrimitiveTypeCode>Binary</doc:PrimitiveTypeCode>
	</xsd:documentation>
</xsd:annotation>

Documentation for a Code List

<xsd:annotation>
	<xsd:documentation xml:lang="en-US">
		<doc:ID schemeID="token" schemeAgencyID="1" schemeVersionID="token">token</doc:ID>
		<doc:VersionID schemeID="token" schemeAgencyID="1" schemeVersionID="token">token</doc:VersionID>
		<doc:AgencyID schemeID="token" schemeAgencyID="1" schemeVersionID="token">token</doc:AgencyID>
		<doc:AcronymCode>CodeList</doc:AcronymCode>
		<doc:Description>String</doc:Description>
		<doc:PrimitiveTypeCode>Binary</doc:PrimitiveTypeCode>
	</xsd:documentation>
</xsd:annotation>

Documentation for a Code Value

<xsd:annotation>
	<xsd:documentation xml:lang="en-US">
		<doc:AcronymCode>CodeValue</doc:AcronymCode>
		<doc:Description>String</doc:Description>
	</xsd:documentation>
</xsd:annotation>
Posted at 11 Jul @ 7:56 AM by gunther.stuhec | 0 comments
  2008/06/19
Last changed: Jun 19, 2008 07:59 by decala
Labels: agenda, atg_news

Title ATG
Topic Plenary
Location Saly, Senegal
Date 10-14 November 2008
Start Time 08:00 – Timezone: CET
End Time 16:00 – Timezone: CET

Agenda

  1. – Welcome
  2. – Agree on agenda
  3. – Select note taker
  4. – Review Open Action Items
  5. – Other business
  6. – Next meeting

Posted at 19 Jun @ 7:47 AM by decala | 0 comments
  2008/06/09
Last changed: Jun 09, 2008 09:33 by decala

The summer 2008 Interim F2F meeting will take place in Roros, Norway from June 16 - 20, 2008.



More info

Posted at 09 Jun @ 8:47 AM by decala | 0 comments
  2008/03/27

NDR - Weekly Meeting

Title NDR meeting
Topic Requirements for NDR 3.0
Date Every Thursday
Start Time 15:00 - Timezone: CET
End Time 16:00 - Timezone: CET
Join Meeting [ SAP Hosting Interwise|https://conferencing.sap.com/global/SyncEvents/EnterEvent.asp?campus=global&campusURL=conferencing.sap.com&Lang=EN&external=183521]
Posted at 27 Mar @ 10:35 AM by Michael Rowell | 0 comments
  2007/09/27
Last changed: Sep 27, 2007 03:13 by gait.boxman@tie.nl

ATG1 is happy to inform you that it concluded it's DMR review for the 11th CEFACT Forum in Stockholm, September 2007.

The results are as follows:

  • 6 DMRs were approved
  • 32 DMRs were JT'd (mostly to assign code values)
  • 1 DMR was postponed
  • 3 DMRs were withdrawn 
Posted at 27 Sep @ 3:12 AM by gait.boxman@tie.nl | 0 comments