<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- 
For use when a committee document points at the OASIS web site for publishing:
<?xml-stylesheet type="text/xsl" 
href="http://docs.oasis-open.org/templates/DocBook/spec-0.6/stylesheets/oasis-specification-html.xsl"?>
<!DOCTYPE article
  PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
         "https://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" 

For use when a committee document points to an embedded installation of DocBook
<?xml-stylesheet type="text/xsl" 
               href="db/spec-0.6/stylesheets/oasis-specification-html.xsl"?>
<!DOCTYPE article
 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" 
        "db/spec-0.6/docbook/docbookx.dtd" 

For use when a committee document is published in a local environment only
(note the instructions for local publishing require adjusting the stylesheet
 and DocBook directories in these declarations):
<?xml-stylesheet type="text/xsl" 
href="file:///z:/oasis/spec-0.6/stylesheets/oasis-specification-html-offline.xsl"?>
<!DOCTYPE article
  PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
         "file:///z:/oasis/spec-0.6/docbook/docbookx.dtd" 
-->
<?xml-stylesheet type="text/xsl"
               href="db/spec-0.6/stylesheets/oasis-specification-html.xsl"?>
<!DOCTYPE article
 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" 
        "db/spec-0.6/docbook/docbookx.dtd" 
[
<!--the document properties-->
<!ENTITY dir "UBL-NDR">
<!ENTITY name "&dir;-v&version;">
<!ENTITY version "3.0">
<!ENTITY title "UBL Naming and Design Rules Version&#xa0;&version;">
<!ENTITY standard "Committee Specification Draft 02 / Public Review Draft 02">
<!ENTITY stage                       "csprd02"><!--remember title ent-->
<!ENTITY pstage                      "csprd01">
<!ENTITY summary SYSTEM "UBL-NDR-v3.0-csprd02-summary.xml">
<!ENTITY this-loc     "http://docs.oasis-open.org/ubl/&dir;/v&version;/&stage;">
<!ENTITY latest-loc   "http://docs.oasis-open.org/ubl/&dir;/v&version;">
<!ENTITY previous-loc "http://docs.oasis-open.org/ubl/&dir;/v&version;/&pstage;">
<!ENTITY pubdate "16 December 2015">
<!ENTITY pubdate "<emphasis role='date'>$Revision: 1.4 $$Date: 2015/12/14 00:40:09 $</emphasis>">
]>
<article status="&standard;">
  <articleinfo>
    <title>&title;</title>
    <releaseinfo role="cvs"> $Id: UBL-NDR-v3.0-csprd02.xml,v 1.4 2015/12/14 00:40:09 admin Exp $ </releaseinfo>
    <productname>&name;</productname>
    <productnumber>&stage;</productnumber>
    <releaseinfo role="track">Standards Track Work Product</releaseinfo>
    <releaseinfo role="OASIS-specification-this-authoritative">&this-loc;/&name;-&stage;.xml</releaseinfo>
    <releaseinfo role="OASIS-specification-this">&this-loc;/&name;-&stage;.html</releaseinfo>
    <releaseinfo role="OASIS-specification-this">&this-loc;/&name;-&stage;.pdf</releaseinfo>
    <releaseinfo role="OASIS-specification-previous-authoritative">&previous-loc;/&name;-&pstage;.xml</releaseinfo>
    <releaseinfo role="OASIS-specification-previous">&previous-loc;/&name;-&pstage;.html</releaseinfo>
    <releaseinfo role="OASIS-specification-previous">&previous-loc;/&name;-&pstage;.pdf</releaseinfo>
    <releaseinfo role="OASIS-specification-latest">&latest-loc;/&name;.html</releaseinfo>
    <releaseinfo role="OASIS-specification-latest">&latest-loc;/&name;.pdf</releaseinfo>
    <releaseinfo role="committee"><ulink url="https://www.oasis-open.org/committees/ubl/">OASIS Universal
        Business Language (UBL) TC</ulink></releaseinfo>
    <authorgroup>
      <editor>
        <firstname>Tim</firstname>
        <surname>McGrath</surname>
        <affiliation>
          <orgname><ulink url="http://www.documentengineeringservices.com/"
              >Document Engineering Services Limited</ulink></orgname>
        </affiliation>
        <email>tim.mcgrath@documentengineeringservices.com</email>
      </editor>
      <editor>
        <firstname>Andy</firstname>
        <surname>Schoka</surname>
        <email>amschoka@comcast.net</email>
      </editor>
      <editor>
        <firstname>G. Ken</firstname>
        <surname>Holman</surname>
        <affiliation>
          <orgname><ulink
              url="http://www.CraneSoftwrights.com/links/info-ubl21.htm">Crane
              Softwrights Ltd.</ulink></orgname>
        </affiliation>
        <email>gkholman@CraneSoftwrights.com</email>
      </editor>
      <othercredit>
        <firstname>Tim</firstname>
        <surname>McGrath</surname>
        <affiliation>
          <orgname><ulink url="http://www.documentengineeringservices.com/"
              >Document Engineering Services Limited</ulink></orgname>
        </affiliation>
        <email>tim.mcgrath@documentengineeringservices.com</email>
      </othercredit>
      <othercredit>
        <firstname>G. Ken</firstname>
        <surname>Holman</surname>
        <affiliation>
          <orgname><ulink
              url="http://www.CraneSoftwrights.com/links/info-ubl21.htm">Crane
              Softwrights Ltd.</ulink></orgname>
        </affiliation>
        <email>gkholman@CraneSoftwrights.com</email>
      </othercredit>
    </authorgroup>
    <pubdate>&pubdate;</pubdate>
    <copyright>
      <year>2015</year>
      <holder>OASIS Open, Inc. All Rights Reserved.</holder>
    </copyright>
    <!--    <legalnotice role="related">
      <title>Related work</title>
      <para>This specification replaces or supersedes:</para>
      <bibliolist>
        <bibliomixed>
          <citetitle>Universal Business Language (UBL) 2.0 Naming and Design
            Rules.</citetitle>
          <bibliomisc>Edited by Mike Grimley and Mavis Cournane.</bibliomisc>
          <date>25 December 2009. </date>
          <releaseinfo>Committee Specification 01. </releaseinfo>
          <bibliomisc>
            <ulink
              url="http://docs.oasis-open.org/ubl/UBL-2.0-NDR/UBL-2.0-NDR.html"
              >http://docs.oasis-open.org/ubl/UBL-2.0-NDR/UBL-2.0-NDR.html</ulink>.
          </bibliomisc>
        </bibliomixed>
      </bibliolist>
      <!-\-
      <para>This specification is related to:</para>
      <bibliolist>
        <bibliomixed>
          <citetitle>Universal Business Language Version 2.1.</citetitle>
          <bibliomisc>Edited by Jon Bosak, Tim McGrath and G. Ken Holman. </bibliomisc>
          <date>04 November 2013. </date>
          <releaseinfo>OASIS Standard. </releaseinfo>
          <bibliomisc>
            <ulink url="http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html"
              >http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html</ulink>.
          </bibliomisc>
        </bibliomixed>
      </bibliolist>
      -\->
    </legalnotice>-->
    <abstract>
      <para>This specification prescribes a set of naming and design rules used
        to create XML document model validation artefacts (W3C Schema XSD files
        and OASIS Context/value association files) associated with abstract
        information bundles formally described using the Core Component
        Technical Specification 2.01 <xref linkend="ccts"/>. </para>
    </abstract>
    <legalnotice role="status" id="STATUS">
      <title>Status</title>
      <!--<para>This <ulink url="https://www.oasis-open.org/policies-guidelines/tc-process#dWorkingDraft">Working Draft</ulink> (WD) has been produced by one or more TC Members; it has not yet been voted on by the TC or <ulink url="https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft">approved</ulink> as a Committee Specification Draft. The OASIS document <ulink url="https://www.oasis-open.org/policies-guidelines/tc-process#standApprovProcess">Approval Process</ulink> begins officially with a TC vote to approve a WD as a Committee Draft. A TC may approve a Working Draft, revise it, and re-approve it any number of times as a Committee Draft.</para>-->
      <para>This document was last revised or approved by the OASIS Universal
        Business Language TC on the above date. The level of approval is also
        listed above. Check the &#x201c;Latest version&#x201d; location noted
        above for possible later revisions of this document. Any other numbered
        Versions and other technical work produced by the Technical Committee
        (TC) are listed at <ulink
          url="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl#technical"
          >https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl#technical</ulink>.</para>
      <para>TC members should send comments on this specification to the
        TC&#8217;s email list. Others should send comments to the TC's public
        comment list, after subscribing to it by following the instructions at
        the &#8220;<ulink
          url="https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ubl"
          >Send A Comment</ulink>&#8221; button on the TC&#8217;s web page at
          <ulink url="https://www.oasis-open.org/committees/ubl/"
          >https://www.oasis-open.org/committees/ubl/</ulink>.</para>
      <para>For information on whether any patents have been disclosed that may
        be essential to implementing this specification, and any offers of
        patent licensing terms, please refer to the Intellectual Property
        Rights section of the Technical Committee web page at <ulink
          url="https://www.oasis-open.org/committees/ubl/ipr.php"
          >https://www.oasis-open.org/committees/ubl/ipr.php</ulink>.</para>
      <para>See <xref linkend="A-RELEASE-NOTES"/> for more information
        regarding this release package.</para>
    </legalnotice>
    <legalnotice role="citation" id="CITATION">
      <title>Citation format</title>
      <para>When referencing this specification the following citation format
        should be used:</para>
      <bibliolist id="citationfmt">
        <bibliomixed><abbrev>&dir;-v&version;</abbrev>
          <citetitle>&title;.</citetitle>
          <bibliomisc>Edited by Tim McGrath, Andy Schoka and G. Ken
            Holman.</bibliomisc>
          <date>&pubdate;.</date>
          <releaseinfo>&standard;.</releaseinfo>
          <bibliomisc>
            <ulink url="&this-loc;/&name;-&stage;.html"
              >&this-loc;/&name;-&stage;.html</ulink>. Latest version: <ulink
              url="&latest-loc;/&name;.html">&latest-loc;/&name;.html</ulink>.
          </bibliomisc>
        </bibliomixed>
      </bibliolist>
    </legalnotice>
    <legalnotice role="notices">
      <title>Notices</title>
      <para>Copyright &#169; OASIS Open 2001-2015. All Rights Reserved. </para>
      <para>All capitalized terms in the following text have the meanings
        assigned to them in the OASIS Intellectual Property Rights Policy (the
        &#8220;OASIS IPR Policy&#8221;). The full <ulink
          url="https://www.oasis-open.org/policies-guidelines/ipr"
          >Policy</ulink> may be found at the OASIS website.</para>
      <para>This document and translations of it may be copied and furnished to
        others, and derivative works that comment on or otherwise explain it or
        assist in its implementation may be prepared, copied, published, and
        distributed, in whole or in part, without restriction of any kind,
        provided that the above copyright notice and this section are included
        on all such copies and derivative works. However, this document itself
        may not be modified in any way, including by removing the copyright
        notice or references to OASIS, except as needed for the purpose of
        developing any document or deliverable produced by an OASIS Technical
        Committee (in which case the rules applicable to copyrights, as set
        forth in the OASIS IPR Policy, must be followed) or as required to
        translate it into languages other than English. </para>
      <para>The limited permissions granted above are perpetual and will not be
        revoked by OASIS or its successors or assigns. </para>
      <para>This document and the information contained herein is provided on
        an &#8220;AS IS&#8221; basis and OASIS DISCLAIMS ALL WARRANTIES,
        EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE
        USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS
        AND ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
        PARTICULAR PURPOSE. </para>
      <para>OASIS requests that any OASIS Party or any other party that
        believes it has patent claims that would necessarily be infringed by
        implementations of this OASIS Committee Specification or OASIS Standard
        notify OASIS TC Administrator and provide an indication of its
        willingness to grant patent licenses to such patent claims in a manner
        consistent with the IPR Mode of the OASIS Technical Committee that
        produced this specification. </para>
      <para>OASIS invites any party to contact the OASIS TC Administrator if it
        is aware of a claim of ownership of any patent claims that would
        necessarily be infringed by implementations of this specification by a
        patent holder that is not willing to provide a license to such patent
        claims in a manner consistent with the IPR Mode of the OASIS Technical
        Committee that produced this specification. OASIS may include such
        claims on its website, but disclaims any obligation to do so. </para>
      <para>OASIS takes no position regarding the validity or scope of any
        intellectual property or other rights that might be claimed to pertain
        to the implementation or use of the technology described in this
        document or the extent to which any license under such rights might or
        might not be available; neither does it represent that it has made any
        effort to identify any such rights. Information on OASIS&#x2019;
        procedures with respect to rights in any document or deliverable
        produced by an OASIS Technical Committee can be found on the OASIS
        website. Copies of claims of rights made available for publication and
        any assurances of licenses to be made available, or the result of an
        attempt made to obtain a general license or permission for the use of
        such proprietary rights by implementers or users of this OASIS
        Committee Specification or OASIS Standard, can be obtained from the
        OASIS TC Administrator. OASIS makes no representation that any
        information or list of intellectual property rights will at any time be
        complete, or that any claims in such list are, in fact, Essential
        Claims. </para>
      <para>The name &#8220;OASIS&#8221; is a trademark of <ulink
          url="https://www.oasis-open.org">OASIS</ulink>, the owner and
        developer of this specification, and should be used only to refer to
        the organization and its official outputs. OASIS welcomes reference to,
        and implementation and use of, specifications, while reserving the
        right to enforce its marks against misleading uses. Please see <ulink
          url="https://www.oasis-open.org/policies-guidelines/trademark.php"
          >https://www.oasis-open.org/policies-guidelines/trademark.php</ulink>
        for guidance.</para>
    </legalnotice>
  </articleinfo>
  <section id="S-INTRODUCTION">
    <title>Introduction</title>
    <section id="S-BASIC-CONCEPTS">
      <title>Basic concepts</title>
      <section id="S-NAMING-AND-DESIGN-RULES">
        <title>Naming and design rules</title>
        <para>The Open-edi Reference Model <xref linkend="iso14662"/> defines
          an information bundle as the abstract description of the structure
          and semantics of the information exchanged between parties.</para>
        <para>An information bundle can be represented as a logical semantic
          model. This logical semantic model can be used to produce a physical
          syntax model that defines the structure and syntax of the Open-edi
          user data actually exchanged in business transactions. </para>
        <para>These naming and design rules formalize a method of representing
          the semantic components of information bundles using the ebXML Core
          Components Technical Specification <xref linkend="ccts"/>. These
          semantic models can then be used to produce equivalent W3C Schema
            <xref linkend="xsd"/> XSD files and OASIS Context/value Association
            <xref linkend="oasiscva"/> expressions suitable for defining and
          validating XML Documents used to convey Open-edi user data.</para>
        <para>This is illustrated in <xref
            linkend="F-XML-NAMING-AND-DESIGN-RULES-IN-AN-OPEN-EDI-APPLICATION"
          />.</para>
        <figure id="F-XML-NAMING-AND-DESIGN-RULES-IN-AN-OPEN-EDI-APPLICATION">
          <title>XML Naming and Design Rules in an Open-edi Application</title>
          <mediaobject>
            <imageobject>
              <imagedata
                fileref="art/&dir;-v&version;-Open-edi-Application.png"
                contentwidth="750px"/>
            </imageobject>
            <textobject>
              <phrase>Open-edi Application</phrase>
            </textobject>
          </mediaobject>
        </figure>
        <para>The rules presume the reader is already familiar with the
          following specifications: </para>
        <itemizedlist>
          <listitem>
            <para>United Nations Centre for Trade Facilitation and Electronic
              Business (UN/CEFACT) Core Components Technical Specification 2.01
              &#x2013; Part 8 of the ebXML Framework <xref linkend="ccts"
              />;</para>
          </listitem>
          <listitem>
            <para>ISO/IEC 11179 Data Elements <xref linkend="iso11179"
              />;</para>
          </listitem>
          <listitem>
            <para>W3C Schema <xref linkend="xsd"/> XSD files for XML document
              constraint specification;</para>
          </listitem>
          <listitem>
            <para>OASIS Context/value association using genericode <xref
                linkend="oasiscva"/> for code list association; and </para>
          </listitem>
          <listitem>
            <para>OASIS genericode <xref linkend="gc"/> for code list
              representation. </para>
          </listitem>
        </itemizedlist>
        <note>
          <para>The OASIS Universal Business Language (UBL) can be considered
            as a reference implementation of these naming and design rules and
            the examples used in this specification are primarily taken from
            the UBL 2.1 specifications. </para>
        </note>
        <note>
          <para>Other validation artefacts (using RelaxNG and ASN.1) are also
            provided for UBL 2.1. The rules for producing these are outside the
            scope of this work product.</para>
        </note>
      </section>
      <section id="S-MODELING-CONCEPTS">
        <title>Modeling concepts</title>
        <para>Information bundles (describing information to be exchanged) are
          modeled as a collection of semantic components.</para>
        <para>Each semantic component in an information bundle corresponds to
          one of the following types of Business Information Entity (BIE) in a
          CCTS Document Model:</para>
        <itemizedlist>
          <listitem>
            <para>a single irreducible semantic component (referred to as a
              Basic Business Information Entity or BBIE);</para>
          </listitem>
          <listitem>
            <para>a structured aggregation of other semantic components
              (referred to as an Aggregate Business Information Entity or
              ABIE); or</para>
          </listitem>
          <listitem>
            <para>an association between ABIEs (referred to as an Association
              Business Information Entity or ASBIE).</para>
          </listitem>
        </itemizedlist>
        <para>The CCTS semantic model is not dependent on the syntax of the
          Open-edi user data actually exchanged. </para>
        <para>The Open-edi user data exchanged between parties is a
          machine-readable instance of an information bundle (CCTS Document
          Model). </para>
        <para>This specification assumes XML is the machine-readable syntax
          used for exchanging the Open-edi user data.</para>
        <para>When using an XML document for exchanging Open-edi user data each
          BIE corresponds to an XML element. </para>
        <para>The relationships between these various concepts are described in
            <xref linkend="T-MODELING-CONCEPTS"/></para>
        <table border="2" width="605" id="T-MODELING-CONCEPTS">
          <title>Modeling concepts</title>
          <tgroup cols="3">
            <colspec colnum="1" colname="col1" colwidth="1*"/>
            <colspec colnum="2" colname="col2" colwidth="1*"/>
            <colspec colnum="3" colname="col3" colwidth="3*"/>
            <tbody>
              <row>
                <entry><emphasis role="bold">Open-edi Reference Model (ISO
                    14882)</emphasis></entry>
                <entry>
                  <para>Semantic Model</para>
                  <para>(ebXML CCTS)</para>
                </entry>
                <entry>
                  <para>Physical representation</para>
                  <para>(W3C XML)</para>
                </entry>
              </row>
              <row>
                <entry><emphasis role="bold">Information
                  bundle</emphasis></entry>
                <entry>Semantic model</entry>
                <entry>Document schema</entry>
              </row>
              <row>
                <entry><emphasis role="bold">Semantic
                  component</emphasis></entry>
                <entry>Business Information Entity</entry>
                <entry>XML element</entry>
              </row>
              <row>
                <entry><emphasis role="bold">Open-edi user
                  data</emphasis></entry>
                <entry>Document</entry>
                <entry>XML document</entry>
              </row>
              <row>
                <entry/>
                <entry>Document ABIE</entry>
                <entry>XML document element schema definition with only element
                  children, and the XML document element itself</entry>
              </row>
              <row>
                <entry/>
                <entry>Library ABIE</entry>
                <entry>XML element schema definition (but not a document
                  element schema definition) with only element children</entry>
              </row>
              <row>
                <entry/>
                <entry>ASBIE</entry>
                <entry>XML element (but not a document element) with only
                  element children, defined by a Library ABIE</entry>
              </row>
              <row>
                <entry/>
                <entry>BBIE</entry>
                <entry>XML element with only text characters as children, no
                  elements as children</entry>
              </row>
            </tbody>
          </tgroup>
        </table>
      </section>
      <section id="S-BUSINESS-INFORMATION-ENTITIES">
        <title>Business Information Entities</title>
        <para>Following the conventions of the ebXML Core Component Technical
          Specification <xref linkend="ccts"/> a Business Information Entity
          (BIE) is piece of business data or a group of pieces of business data
          with a unique business semantic definition.</para>
        <para>A BIE is the result of using a core component within a specific
          business context. As such each BIE must be based on a core component.
          The definition of core components is outside the scope of this
          specification.</para>
        <para>It is the Business Information Entities that provide the
          structure for the semantic components of the body of the business
          document. </para>
        <para>The semantic components used to create the Open-edi user data
          validation artefacts (following these naming and design rules) are to
          be applied in a specific business context. Therefore it is the
          contextualized Business Information Entities to which these rules
          apply and not the core components from which they have been
          derived.</para>
      </section>
    </section>
    <section id="S-TERMINOLOGY">
      <title>Terminology</title>
      <section id="S-KEY-WORDS">
        <title>Key words</title>
        <para>The key words <glossterm>must</glossterm>, <glossterm>must
            not</glossterm>, <glossterm>required</glossterm>,
            <glossterm>shall</glossterm>, <glossterm>shall not</glossterm>,
            <glossterm>should</glossterm>, <glossterm>should not</glossterm>,
            <glossterm>recommended</glossterm>, <glossterm>may</glossterm>, and
            <glossterm>optional</glossterm> in this document are to be
          interpreted as described in <xref linkend="rfc2119"/>. Note that for
          reasons of style, these words are not capitalized in this
          document.</para>
      </section>
      <section id="S-TERMS-AND-DEFINITIONS">
        <title>Terms and Definitions</title>
        <variablelist>
          <varlistentry>
            <term>Business Information Entity (BIE)</term>
            <listitem>
              <para>A piece of business data or a group of pieces of business
                data with a unique Business Semantic definition, see <xref
                  linkend="ccts"/>.</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>Context/value Association (CVA)</term>
            <listitem>
              <para>The association of value constraints imposed on information
                found in a particular document context, see <xref
                  linkend="oasiscva"/>.</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>document ABIE</term>
            <listitem>
              <para>The apex ABIE of an information bundle.</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>document element</term>
            <listitem>
              <para>The apex element of information in an XML document, see
                  <xref linkend="xml"/>.</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>extension collection</term>
            <listitem>
              <para>The set of extension elements found in an XML document,
                constrained by an extension schema, that supplements the base
                information that is constrained by the published document
                model.</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>extension item</term>
            <listitem>
              <para>A single instance of structured supplemental information
                and its associated metadata distinguishing it from other
                extension items.</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>extension point</term>
            <listitem>
              <para>The apex element of structured supplemental information
                described by its metadata.</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>information bundle</term>
            <listitem>
              <para>The formal description of the semantics of the recorded
                information to be exchanged, as defined in <xref
                  linkend="iso14662"/>.</para>
            </listitem>
          </varlistentry>
          <varlistentry id="NDR">
            <term>naming and design rules</term>
            <listitem>
              <para>A set of rules governing the expression of information
                bundles using <xref linkend="ccts"/>, and the creation of
                associated XML document model validation artefacts using <xref
                  linkend="oasiscva"/> and <xref linkend="xsd"/>. </para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>object class</term>
            <listitem>
              <para>A set of ideas, abstractions, or things in the real world
                that are identified with explicit boundaries and meaning and
                whose properties and behavior follow the same rules <xref
                  linkend="iso11179"/> (definition 3.3.22).</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>Open-edi user data</term>
            <listitem>
              <para>Machine-readable instance of the content of information
                bundles or components of information bundles (as semantic
                components), see <xref linkend="iso14662"/>.</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>property</term>
            <listitem>
              <para>A characteristic common to all members of an object class
                  <xref linkend="iso11179"/> (definition 3.3.29).</para>
            </listitem>
          </varlistentry>
          <!--          <varlistentry>
            <term>validation</term>
            <listitem>
              <para>The processing involved in confirming that an XML document
                satisfies the document constraints expressed in a set of
                artefacts governing aspects of document content according to a
                document model.</para>
            </listitem>
          </varlistentry>-->
          <varlistentry>
            <term>semantic component</term>
            <listitem>
              <para>A unit of information unambiguously defined in the context
                of the business goal of the business transaction. A semantic
                component may be atomic or composed of other semantic
                components, see <xref linkend="iso14662"/>. </para>
            </listitem>
          </varlistentry>
          <varlistentry id="xsd">
            <term>XSD schema</term>
            <listitem>
              <para>An XML document model definition conforming to the W3C XML
                Schema language <xref linkend="xsd1"/><xref linkend="xsd2"
                />.</para>
            </listitem>
          </varlistentry>
        </variablelist>
        <para>The terms Core Component (CC), Basic Core Component (BCC),
          Aggregate Core Component (ACC), Association Core Component (ASCC),
          Business Information Entity (BIE), Basic Business Information Entity
          (BBIE), and Aggregate Business Information Entity (ABIE) are used in
          this specification with the meanings given in <xref linkend="ccts"
          />.</para>
        <para>The terms Object Class, Property Term, Representation Term, and
          Qualifier are used in this specification with the meanings given in
            <xref linkend="iso11179"/>.</para>
      </section>
      <section id="S-SYMBOLS-AND-ABBREVIATIONS">
        <title>Symbols and Abbreviations</title>
        <variablelist>
          <varlistentry>
            <term>ABIE</term>
            <listitem>
              <para>Aggregate Business Information Entity <xref linkend="ccts"
                /></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>ASBIE</term>
            <listitem>
              <para>Association Business Information Entity <xref
                  linkend="ccts"/></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>BIE</term>
            <listitem>
              <para>Business Information Entity <xref linkend="ccts"/></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>BBIE</term>
            <listitem>
              <para>Basic Business Information Entity <xref linkend="ccts"
                /></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>CCTS</term>
            <listitem>
              <para>Core Component Technical Specification <xref linkend="ccts"
                /></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>CVA</term>
            <listitem>
              <para>Context/value Association <xref linkend="oasiscva"/></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>NDR</term>
            <listitem>
              <para>Naming and Design Rules <xref linkend="NDR"/></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>TC</term>
            <listitem>
              <para>Technical Committee</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>XSD</term>
            <listitem>
              <para>W3C XML Schema Definition <xref linkend="xsd"/></para>
            </listitem>
          </varlistentry>
        </variablelist>
      </section>
    </section>
    <section id="S-NORMATIVE-REFERENCES">
      <title>Normative References</title>
      <bibliolist>
        <bibliomixed id="ccts"><abbrev>CCTS</abbrev>
          <title>UN/CEFACT Core Component Technical Specification - Part 8 of
            the ebXML Framework) </title>
          <date>15 November 2003</date><edition>Vresion
              2.01</edition><citetitle><ulink
              url="http://www.unece.org/fileadmin/DAM/cefact/codesfortrade/CCTS/CCTS_V2-01_Final.pdf"
              >http://www.unece.org/fileadmin/DAM/cefact/codesfortrade/CCTS/CCTS_V2-01_Final.pdf</ulink></citetitle></bibliomixed>
        <bibliomixed id="oasiscva">
          <abbrev>CVA</abbrev>
          <citetitle>OASIS Context/value association using genericode 1.0. </citetitle>
          <date>15 April 2010. </date>
          <releaseinfo>Committee Specification 01. </releaseinfo>
          <bibliomisc>
            <ulink
              url="http://docs.oasis-open.org/codelist/cs01-ContextValueAssociation-1.0/doc/context-value-association.html"
              >http://docs.oasis-open.org/codelist/cs01-ContextValueAssociation-1.0/doc/context-value-association.html</ulink>.
          </bibliomisc>
        </bibliomixed>
        <bibliomixed id="gc">
          <abbrev>genericode</abbrev>
          <citetitle>OASIS Code List Representation (Genericode) Version
            1.0.</citetitle>
          <date>28 December 2007. </date>
          <releaseinfo>Committee Specification 01. </releaseinfo>
          <bibliomisc>
            <ulink
              url="http://docs.oasis-open.org/codelist/cs-genericode-1.0/doc/oasis-code-list-representation-genericode.html"
              >http://docs.oasis-open.org/codelist/cs-genericode-1.0/doc/oasis-code-list-representation-genericode.html</ulink>.
          </bibliomisc>
        </bibliomixed>
        <bibliomixed id="iso11179"><abbrev>ISO 11179</abbrev>
          <title>ISO/IEC 11179-1:2004 Information technology &#8212;
            Specification and standardization of data elements &#8212; Part 1:
            Framework for the specification and standardization of data
            elements </title>
          <citetitle>
            <ulink
              url="http://standards.iso.org/ittf/PubliclyAvailableStandards/c035343_ISO_IEC_11179-1_2004(E).zip"
              >http://standards.iso.org/ittf/PubliclyAvailableStandards/c035343_ISO_IEC_11179-1_2004(E).zip</ulink></citetitle></bibliomixed>
        <bibliomixed id="iso14662"><abbrev>ISO 14662</abbrev>
          <title>ISO/IEC 14662:2004 Information technology &#8212; Open-edi
            reference model</title>
          <citetitle>
            <ulink
              url="http://standards.iso.org/ittf/PubliclyAvailableStandards/"
              >http://standards.iso.org/ittf/PubliclyAvailableStandards/</ulink></citetitle></bibliomixed>
        <bibliomixed id="rfc2119"><abbrev>RFC 2119</abbrev>
          <author>
            <surname>Bradner, </surname>
            <firstname>S.</firstname>
          </author>, <title>Key words for use in RFCs to Indicate Requirement
            Levels</title>, <releaseinfo>BCP 14, RFC 2119</releaseinfo>,
            <date>March 1997</date>, <citetitle>&lt;<ulink
              url="http://www.rfc-editor.org/info/rfc2119"
              >http://www.rfc-editor.org/info/rfc2119</ulink>></citetitle>. </bibliomixed>
        <bibliomixed id="xml"><abbrev>XML</abbrev>
          <title>Extensible Markup Language (XML) 1.0 (Fifth Edition)</title>, <author>
            <firstname>T. </firstname>
            <surname>Bray</surname>
          </author>, <author>
            <firstname>J. </firstname>
            <surname>Paoli</surname>
          </author>, <author>
            <firstname>C. M. </firstname>
            <surname>Sperberg-McQueen</surname>
          </author>, <author>
            <firstname>E. </firstname>
            <surname>Maler</surname>
          </author>, <author>
            <firstname>F. </firstname>
            <surname>Yergeau</surname>
          </author>, Editors, <releaseinfo>W3C Recommendation</releaseinfo>,
            <date>26 November 2008</date>, <citetitle><ulink
              url="http://www.w3.org/TR/2008/REC-xml-20081126/"
              >http://www.w3.org/TR/2008/REC-xml-20081126/</ulink></citetitle>.
          Latest version available at <citetitle><ulink
              url="http://www.w3.org/TR/xml"
            >http://www.w3.org/TR/xml</ulink></citetitle>. </bibliomixed>
        <bibliomixed id="xpath10"><abbrev>XPath 1.0</abbrev>
          <title>XML Path Language (XPath) Version 1.0</title>, <author>
            <firstname>J. </firstname>
            <surname>Clark</surname>
          </author>, <author>
            <firstname>S. </firstname>
            <surname>DeRose</surname>
          </author>, Editors, <releaseinfo>W3C Recommendation</releaseinfo>,
            <date>16 November 1999</date>, <citetitle><ulink
              url="http://www.w3.org/TR/1999/REC-xpath-19991116/"
              >http://www.w3.org/TR/1999/REC-xpath-19991116/</ulink></citetitle>.
          Latest version available at <citetitle><ulink
              url="http://www.w3.org/TR/xpath"
              >http://www.w3.org/TR/xpath</ulink></citetitle>. </bibliomixed>
        <bibliomixed id="xsd1"><abbrev>XSD1</abbrev>
          <title>XML Schema Part 1: Structures Second Edition</title>, <author>
            <firstname>H. S. </firstname>
            <surname>Thompson</surname>
          </author>, <author>
            <firstname>D. </firstname>
            <surname>Beech</surname>
          </author>, <author>
            <firstname>M. </firstname>
            <surname>Maloney</surname>
          </author>, <author>
            <firstname>N. </firstname>
            <surname>Mendelsohn</surname>
          </author>, Editors, <releaseinfo>W3C Recommendation</releaseinfo>,
            <date>28 October 2004</date>, <citetitle><ulink
              url="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"
              >http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/</ulink></citetitle>.
          Latest version available at <citetitle><ulink
              url="http://www.w3.org/TR/xmlschema-1"
              >http://www.w3.org/TR/xmlschema-1</ulink></citetitle>. </bibliomixed>
        <bibliomixed id="xsd2"><abbrev>XSD2</abbrev>
          <title>XML Schema Part 2: Datatypes Second Edition</title>, <author>
            <firstname>P. V. </firstname>
            <surname>Biron</surname>
          </author>, <author>
            <firstname>A. </firstname>
            <surname>Malhotra</surname>
          </author>, Editors, <releaseinfo>W3C Recommendation</releaseinfo>,
            <date>28 October 2004</date>, <citetitle><ulink
              url="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"
              >http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/</ulink></citetitle>.
          Latest version available at <citetitle><ulink
              url="http://www.w3.org/TR/xmlschema-2"
              >http://www.w3.org/TR/xmlschema-2</ulink></citetitle>.
        </bibliomixed>
      </bibliolist>
    </section>
    <section id="S-NON-NORMATIVE-REFERENCES">
      <title>Non-Normative References</title>
      <bibliolist>
        <bibliomixed id="UBL"><abbrev>UBL-2.1</abbrev>
          <citetitle>Universal Business Language Version 2.1.</citetitle>
          <date>04 November 2013. </date>
          <releaseinfo>OASIS Standard. </releaseinfo>
          <bibliomisc>
            <ulink url="http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html"
              >http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html</ulink>.
          </bibliomisc>
        </bibliomixed>
        <bibliomixed id="UBLCCTS"><abbrev>UBL-CCTS</abbrev>
          <citetitle>UBL Conformance to ebXML CCTS ISO/TS 15000-5:2005 Version
            1.0</citetitle>
          <date>08 May 2014. </date>
          <releaseinfo>Committee Note 01. </releaseinfo>
          <bibliomisc>
            <ulink
              url="http://docs.oasis-open.org/ubl/UBL-conformance-to-CCTS/v1.0/"
              >http://docs.oasis-open.org/ubl/UBL-conformance-to-CCTS/v1.0/</ulink>.
          </bibliomisc>
        </bibliomixed>
        <bibliomixed id="xmldsig"><abbrev>xmldsig</abbrev>
          <title>XML-Signature Syntax and Processing Version 1.1</title>, <author>
            <firstname>D. E. </firstname>
            <surname>Eastlake</surname>
          </author>, <author>
            <firstname>J. </firstname>
            <surname>Reagle</surname>
          </author>, <author>
            <firstname>D. </firstname>
            <surname>Solo</surname>
          </author>, <author>
            <firstname>F. </firstname>
            <surname>Hirsch</surname>
          </author>, <author>
            <firstname>M. </firstname>
            <surname>Nyström</surname>
          </author>, <author>
            <firstname>T. </firstname>
            <surname>Roessler</surname>
          </author>, <author>
            <firstname>K. </firstname>
            <surname>Yiu</surname>
          </author>, Editors, <releaseinfo>W3C Recommendation</releaseinfo>,
            <date>11 April 2013</date>, <citetitle><ulink
              url="http://www.w3.org/TR/2013/REC-xmldsig-core1-20130411/"
              >http://www.w3.org/TR/2013/REC-xmldsig-core1-20130411/</ulink></citetitle>.
          Latest version available at <citetitle><ulink
              url="http://www.w3.org/TR/xmldsig-core1"
              >http://www.w3.org/TR/xmldsig-core1</ulink></citetitle>.
        </bibliomixed>
      </bibliolist>
    </section>
  </section>
  <section id="S-CONTEXT-OF-USE-AND-APPLICATION-OF-THESE-RULES">
    <title>Context of use and application of these rules</title>
    <para>These XML Naming and Design Rules may be used to create a collection
      of artefacts for defining and validated a set of extensible XML document
      types. </para>
    <para>They describe processes for:</para>
    <orderedlist numeration="upperalpha">
      <listitem>
        <para>expressing the semantic components of information bundles using
          the ebXML Core Components Technical Specification <xref
            linkend="ccts"/>, and</para>
      </listitem>
      <listitem>
        <para>producing XML definition and validation artefacts based on those
          semantic components, specifically: </para>
        <orderedlist>
          <listitem>
            <para>Document structural constraints of elements and attributes
              (for example, nesting and cardinality) using W3C Schema <xref
                linkend="xsd"/>, and </para>
          </listitem>
          <listitem>
            <para>Data value constraints using OASIS Context/value Association
                <xref linkend="oasiscva"/> expressions of values <xref
                linkend="gc"/> (for example, coded value domains or code lists)
              with XML document locations using XPath <xref linkend="xpath10"
              />. </para>
          </listitem>
        </orderedlist>
      </listitem>
    </orderedlist>
    <para>These processes are depicted in <xref
        linkend="F-GENERIC-NDR-PROCESSES-TO-CREATE-XML-VALIDATION-ARTEFACTS"
      />.</para>
    <figure id="F-GENERIC-NDR-PROCESSES-TO-CREATE-XML-VALIDATION-ARTEFACTS">
      <title>Generic NDR processes to create XML validation artefacts</title>
      <mediaobject>
        <imageobject>
          <imagedata fileref="art/&dir;-v&version;-procgen.png"
            contentwidth="750px"/>
        </imageobject>
        <textobject>
          <phrase>Generic Process Diagram</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>Designers (and implementers) may choose to adopt other, optional
      processes to produce additional artefacts. For example, the serialization
      of the information bundle (as a CCTS model) into a form suitable for
      further processing or the production of reports useful in the design and
      review of the model. See <xref
        linkend="A-ADDITIONAL-PRODUCTION-PROCESSES"/> for more details.</para>
  </section>
  <section id="S-INFORMATION-MODELING">
    <title>Information modeling</title>
    <section id="S-DOCUMENT-ABIES">
      <title>Document ABIEs</title>
      <para>A Document ABIE structures the apex of the information bundle to be
        exchanged between parties.</para>
      <blockquote role="rule" id="MOD01">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>MOD01 Document ABIE</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>The apex of the information bundle shall be structured as
                  a single top-level ABIE, referred to in this specification as
                  a Document ABIE.</para>
                <note>
                  <para>The rationale is that the Document ABIE is always
                    considered a one-member collection in and of itself with no
                    other members in the collection.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
    </section>
    <section id="S-ABIE-LIBRARY">
      <title>ABIE library</title>
      <para>The ABIE library is a collection of common, reusable ABIEs
        available to be referenced by ASBIEs.</para>
      <para>The ABIE library does not include any Document ABIEs.</para>
      <blockquote role="rule" id="MOD02">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>MOD02 ABIE library contents</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>The ABIE library shall not contain any Document
                  ABIEs.</para>
                <note>
                  <para>The rationale is that Document ABIEs are identified in
                    syntax implementations separately from other collections of
                    ABIEs.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="MOD03">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>MOD03 ABIE library ordering</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>The ABIE library shall have all ABIEs defined in
                  alphabetical order of the ABIE's dictionary entry
                  name.</para>
                <note>
                  <para>The rationale is that the library can be very large and
                    a reader new to the library may be unfamiliar with any
                    arbitrary ordering of the ABIEs. Designers and implementers
                    can navigate a collection of ABIEs more easily when they
                    are in alphabetical order.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
    </section>
    <section id="S-EXTENSIONS">
      <title>Extensions</title>
      <para>Wherever possible semantic components within an information bundle
        should be expressed using the BIEs found in an existing Document ABIE
        or the ABIE Library. However there may be implementations where
        supplementary information is required to be exchanged in the
        information bundle in a way that does not interfere with existing BIEs. </para>
      <para>The extension mechanism in this specification provides for
        including additional semantic components that may augment a
        standardized information bundle with customized additional information. </para>
      <para>Extensions can contain new BIEs or can reference BIEs from existing
        ABIEs but used in a different context. Extensions can also include
        foreign constructs not defined as BIEs.</para>
      <para>Extensions may be horizontal in nature in that they are available
        to use for all information bundles. An example might be the structure
        of digital signatures.</para>
      <para>Extensions may also be vertical in nature, in that they are
        applicable only to a single information bundle. For example, additional
        invoice line detail information to augment an invoice for a specific
        industry.</para>
      <para>An extension collection provides a placeholder for the extensions
        to be used with a set of Open-edi user data. Within each collection
        there may be a number of extensions, each with metadata properties
        regarding the extension and each with a single extension point (the
        apex structure of the supplemental information). </para>
      <blockquote role="rule" id="MOD04">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>MOD04 Extension availability</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>Each document shall allow for optional augmentation with
                  a collection of information not conceptually described by
                  existing BIEs.</para>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <note>
        <para>There are no constraints on the information that may be included
          in an extension, including reusing BIEs from existing ABIEs.</para>
      </note>
      <note>
        <para>When using an XML document for exchanging Open-edi user data,
          extension XSD schema fragments augment the document's XSD schema
          created for a document ABIE.</para>
      </note>
    </section>
  </section>
  <section id="S-DICTIONARY-INFORMATION">
    <title>Dictionary information</title>
    <section id="S-DICTIONARY-INFORMATION-OVERVIEW">
      <title>Dictionary information overview</title>
      <para>A BIE is described by the values of its dictionary information as
        specified by the Core Components Technical Specification 2.01 <xref
          linkend="ccts"/>.</para>
      <para>To facilitate the definition of the appropriate name for a BBIE,
        the CCTS property term is specified as the concatenation of two
        contributing dictionary information values. The optional property term
        possessive noun and the mandatory property term primary noun are used.
        When the possessive noun is used the values are separated by a space
        character.</para>
      <para>To facilitate the definition of the appropriate name for a ASBIE,
        the CCTS property term is specified as the concatenation of two
        contributing dictionary information values. The optional associated
        object class qualifier and the mandatory associated object class are
        used. When the associated object class qualifier is used the qualifier
        value is suffixed with an underscore character and the values are
        separated by a space character.</para>
    </section>
    <section id="S-DICTIONARY-INFORMATION-VALUES">
      <title>Dictionary information values</title>
      <para>Certain rules govern the creation and expression of dictionary
        information values for all BIEs defined in the semantic model of an
        information bundle.</para>
      <blockquote id="COM01" role="rule">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>COM01 Dictionary information values</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>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.</para>
                <note>
                  <para>The rationale is that the dictionary information values
                    may be constrained in its expression, such as is true in an
                    XML attribute.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="COM02">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>COM02 Dictionary information value prohibited characters and
                character sequences</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>The following characters shall not be contained in any
                  dictionary information value:</para>
                <itemizedlist>
                  <listitem>
                    <para>the characters "&lt;", ">", "&amp;"</para>
                  </listitem>
                  <listitem>
                    <para>white-space characters other than the " " (space)
                      character</para>
                  </listitem>
                  <listitem>
                    <para>the character sequence "--"</para>
                  </listitem>
                </itemizedlist>
                <note>
                  <para>The rationale is that prohibiting these characters and
                    sequences will allow the dictionary information values to
                    be processed more simply in different XML contexts without
                    special handling.</para>
                </note>
                <note>
                  <para>The constraint on white-space characters prohibits
                    values from being structured as paragraphs.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
    </section>
    <section id="S-ABBREVIATIONS">
      <title>Abbreviations</title>
      <para>It may be convenient to abbreviate complex terms or to use
        commonly-accepted abbreviations in dictionary information
        values.</para>
      <blockquote role="rule" id="COM03">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>COM03 Controlled list of abbreviations in BIE names</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>Abbreviations for terms used in BIE names shall be taken
                  from a controlled list of abbreviations agreed for use within
                  the semantic model.</para>
                <note>
                  <title>Examples</title>
                  <simplelist>
                    <member>"Identifier" is abbreviated as "ID".</member>
                    <member>"Universally Unique Identifier" is abbreviated as
                      "UUID".</member>
                  </simplelist>
                </note>
                <note>
                  <para>The rationale is that some common or complex terms have
                    commonly-accepted abbreviations suitable for shortening the
                    length of BIE names.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="COM04">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>COM04 Controlled list of abbreviations in dictionary
                information values</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>Abbreviations for terms used in dictionary information
                  values shall be taken from a controlled list of
                  commonly-agreed abbreviations.</para>
                <note>
                  <title>Examples</title>
                  <simplelist>
                    <member>"XML Path Language" is abbreviated as
                      "XPath".</member>
                    <member>"Card Verification Value" is abbreviated as
                      "CV2".</member>
                  </simplelist>
                </note>
                <note>
                  <para>The rationale is that some common terms have
                    widely-accepted abbreviations in general use or in
                    particular use within the information domain. Inconsistent
                    use of abbreviations may lead to semantic ambiguity.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="COM05">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>COM05 List of equivalent terms in BIE names</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>Equivalent terms used in BIE names shall be taken from a
                  list of commonly-agreed equivalent terms.</para>
                <note>
                  <title>Example</title>
                  <para>The property term primary noun "URI" is considered
                    equivalent to the representation term "Identifier".</para>
                </note>
                <note>
                  <para>The rationale is that some common terms wholly include
                    the concepts presented in other terms and so should be
                    considered equivalent in order to prevent
                    duplication.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
    </section>
    <section id="S-DICTIONARY-INFORMATION-FOR-BIES">
      <title>Dictionary information for BIEs</title>
      <section id="S-DICTIONARY-INFORMATION-FOR-ABIES">
        <title>Dictionary information for ABIEs</title>
        <blockquote id="COM06" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM06 Minimum set of dictionary information values
                  describing an ABIE</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each ABIE shall have the following set of dictionary
                    information values:</para>
                  <itemizedlist>
                    <listitem>
                      <para>Component Type (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>shall be the value "ABIE"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Definition (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall describe the ABIE using
                            complete natural language sentences in a single
                            paragraph</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Alternative Business Terms (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall list any other commonly used
                            terms that are synonyms for the ABIE</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Object Class Qualifier (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall qualify the object class for a
                            specific context</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Object Class (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall identify the object of
                            interest within an information bundle; it is the
                            class to which the ABIE's BIEs belong</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Name (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall be the concatenation of Object
                            Class Qualifier and the Object Class without any
                            spaces, abbreviating the values as required</para>
                        </listitem>
                      </itemizedlist>
                      <note>
                        <title>Example (using an XPath expression)</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$OCQ = Object Class Qualifier</member>
                          <member>$OC = Object Class</member>
                          <member>C:ABBREV(arg) = custom function to return the
                            abbreviation of an argument, or the argument itself
                            if no abbreviation, and all spaces removed</member>
                        </simplelist>
                        <programlisting>concat( C:ABBREV($OCQ),
        C:ABBREV($OC)
      )</programlisting>
                        <!--<para>=SUBSTITUTE( CONCATENATE( $OCQ;$OC);" ";"")</para>-->
                      </note>
                    </listitem>
                    <listitem>
                      <para>Dictionary Entry Name (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>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"</para>
                        </listitem>
                      </itemizedlist>
                      <note>
                        <title>Example (using an XPath expression)</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$OCQ = Object Class Qualifier</member>
                          <member>$OC = Object Class</member>
                        </simplelist>
                        <programlisting>concat( if( $OCQ )
          then concat($OCQ,'_ ') else '',
        $OC,
        '. Details' 
      )</programlisting>
                        <!--<para>=CONCATENATE( IF( $OCQ="";"";CONCATENATE( $OCQ;"_ "));$OC;". Details")</para>-->
                      </note>
                    </listitem>
                  </itemizedlist>
                  <note>
                    <title>Example ABIE</title>
                    <para>Fixed value:</para>
                    <simplelist>
                      <member>Component Type="ABIE"</member>
                    </simplelist>
                    <para>Entered values:</para>
                    <simplelist>
                      <member>Definition="A class to define common information
                        related to an address."</member>
                      <member>Object Class="Address"</member>
                    </simplelist>
                    <para>Derived values:</para>
                    <simplelist>
                      <member>Name="Address"</member>
                      <member>Dictionary Entry Name="Address. Details"</member>
                    </simplelist>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-DICTIONARY-INFORMATION-FOR-BBIES">
        <title>Dictionary information for BBIEs</title>
        <blockquote role="rule" id="COM07">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM07 Minimum set of dictionary information values
                  describing a BBIE</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each BBIE shall have the following set of dictionary
                    information values:</para>
                  <itemizedlist>
                    <listitem>
                      <para>Component Type (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>shall be the value "BBIE"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Cardinality (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>shall be one of: <itemizedlist>
                              <listitem>
                                <para>"1" (required and not repeatable),</para>
                              </listitem>
                              <listitem>
                                <para> "0..1" (optional and not repeatable),
                                </para>
                              </listitem>
                              <listitem>
                                <para>"0..n" (optional and repeatable) or
                                </para>
                              </listitem>
                              <listitem>
                                <para>"1..n" (required and repeatable)</para>
                              </listitem>
                            </itemizedlist></para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Definition (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall describe the BBIE using
                            complete natural language sentences in a single
                            paragraph</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Alternative Business Terms (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall list any other commonly used
                            terms that are synonyms for the ABIE</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Object Class Qualifier (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall qualify the object class for a
                            specific context</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Object Class (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall identify the object class of
                            the ABIE to which the BBIE belongs</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Property Term Qualifier (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall qualify the property term for
                            a specific context</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Property Term Possessive Noun (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall identify a distinguishing
                            nature of the characteristic of the object
                            class</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Property Term Primary Noun (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall identify the principle nature
                            of the characteristic of the object class</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Property Term (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>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</para>
                        </listitem>
                      </itemizedlist>
                      <note>
                        <title>Example (using an XPath expression)</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$PTPsN = Property Term Possessive
                            Noun</member>
                          <member>$PTPrN = Property Term Primary Noun</member>
                        </simplelist>
                        <programlisting>concat( $PTPSN, 
        if( $PTPSN )
          then ' ' else '',
        $PTPRN
      )</programlisting>
                        <!--<para>=IF( $PTPsN&lt;>"";CONCATENATE( $PTPsN;" ";$PTPrN);$PTPrN)</para>-->
                      </note>
                    </listitem>
                    <listitem>
                      <para>Representation Term (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>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):</para>
                          <itemizedlist>
                            <listitem>
                              <para>Amount</para>
                            </listitem>
                            <listitem>
                              <para>Binary Object (Graphic, Picture, Sound,
                                Video)</para>
                            </listitem>
                            <listitem>
                              <para>Code</para>
                            </listitem>
                            <listitem>
                              <para>Date Time (Date, Time)</para>
                            </listitem>
                            <listitem>
                              <para>Identifier</para>
                            </listitem>
                            <listitem>
                              <para>Indicator</para>
                            </listitem>
                            <listitem>
                              <para>Measure</para>
                            </listitem>
                            <listitem>
                              <para>Numeric (Value, Rate, Percent)</para>
                            </listitem>
                            <listitem>
                              <para>Quantity</para>
                            </listitem>
                            <listitem>
                              <para>Text (Name)</para>
                            </listitem>
                          </itemizedlist>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Name (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>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</para>
                        </listitem>
                      </itemizedlist>
                      <note>
                        <title>Example (using an XPath expression)</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$PTQ = Property Term Qualifier</member>
                          <member>$PTPsN = Property Term Possessive
                            Noun</member>
                          <member>$PTPrN = Property Term Primary Noun</member>
                          <member>$RT = Representation Term</member>
                          <member>C:ABBREV(arg) = custom function to return the
                            abbreviation of an argument, or the argument itself
                            if no abbreviation, and all spaces removed, or the
                            argument itself if no abbreviation, and all spaces
                            removed</member>
                          <member>C:EQUIVALENT(noun,term) = custom function to
                            return TRUE/FALSE if the primary noun and
                            representation term are to be considered
                            equivalent</member>
                        </simplelist>
                        <programlisting>concat( C:ABBREV($PTQ),
        C:ABBREV($PTPSN),
        if( $PTPRN!='Text' OR 
            ( not($PTQ) AND not($PTPSN) ) )
          then C:ABBREV($PTPRN) else '',
        if( $RT!='Text' AND not(C:EQUIVALENT($PTPRN,$RT)))
          then C:ABBREV($RT) else ''
      )</programlisting>
                        <!--<para>=SUBSTITUTE( CONCATENATE( $PTQ;$PTPsN;IF( $PTPrN="Identifier";"ID"; IF( AND( $PTPrN="Text";OR( $PTQ&lt;>"";$PTPsN&lt;>""));"";$PTPrN)); IF( AND( $RT&lt;>"Text";$PTPrN&lt;>$RT;NOT( AND( $PTPrN="URI";$RT="Identifier")); NOT( AND( $PTPrN="UUID";$RT="Identifier")));IF( $RT="Identifier";"ID";$RT);""));" ";"") </para>-->
                      </note>
                    </listitem>
                    <listitem>
                      <para>Dictionary Entry Name (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>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</para>
                        </listitem>
                      </itemizedlist>
                      <note>
                        <title>Example (using an XPath expression)</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$OCQ = Object Class Qualifier</member>
                          <member>$OC = Object Class</member>
                          <member>$PTQ = Property Term Qualifier</member>
                          <member>$PT = Property Term</member>
                          <member>$RT = Representation Term</member>
                        </simplelist>
                        <programlisting>concat( $OCQ, 
        if( $OCQ )
          then '_ ' else '',$OC,'. ',
        $PTQ, 
        if( $PTQ )
          then '_ ' else '',$PT,
        if( $PTQ OR ( $PT != $RT ) )
          then concat( '. ',$RT) else ''
      )</programlisting>
                        <!--<para>=CONCATENATE( IF( $OCQ="";"";CONCATENATE( $OCQ;"_ "));$OC;". ";IF( $PTQ="";"";CONCATENATE( $PTQ;"_ "));$PT;IF( OR( $PTQ&lt;>"";$PT&lt;>$RT);CONCATENATE( ". ";$RT);""))</para>-->
                      </note>
                    </listitem>
                    <listitem>
                      <para>Data Type Qualifier (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall distinguish particular
                            restrictions on a data type from the use of a data
                            type with other (or no) restrictions</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Data Type (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>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"</para>
                        </listitem>
                      </itemizedlist>
                      <note>
                        <title>Example (using an XPath expression)</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$DTQ = Data Type Qualifier</member>
                          <member>$RT = Representation Term</member>
                        </simplelist>
                        <programlisting>concat( $DTQ, 
        if( $DTQ )
          then '_ ' else '', 
        $RT,
        '. Type'
      )</programlisting>
                        <!--<para>=CONCATENATE( IF( $DTQ="";"";CONCATENATE( $DTQ;"_ "));$RT;". Type")</para>-->
                      </note>
                    </listitem>
                  </itemizedlist>
                  <note>
                    <title>Example BBIE</title>
                    <para>Fixed value:</para>
                    <simplelist>
                      <member>Component Type="BBIE"</member>
                    </simplelist>
                    <para>Entered values:</para>
                    <simplelist>
                      <member>Cardinality="0..1"</member>
                      <member>Definition="An additional street name used to
                        further clarify the address."</member>
                      <member>Object Class="Address"</member>
                      <member>Property Term Qualifier="Additional"</member>
                      <member>Property Term Possessive Noun="Street"</member>
                      <member>Property Term Primary Noun="Name"</member>
                      <member>Representation Term="Name"</member>
                    </simplelist>
                    <para>Derived values:</para>
                    <simplelist>
                      <member>Name="AdditionalStreetName"</member>
                      <member>Dictionary Entry Name="Address. Additional_
                        Street Name. Name"</member>
                      <member>Property Term="Street Name"</member>
                      <member>Data Type="Name. Type"</member>
                    </simplelist>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-DICTIONARY-INFORMATION-FOR-ASBIES">
        <title>Dictionary information for ASBIEs</title>
        <blockquote role="rule" id="COM08">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM08 Minimum set of dictionary information values
                  describing an ASBIE</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each ASBIE shall have the following set of dictionary
                    information values:</para>
                  <itemizedlist>
                    <listitem>
                      <para>Component Type (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>shall be the value "ASBIE"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Cardinality (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>shall be one of: <itemizedlist>
                              <listitem>
                                <para>"1" (required and not repeatable),</para>
                              </listitem>
                              <listitem>
                                <para> "0..1" (optional and not repeatable),
                                </para>
                              </listitem>
                              <listitem>
                                <para>"0..n" (optional and repeatable) or
                                </para>
                              </listitem>
                              <listitem>
                                <para>"1..n" (required and repeatable)</para>
                              </listitem>
                            </itemizedlist></para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Definition (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall describe the BBIE using
                            complete natural language sentences in a single
                            paragraph</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Alternative Business Terms (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall list any other commonly used
                            terms that are synonyms for the ABIE</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Object Class Qualifier (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall qualify the object class for a
                            specific context</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Object Class (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall identify the object class of
                            the ABIE to which the BBIE belongs</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Associated Object Class Qualifier (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall qualify the object class of
                            the associated ABIE for a specific context</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Associated Object Class (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall identify the object class of
                            the ABIE the ASBIE associates to</para>
                        </listitem>
                        <listitem>
                          <para>the ABIE must exist in the model with the same
                            qualification (or lack thereof) as the ASBIE's
                            associated object class qualifier</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Property Term Qualifier (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall qualify the property term for
                            a specific context</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Property Term (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall be the concatenation of the
                            Associated Object Class Qualifier, an underscore
                            and a space when defined, and the Associated Object
                            Class</para>
                        </listitem>
                      </itemizedlist>
                      <note>
                        <title>Example (using an XPath expression)</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$AOCQ = Associated Object Class
                            Qualifier</member>
                          <member>$AOC = Associated Object Class</member>
                        </simplelist>
                        <programlisting>concat( $AOCQ, 
        if( $AOCQ )
          then '_ ' else '',
        $AOC
      )</programlisting>
                        <!--<para>=CONCATENATE( IF( $AOCQ="";"";CONCATENATE( $AOCQ;"_ "));$AOC)</para>-->
                      </note>
                    </listitem>
                    <listitem>
                      <para>Representation Term (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall be the same as the Property
                            Term</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Name (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value shall be the concatenation of
                            Property Term Qualifier and the Property Term
                            without any spaces or underscore, abbreviating the
                            values as required</para>
                        </listitem>
                      </itemizedlist>
                      <note>
                        <title>Example (using an XPath expression)</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$PTQ = Property Term Qualifier</member>
                          <member>$PT = Property Term</member>
                          <member>C:ABBREV(arg) = custom function to return the
                            abbreviation of an argument, or the argument itself
                            if no abbreviation, and all spaces removed, or the
                            argument itself if no abbreviation, and all spaces
                            removed</member>
                        </simplelist>
                        <programlisting>concat( C:ABBREV($PTQ),
        C:ABBREV($PT)
      )</programlisting>
                        <!--<para>=SUBSTITUTE( SUBSTITUTE( CONCATENATE( $PTQ;IF( $PT="Identifier";"ID";$PT));" ";"");"_";"")</para>-->
                      </note>
                    </listitem>
                    <listitem>
                      <para>Dictionary Entry Name (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>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</para>
                        </listitem>
                      </itemizedlist>
                      <note>
                        <title>Example (using an XPath expression)</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$OCQ = Object Class Qualifier</member>
                          <member>$OC = Object Class</member>
                          <member>$PTQ = Property Term Qualifier</member>
                          <member>$PT = Property Term</member>
                          <member>$RT = Representation Term</member>
                        </simplelist>
                        <programlisting>concat( $OCQ, 
        if( $OCQ )
          then '_ ' else '',
        $OC,
        '. ',
        $PTQ, 
        if( $PTQ )
          then '_ ' else '',
        $PT,
        if( $PTQ )
          then concat('. ',$RT) else '' 
      )</programlisting>
                        <!--<para>=CONCATENATE( IF( $OCQ="";"";CONCATENATE( $OCQ;"_ "));$OC;". ";IF( $PTQ="";"";CONCATENATE( $PTQ;"_ "));$PT;IF( $PTQ="";"";CONCATENATE( ". ";$RT)))</para>-->
                      </note>
                    </listitem>
                  </itemizedlist>
                  <note>
                    <title>Example ASBIE</title>
                    <para>Fixed value:</para>
                    <simplelist>
                      <member>Component Type="ASBIE"</member>
                    </simplelist>
                    <para>Entered values:</para>
                    <simplelist>
                      <member>Cardinality="0..1"</member>
                      <member>Definition="The buyer of the item."</member>
                      <member>Object Class="Forecast"</member>
                      <member>Associated Object Class="Customer Party"</member>
                      <member>Property Term Qualifier="Buyer"</member>
                    </simplelist>
                    <para>Derived values:</para>
                    <simplelist>
                      <member>Name="BuyerCustomerParty"</member>
                      <member>Dictionary Entry Name="Forecast. Buyer_ Customer
                        Party. Customer Party"</member>
                      <member>Property Term="CustomerParty"</member>
                      <member>Representation Term="CustomerParty"</member>
                    </simplelist>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-DICTIONARY-ENTRY-NAMES">
        <title>Dictionary entry names</title>
        <blockquote role="rule" id="COM09">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM09 Dictionary entry name uniqueness</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>All dictionary entry names in a semantic model shall be
                    unique.</para>
                  <note>
                    <para>The rationale is that a BIE describes a unique
                      semantic component of business data within a specific
                      business context.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="COM10">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM10 CCTS dictionary information item name value
                  prohibited characters</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>All information items contributing to a component's
                    dictionary entry name shall be void of all sensitive
                    dictionary entry name markup characters.</para>
                  <para>The following characters must not be used in any
                    dictionary information values that contribute to the
                    dictionary entry name:</para>
                  <itemizedlist>
                    <listitem>
                      <para>the characters "." (period) and "_"
                        (underscore)</para>
                    </listitem>
                    <listitem>
                      <para>leading, trailing or multiple sequential " "
                        (space) characters</para>
                    </listitem>
                  </itemizedlist>
                  <note>
                    <para>The rationale is that prohibiting these characters in
                      name values prevents ambiguity when assembled into the
                      dictionary entry name using these characters to provide
                      structure.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="COM11">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM11 Use of the singular form in names</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>All information items contributing to a component's
                    dictionary entry name shall be in the singular form unless
                    the concept itself is plural.</para>
                  <note>
                    <title>Example</title>
                    <para>"Payment Terms" is the noun used for the collection
                      of a plurality of various aspects of payment and has a
                      cardinality of only "0..1".</para>
                  </note>
                  <note>
                    <para>The rationale is that the cardinality of an item
                      named in the singular confers the plurality of the
                      item.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="COM12">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM12 Use of leading upper case letter in dictionary entry
                  name values</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
    </section>
    <section id="S-STRUCTURE-OF-AN-ABIE">
      <title>Structure of an ABIE</title>
      <blockquote role="rule" id="COM13">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>COM13 ABIE contents cannot be empty</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>Every ABIE shall contain at least one BIE.</para>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="COM14">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>COM14 ABIE organization</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>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.</para>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="COM15">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>COM15 ABIE children ordering</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>Every ABIE shall have all of its BBIE children listed
                  before its ASBIE children.</para>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
    </section>
  </section>
  <section id="S-XML-VALIDATION-ARTEFACTS">
    <title>XML validation artefacts</title>
    <section id="S-XML-VALIDATION-ARTEFACTS-OVERVIEW">
      <title>XML validation artefacts overview</title>
      <para>These NDR provide for expressing the semantic model of an
        information bundle as XML artefacts that provide for definition and
        validation of the structure and content of XML Documents. </para>
      <para>There are two types of validation artefacts required for XML
        Documents:</para>
      <orderedlist>
        <listitem>
          <para>W3C Schemas are used to define and validate <emphasis
              role="italic">the structure</emphasis> of elements and data
            content, and</para>
        </listitem>
        <listitem>
          <para>OASIS CVA expressions and OASIS genericode files are used to
            define and validate <emphasis role="italic">the values</emphasis>
            of data content. </para>
        </listitem>
      </orderedlist>
      <para>These rules do not require these artefacts to be located in any
        particular directory structure. </para>
    </section>
    <section id="S-NAMESPACES">
      <title>Namespaces</title>
      <para>An important aspect of identifying and distinguishing the names
        used for information in XML documents is by using namespaces.
        Like-named constructs are distinguished by having different namespaces. </para>
      <note>
        <para>Namespace abbreviations (also used here as namespace prefixes) in
          these examples are not mandatory and have been selected solely for
          convenience and consistency. Implementations of these NDR and the
          documents governed by these NDR are welcome to use any namespace
          abbreviation or namespace prefix for any of the namespaces defined or
          referenced.</para>
      </note>
      <blockquote id="NAM01" role="rule">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>NAM01 Namespaces for information found in information
                bundles</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>BIEs expressed in XML documents shall use the following
                  set of namespaces:</para>
                <itemizedlist>
                  <listitem>
                    <para>one namespace for each Document ABIE</para>
                    <note>
                      <para>These namespaces are not abbreviated in these
                        examples as they are not imported or included.</para>
                    </note>
                  </listitem>
                  <listitem>
                    <para>one namespace for all BBIE components</para>
                    <note>
                      <para>This namespace is abbreviated in these examples as
                        "cbc" for "common basic components".</para>
                    </note>
                  </listitem>
                  <listitem>
                    <para>one namespace for all Library ABIE components</para>
                    <note>
                      <para>This namespace is abbreviated in these examples as
                        "cac" for "common aggregate components".</para>
                    </note>
                  </listitem>
                  <listitem>
                    <para>one namespace for the extension collection and
                      extension metadata elements</para>
                    <note>
                      <para>This namespace is abbreviated in these examples as
                        "ext".</para>
                    </note>
                  </listitem>
                </itemizedlist>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <para>Each extension has a number of namespaces distinct from the
        document, library and other extensions.</para>
      <blockquote id="NAM02" role="rule">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>NAM02 Namespaces for an extension</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>BIEs expressed in extensions shall use the following set
                  of namespaces:</para>
                <itemizedlist>
                  <listitem>
                    <para>one namespace for the apex ABIE of the
                      extension</para>
                    <note>
                      <para>This namespace is abbreviated in these examples as
                        "myext1".</para>
                    </note>
                  </listitem>
                  <listitem>
                    <para>one namespace for all BBIE extension components that
                      are not existing library components</para>
                    <note>
                      <para>This namespace is abbreviated in these examples as
                        "mycbc1".</para>
                    </note>
                  </listitem>
                  <listitem>
                    <para>one namespace for all ABIE extension components that
                      are not existing Library ABIE components</para>
                    <note>
                      <para>This namespace is abbreviated in these examples as
                        "mycac1".</para>
                    </note>
                  </listitem>
                </itemizedlist>
                <note>
                  <para>The structure of an extension parallels that of a
                    Document ABIE with the distinct apex namespace, BBIE
                    namespace and Library ABIE namespace. Where possible the
                    extension should reuse existing library components that
                    have their own namespaces. This parallel approach makes it
                    easier to consider incorporating extension elements in
                    future versions of the library simply by changing the
                    namespace.</para>
                </note>
                <note>
                  <para>In these abbreviations "my" is used as in the
                    first-person possessive pronoun, and "1" implies one of
                    multiple extension namespaces</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <para>In addition to the namespaces for the elements in XML documents,
        the dictionary information regarding BBIE data types is also
        distinguished using namespaces. </para>
      <blockquote id="NAM03" role="rule">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>NAM03 Namespaces for BBIE data types</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>The expression of data type information supporting BBIE
                  definitions shall use the following set of namespaces:</para>
                <itemizedlist>
                  <listitem>
                    <para>one namespace for all qualified data types</para>
                    <note>
                      <para>This namespace is abbreviated in these examples as
                        "qdt".</para>
                    </note>
                  </listitem>
                  <listitem>
                    <para>one namespace for all unqualified data types</para>
                    <note>
                      <para>This namespace is abbreviated in these examples as
                        "udt".</para>
                    </note>
                  </listitem>
                  <listitem>
                    <para>one namespace for CCTS Core Component Type
                      definitions</para>
                    <note>
                      <para>This namespace is abbreviated in these examples as
                        "ccts-cct".</para>
                    </note>
                  </listitem>
                </itemizedlist>
                <note>
                  <para>These namespaces are used only for dictionary
                    information definition and not for BIEs themselves. As such
                    they never appear in the XML document and are therefore
                    never declared in an XML artefact governed by these
                    NDR.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <para>Schema annotations describing the dictionary information require
        the use of their own namespace.</para>
      <blockquote id="NAM04" role="rule">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>NAM04 Namespace for schema annotations</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>A namespace for CCTS documentation found in schema
                  annotations shall be defined as distinct from all other
                  namespaces.</para>
                <note>
                  <para>This namespace is abbreviated in these examples as
                    "ccts".</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <para>An implementation of these NDR may choose to have additional
        namespaces for the expression of type information.</para>
    </section>
    <section id="S-XSD-IMPORT-INCLUDE-TREE">
      <title>XSD import/include tree</title>
      <para>The relationships between the XSD schema fragments that are
        described in this section are shown in <xref
          linkend="F-POSSIBLE-IMPORT-INCLUDE-HIERARCHY-OF-XSD-SCHEMA-EXPRESSIONS"
        />.</para>
      <para>For reference purposes each box is a schema fragment and the
        parenthesized name tokens identify the namespace associated with the
        schema fragment. </para>
      <figure
        id="F-POSSIBLE-IMPORT-INCLUDE-HIERARCHY-OF-XSD-SCHEMA-EXPRESSIONS">
        <title>Possible import/include hierarchy of XSD schema
          expressions</title>
        <mediaobject>
          <imageobject>
            <imagedata fileref="art/&dir;-v&version;-allschema.png"
              contentwidth="750px"/>
          </imageobject>
          <textobject>
            <phrase>XSD Schema Structure</phrase>
          </textobject>
        </mediaobject>
      </figure>
      <para>In this diagram the unshaded boxes represent fragments of the
        common schema. Once created there is no need for implementers of the
        schema to modify these fragments. To ensure they are not inadvertently
        modified, these may be marked as read-only files in the file system. </para>
      <para>The shaded boxes represent fragments that extend the common schema.
        The Extension Content Data Type defines which schemas are in play for
        the extension point of an extension item in the extension collection.
        This fragment is distinguished from other fragments in that it is
        initially created by the designers of the schema and subsequently may
        be replaced by implementers. </para>
    </section>
    <section id="S-SCHEMA-FRAGMENT-ANNOTATIONS">
      <title>Schema fragment annotations</title>
      <para>There are no constraints regarding what annotation information may
        be added to the W3C Schema expressions in XSD files. </para>
      <para>Provision is made in these NDR for annotating the schema fragments
        with dictionary information and governance information using W3C Schema
        declaration annotations and XML comments. This information may be
        useful to the human reader or to tools exploiting the schema
        information in providing functionality to operators, but it does not
        impact on the interpretation of constraints imposed on XML documents
        being validated with the XSD documents. </para>
      <para>W3C Schema annotations are typically defined for and with each of
        the many declarations in the XSD file. Good practice suggests providing
        a version of the published XSD files without annotations so as not to
        burden runtime processing. A runtime schema processor has no use of
        informational annotations and may incur unnecessary processing time
        ingesting and accommodating the information. </para>
      <para>Separate from the concept of W3C Schema annotations are simple XML
        comments that annotate schema. Such comments are ignored by schema
        processors and do not burden their processing. The information in these
        comments may be useful to implementers and, in some cases, may be
        required for intellectual property reasons imposed by the designers.
        Good practice suggests that such information includes module
        identification, module revision metadata and copyright declarations.
        The information in these comments may be useful to implementers and may
        by required by licensing conditions on the use of the files.</para>
      <para>The W3C Schema version annotation (the "version" attribute of the
        xsd:schema element) may be used to record the release version of the
        collection of schema fragments. </para>
    </section>
    <section id="S-SCHEMA-FRAGMENTS-AND-DECLARATIONS">
      <title>Schema fragments and declarations</title>
      <section id="S-SCHEMA-FRAGMENTS-FOR-DOCUMENT-ABIES">
        <title>Schema fragments for Document ABIEs</title>
        <blockquote role="rule" id="FRG01">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>FRG01 Document ABIE schema fragments</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>There shall be one schema fragment created for each
                    Document ABIE.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="FRG02">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>FRG02 Document ABIE element declaration</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each Document ABIE schema fragment shall include a
                    single element declaration, that being for the Document
                    ABIE.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="FRG03">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>FRG03 Document ABIE type declaration</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each Document ABIE schema fragment shall include a
                    single type declaration, that being for the content of the
                    Document ABIE.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-SCHEMA-FRAGMENT-FOR-LIBRARY-ABIES">
        <title>Schema fragment for Library ABIEs</title>
        <blockquote role="rule" id="FRG04">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>FRG04 Library ABIE schema fragment</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                  <note>
                    <title>Example</title>
                    <para>In UBL 2.1 the
                        <literal>UBL-CommonAggregateComponents-2.1.xsd</literal>
                      fragment serves this purpose.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="FRG05" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>FRG05 Library ABIE element declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="FRG06" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>FRG06 Library ABIE type declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The common Library ABIE schema fragment shall include a
                    type declaration for every Library ABIE, each being for the
                    content of each Library ABIE.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <para>There are no constraints on the order of the ABIE declarations in
          the schema expression.</para>
        <note>
          <para>This lack of an order constraint may seem in conflict with the
            semantic model library constraint of alphabetical order of ABIE
            components. Whereas the semantic ABIE components are organized for
            the benefit of the human reader, the order of the schema component
            declarations does not affect the schema processor. However, using
            alphabetical order in the schema fragment may be a convenience for
            the human reader of the schema expressions.</para>
        </note>
      </section>
      <section id="S-SCHEMA-FRAGMENT-FOR-BBIES">
        <title>Schema fragment for BBIEs</title>
        <blockquote role="rule" id="FRG07">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>FRG07 BBIE schema fragment</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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).</para>
                  <note>
                    <title>Example</title>
                    <para>In UBL 2.1 the
                        <literal>UBL-CommonBasicComponents-2.1.xsd</literal>
                      fragment serves this purpose.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="FRG08">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>FRG08 BBIE element declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="FRG09">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>FRG09 Library ABIE type declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <para>There are no constraints on the order of the BBIE declarations in
          the schema expression.</para>
        <note>
          <para>The order of the schema component declarations does not affect
            the schema processor. However, using alphabetical order in the
            schema fragment may be a convenience for the human reader of the
            schema expressions.</para>
        </note>
      </section>
      <section id="S-SCHEMA-DECLARATIONS-FOR-ALL-BIES">
        <title>Schema declarations for all BIEs</title>
        <blockquote role="rule" id="DCL01">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL01 Element declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Every BIE element declaration shall be global.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="DCL02">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL02 Element declaration references</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Every BIE element in an ABIE type definition shall be
                    declared by reference.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="DCL03">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL03 Type declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Every BIE type declaration shall be global.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-SCHEMA-DECLARATIONS-FOR-ABIES">
        <title>Schema declarations for ABIEs</title>
        <blockquote role="rule" id="DCL04">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL04 ABIE element declaration</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Every ABIE element shall be declared with the ABIE name
                    as the element name and the ABIE name suffixed with "Type"
                    as the type.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:element name="ApplicationResponse"
             type="ApplicationResponseType"/></programlisting>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="DCL05">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL05 ABIE type declaration</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Every ABIE complex type name shall be declared with the
                    name of the ABIE suffixed with "Type" as the name.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:complexType name="ApplicationResponseType">
 <emphasis>(... contents ...}</emphasis>
&lt;/xsd:complexType></programlisting>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="DCL06" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL06 Library ABIE type declaration content order</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:complexType name="CatalogueRequestLineType">
 &lt;xsd:sequence>
  &lt;xsd:element ref="cbc:ID" minOccurs="1" maxOccurs="1"/>
  &lt;xsd:element ref="cbc:ContractSubdivision"
               minOccurs="0" maxOccurs="1"/>
  &lt;xsd:element ref="cbc:Note" minOccurs="0"
               maxOccurs="unbounded"/>
  &lt;xsd:element ref="cac:LineValidityPeriod"
               minOccurs="0" maxOccurs="1"/>
  &lt;xsd:element ref="cac:RequiredItemLocationQuantity"
               minOccurs="0" maxOccurs="unbounded"/>
  &lt;xsd:element ref="cac:Item" minOccurs="1" maxOccurs="1"/>
  &lt;/xsd:sequence>
&lt;/xsd:complexType></programlisting>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="DCL07" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL07 Document ABIE type declaration content order</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:complexType name="ApplicationResponseType">
  &lt;xsd:sequence>
     &lt;xsd:element ref="ext:UBLExtensions"
                     minOccurs="0" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:UBLVersionID"
                      minOccurs="0" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:CustomizationID"
                      minOccurs="0" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:ProfileID"
                      minOccurs="0" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:ProfileExecutionID"
                      minOccurs="0" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:ID" 
                     minOccurs="1" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:UUID" 
                     minOccurs="0" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:IssueDate" 
                     minOccurs="1" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:IssueTime" 
                     minOccurs="0" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:ResponseDate" 
                     minOccurs="0" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:ResponseTime" 
                     minOccurs="0" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:Note" 
                     minOccurs="0" maxOccurs="unbounded"/>
     &lt;xsd:element ref="cbc:VersionID" 
                     minOccurs="0" maxOccurs="1"/>
     &lt;xsd:element ref="cac:Signature" 
                     minOccurs="0" maxOccurs="unbounded"/>
     &lt;xsd:element ref="cac:SenderParty"
                      minOccurs="1" maxOccurs="1"/>
     &lt;xsd:element ref="cac:ReceiverParty" 
                     minOccurs="1" maxOccurs="1"/>
     &lt;xsd:element ref="cac:DocumentResponse" 
                     minOccurs="0" maxOccurs="unbounded"/>
  &lt;/xsd:sequence>
&lt;/xsd:complexType></programlisting>
                  </note>
                  <note>
                    <para>The rationale for positioning extension information
                      at the very start of the XML instance is to allow
                      processing applications acting sequentially on the
                      document to consume and cache all non-modeled extension
                      information in preparation for consuming any of the
                      modeled document information. Should extension
                      information follow modeled information, the sequential
                      processing of the modeled information would have passed
                      before recognizing the need to associate extension
                      information. In essence, such a sequential processing
                      application would have to cache the entire document, thus
                      losing the benefit of sequential processing.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="DCL08">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL08 Document ABIE extension element cardinality</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>In the content type for every Document ABIE the
                    extension collection element cardinality shall be declared
                    as optional and not repeatable.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>     &lt;xsd:element ref="ext:UBLExtensions"
                     minOccurs="0" maxOccurs="1"/></programlisting>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-SCHEMA-DECLARATIONS-FOR-ASBIES">
        <title>Schema declarations for ASBIEs</title>
        <blockquote role="rule" id="DCL09">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL09 ASBIE schema element declaration</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:element name="Party" type="PartyType"/></programlisting>
                  </note>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:element name="AgentParty" type="PartyType"/></programlisting>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-SCHEMA-DECLARATIONS-FOR-BBIES">
        <title>Schema declarations for BBIEs</title>
        <blockquote id="DCL10" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL10 BBIE element declaration</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:element name="SourceCurrencyCode" 
             type="SourceCurrencyCodeType"/></programlisting>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="DCL11" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL11 BBIE type declaration</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:complexType name="SourceCurrencyCodeType">
   &lt;xsd:simpleContent>
      &lt;xsd:extension base="udt:CodeType"/>
   &lt;/xsd:simpleContent>
&lt;/xsd:complexType></programlisting>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
    </section>
    <section id="S-EXTENSION-SCHEMA-FRAGMENTS-AND-DECLARATIONS">
      <title>Extension schema fragments and declarations</title>
      <section id="S-EXTENSION-INFORMATION">
        <title>Extension information</title>
        <para>The content type for a Document ABIE contains a single optional
          extension collection element in order to provide for the inclusion of
          data in the XML that is in addition to the data of the information
          bundle for the document. Such data may include content designed by
          other organizations (e.g. signature information) as well as
          augmentations of the semantic model. </para>
        <para>An extension collection element contains one or more extension
          elements. Each extension element has a suite of metadata elements
          used to describe the extension. The extension content may reuse
          existing ABIEs or BBIEs and may contain XML content not modeled as
          BIEs.</para>
        <para>The extension collection and metadata are XML elements
          implemented as schema fragments and constructs independent of the
          semantic model.</para>
        <!--<blockquote role="rule"><informaltable frame="all" border="1" width="100%"><thead><tr><td>EXT01 Document ABIE reference to extension collection element</td></tr></thead><tbody><tr><td>The first element referenced in every Document ABIE shall be to the extension collection element, followed by the declarations for the BIEs modeled for the Document ABIE.<note><title>Example</title><programlisting>&lt;xsd:complexType name="ApplicationResponseType">
  &lt;xsd:sequence>
     &lt;xsd:element ref="ext:UBLExtensions"
                     minOccurs="0" maxOccurs="1"/>
     {... content ...}
  &lt;/xsd:sequence>
&lt;/xsd:complexType></programlisting></note><note><para>The rationale for positioning extension information at the very start of the XML instance is to allow processing applications acting sequentially on the document to consume and cache all non-modeled extension information in preparation for consuming any of the modeled document information. Should extension information follow modeled information, the sequential processing of the modeled information would have passed before recognizing the need to associate extension information. In essence, such a sequential processing application would have to cache the entire document, thus losing the benefit of sequential processing.</para></note></td></tr></tbody></informaltable></blockquote>-->
      </section>
      <section id="S-EXTENSION-COLLECTION-SCHEMA-FRAGMENTS-AND-DECLARATIONS">
        <title>Extension collection schema fragments and declarations</title>
        <blockquote role="rule" id="EXT01">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT01 Extension collection schema fragment</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                  <note>
                    <title>Example</title>
                    <para>In UBL 2.1 the
                        <literal>UBL-CommonExtensionComponents-2.1.xsd</literal>
                      fragment serves this purpose.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="EXT02">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT02 Extension content element declaration</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                  <note>
                    <para>The rationale for not including the type information
                      for the extension point element is that the type is
                      subject to change, while the extension collection, the
                      extension item and extension item metadata element and
                      type information is not. This separation allows the
                      extension collection and item schema fragment to be
                      deployed as read-only, while the extension point data
                      type schema fragment can be deployed as writable in order
                      to be defined by users.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="EXT03">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT03 Extension collection element content</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The document's extension collection shall have one or
                    more extension elements as its content.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:complexType name="UBLExtensionsType">
  &lt;xsd:sequence>
    &lt;xsd:element ref="UBLExtension"
          minOccurs="1" maxOccurs="unbounded"/>
  &lt;/xsd:sequence>
&lt;/xsd:complexType></programlisting>
                  </note>
                  <note>
                    <para>The rationale is that different users of a document
                      may have different extension items added to the content.
                      Also, different extensions may be thematically
                      distinguished (e.g. the digital signature extension is
                      semantically separate from an extension augmenting
                      invoice line content).</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="EXT04" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT04 Extension element content ordering</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:complexType name="UBLExtensionType">
  &lt;xsd:sequence>
    &lt;xsd:element ref="cbc:ID"
                 minOccurs="0" maxOccurs="1"/>
    &lt;xsd:element ref="cbc:Name" 
                 minOccurs="0" maxOccurs="1"/>
    &lt;xsd:element ref="ExtensionAgencyID"
                 minOccurs="0" maxOccurs="1"/>
    &lt;xsd:element ref="ExtensionAgencyName" 
                 minOccurs="0" maxOccurs="1"/>
    &lt;xsd:element ref="ExtensionVersionID" 
                 minOccurs="0" maxOccurs="1"/>
    &lt;xsd:element ref="ExtensionAgencyURI" 
                 minOccurs="0" maxOccurs="1"/>
    &lt;xsd:element ref="ExtensionURI" 
                 minOccurs="0" maxOccurs="1"/>
    &lt;xsd:element ref="ExtensionReasonCode" 
                 minOccurs="0" maxOccurs="1"/>
    &lt;xsd:element ref="ExtensionReason" 
                 minOccurs="0" maxOccurs="1"/>
    &lt;xsd:element ref="ExtensionContent" 
                 minOccurs="1" maxOccurs="1"/>
  &lt;/xsd:sequence>
&lt;/xsd:complexType></programlisting>
                  </note>
                  <note>
                    <para>There are no constraints on the selection, name,
                      definition or cardinality of the extension metadata
                      elements.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section
        id="S-SCHEMA-FRAGMENT-FOR-THE-EXTENSION-CONTENT-DATA-TYPE-DECLARATION">
        <title>Schema fragment for the extension content data type
          declaration</title>
        <blockquote role="rule" id="EXT05">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT05 Extension content data type schema fragment</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                  <note>
                    <title>Example</title>
                    <para>In UBL 2.1 the
                        <literal>UBL-ExtensionContentDataType-2.1.xsd</literal>
                      fragment serves this purpose.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="EXT06" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT06 Extension content data type declaration</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>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.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>  &lt;xsd:complexType name="ExtensionContentType">
    &lt;xsd:sequence>
      &lt;xsd:any namespace="##other" processContents="lax"
               minOccurs="1" maxOccurs="1"/>
    &lt;/xsd:sequence>
  &lt;/xsd:complexType></programlisting>
                  </note>
                  <note>
                    <para>The rationale for the lax validation is to allow for
                      the extension point to contain, without error, any
                      element for which there are no constraints in any schema
                      fragment imported or included in the validation
                      step.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="EXT07">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT07 Extension content data type imports</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The extension content element type schema fragment may
                    contain import directives for the expected data content of
                    an extension.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:import namespace="urn:oasis:names:specification:
ubl:schema:xsd:CommonSignatureComponents-2"
  schemaLocation="UBL-CommonSignatureComponents-2.1.xsd"/></programlisting>
                  </note>
                  <note>
                    <para>The rationale for including import directives is to
                      validate those constructs found in an extension that are
                      expected.</para>
                  </note>
                  <note>
                    <para>There is no order to the import directives.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
    </section>
    <section id="S-QUALIFIED-DATA-TYPES-SCHEMA-FRAGMENT-AND-DECLARATIONS">
      <title>Qualified data types schema fragment and declarations</title>
      <blockquote role="rule" id="QDT01">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>QDT01 Qualified data types schema fragment</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>The qualified data types schema fragment shall include
                  the declarations of any qualified data types referenced in
                  the schema fragment for BBIEs. </para>
                <note>
                  <title>Example</title>
                  <para>In UBL 2.1 the
                      <literal>UBL-QualifiedDataTypes-2.1.xsd</literal>
                    fragment serves this purpose.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="QDT02">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>QDT02 Qualified data type declaration name</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>Every qualified data type shall be declared using the
                  name of the data type qualifier followed by the unqualified
                  data type name.</para>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="QDT03">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>QDT03 Qualified data type declaration basis</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>Every qualified data type shall be based on an
                  unqualified data type, imposing whatever qualifications are
                  required to be expressed using XSD schema semantics. </para>
                <note>
                  <para>In UBL 2.1 there are no qualifications expressed using
                    XSD schema semantics.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="QDT04">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>QDT04 Qualified data type declaration constraint</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>Every qualified data type declaration shall be such that
                  every possible instance of the declared type is also an
                  instance of the base type.</para>
                <note>
                  <para>This constraint prevents additions of anything that is
                    not part of the base type, such as the introduction of any
                    new attributes or sub-elements, or any less-constrained
                    element or attribute values.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
    </section>
    <section id="S-UNQUALIFIED-DATA-TYPES-SCHEMA-FRAGMENT-AND-DECLARATIONS">
      <title>Unqualified data types schema fragment and declarations</title>
      <blockquote role="rule" id="UDT01">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>UDT01 Unqualified data types schema fragment</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>The unqualified data types schema fragment shall include
                  the declarations of all unqualified data types referenced in
                  the schema fragment for BBIEs. </para>
                <note>
                  <title>Example</title>
                  <para>In UBL 2.1 the
                      <literal>UBL-UnqualifiedDataTypes-2.1.xsd</literal>
                    fragment serves this purpose.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote id="UDT02" role="rule">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>UDT02 Unqualified data types declaration inclusions</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>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 <xref
                    linkend="ccts"/>.</para>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="UDT03">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>UDT03 Unqualified data types declaration exclusions</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>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 <xref
                    linkend="ccts"/>.</para>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote id="UDT04" role="rule">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>UDT04 Unqualified data types declaration base</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>Every unqualified data type shall be based on one of the
                  approved Core Component Types defined in the Core Component
                  Technical Specification <xref linkend="ccts"/>.</para>
                <note>
                  <para>This constraint may be accomplished by either
                    restricting a declaration imported from the Core Component
                    Types schema or by wholly replacing the corresponding Core
                    Component Types schema declaration.</para>
                </note>
                <note>
                  <para>The rational for having UDT declarations is to impose
                    some XSD syntax semantics on top of the more general
                    decimal and string lexical syntax defined in the CCTS
                    specification of Core Component Types. For example, the
                    CCTS Core Component Type for date and time is a simple
                    string without constraint. Such lax structuring of the
                    field value does not serve users in that no particular
                    format is obligated. The UDT can impose, for example, the
                    xsd:dateTime lexical syntax on all date and time values,
                    overriding the CCTS definition.</para>
                </note>
                <note>
                  <para>This rule does allow an optional supplementary
                    component defined in the CCTS Core Component Type not to be
                    available in the associated unqualified data type. For
                    example, if the UDT implements a built-in XSD data type for
                    the component then there is no use of a format
                    supplementary component and associated attribute and so the
                    format attribute declaration can be omitted and, thereby,
                    be unavailable for use for that data type.</para>
                </note>
                <note>
                  <title>Example 1</title>
                  <para>In this example the unqualified data type uses the base
                    type without change:</para>
                  <programlisting>  &lt;xsd:complexType name="NumericType">
    &lt;xsd:simpleContent>
      &lt;xsd:extension base="ccts-cct:NumericType"/>
    &lt;/xsd:simpleContent>
  &lt;/xsd:complexType></programlisting>
                </note>
                <note>
                  <title>Example 2</title>
                  <para>In this example the unqualified data type redeclares
                    the base type's optional attribute as mandatory:</para>
                  <programlisting>  &lt;xsd:complexType name="MeasureType">
    &lt;xsd:simpleContent>
      &lt;xsd:restriction base="ccts-cct:MeasureType">
        &lt;xsd:attribute name="unitCode" 
                       type="xsd:normalizedString"
                       use="required"/>
      &lt;/xsd:restriction>
    &lt;/xsd:simpleContent>
  &lt;/xsd:complexType></programlisting>
                </note>
                <note>
                  <title>Example 3</title>
                  <para>In this example the unqualified data type replaces the
                    base type with no attributes and with an XSD built-in type
                    for content:</para>
                  <programlisting>  &lt;xsd:complexType name="DateTimeType">
    &lt;xsd:simpleContent>
      &lt;xsd:extension base="xsd:dateTime"/>
    &lt;/xsd:simpleContent>
  &lt;/xsd:complexType></programlisting>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="UDT05">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>UDT05 Unqualified data types declaration constraint</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>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.</para>
                <note>
                  <para>This constraint prevents additions of anything that is
                    not part of the base type, such as the introduction of any
                    new attributes or sub-elements, or any less-constrained
                    element or attribute values.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
    </section>
    <section id="S-CCTS-CORE-COMPONENT-TYPES-SCHEMA">
      <title>CCTS Core Component Types schema</title>
      <para>All primitive data types correspond to the 10 CCTS Primary
        Representation Terms defined in <xref linkend="ccts"/> Section 8-3
        "Permissible Representation Terms".</para>
      <blockquote id="CCT01" role="rule">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>CCT01 CCTS Core Component Type schema</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>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:</para>
                <programlisting>CCTS Core Component Type Schema Module

Module of Core Component Type
Agency: UN/CEFACT
VersionID: 1.1
Last change: 14 January 2005</programlisting>
                <note>
                  <title>Example</title>
                  <para>In UBL 2.1 the
                      <literal>CCTS_CCT_SchemaModule-2.1.xsd</literal> fragment
                    serves this purpose.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
    </section>
    <section id="S-XML-ATTRIBUTE-NAMES">
      <title>XML attribute names</title>
      <blockquote role="rule" id="ATT01">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>ATT01 Leading name part in attribute names</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>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.</para>
                <note>
                  <title>Example</title>
                  <para>The data type of the BBIE known as "Binary Object.
                    Uniform Resource. Identifier" is represented with the
                    attribute named "uri"</para>
                </note>
                <note>
                  <para>Terms used in attribute names of supplementary
                    components of CCTS Table 8-2 "Approved Core Component Type
                    Content and Supplementary Components" are subject to
                    abbreviation.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="ATT02">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>ATT02 Non-leading abbreviations in attribute names</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>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.</para>
                <note>
                  <title>Examples</title>
                  <simplelist>
                    <member>The data type of the BBIE known as "Amount
                      Currency. Identifier" is represented with the attribute
                      named "currencyID"</member>
                    <member>The data type of the BBIE known as "Amount
                      Currency. Code List Version. Identifier" is represented
                      with the attribute named
                      "currencyCodeListVersionID"</member>
                  </simplelist>
                </note>
                <note>
                  <para>Terms used in attribute names of supplementary
                    components of CCTS Table 8-2 "Approved Core Component Type
                    Content and Supplementary Components" are subject to
                    abbreviation.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
    </section>
    <section id="S-DATA-TYPE-QUALIFICATIONS">
      <title>Data type qualifications</title>
      <para>&#xfeff;Data types may be qualified to define additional
        constraints on the possible values of the BBIEs of that data type.
        These constraints may be subject to change over time and so should be
        applied in a manner that allows modification of the data type
        qualifications without impacting the schema. </para>
      <para>Code lists and identifier lists are examples of controlled sets of
        values (e.g. currency codes, country codes, product identifiers,
        etc.).</para>
      <para>For some communities of users (e.g. those with business-oriented
        XML documents) the management of controlled vocabularies presents
        particular challenges for document modeling. While communities may
        standardize document structures, trading partners within the community
        have their own constraints that may change on an hourly basis yet must
        work within the community framework. </para>
      <para>Externalizing the list in a genericode file expresses the
        enumeration as a resource available to the application for data entry.
        However, the choice of genericode file may vary on a per-information
        item basis due to the item's document context, or perhaps vary again
        for particular trading partners. Expressing the appropriate mappings in
        a colloquial fashion inhibits interoperability and the sharing of
        resources and program code. </para>
      <para>A context/value association file specifies the relationship from
        information items found in different document contexts to one or more
        external genericode files for each item. With these relationships a
        directed authoring environment can precisely direct the editing of
        individual information items. Different context/value association files
        can then be used to create instances for different purposes that have
        different constraints on the enumerations used therein.</para>
      <blockquote role="rule" id="DTQ01">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>DTQ01 Data type qualification CVA file</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>Data type qualifications that are not expressed as
                  qualified data types using XSD schema semantics may be
                  expressed using the OASIS Context Value Association <xref
                    linkend="oasiscva"/> XML vocabulary. </para>
                <note>
                  <para>The CVA file provides for users to associate value
                    validation constraint expressions and/or coded domain value
                    enumerations with different CVA contexts. A value
                    validation constraint is expressed using XPath. A coded
                    domain value enumeration is expressed using one or the
                    union of more than one OASIS genericode file.</para>
                </note>
                <note>
                  <para>The CVA expressions typically are not used at runtime.
                    More likely the CVA expressions and their associated
                    genericode files would be processed or compiled into a
                    runtime validation artefact. These rules do not constrain
                    where this runtime artefact would be kept, but good
                    practice suggests a location separate from the XSD
                    schemas.</para>
                </note>
                <note>
                  <title>Example</title>
                  <para>In UBL 2.1 the CVA expression is the
                      <literal>cva/UBL-DefaultDTQ-2.1.cva</literal> file, the
                    associated runtime artefact is the
                      <literal>val/UBL-DefaultDTQ-2.1.xsl</literal> XSLT
                    stylesheet and the referenced genericode files are located
                    in the <literal>cl/</literal> subdirectory of each of the
                    UBL 2.1 distribution and the UBL 2.0 distribution.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote id="DTQ02" role="rule">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>DTQ02 Data type element content qualifications</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>A CVA context shall be created for every BBIE with a
                  non-empty value in the CCTS dictionary information for the
                  data type qualifier.</para>
                <note>
                  <title>Example</title>
                  <para>Entered dictionary information values:</para>
                  <simplelist>
                    <member>Name="ChannelCode"</member>
                    <member>Data Type Qualifier="Channel"</member>
                    <member>Representation Term="Code"</member>
                    <member>Data Type="Channel_ Code. Type"</member>
                  </simplelist>
                  <para>In this example the constraints on the value of the
                      <literal>cbc:ChannelCode</literal> element are described
                    by the union of two constraint expressions identified by
                      "<literal>Channel-2.0</literal>" and
                      "<literal>Channel-2.1</literal>":</para>
                  <programlisting>&lt;Context values="Channel-2.0 Channel-2.1"
         metadata="cctsV2.01-code"
         address="cbc:ChannelCode"/></programlisting>
                </note>
                <note>
                  <title>Example</title>
                  <para>In this example the constraints on the value of the
                      <literal>cbc:PayableAmount</literal> element child of the
                      <literal>cac:LegalMonetaryTotal</literal> element are
                    described by the single constraint expression identified by
                    "maxValue":</para>
                  <programlisting>&lt;Context values="maxValue"
         address="cac:LegalMonetaryTotal/
                  cbc:PayableAmount"/></programlisting>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote id="DTQ03" role="rule">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>DTQ03 Data type attribute content qualifications</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>A CVA context shall be created for every CCTS
                  supplementary component to be validated.</para>
                <note>
                  <title>Example</title>
                  <para>In this example the constraints on the value of the
                      <literal>currencyID</literal> attribute are described by
                    the union of two constraint expressions identified by
                      "<literal>Currency-2.0</literal>" and
                      "<literal>Currency-2.1</literal>":</para>
                  <programlisting>&lt;Context values="Currency-2.0 Currency-2.1"
         metadata="cctsV2.01-amount"
         address="@currencyID"/></programlisting>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="DTQ04">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>DTQ04 Value test constraints</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>A CVA value test constraint shall be written as an XPath
                  expression.</para>
                <note>
                  <title>Example</title>
                  <para>In this example the constraint on the value is that its
                    numeric value be less than 10,000:</para>
                  <programlisting>&lt;ValueTest xml:id="maxValue"
           test=". &amp;lt; 10000"/></programlisting>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="DTQ05">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>DTQ05 Value list constraints</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>A CVA value list constraint shall reference an OASIS
                  genericode <xref linkend="gc"/> file.</para>
                <note>
                  <title>Example</title>
                  <programlisting>&lt;ValueList xml:id="Channel-2.1"
  uri="../cl/gc/default/ChannelCode-2.1.gc"/></programlisting>
                </note>
                <note>
                  <para>Each genericode file defines the metadata associated
                    with the enumeration of values therein. Therefore, the
                    union of multiple genericode files is required when the
                    constraint includes values from different enumerations
                    associated with distinctive metadata.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <blockquote role="rule" id="DTQ06">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>DTQ06 Value metadata association</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>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.</para>
                <note>
                  <title>Example</title>
                  <para>In UBL 2.1 the
                      <literal>UBL-DefaultDTQ-2.1.cva</literal> fragment
                    includes such declarations.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
    </section>
  </section>
  <section id="S-CONFORMANCE">
    <title>Conformance</title>
    <para>An information bundle and its associated XML validation artefacts
      conforming to these naming and design rules does not violate any rule or
      requirement expressed in normative sections of this specification where
      the words <emphasis>shall</emphasis>, <emphasis>mandatory</emphasis> or
        <emphasis>required</emphasis> are used in the context for which the
      user is utilizing these rules. </para>
  </section>
  <appendix role="iso-informative" id="A-RELEASE-NOTES">
    <title>Release notes</title>
    <section id="S-AVAILABILITY">
      <title>Availability</title>
      <para>Online and downloadable versions of this release are available from
        the locations specified at the top of this document.</para>
    </section>
    <section id="S-STATUS-OF-THIS-RELEASE">
      <title>Status of this release</title>
      <!--
      <para>This is an internal working draft for editors.</para>
      -->
      <para> Release of this package marks the continuation of its internal
        committee review.</para>
      <!--      <para>Release of this package to the public marks the beginning of its
        first public review. The UBL Technical Committee actively solicits
        input from the user community regarding this release. See <xref
          linkend="STATUS"/> at the beginning of this document for procedures
        to be used in submitting comments to the Committee. Note that in
        accordance with OASIS policies regarding intellectual property, the UBL
        TC <emphasis role="italic">cannot</emphasis> accept input from persons
        outside the UBL TC (including OASIS members) unless it is submitted via
        the comment list.</para>-->
      <para><emphasis role="bold"><emphasis role="italic">THIS RELEASE IS
            SUBJECT TO CHANGE. IT IS PROVIDED FOR TESTING PURPOSES ONLY AND
            SHOULD NOT BE USED FOR PRODUCTION
        SYSTEMS.</emphasis></emphasis></para>
    </section>
    <section id="S-PACKAGE-STRUCTURE">
      <title>Package structure</title>
      <para>This &standard; is published as a zip archive in the <ulink
          url="&this-loc;/">&this-loc;/</ulink> directory. Unzipping this
        archive creates a directory tree containing a number of files and
        subdirectories. Note that while the two XML files comprise the
        revisable version of this specification, this revisable XML may not be
        directly viewable in all currently available web browsers.</para>
      <para>The base directory has the following files:</para>
      <blockquote>
        <variablelist>
          <varlistentry>
            <term><emphasis role="bold"><literal>&name;-&stage;.xml</literal>
              </emphasis></term>
            <listitem>
              <para>The revisable form of the document.</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term><emphasis role="bold"
                  ><literal>&name;-&stage;-summary.xml</literal>
              </emphasis></term>
            <listitem>
              <para>A distillation of the rules, comprising only the rule title
                and first paragraph. This XML document is incorporated in the
                revisable form of the document by way of an entity reference.
                During the publishing process this file is first distilled from
                the revisable form and then subsequently incorporated in the
                revisable form for publishing.</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term><emphasis role="bold"><literal>&name;-&stage;.html</literal>
              </emphasis></term>
            <listitem>
              <para>An HTML rendering of the document.</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term><emphasis role="bold"><literal>&name;-&stage;.pdf</literal>
              </emphasis></term>
            <listitem>
              <para>A PDF rendering of the document.</para>
            </listitem>
          </varlistentry>
        </variablelist>
      </blockquote>
      <para>These are the subdirectories in the package:</para>
      <blockquote>
        <variablelist>
          <varlistentry>
            <term><emphasis role="bold"><literal>art</literal>
              </emphasis></term>
            <listitem>
              <para>Diagrams and illustrations used in this
                specification</para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term><emphasis role="bold"><literal>db</literal>
              </emphasis></term>
            <listitem>
              <para>DocBook stylesheets for viewing in HTML the XML of this
                work product</para>
            </listitem>
          </varlistentry>
        </variablelist>
      </blockquote>
    </section>
  </appendix>
  <appendix id="A-ACKNOWLEDGEMENTS" role="iso-informative">
    <title>Acknowledgements</title>
    <para>The following individuals have participated in the creation of this
      specification and are gratefully acknowledged:</para>
    <simplelist>
      <member>Oriol Bausa Peris, Individual</member>
      <member>Kenneth Bengtsson, Alfa1lab</member>
      <member>Peter Borresen, Document Engineering Services Limited</member>
      <member>Jon Bosak, Individual</member>
      <member>Kees Duvekot, RFS Holland Holding B.V.</member>
      <member>Martin Forsberg, Swedish Association of Local Authorities &amp;
        Regions</member>
      <member>G. Ken Holman, Crane Softwrights Ltd.</member>
      <member>Ole Madsen, Danish Agency for Digitisation, Ministry of
        Finance</member>
      <member>Tim McGrath, Document Engineering Services Limited</member>
      <member>Andrew Schoka, Individual</member>
    </simplelist>
  </appendix>
  <appendix role="iso-informative" id="A-SUMMARY-OF-RULES">
    <title>Summary of rules</title>
    <para>As a convenience to the reader, the following is an alphabetical list
      of all rules expressed in this document. Only the normative content of
      each rule is copied here. Non-normative examples are not included here,
      and the reader is directed to the body of the text where this helpful
      text is found. The title of each rule here is linked to the location in
      the document where the rule is presented, and the section number of the
      specification is indicated in parentheses. Click on the rule title to
      jump to the rule. Click on the section number to jump to the section with
      the rule.</para>
    &summary;
  </appendix>
  <appendix id="A-ADDITIONAL-PRODUCTION-PROCESSES" role="iso-informative">
    <title>Additional production processes</title>
    <section id="S-CCTS-SERIALIZATION">
      <title>CCTS serialization</title>
      <para>An implementation of these naming and design rules may choose to
        create a serialization of the CCTS information. This can be a useful
        convenience when processing the CCTS information as a whole. The CCTS
        collaboration tool is not required to produce a serialization if such
        is not needed to fulfill its obligation to produce validation
        artefacts. </para>
      <para>There are no formal rules for CCTS serialization.</para>
    </section>
    <section id="S-REPORTING">
      <title>Reporting</title>
      <para>An implementation of these naming and design rules is not required
        to produce any supplementary reports. These reports can be useful
        reference materials for review of the CCTS information maintained for
        the information bundles. </para>
      <para>There are no formal rules for reporting. </para>
    </section>
  </appendix>
  <appendix role="iso-informative" id="A-REVISION-HISTORY">
    <title>Revision History</title>
    <informaltable frame="all">
      <tgroup cols="4">
        <colspec colwidth="2*"/>
        <colspec colwidth="4*"/>
        <colspec colwidth="2*"/>
        <colspec colwidth="8*"/>
        <thead>
          <row>
            <entry>Revision</entry>
            <entry>Date</entry>
            <entry>Editor</entry>
            <entry>Changes made</entry>
          </row>
        </thead>
        <tbody>
          <row>
            <entry>csd01wd01</entry>
            <entry>06 January 2015</entry>
            <entry>GKH</entry>
            <entry>Initial version</entry>
          </row>
          <row>
            <entry>csd01wd02</entry>
            <entry>20 January 2015</entry>
            <entry>GKH</entry>
            <entry>Added examples; repaired COM13; added equivalences concept
            </entry>
          </row>
          <row>
            <entry>csd01wd03</entry>
            <entry>23 January 2015</entry>
            <entry>GKH</entry>
            <entry>Repaired prose derived expressions and included formula
              examples </entry>
          </row>
          <row>
            <entry>csd01wd04</entry>
            <entry>2 February 2015</entry>
            <entry>GKH</entry>
            <entry>Copyfit code fragments; improve grammar</entry>
          </row>
          <row>
            <entry>csd01</entry>
            <entry>4 February 2015</entry>
            <entry>GKH</entry>
            <entry>Date, stage and status of release</entry>
          </row>
          <row>
            <entry>csd02wd01</entry>
            <entry>4 May 2015</entry>
            <entry>GKH</entry>
            <entry>Edits for proposed (but not yet agreed) disposition of
              comments for csprd01</entry>
          </row>
          <row>
            <entry>csd02wd02</entry>
            <entry>25 May 2015</entry>
            <entry>GKH</entry>
            <entry>Additional edits based on implementation feedback. Changed
              spreadsheet formulae to XPath</entry>
          </row>
          <row>
            <entry>csd02wd03</entry>
            <entry>08 September 2015</entry>
            <entry>GKH</entry>
            <entry>Split into NDR Standard and UBL TC Committee Note</entry>
          </row>
          <row>
            <entry>csd02wd04</entry>
            <entry>21 November 2015</entry>
            <entry>GKH</entry>
            <entry>Incorporating new content from Tim and Andy. No work done
              (yet) on cover page.</entry>
          </row>
          <row>
            <entry>csd02wd05</entry>
            <entry>28 November 2015</entry>
            <entry>GKH</entry>
            <entry>Polishing content and cover page with new title.</entry>
          </row>
          <row>
            <entry>csd02</entry>
            <entry>10 December 2015</entry>
            <entry>GKH</entry>
            <entry>New version number and new content from Tim. Package dated
              for voting at next meeting.</entry>
          </row>
          <row>
            <entry>csprd02</entry>
            <entry>10 December 2015</entry>
            <entry>GKH</entry>
            <entry>Package prepared for public review</entry>
          </row>
          <row>
            <entry>csd02</entry>
            <entry>12 December 2015</entry>
            <entry>GKH </entry>
            <entry>Rearranged informative sections to introduction to mimic ISO
              style; use latest OASIS stylesheets supporting ISO
              placards</entry>
          </row>
          <row>
            <entry>csprd02</entry>
            <entry>12 December 2015</entry>
            <entry>GKH</entry>
            <entry>Package prepared for public review</entry>
          </row>
          <row>
            <entry>csd02</entry>
            <entry>14 December 2015</entry>
            <entry>GKH </entry>
            <entry>Another title consideration for the public review.</entry>
          </row>
          <row>
            <entry>csprd02</entry>
            <entry>14 December 2015</entry>
            <entry>GKH</entry>
            <entry>Package prepared for public review</entry>
          </row>
        </tbody>
      </tgroup>
    </informaltable>
  </appendix>
</article>
