ATT01 Leading name part in attribute names (5.10) Every attribute's derived name shall be composed with the leading name part entirely in lower-case, even when that name part is an agreed-upon abbreviation.
ATT02 Non-leading abbreviations in attribute names (5.10) When an attribute's derived name is composed with an agreed-upon abbreviation in other than the leading name part, the abbreviation shall be used unchanged.
CCT01 CCTS Core Component Type schema (5.9) The core component type schema of primitive data types for primary representation terms on which the unqualified data types are based shall be an unmodified copy of the schema fragment published by UN/CEFACT with the following embedded title and metadata: CCTS Core Component Type Schema Module Module of Core Component Type Agency: UN/CEFACT VersionID: 1.1 Last change: 14 January 2005
COM01 Dictionary information values (4.2) The text describing dictionary information values shall be a string value of Unicode characters without embedded hierarchical structure. The value itself may be structured in its syntax within the string.
COM02 Dictionary information value prohibited characters and character sequences (4.2) The following characters shall not be contained in any dictionary information value: the characters "<", ">", "&" white-space characters other than the " " (space) character the character sequence "--"
COM03 Controlled list of abbreviations in BIE names (4.3) Abbreviations for terms used in BIE names shall be taken from a controlled list of abbreviations agreed for use within the semantic model.
COM04 Controlled list of abbreviations in dictionary information values (4.3) Abbreviations for terms used in dictionary information values shall be taken from a controlled list of commonly-agreed abbreviations.
COM05 List of equivalent terms in BIE names (4.3) Equivalent terms used in BIE names shall be taken from a list of commonly-agreed equivalent terms.
COM06 Minimum set of dictionary information values describing an ABIE (4.4.1) Each ABIE shall have the following set of dictionary information values: Component Type (mandatory) shall be the value "ABIE" Definition (mandatory) this value shall describe the ABIE using complete natural language sentences in a single paragraph Alternative Business Terms (optional) this value shall list any other commonly used terms that are synonyms for the ABIE Object Class Qualifier (optional) this value shall qualify the object class for a specific context Object Class (mandatory) this value shall identify the object of interest within an information bundle; it is the class to which the ABIE's BIEs belong Name (mandatory) this value shall be the concatenation of Object Class Qualifier and the Object Class without any spaces, abbreviating the values as required Dictionary Entry Name (mandatory) this value shall be the concatenation of the Object Class Qualifier, followed by an underscore and space when defined, followed by the Object Class, followed by a period and space, followed by the word "Details"
COM07 Minimum set of dictionary information values describing a BBIE (4.4.2) Each BBIE shall have the following set of dictionary information values: Component Type (mandatory) shall be the value "BBIE" Cardinality (mandatory) shall be one of: "1" (required and not repeatable), "0..1" (optional and not repeatable), "0..n" (optional and repeatable) or "1..n" (required and repeatable) Definition (mandatory) this value shall describe the BBIE using complete natural language sentences in a single paragraph Alternative Business Terms (optional) this value shall list any other commonly used terms that are synonyms for the ABIE Object Class Qualifier (optional) this value shall qualify the object class for a specific context Object Class (mandatory) this value shall identify the object class of the ABIE to which the BBIE belongs Property Term Qualifier (optional) this value shall qualify the property term for a specific context Property Term Possessive Noun (optional) this value shall identify a distinguishing nature of the characteristic of the object class Property Term Primary Noun (mandatory) this value shall identify the principle nature of the characteristic of the object class Property Term (mandatory) this value shall identify a characteristic of the object class as the concatenation of Property Term Possessive Noun followed by a space should it exist, followed by the Property Term Primary Noun Representation Term (mandatory) this value shall identify the form of the value domain and shall be selected from the set of primary and secondary representation terms specified in CCTS Table 8.3 Permissible Representation Terms (ordered by primary term with secondary terms in parentheses): Amount Binary Object (Graphic, Picture, Sound, Video) Code Date Time (Date, Time) Identifier Indicator Measure Numeric (Value, Rate, Percent) Quantity Text (Name) Name (mandatory) this value shall be the concatenation of Property Term Qualifier, Property Term Possessive Noun and, when the Property Term Primary Noun is not "Text" or it is "Text" and both the Property Term Qualifier and the Property Term Possessive Noun are not defined, then the Property Term Primary Noun (abbreviating it as required) and, when the Representation Term is not "Text" and the Property Term Primary Noun is not equivalent to the Representation Term, then also the Representation Term component (abbreviating it as required), all without intervening spaces Dictionary Entry Name (mandatory) this value shall be the concatenation of the Object Class Qualifier, followed by an underscore and space when defined, followed by the Object Class, followed by a period and space, followed by the Property Term Qualifier, followed by an underscore and space when defined, followed by the Property Term, and then, when either the Property Term Qualifier is defined or the Property Term is not equal to the Representation Term, followed by a period and space and the Representation Term Data Type Qualifier (optional) this value shall distinguish particular restrictions on a data type from the use of a data type with other (or no) restrictions Data Type (mandatory) this value shall be the concatenation of the Data Type Qualifier followed by an underscore and space when it exists, the Representation Term, followed by a period and space, followed by the word "Type"
COM08 Minimum set of dictionary information values describing an ASBIE (4.4.3) Each ASBIE shall have the following set of dictionary information values: Component Type (mandatory) shall be the value "ASBIE" Cardinality (mandatory) shall be one of: "1" (required and not repeatable), "0..1" (optional and not repeatable), "0..n" (optional and repeatable) or "1..n" (required and repeatable) Definition (mandatory) this value shall describe the BBIE using complete natural language sentences in a single paragraph Alternative Business Terms (optional) this value shall list any other commonly used terms that are synonyms for the ABIE Object Class Qualifier (optional) this value shall qualify the object class for a specific context Object Class (mandatory) this value shall identify the object class of the ABIE to which the BBIE belongs Associated Object Class Qualifier (optional) this value shall qualify the object class of the associated ABIE for a specific context Associated Object Class (mandatory) this value shall identify the object class of the ABIE the ASBIE associates to the ABIE must exist in the model with the same qualification (or lack thereof) as the ASBIE's associated object class qualifier Property Term Qualifier (optional) this value shall qualify the property term for a specific context Property Term (mandatory) this value shall be the concatenation of the Associated Object Class Qualifier, an underscore and a space when defined, and the Associated Object Class Representation Term (mandatory) this value shall be the same as the Property Term Name (mandatory) this value shall be the concatenation of Property Term Qualifier and the Property Term without any spaces or underscore, abbreviating the values as required Dictionary Entry Name (mandatory) this value shall be the concatenation of the Object Class Qualifier, followed by an underscore and space when defined, followed by the Object Class, followed by a period and space, followed by the Property Term Qualifier, followed by and underscore and space when defined, followed by the Property Term, and then when the Property Term Qualifier is defined, followed by a period and space and the Representation Term
COM09 Dictionary entry name uniqueness (4.4.4) All dictionary entry names in a semantic model shall be unique.
COM10 CCTS dictionary information item name value prohibited characters (4.4.4) All information items contributing to a component's dictionary entry name shall be void of all sensitive dictionary entry name markup characters. The following characters must not be used in any dictionary information values that contribute to the dictionary entry name: the characters "." (period) and "_" (underscore) leading, trailing or multiple sequential " " (space) characters
COM11 Use of the singular form in names (4.4.4) All information items contributing to a component's dictionary entry name shall be in the singular form unless the concept itself is plural.
COM12 Use of leading upper case letter in dictionary entry name values (4.4.4) All words that are not abbreviated in name values contributing to the dictionary entry name shall have a leading upper-case letter and all other letters in lower-case.
COM13 ABIE contents cannot be empty (4.5) Every ABIE shall contain at least one BIE.
COM14 ABIE organization (4.5) Every BIE for a given ABIE shall be organized in the semantic model in the order the BIEs are to be expressed in Open-edi user data.
COM15 ABIE children ordering (4.5) Every ABIE shall have all of its BBIE children listed before its ASBIE children.
DCL01 Element declarations (5.5.4) Every BIE element declaration shall be global.
DCL02 Element declaration references (5.5.4) Every BIE element in an ABIE type definition shall be declared by reference.
DCL03 Type declarations (5.5.4) Every BIE type declaration shall be global.
DCL04 ABIE element declaration (5.5.5) Every ABIE element shall be declared with the ABIE name as the element name and the ABIE name suffixed with "Type" as the type.
DCL05 ABIE type declaration (5.5.5) Every ABIE complex type name shall be declared with the name of the ABIE suffixed with "Type" as the name.
DCL06 Library ABIE type declaration content order (5.5.5) The members of a Library ABIE shall be ordered as the sequence (in the order the BIEs appear in the semantic model of the ABIE) of all BBIE element references first, followed by all ASBIE references.
DCL07 Document ABIE type declaration content order (5.5.5) The members of a Document ABIE shall be ordered first with a reference to the extension collection element, followed by the sequence (in the order the BIEs appear in the semantic model of the ABIE) of all BBIE element references first, followed by all ASBIE references.
DCL08 Document ABIE extension element cardinality (5.5.5) In the content type for every Document ABIE the extension collection element cardinality shall be declared as optional and not repeatable.
DCL09 ASBIE schema element declaration (5.5.6) Every ASBIE element shall be declared with the ASBIE name as the element name and the ABIE name of the associated object class suffixed with "Type" as the type.
DCL10 BBIE element declaration (5.5.7) Every BBIE element shall be declared with the BBIE name as the element name and the concatenation of the BBIE name and "Type" as the type.
DCL11 BBIE type declaration (5.5.7) Every BBIE element type shall be declared as simple content extended from a base of either a qualified data type or an unqualified data type without the addition of any additional attributes.
DTQ01 Data type qualification CVA file (5.11) Data type qualifications that are not expressed as qualified data types using XSD schema semantics may be expressed using the OASIS Context Value Association XML vocabulary.
DTQ02 Data type element content qualifications (5.11) A CVA context shall be created for every BBIE with a non-empty value in the CCTS dictionary information for the data type qualifier.
DTQ03 Data type attribute content qualifications (5.11) A CVA context shall be created for every CCTS supplementary component to be validated.
DTQ04 Value test constraints (5.11) A CVA value test constraint shall be written as an XPath expression.
DTQ05 Value list constraints (5.11) A CVA value list constraint shall reference an OASIS genericode file.
DTQ06 Value metadata association (5.11) The CVA instance metadata sets shall identify the XML attributes used in Open-edi user data that are associated with the supplementary components of the unqualified data types.
EXT01 Extension collection schema fragment (5.6.2) The extension collection schema fragment shall include the declarations of the extension collection element, the extension element, the extension content element, the extension metadata elements and any required type information for metadata elements that are not BIEs in the Document ABIEs and Library ABIEs.
EXT02 Extension content element declaration (5.6.2) The extension collection schema fragment shall include the declaration of the mandatory extension content element, but not the type information for the extension content element.
EXT03 Extension collection element content (5.6.2) The document's extension collection shall have one or more extension elements as its content.
EXT04 Extension element content ordering (5.6.2) The extension element shall declare all available metadata elements (if any) in advance of a last mandatory single extension content element being the extension point under which the extension information is added to the document.
EXT05 Extension content data type schema fragment (5.6.3) The extension content element type schema fragment shall include the declaration of the content type for the extension content element and any import statements defining constraints on recognized constructs.
EXT06 Extension content data type declaration (5.6.3) The extension content element type schema fragment shall contain only a single complex type declaration being a sequence of exactly one element in a namespace other than the extension namespace to be processed with lax validation.
EXT07 Extension content data type imports (5.6.3) The extension content element type schema fragment may contain import directives for the expected data content of an extension.
FRG01 Document ABIE schema fragments (5.5.1) There shall be one schema fragment created for each Document ABIE.
FRG02 Document ABIE element declaration (5.5.1) Each Document ABIE schema fragment shall include a single element declaration, that being for the Document ABIE.
FRG03 Document ABIE type declaration (5.5.1) Each Document ABIE schema fragment shall include a single type declaration, that being for the content of the Document ABIE.
FRG04 Library ABIE schema fragment (5.5.2) There shall be one common schema fragment created to contain all ASBIEs (that is, from every Document ABIE and every Library ABIE) and all Library ABIEs.
FRG05 Library ABIE element declarations (5.5.2) The common Library ABIE schema fragment shall include an element declaration for every ASBIE in the model (that is, from every Document ABIE and every Library ABIE) and for every Library ABIE.
FRG06 Library ABIE type declarations (5.5.2) The common Library ABIE schema fragment shall include a type declaration for every Library ABIE, each being for the content of each Library ABIE.
FRG07 BBIE schema fragment (5.5.3) There shall be one common schema fragment created to describe all BBIEs in the model (that is, from every Document ABIE and every Library ABIE).
FRG08 BBIE element declarations (5.5.3) The common BBIE schema fragment shall include an element declaration for every BBIE in the model (that is, from every Document ABIE and every Library ABIE) describing the content of each BBIE.
FRG09 Library ABIE type declarations (5.5.3) The one BBIE schema fragment shall include a type declaration for every BBIE in the model (that is, from every Document ABIE and every Library ABIE), each being for the content of each BBIE.
MOD01 Document ABIE (3.1) The apex of the information bundle shall be structured as a single top-level ABIE, referred to in this specification as a Document ABIE.
MOD02 ABIE library contents (3.2) The ABIE library shall not contain any Document ABIEs.
MOD03 ABIE library ordering (3.2) The ABIE library shall have all ABIEs defined in alphabetical order of the ABIE's dictionary entry name.
MOD04 Extension availability (3.3) Each document shall allow for optional augmentation with a collection of information not conceptually described by existing BIEs.
NAM01 Namespaces for information found in information bundles (5.2) BIEs expressed in XML documents shall use the following set of namespaces: one namespace for each Document ABIE one namespace for all BBIE components one namespace for all Library ABIE components one namespace for the extension collection and extension metadata elements
NAM02 Namespaces for an extension (5.2) BIEs expressed in extensions shall use the following set of namespaces: one namespace for the apex ABIE of the extension one namespace for all BBIE extension components that are not existing library components one namespace for all ABIE extension components that are not existing Library ABIE components
NAM03 Namespaces for BBIE data types (5.2) The expression of data type information supporting BBIE definitions shall use the following set of namespaces: one namespace for all qualified data types one namespace for all unqualified data types one namespace for CCTS Core Component Type definitions
NAM04 Namespace for schema annotations (5.2) A namespace for CCTS documentation found in schema annotations shall be defined as distinct from all other namespaces.
QDT01 Qualified data types schema fragment (5.7) The qualified data types schema fragment shall include the declarations of any qualified data types referenced in the schema fragment for BBIEs.
QDT02 Qualified data type declaration name (5.7) Every qualified data type shall be declared using the name of the data type qualifier followed by the unqualified data type name.
QDT03 Qualified data type declaration basis (5.7) Every qualified data type shall be based on an unqualified data type, imposing whatever qualifications are required to be expressed using XSD schema semantics.
QDT04 Qualified data type declaration constraint (5.7) Every qualified data type declaration shall be such that every possible instance of the declared type is also an instance of the base type.
UDT01 Unqualified data types schema fragment (5.8) The unqualified data types schema fragment shall include the declarations of all unqualified data types referenced in the schema fragment for BBIEs.
UDT02 Unqualified data types declaration inclusions (5.8) An unqualified data type shall be declared for every one of the permitted Primary Representation Terms and Secondary Representation Terms defined as Permissible Representation Terms in the Core Component Technical Specification .
UDT03 Unqualified data types declaration exclusions (5.8) Unqualified data types shall only be declared for the permitted Primary Representation Terms and Secondary Representation Terms defined as Permissible Representation Terms in the Core Component Technical Specification .
UDT04 Unqualified data types declaration base (5.8) Every unqualified data type shall be based on one of the approved Core Component Types defined in the Core Component Technical Specification .
UDT05 Unqualified data types declaration constraint (5.8) Every unqualified data type declaration shall be such that every possible instance of the declared type is also an instance of the type on which it is based.