<?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"
         "http://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 stage                       "csprd01"><!--remember title ent-->
<!ENTITY summary SYSTEM "UBL-NDR-v3.0-csprd01-summary.xml">
<!ENTITY title "UBL Naming and Design Rules Version&#xa0;&version;">
<!ENTITY standard "Committee Specification Draft 01 / Public Review Draft 01">
<!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 pubdate "4 February 2015">
<!ENTITY pubdate "<emphasis role='date'>$Revision: 1.2 $$Date: 2015/02/27 18:35:18 $</emphasis>">
]>
<article status="&standard;">
  <articleinfo>
    <title>&title;</title>
    <releaseinfo role="cvs"> $Id: UBL-NDR-v3.0-csprd01.xml,v 1.2 2015/02/27 18:35:18 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>
    <!-- generic form of above
      <releaseinfo role="OASIS-specification-previous"
         >&previous-loc;/&name;-&stage;.html</releaseinfo>
      <releaseinfo role="OASIS-specification-previous"
         >&previous-loc;/&name;-&stage;.pdf</releaseinfo>
      <releaseinfo role="OASIS-specification-previous-authoritative"
         >&previous-loc;/&name;-&stage;.xml</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>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 XSD schemas and
        OASIS Context/value association files) associated with abstract
        information bundles formally described using the ISO/TS 15000-5:2005
        Core Component Technical Specification <xref linkend="isoccts"/>. These
        rules are not limited only for use with UBL.</para>
      <para>This work product also describes how, in particular, these rules
        were followed to create the information bundles and XML document model
        validation artefacts for UBL <xref linkend="UBL"/> documents and
        extensions starting with UBL version 2.1.</para>
      <para>These rules can be followed to create any or all of the
        following:</para>
      <para>
        <itemizedlist>
          <listitem>
            <para>custom extensions for use with UBL documents; and</para>
          </listitem>
          <listitem>
            <para>custom standalone documents based on the UBL common
              library.</para>
          </listitem>
        </itemizedlist>
      </para>
    </abstract>
    <legalnotice role="status" id="STATUS">
      <title>Status</title>
      <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 id="UBL-NDR"><abbrev>UBL-NDR-3.0</abbrev>
          <citetitle>&title;.</citetitle>
          <bibliomisc>Edited by 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>
    <para/>
    <para>The Open-edi Reference Model <xref linkend="iso14662"/> distinguishes
      an information bundle as the abstract description of the structure and
      semantics of the information exchanged between parties, separate from the
      user data syntax of the exchange of that information. </para>
    <para>The use of the user data syntax in that exchange can be constrained
      by validation artefacts derived from the information bundles. A
      validation process can then report violations of the syntax
      constraints.</para>
    <para>Naming and Design Rules (NDR) describe the process by which the user
      data syntax constraint mechanisms are created from the abstract
      definition of the information bundles. This is illustrated in <xref
        linkend="F-OPEN-EDI-APPLICATION"/>, reproduced from OASIS Standard UBL
      2.1 Figure H.2 with an annotation highlighting the relationship of the
      NDR applied to UBL. The original figure depicts the roles of the four
      normative sections of the UBL 2.1 specification. </para>
    <figure id="F-OPEN-EDI-APPLICATION">
      <title>Open-edi Application</title>
      <mediaobject>
        <imageobject>
          <imagedata fileref="art/UBL-2.1-NDR-Open-edi-Application.png"
            contentwidth="750px"/>
        </imageobject>
        <textobject>
          <phrase>[Open-edi Application]</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>This work product fulfills a commitment by the UBL Technical
      Committee to document the maintenance of the information bundles and the
      production of the XML document model validation artefacts for UBL 2.1
        <xref linkend="UBL"/> documents expressing user data. The UBL
      information bundles are described in the abstract using CCTS <xref
        linkend="isoccts"/>. The UBL XML user data document model validation
      artefacts are described using W3C XML Schema [<xref linkend="xsd"/>] and
      OASIS Context/value association <xref linkend="oasiscva"/> expressions. </para>
    <para>This work product has been written primarily as a normative
      prescriptive document, including a conformance section, for those
      designing new information bundles for new validation artefacts for any
      business vocabulary, not just UBL.</para>
    <para>Part of this work product is a non-normative descriptive document for
      reference regarding the application of these maintenance and production
      practices as applied by the UBL Technical Committee when creating UBL
      2.1.</para>
    <note>
      <para>Until these rules change, further releases of UBL will continue to
        be created according to these rules, but the non-normative sections of
        this document will not be revised to reflect any new release.</para>
    </note>
    <para>For readers working with UBL either for use with the UBL validation
      artefacts, or for standalone use these rules provide guidance when
      writing custom extensions for UBL document models and when writing custom
      documents using the UBL common library.</para>
    <para>To achieve these two prescriptive and descriptive goals, this work
      product expresses a set of naming and design rules used to create and use
      tools to express the information bundle of an exchange between parties,
      and then create XML document model validation artefacts (XSD schemas and
      context/value association files) from those tools.</para>
    <note>
      <para>The UBL 2.1 specification is backwards compatible with its
        predecessor UBL 2.0. Both specifications were completed before these
        Naming and Design Rules were formalized. There may very well be in
        those specifications some isolated violations of these rules. Changing
        the specifications to remove these violations is not possible because
        of the commitment to maintain backward compatibility with established
        implementations of the published specifications. Such rule violations
        do not impact on the integrity of the specifications, as these rules
        represent a best practice promoted by the UBL Technical Committee.
      </para>
    </note>
    <para>These rules presume the reader is already familiar with the following
      and this document makes no attempt to reiterate any or all definitions,
      principles, rules, syntax or constraints found in the following: </para>
    <itemizedlist>
      <listitem>
        <para>the principles of ISO/TS 15000-5:2005 Core Component Technical
          Specification <xref linkend="isoccts"/>;</para>
      </listitem>
      <listitem>
        <para>the principles of ISO/IEC 11179 Data Elements <xref
            linkend="iso11179"/>;</para>
      </listitem>
      <listitem>
        <para>the semantics and syntax of W3C XSD [<xref linkend="xsd"/>] for
          XML document constraint specification;</para>
      </listitem>
      <listitem>
        <para> the semantics and syntax of OASIS Context/value association
          using genericode <xref linkend="oasiscva"/> for code list
          association; and </para>
      </listitem>
      <listitem>
        <para> the semantics and syntax of OASIS genericode <xref linkend="gc"
          /> for code list representation. </para>
      </listitem>
    </itemizedlist>
    <para>Naming and design rules govern the application of the above works to
      the objective of creating concrete user data validation artefacts from
      abstract information bundles.</para>
    <note>
      <title>Documentation conventions</title>
      <para>The documentation convention followed in the major normative
        clauses of this specification details the normative prescriptive rules
        in the first subclause and describe the non-normative UBL 2.1
        application of those rules in the second subclause. Where possible,
        subsequent sub-subclauses under each subclause correspond the NDR rules
        with the UBL 2.1 application of those rules.</para>
    </note>
    <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 id="cva">
            <term>Context/value Association</term>
            <listitem>
              <para>The association of value constraints imposed on information
                found in a particular document context.</para>
            </listitem>
          </varlistentry>
          <varlistentry id="CCTS">
            <term>Core Component Technical Specification</term>
            <listitem>
              <para> A methodology for creating a business vocabulary that can
                be expressed in one or more syntactic expressions, as defined
                in <xref linkend="isoccts"/>. </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, as
                defined in <xref linkend="xml"/>.</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="cva"/> 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>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 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 <emphasis>Core Component (CC), Basic Core Component
            (BCC), Aggregate Core Component (ACC), Association Core Component
            (ASCC), Business Information Entity (BIE), Basic Business
            Information Entity (BBIE),</emphasis> and <emphasis>Aggregate
            Business Information Entity (ABIE)</emphasis> are used in this
          specification with the meanings given in <xref linkend="isoccts"
          />.</para>
        <para>The terms <emphasis>Object Class, Property Term, Representation
            Term,</emphasis> and <emphasis>Qualifier</emphasis> 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="isoccts"/></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>ASBIE</term>
            <listitem>
              <para>Association Business Information Entity <xref
                  linkend="isoccts"/></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>BIE</term>
            <listitem>
              <para>Business Information Entity <xref linkend="isoccts"
                /></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>BBIE</term>
            <listitem>
              <para>Basic Business Information Entity <xref linkend="isoccts"
                /></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>CCTS</term>
            <listitem>
              <para><xref linkend="CCTS"/></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>CVA</term>
            <listitem>
              <para><xref linkend="cva"/></para>
            </listitem>
          </varlistentry>
          <varlistentry>
            <term>NDR</term>
            <listitem>
              <para><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 id="S-KEY-CONCEPTS">
        <title>Key concepts</title>
        <variablelist>
          <varlistentry>
            <term> Extension collection</term>
            <listitem>
              <para>The set of extension items 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> XML document 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>
        </variablelist>
      </section>
    </section>
    <section id="S-NORMATIVE-REFERENCES">
      <title>Normative References</title>
      <bibliolist>
        <bibliomixed id="isoccts"><abbrev>CCTS - ISO/TS
              15000-5:2005</abbrev><citetitle><ulink
              url="https://www.oasis-open.org/committees/download.php/6232/CEFACT-CCTS-Version-2pt01.zip"
              >ISO/TS 15000-5:2005 Electronic Business Extensible Markup
              Language (ebXML)&#8212; Part 5: ebXML Core Components Technical
              Specification, Version 2.01</ulink> (identical to Part 8 of the
            ebXML Framework) </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="iso14662"><abbrev>ISO 14662</abbrev><citetitle>
            <ulink
              url="http://standards.iso.org/ittf/PubliclyAvailableStandards/"
              >ISO/IEC 14662:2004 Information technology &#8212; Open-edi
              reference model</ulink></citetitle></bibliomixed>
        <bibliomixed id="rfc2119"><abbrev>RFC 2119</abbrev>
          <title>Key words for use in RFCs to Indicate Requirement
            Levels</title>, <date>March 1997. </date>
          <author>
            <firstname>S. </firstname>
            <surname>Bradner</surname>
          </author>. <releaseinfo>IETF (Internet Engineering Task Force) RFC
            2119, </releaseinfo>
          <citetitle><ulink url="http://www.ietf.org/rfc/rfc2119.txt"
              >http://www.ietf.org/rfc/rfc2119.txt</ulink></citetitle>
        </bibliomixed>
        <bibliomixed id="xml"><abbrev>XML</abbrev><citetitle><ulink
              url="http://www.w3.org/TR/2008/REC-xml-20081126/">Extensible
              Markup Language (XML) 1.0 (Fifth Edition), W3C Recommendation 26
              November 2008</ulink></citetitle></bibliomixed>
        <bibliomixed id="xpath10"><abbrev>XPath 1.0</abbrev>James Clark, Steve
          DeRose, <citetitle><ulink
              url="http://www.w3.org/TR/1999/REC-xpath-19991116/">XML Path
              Language (XPath) Version 1.0, 16 November 1999</ulink>.
          </citetitle></bibliomixed>
        <bibliomixed id="xsd1"><abbrev>XSD1</abbrev><citetitle><ulink
              url="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML
              Schema Part 1: Structures. Second Edition. W3C Recommendation 28
              October 2004</ulink></citetitle></bibliomixed>
        <bibliomixed id="xsd2"><abbrev>XSD2</abbrev><citetitle><ulink
              url="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML
              Schema Part 2: Datatypes. Second Edition. W3C Recommendation 28
              October 2004</ulink></citetitle></bibliomixed>
      </bibliolist>
    </section>
    <section id="S-NON-NORMATIVE-REFERENCES">
      <title>Non-Normative References</title>
      <bibliolist>
        <bibliomixed id="iso11179"><abbrev>ISO 11179</abbrev><citetitle>
            <ulink
              url="http://www.oasis-open.org/committees/download.php/6233/c002349_ISO_IEC_11179-1_1999%28E%29.pdf"
              >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</ulink></citetitle></bibliomixed>
        <bibliomixed id="UBL"><abbrev>UBL-2.1</abbrev>
          <citetitle>Universal Business Language Version 2.1.</citetitle>
          <date>&pubdate;. </date>
          <releaseinfo>&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>&pubdate;. </date>
          <releaseinfo>&standard;. </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><citetitle>
            <ulink url="http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/"
              >XML-Signature Syntax and Processing. W3C Recommendation 12
              February 2002</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>Naming and design rules govern the production of user data validation
      artefacts from the structure of information bundles describing the
      content of exchanges between parties as described in the Open-edi
      Reference Model <xref linkend="iso14662"/>. </para>
    <para>This standard mandates that for a given suite of document types, all
      information bundles be organized and maintained in such a way as to
      create the user data validation artefacts for that information using a
      well-defined process. </para>
    <para>The information bundle is expressed in terms and concepts of the Core
      Component Technical Specification. The user data validation artefacts for
      a document model are twofold: the document structural constraints (e.g.
      nesting and cardinality) of elements and attributes in XML documents
        <xref linkend="xml"/>, and the data type qualifications (e.g. coded
      value domains, a.k.a. code lists). Document structural constraints are
      expressed using XSD schema semantics and syntax <xref linkend="xsd"/>.
      Data type qualifications are expressed using CVA associations <xref
        linkend="cva"/> of code list values <xref linkend="gc"/> with XML
      document locations using XPath <xref linkend="xpath10"/>.</para>
    <section id="S-GENERIC-PROCESS-OVERVIEW">
      <title>Generic process overview</title>
      <para>This specification presents this process of producing user data
        validation artefacts as having at least four steps, two of which are
        always present and at least two, among possible others, that are
        optional. </para>
      <para>There shall be a process by which CCTS information regarding the
        information bundles is managed. This may be in a collaboration tool of
        some kind so as to involve multiple participants. The tool itself may
        be as simple as a file being shared back and forth between participants
        (or maintained solely by an individual if there are no other
        participants), or as complex as an online interactive browser-based
        tool with credentialed access offering information bundle
        visualization.</para>
      <blockquote id="GEN01" role="rule">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>GEN01 Maintenance of information bundle composition</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>There shall be a documented process by which information
                  bundles are managed. Such a process shall support principles
                  of the <xref linkend="CCTS"/> as described in other rules in
                  this specification.</para>
                <note>
                  <para>While not mandatory, such a process should support
                    collaborative interaction among project members responsible
                    for the information being maintained.</para>
                </note>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <para>There shall be a process in which user data validation artefacts
        are produced. These artefacts reflect the information bundles as
        constraints on the user data syntax used to represent instances being
        exchanged. These may be produced directly from the collaboration tool
        or indirectly from intermediate files created from the collaboration
        tool.</para>
      <blockquote id="GEN02" role="rule">
        <informaltable frame="all" border="1" width="100%">
          <thead>
            <tr>
              <td>GEN02 Production of validation artefacts</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>
                <para>There shall be a documented process by which user data
                  validation artefacts are created from the information
                  maintained for information bundles.</para>
              </td>
            </tr>
          </tbody>
        </informaltable>
      </blockquote>
      <para>There may be any number of optional processes to produce additional
        artefacts may be useful, two of which are depicted in <xref
          linkend="F-GENERIC-NDR-PROCESS-TO-CREATE-VALIDATION-ARTEFACTS"/>: the
        serialization of the CCTS information into a form suitable for
        additional processing, and the production of reports useful in the
        collaboration and review of the work.</para>
      <figure id="F-GENERIC-NDR-PROCESS-TO-CREATE-VALIDATION-ARTEFACTS">
        <title>Generic NDR process to create validation artefacts</title>
        <mediaobject>
          <imageobject>
            <imagedata fileref="art/UBL-2.1-NDR-procgen.png"
              contentwidth="750px"/>
          </imageobject>
          <textobject>
            <phrase>[Generic Process Diagram]</phrase>
          </textobject>
        </mediaobject>
      </figure>
    </section>
    <section id="S-UBL-PROCESS-OVERVIEW" role="non-normative">
      <title>UBL process overview</title>
      <para>The processes to produce artefacts engaged by the UBL TC are
        depicted in <xref
          linkend="F-UBL-NDR-PROCESS-TO-CREATE-VALIDATION-ARTEFACTS"/>. </para>
      <para>Office spreadsheets are used to maintain CCTS information
        describing information bundles in a manner suitable for collaboration
        amongst members of the technical committee. This information is
        exported in an XML vocabulary using OASIS Open Document Format. This is
        then merged using XSLT to produce a single serialization of the CCTS
        information in XML using the OASIS genericode vocabulary. </para>
      <para>The genericode file is then used to produce both an HTML summary of
        all of the models and a model checking report detailing problems with
        the CCTS information. These reporting artefacts are used by the
        collaborators to polish the CCTS information. </para>
      <para>The genericode file is also used to create the validation
        artefacts.</para>
      <figure id="F-UBL-NDR-PROCESS-TO-CREATE-VALIDATION-ARTEFACTS">
        <title>UBL NDR process to create validation artefacts</title>
        <mediaobject>
          <imageobject>
            <imagedata fileref="art/UBL-2.1-NDR-procubl.png"
              contentwidth="750px"/>
          </imageobject>
          <textobject>
            <phrase>[UBL Process Diagram]</phrase>
          </textobject>
        </mediaobject>
      </figure>
    </section>
  </section>
  <section id="S-DOCUMENTS-LIBRARIES-COMPONENTS-AND-EXTENSIONS">
    <title>Documents, libraries, components and extensions</title>
    <para>These naming and design rules provide for creating a collection of
      extensible documents. Each document is an information bundle of business
      information entities sharing one or more common libraries of business
      information entities. Each business information entity is referred to as
      a component of the information bundle of the document or library. Each
      component corresponds to an XML element.</para>
    <para>A document extension provides for content that augments an
      information bundle with additional information not previously defined for
      the information bundle. Extensions, themselves, can contain components
      and can reference components. Extensions can also include foreign
      constructs defined by other organizations not using CCTS for structuring
      information. An extension can have horizontal applicability to all
      documents, such as the scaffolding to house a digital signature. An
      extension can have vertical applicability to only a single document, such
      as additional invoice line detail information to augment an invoice for a
      specific industry.</para>
    <para>Each exchange between partners is realized as a machine-readable
      instance of the information bundle and its use of any common libraries.
      When using XML for exchange, the XML document presents the information
      bundle as a serialization of components, each component being an XML
      element. Extensions in XML documents provide for including XML elements
      of components or of other XML vocabularies.</para>
    <section id="S-RULES-FOR-STRUCTURING-INFORMATION-BUNDLES">
      <title>Rules for structuring information bundles</title>
      <para>An information bundle is described as a collection of components.
        Per CCTS, a component's type is either an Aggregate Business
        Information Entity (ABIE), an Association Business Information Entity
        (ASBIE) or a Basic Business Information Entity (BBIE). </para>
      <section id="S-DOCUMENTS">
        <title>Documents</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 Information bundle structured as a document ABIE</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each document shall be structured as a single top-level
                    ABIE, referred to in this specification as a
                      <emphasis>document ABIE</emphasis>.</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. The collection is
                      identified in syntax separately from other collections of
                      ABIEs.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-LIBRARIES">
        <title>Libraries</title>
        <para>A library is a collection of shared ABIEs that does not include a
          document ABIE. There may be one or more libraries.</para>
        <blockquote role="rule" id="MOD02">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>MOD02 Libraries of available ABIEs</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each library shall be structured as a collection of one
                    or more ABIEs. Every collection shall not contain a
                    document ABIE.</para>
                  <note>
                    <para>The rationale is that each library collection is
                      identified in syntax distinguished 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 Library ordering</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The ABIEs in a library shall be arranged in
                    alphabetical order of the ABIE's dictionary entry
                    name.</para>
                  <note>
                    <para>The rationale is that libraries can be very large and
                      a reader new to the library may be unfamiliar with any
                      arbitrary semantic ordering of the ABIE components. The
                      collection of ABIEs can be navigated more easily when in
                      alphabetical order.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-COMPONENTS">
        <title>Components</title>
        <para>By CCTS definition each component business information entity is
          based on a core component, either implicitly inferred or explicitly
          identified. </para>
        <para>These rules do not mandate that a BIE's core component be
          explicitly identified if the designers accept that the BIE's core
          component is implicitly inferred.</para>
      </section>
      <section id="S-EXTENSIONS">
        <title>Extensions</title>
        <para>By definition an extension is information that cannot otherwise
          be expressed using the components of a document or library. Wherever
          possible information should be expressed using the components found
          in a document library. Situations exist, however, where supplementary
          information must be added to the information bundle in a way that
          does not interfere with existing components. </para>
        <para>Multiple extensions may apply for any given document information
          bundle. Extensions may be horizontal in nature, available to use for
          all documents. Extensions may be vertical in nature, applicable only
          to a single document.</para>
        <para>The extension collection provides a home for the extensions to be
          used with a document information bundle. Within each collection there
          may be a number of extension items, each with extension metadata
          regarding the item and each with a single extension point at which is
          placed the apex element of the supplemental information.</para>
        <blockquote id="MOD04" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>MOD04 Extension collection in each document information
                  bundle</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each information bundle shall allow for optional
                    augmentation of a document with a collection of information
                    not conceptually modeled by the document ABIE or the
                    library ABIEs. There are no constraints on the information
                    that may be included in an extension, including information
                    concepts built using existing library components.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
    </section>
    <section id="S-UBL-STRUCTURING-OF-INFORMATION-BUNDLES" role="non-normative">
      <title>UBL structuring of information bundles</title>
      <section id="S-UBL-DOCUMENTS">
        <title>UBL Documents</title>
        <para>In UBL 2.1 no document-level ABIE is referenced by an ASBIE. This
          merely reflects user requirements to date and in a future revision of
          UBL there may be such references.</para>
        <para>There are 65 document ABIEs representing information bundles in
          UBL 2.1. The class names for these ABIEs are as follows:</para>
        <table frame="all" id="T-UBL-DOCUMENT-ABIES">
          <title>UBL 2.1 Document ABIEs</title>
          <tgroup cols="3">
            <colspec colname="c1" colnum="1" colwidth="1.0*"/>
            <colspec colname="c2" colnum="2" colwidth="1.0*"/>
            <colspec colname="c3" colnum="3" colwidth="1.0*"/>
            <tbody>
              <row valign="top">
                <entry>
                  <itemizedlist>
                    <listitem>
                      <para>Application Response</para>
                    </listitem>
                    <listitem>
                      <para>Attached Document</para>
                    </listitem>
                    <listitem>
                      <para>Awarded Notification</para>
                    </listitem>
                    <listitem>
                      <para>Bill Of Lading</para>
                    </listitem>
                    <listitem>
                      <para>Call For Tenders</para>
                    </listitem>
                    <listitem>
                      <para>Catalogue</para>
                    </listitem>
                    <listitem>
                      <para>Catalogue Deletion</para>
                    </listitem>
                    <listitem>
                      <para>Catalogue Item Specification Update</para>
                    </listitem>
                    <listitem>
                      <para>Catalogue Pricing Update</para>
                    </listitem>
                    <listitem>
                      <para>Catalogue Request</para>
                    </listitem>
                    <listitem>
                      <para>Certificate Of Origin</para>
                    </listitem>
                    <listitem>
                      <para>Contract Award Notice</para>
                    </listitem>
                    <listitem>
                      <para>Contract Notice</para>
                    </listitem>
                    <listitem>
                      <para>Credit Note</para>
                    </listitem>
                    <listitem>
                      <para>Debit Note</para>
                    </listitem>
                    <listitem>
                      <para>Despatch Advice</para>
                    </listitem>
                    <listitem>
                      <para>Document Status</para>
                    </listitem>
                    <listitem>
                      <para>Document Status Request</para>
                    </listitem>
                    <listitem>
                      <para>Exception Criteria</para>
                    </listitem>
                    <listitem>
                      <para>Exception Notification</para>
                    </listitem>
                    <listitem>
                      <para>Forecast</para>
                    </listitem>
                    <listitem>
                      <para>Forecast Revision</para>
                    </listitem>
                  </itemizedlist>
                </entry>
                <entry>
                  <itemizedlist>
                    <listitem>
                      <para>Forwarding Instructions</para>
                    </listitem>
                    <listitem>
                      <para>Freight Invoice</para>
                    </listitem>
                    <listitem>
                      <para>Fulfilment Cancellation</para>
                    </listitem>
                    <listitem>
                      <para>Goods Item Itinerary</para>
                    </listitem>
                    <listitem>
                      <para>Guarantee Certificate</para>
                    </listitem>
                    <listitem>
                      <para>Instruction For Returns</para>
                    </listitem>
                    <listitem>
                      <para>Inventory Report</para>
                    </listitem>
                    <listitem>
                      <para>Invoice</para>
                    </listitem>
                    <listitem>
                      <para>Item Information Request</para>
                    </listitem>
                    <listitem>
                      <para>Order</para>
                    </listitem>
                    <listitem>
                      <para>Order Cancellation</para>
                    </listitem>
                    <listitem>
                      <para>Order Change</para>
                    </listitem>
                    <listitem>
                      <para>Order Response</para>
                    </listitem>
                    <listitem>
                      <para>Order Response Simple</para>
                    </listitem>
                    <listitem>
                      <para>Packing List</para>
                    </listitem>
                    <listitem>
                      <para>Prior Information Notice</para>
                    </listitem>
                    <listitem>
                      <para>Product Activity</para>
                    </listitem>
                    <listitem>
                      <para>Quotation</para>
                    </listitem>
                    <listitem>
                      <para>Receipt Advice</para>
                    </listitem>
                    <listitem>
                      <para>Reminder</para>
                    </listitem>
                    <listitem>
                      <para>Remittance Advice</para>
                    </listitem>
                    <listitem>
                      <para>Request For Quotation</para>
                    </listitem>
                  </itemizedlist>
                </entry>
                <entry>
                  <itemizedlist>
                    <listitem>
                      <para>Retail Event</para>
                    </listitem>
                    <listitem>
                      <para>Self Billed Credit Note</para>
                    </listitem>
                    <listitem>
                      <para>Self Billed Invoice</para>
                    </listitem>
                    <listitem>
                      <para>Statement</para>
                    </listitem>
                    <listitem>
                      <para>Stock Availability Report</para>
                    </listitem>
                    <listitem>
                      <para>Tender</para>
                    </listitem>
                    <listitem>
                      <para>Tenderer Qualification</para>
                    </listitem>
                    <listitem>
                      <para>Tenderer Qualification Response</para>
                    </listitem>
                    <listitem>
                      <para>Tender Receipt</para>
                    </listitem>
                    <listitem>
                      <para>Trade Item Location Profile</para>
                    </listitem>
                    <listitem>
                      <para>Transportation Status</para>
                    </listitem>
                    <listitem>
                      <para>Transportation Status Request</para>
                    </listitem>
                    <listitem>
                      <para>Transport Execution Plan</para>
                    </listitem>
                    <listitem>
                      <para>Transport Execution Plan Request</para>
                    </listitem>
                    <listitem>
                      <para>Transport Progress Status</para>
                    </listitem>
                    <listitem>
                      <para>Transport Progress Status Request</para>
                    </listitem>
                    <listitem>
                      <para>Transport Service Description</para>
                    </listitem>
                    <listitem>
                      <para>Transport Service Description Request</para>
                    </listitem>
                    <listitem>
                      <para>Unawarded Notification</para>
                    </listitem>
                    <listitem>
                      <para>Utility Statement</para>
                    </listitem>
                    <listitem>
                      <para>Waybill</para>
                    </listitem>
                  </itemizedlist>
                </entry>
              </row>
            </tbody>
          </tgroup>
        </table>
      </section>
      <section id="S-UBL-LIBRARIES">
        <title>UBL Libraries</title>
        <para>In UBL 2.1 there is one collection of library ABIEs:</para>
        <itemizedlist>
          <listitem>
            <para>a common library of 228 ABIEs for reference by ASBIEs in the
              document ABIEs and extension ABIEs</para>
          </listitem>
        </itemizedlist>
      </section>
      <section id="S-UBL-COMPONENTS">
        <title>UBL Components</title>
        <para>The core components upon which UBL BIEs are based are not
          instantiated or published. Only the BIEs that are based upon them are
          published. This is described in detail in <xref linkend="UBLCCTS"
          /></para>
      </section>
      <section id="S-UBL-EXTENSIONS">
        <title>UBL Extensions</title>
        <para>UBL provides an extension collection for every document type.
          Using the collection is optional and when it exists it contains one
          or more extensions. For each extension there is provision for a
          number of extension metadata information items defined by UBL in
          addition to the extension point itself and its content.</para>
        <para>In UBL 2.1 there is one extension provided, that being for
          digital signatures. The information in this extension is modeled
          primarily using CCTS but with an additional data item modeled by the
          W3C in <xref linkend="xmldsig"/>. The components described using CCTS
          are in a single collection of two ABIEs describing the signature
          extension ABIE and another ABIE for reference by the extension's
          ASBIEs.</para>
      </section>
    </section>
  </section>
  <section id="S-COMPONENT-DESCRIPTIONS">
    <title>Component descriptions</title>
    <para>A component in the information bundle model corresponds to an element
      in the XML document.</para>
    <para>A single component in the document models is described by a number of
      values. Some of these values are available to be defined by the data
      modelers, and some of those are optional while others are mandatory.
      Those values of the description not available to be defined by the data
      modeler are derived from the definitions of other values which may be
      entered or, themselves, derived.</para>
    <para>The derived values are mandatory but some tools may not provide for
      their dynamic evaluation into the target value. Where such control is not
      available and these values are entered manually, a verification process
      should be run on the values to ensure they were entered without error.
      Another option would be to prevent the manual entry of these items and
      require the extraction process to export the derived values.</para>
    <section id="S-RULES-FOR-DESCRIBING-COMPONENTS">
      <title>Rules for describing components</title>
      <note>
        <para>When reading these rules, be sure to distinguish the edited
          fields that contribute to the component's dictionary entry name from
          the one derived field that is the component's name to be used in user
          data.</para>
      </note>
      <section id="S-RECORDED-CCTS-INFORMATION">
        <title>Recorded CCTS information</title>
        <para>These rules govern the creation and expression of values found in
          the CCTS information model describing the information bundle.</para>
        <blockquote id="COM01" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM01 CCTS information item description values</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each item of describing information 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 downstream expressions of the
                      model information 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 CCTS information item prohibited characters and
                  sequence</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>All items of describing information shall be void of
                    all sensitive XML markup characters and sequences. The
                    following characters are prohibited in any CCTS information
                    item:</para>
                  <itemizedlist>
                    <listitem>
                      <para>the characters "&lt;", ">", "&amp;"</para>
                    </listitem>
                    <listitem>
                      <para>the character sequence "--"</para>
                    </listitem>
                  </itemizedlist>
                  <note>
                    <para>The rationale is that prohibiting these characters
                      and sequence will allow the information to be processed
                      more simply in different XML contexts without special
                      handling.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-ABBREVIATIONS">
        <title>Abbreviations</title>
        <para>It may be convenient to abbreviate often-repeated words or to use
          industry-accepted abbreviations in CCTS information.</para>
        <blockquote role="rule" id="COM03">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM03 Agreement on a list and rules of abbreviation in
                  names</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The users of a CCTS model shall agree on a list (that
                    may be empty) of words found in naming values that shall be
                    abbreviated when a word is used in the component's derived
                    name.</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 terms have
                      widely-accepted abbreviations suitable for shortening
                      derived names.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="COM04">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM04 Agreement on a list and rules of abbreviation in
                  model values</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The users of a CCTS model shall agree on a list (that
                    may be empty) of accepted abbreviations allowed in
                    values.</para>
                  <para>The only abbreviations that shall be used in values are
                    those found in the agreed-upon list.</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 confusion
                      by users.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="COM05">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM05 Agreement on a list of equivalences in names</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The users of a CCTS model shall agree on a list (that
                    may be empty) of words found in naming values that shall be
                    considered equivalent when a word is used in the
                    component's derived name.</para>
                  <note>
                    <title>Example</title>
                    <simplelist>
                      <member>The property term primary noun "URI" is
                        considered equivalent to the representation term
                        "Identifier".</member>
                    </simplelist>
                  </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>
        <blockquote role="rule" id="COM06">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM06 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>
                    <simplelist>
                      <member>"Numeric. Format. Text" is represented with the
                        attribute named "format"</member>
                    </simplelist>
                  </note>
                  <note>
                    <para>Words 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="COM07">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM07 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 entirely in
                    upper-case.</para>
                  <note>
                    <title>Example</title>
                    <simplelist>
                      <member>"Amount Currency. Identifier" is represented with
                        the attribute named "currencyID"</member>
                      <member>"Amount Currency. Code List Version. Identifier"
                        is represented with the attribute named
                        "currencyCodeListVersionID"</member>
                    </simplelist>
                  </note>
                  <note>
                    <para>Words 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-CCTS-NAME-VALUE-CONVENTIONS">
        <title>CCTS name value conventions</title>
        <blockquote role="rule" id="COM08">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM08 CCTS 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 are prohibited in any CCTS
                    information item that contributes to the dictionary entry
                    name:</para>
                  <itemizedlist>
                    <listitem>
                      <para>the characters " " (space), "." (period) and "_"
                        (underscore)</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="COM09">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM09 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="COM10">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM10 Use of leading upper case letter in name value
                  items</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>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.</td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-BIE-DEFINITION-CONVENTIONS">
        <title>BIE definition conventions</title>
        <para>These NDR require a minimum set of information to be recorded for
          each type of BIE.</para>
        <note>
          <para>The "Name" value in BIE definitions may also be labeled the
            "Component Name" value or some other characteristic label provided
            such label does not conflict with any other value's label.</para>
        </note>
        <blockquote id="COM11" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM11 Minimum set of values describing an ABIE
                  component</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each ABIE component of the model shall have at least a
                    prescribed set of values required or available for
                    definition.</para>
                  <para>This set is as follows:</para>
                  <itemizedlist>
                    <listitem>
                      <para>Component Type (fixed)</para>
                      <itemizedlist>
                        <listitem>
                          <para>shall be the value "ABIE"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Definition (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value identifies the component 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 lists other natural language
                            terminology for the component that is acceptable in
                            common use</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Object Class Qualifier (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>when used this value distinguishes one object
                            class from a like-named other</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Object Class (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value identifies the object class as a
                            collection of BBIE and ASBIE components</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Name (mandatory; derived)</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 defined</para>
                        </listitem>
                      </itemizedlist>
                      <note>
                        <title>Example formula</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$OCQ = Object Class Qualifier</member>
                          <member>$OC = Object Class</member>
                        </simplelist>
                        <para>=SUBSTITUTE( CONCATENATE( $OCQ;$OC);"
                          ";"")</para>
                      </note>
                    </listitem>
                    <listitem>
                      <para>Dictionary Entry Name (mandatory; derived)</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 formula</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$OCQ = Object Class Qualifier</member>
                          <member>$OC = Object Class</member>
                        </simplelist>
                        <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>
        <para>
          <blockquote role="rule" id="COM12">
            <informaltable frame="all" border="1" width="100%">
              <thead>
                <tr>
                  <td>COM12 Minimum set of values describing a BBIE
                    component</td>
                </tr>
              </thead>
              <tbody>
                <tr>
                  <td>
                    <para>Each BBIE component of the model shall have at least
                      a prescribed set of values required or available for
                      definition.</para>
                    <para>This set is as follows:</para>
                    <itemizedlist>
                      <listitem>
                        <para>Component Type (fixed)</para>
                        <itemizedlist>
                          <listitem>
                            <para>shall be the value "BBIE"</para>
                          </listitem>
                        </itemizedlist>
                      </listitem>
                      <listitem>
                        <para>Cardinality (mandatory)</para>
                        <itemizedlist>
                          <listitem>
                            <para>one of "1" (required and not repeatable),
                              "0..1" (optional and not repeatable), "0..n"
                              (optional and repeatable) and "1..n" (required
                              and repeatable)</para>
                          </listitem>
                        </itemizedlist>
                      </listitem>
                      <listitem>
                        <para>Definition (mandatory)</para>
                        <itemizedlist>
                          <listitem>
                            <para>this value identifies the component 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 lists other natural language
                              terminology for the component that is acceptable
                              in common use</para>
                          </listitem>
                        </itemizedlist>
                      </listitem>
                      <listitem>
                        <para>Object Class Qualifier (optional)</para>
                        <itemizedlist>
                          <listitem>
                            <para>when used this value distinguishes one object
                              class from a like-named other</para>
                          </listitem>
                        </itemizedlist>
                      </listitem>
                      <listitem>
                        <para>Object Class (mandatory)</para>
                        <itemizedlist>
                          <listitem>
                            <para>this value identifies 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>when used this value distinguishes one
                              property term from a like-named other</para>
                          </listitem>
                        </itemizedlist>
                      </listitem>
                      <listitem>
                        <para>Property Term Possessive Noun (optional)</para>
                        <itemizedlist>
                          <listitem>
                            <para>when used this value identifies a
                              characteristic of the nature of the
                              component</para>
                          </listitem>
                        </itemizedlist>
                      </listitem>
                      <listitem>
                        <para>Property Term Primary Noun (mandatory)</para>
                        <itemizedlist>
                          <listitem>
                            <para>this value identifies the principle nature of
                              the component</para>
                          </listitem>
                        </itemizedlist>
                      </listitem>
                      <listitem>
                        <para>Representation Term (mandatory)</para>
                        <itemizedlist>
                          <listitem>
                            <para>this value identifies the form of the
                              instantiated component value and shall be
                              selected from the set of 20 primary and secondary
                              representation terms itemized 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>Data Type Qualifier (optional)</para>
                        <itemizedlist>
                          <listitem>
                            <para>when used this value distinguishes particular
                              restrictions on a data type from the use of a
                              data type with other (or no) restrictions</para>
                          </listitem>
                        </itemizedlist>
                      </listitem>
                      <listitem>
                        <para>Name (mandatory; derived)</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 formula</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>
                          </simplelist>
                          <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; derived)</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 formula</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>
                          <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>Property Term (mandatory; derived)</para>
                        <itemizedlist>
                          <listitem>
                            <para>this value shall be 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 formula</title>
                          <para>Given the following:</para>
                          <simplelist>
                            <member>$PTPsN = Property Term Possessive
                              Noun</member>
                            <member>$PTPrN = Property Term Primary
                              Noun</member>
                          </simplelist>
                          <para>=IF( $PTPsN&lt;>"";CONCATENATE( $PTPsN;"
                            ";$PTPrN);$PTPrN)</para>
                        </note>
                      </listitem>
                      <listitem>
                        <para>Data Type (mandatory; derived)</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 formula</title>
                          <para>Given the following:</para>
                          <simplelist>
                            <member>$DTQ = Data Type Qualifier</member>
                            <member>$RT = Representation Term</member>
                          </simplelist>
                          <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>
        </para>
        <blockquote role="rule" id="COM13">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM13 Minimum set of values describing an ASBIE
                  component</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each ASBIE component of the model shall have at least a
                    prescribed set of values required or available for
                    definition.</para>
                  <para>This set is as follows:</para>
                  <itemizedlist>
                    <listitem>
                      <para>Component Type (fixed)</para>
                      <itemizedlist>
                        <listitem>
                          <para>shall be the value "ASBIE"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Cardinality (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>one of "1" (required and not repeatable),
                            "0..1" (optional and not repeatable), "0..n"
                            (optional and repeatable) and "1..n" (required and
                            repeatable)</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Definition (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value identifies the component 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 lists other natural language
                            terminology for the component that is acceptable in
                            common use</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Examples (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this is a free-form value used to illustrate
                            the definition</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Object Class Qualifier (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>when used this value distinguishes one object
                            class from a like-named other</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Object Class (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value identifies the object class of the
                            ABIE to which the ASBIE belongs</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Associated Object Class Qualifier (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>when used this value distinguishes one object
                            class from a like-named other</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Associated Object Class (mandatory)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value identifies the object class of the
                            ABIE to which the ASBIE belongs</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Property Term Qualifier (optional)</para>
                      <itemizedlist>
                        <listitem>
                          <para>when used this value distinguishes one property
                            term from a like-named other</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>Name (mandatory; derived)</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 defined</para>
                        </listitem>
                      </itemizedlist>
                      <note>
                        <title>Example formula</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$PTQ = Property Term Qualifier</member>
                          <member>$PT = Property Term</member>
                        </simplelist>
                        <para>=SUBSTITUTE( SUBSTITUTE( CONCATENATE( $PTQ;IF(
                          $PT="Identifier";"ID";$PT));" ";"");"_";"")</para>
                      </note>
                    </listitem>
                    <listitem>
                      <para>Dictionary Entry Name (mandatory; derived)</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 formula</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>
                        <para>=CONCATENATE( IF( $OCQ="";"";CONCATENATE( $OCQ;"_
                          "));$OC;". ";IF( $PTQ="";"";CONCATENATE( $PTQ;"_
                          "));$PT;IF( $PTQ="";"";CONCATENATE( ".
                          ";$RT)))</para>
                      </note>
                    </listitem>
                    <listitem>
                      <para>Property Term (mandatory; derived)</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 formula</title>
                        <para>Given the following:</para>
                        <simplelist>
                          <member>$AOCQ = Associated Object Class
                            Qualifier</member>
                          <member>$AOC = Associated Object Class</member>
                        </simplelist>
                        <para>=CONCATENATE( IF( $AOCQ="";"";CONCATENATE(
                          $AOCQ;"_ "));$AOC)</para>
                      </note>
                    </listitem>
                    <listitem>
                      <para>Representation Term (mandatory; derived)</para>
                      <itemizedlist>
                        <listitem>
                          <para>this value is a copy of the Property
                            Term</para>
                        </listitem>
                      </itemizedlist>
                    </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>
        <blockquote role="rule" id="COM14">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>COM14 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>
      </section>
    </section>
    <section id="S-UBL-MAINTENANCE-OF-COMPONENTS" role="non-normative">
      <title>UBL maintenance of components</title>
      <para>The UBL TC uses office spreadsheets as the collaborative tool to
        maintain the CCTS model of the UBL documents, the common library and
        the signature extension. A spreadsheet row is used for each component.
        A spreadsheet column is used for each mandatory and optional CCTS
        facet.</para>
      <para>The 65 document ABIEs are described using individual spreadsheets
        that are found here:</para>
      <blockquote>
        <para><ulink
            url="http://docs.oasis-open.org/ubl/os-UBL-2.1/mod/maindoc/"
          /></para>
      </blockquote>
      <para>The common library ABIEs are in a single spreadsheet and the
        signature extension ABIEs are in a single spreadsheet that are found
        here:</para>
      <blockquote>
        <para><ulink
            url="http://docs.oasis-open.org/ubl/os-UBL-2.1/mod/common/"
          /></para>
      </blockquote>
      <section id="S-UBL-RECORDED-CCTS-INFORMATION">
        <title>UBL Recorded CCTS information</title>
        <para>UBL imposes an additional constraint on the values of recorded
          CCTS information that all characters used be ASCII characters. This
          prohibits accented letters, exotic symbols, and stylized punctuation
          such as "smart quotes". The rationale for this is that the resulting
          character sequences are then not subject to character encoding
          vagaries that may not be properly handled by downstream processing
          applications.</para>
      </section>
      <section id="S-UBL-ABBREVIATIONS-AND-EQUIVALENCES">
        <title>UBL Abbreviations and equivalences</title>
        <para>UBL abbreviates the following name value words when used in a
          component's name:</para>
        <itemizedlist>
          <listitem>
            <para>"Identifier" is abbreviated as "ID"</para>
          </listitem>
        </itemizedlist>
        <para>UBL considers the following name value words equivalent when used
          in a component's name:</para>
        <itemizedlist>
          <listitem>
            <para>the property term "UUID" is equivalent to the representation
              term "Identifier"</para>
          </listitem>
          <listitem>
            <para>the property term primary noun "URI" is equivalent to the
              representation term "Identifier"</para>
          </listitem>
        </itemizedlist>
        <para>UBL allows the use of the following abbreviations in
          descriptions, name values and in a component's name:</para>
        <itemizedlist>
          <listitem>
            <para>CV2 is allowed for "Card Verification Value"</para>
          </listitem>
          <listitem>
            <para>UBL is allowed for "Universal Business Language"</para>
          </listitem>
          <listitem>
            <para>UNDG is allowed for "United Nations Dangerous Goods"</para>
          </listitem>
          <listitem>
            <para>URI is allowed for "Uniform Resource Identifier"</para>
          </listitem>
          <listitem>
            <para>UUID is allowed for "Universally Unique Identifier"</para>
          </listitem>
          <listitem>
            <para>XPath is allowed for "XML Path Language"</para>
          </listitem>
        </itemizedlist>
      </section>
      <section id="S-UBL-CCTS-VALUE-CONVENTIONS">
        <title>UBL CCTS value conventions</title>
        <para>In addition to the constraints mandated by these NDR, the words
          comprising CCTS information items for a component in UBL that are not
          abbreviations are in Oxford English.</para>
      </section>
      <section id="S-UBL-BIE-DEFINITION-CONVENTIONS">
        <title>UBL BIE definition conventions</title>
        <para>The CCTS information "Name" value for a BIE definition is labeled
          "UBL Name" in the UBL spreadsheets.</para>
        <para>In addition to the CCTS columns indicated as having to be
          maintained by these NDR, the UBL spreadsheets contain the following
          columns of additional information used and recorded during analysis,
          all of which are optional:</para>
        <itemizedlist>
          <listitem>
            <para>Examples</para>
          </listitem>
          <listitem>
            <para>UN/TDED Code</para>
          </listitem>
          <listitem>
            <para>Current Version</para>
          </listitem>
          <listitem>
            <para>Analyst Notes</para>
          </listitem>
          <listitem>
            <para>CCL Dictionary Entry Name</para>
          </listitem>
          <listitem>
            <para>Context: Business Process</para>
          </listitem>
          <listitem>
            <para>Context: Region (Geopolitical)</para>
          </listitem>
          <listitem>
            <para>Context: Official Constraints</para>
          </listitem>
          <listitem>
            <para>Context: Product</para>
          </listitem>
          <listitem>
            <para>Context: Industry</para>
          </listitem>
          <listitem>
            <para>Context Role</para>
          </listitem>
          <listitem>
            <para>Context: Supporting Role</para>
          </listitem>
          <listitem>
            <para>Context: System Constraint</para>
          </listitem>
          <listitem>
            <para>Editor's Notes</para>
          </listitem>
          <listitem>
            <para>Changes from Previous Version</para>
          </listitem>
        </itemizedlist>
        <para>Object classes are never qualified in UBL. Accordingly, the
          "Object Class Qualifier" and "Associated Object Class Qualifier"
          columns are present but always empty in instances of the
          spreadsheets. </para>
        <para>Every Document ABIE contains as its first four BBIE children, in
          order and all with property Term Primary Noun "Identifier" and
          Representation Term "Identifier", items with the following Property
          Term Possessive Nouns:</para>
        <itemizedlist>
          <listitem>
            <para>UBL Version</para>
          </listitem>
          <listitem>
            <para>Customization</para>
          </listitem>
          <listitem>
            <para>Profile</para>
          </listitem>
          <listitem>
            <para>Profile Execution</para>
          </listitem>
        </itemizedlist>
      </section>
    </section>
  </section>
  <section id="S-OPTIONAL-CCTS-SERIALIZATION">
    <title>Optional 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>
    <section id="S-RULES-FOR-CCTS-SERIALIZATION">
      <title>Rules for CCTS serialization</title>
      <para>There are no formal rules for CCTS serialization.</para>
    </section>
    <section id="S-UBL-CCTS-SERIALIZATION" role="non-normative">
      <title>UBL CCTS serialization</title>
      <para>The UBL distribution includes the following serializations of CCTS
        information expressed using the OASIS genericode XML vocabulary:</para>
      <blockquote>
        <para><ulink url="http://docs.oasis-open.org/ubl/os-UBL-2.1/mod/"
          /></para>
        <itemizedlist>
          <listitem>
            <para>UBL-Entities-2.1.gc - all document ABIEs and common library
              ABIEs</para>
          </listitem>
          <listitem>
            <para>UBL-Signature-Entities-2.1.gc - all signature extension
              ABIEs</para>
          </listitem>
        </itemizedlist>
      </blockquote>
      <note>
        <para>The rationale is that while OASIS genericode was designed for use
          with code lists, it is a suitable XML serialization of any
          sparsely-populated tabular construct. The table of CCTS information
          in a model is sparsely-populated with numerous undefined
          cells.</para>
      </note>
      <para>In addition to a column for each piece of CCTS information saved
        for each BIE, there is a column named "ModelName" populated by every
        row. The value in this column indicates the model in which the BIE is
        defined. The values include "UBL-CommonLibrary-2.1" for all BIEs
        defined in the common library, and "UBL-XXXX-2.1" where "XXXX" is the
        component name of the ABIE for the object class (e.g. "FreightInvoice")
        for the document ABIE and its child BIEs.</para>
      <para>The key column in the genericode serialization is declared to be
        the "DictionaryEntryName" column.</para>
      <para>The genericode specification imposes no order on the values in a
        row. In UBL 2.1 the order happens to correspond to the order of column
        declarations.</para>
      <para>An example serialization of all three kinds of BIE is as follows
        for the common library ABIE "Winning Party", one of 8 ABIEs in UBL 2.1
        that have a single BBIE and a single ASBIE (note that commented numbers
        indicate the row number from the spreadsheet; this supplemental
        information is not required to be included but exists as a convenient
        reference):</para>
      <literallayout><literal>&lt;Row>&lt;!--2354-->
   &lt;Value ColumnRef="ModelName">
      &lt;SimpleValue>UBL-CommonLibrary-2.1&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="UBLName">
      &lt;SimpleValue>WinningParty&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="DictionaryEntryName">
      &lt;SimpleValue>Winning Party. Details&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ObjectClass">
      &lt;SimpleValue>Winning Party&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ComponentType">
      &lt;SimpleValue>ABIE&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="Definition">
      &lt;SimpleValue>A party that is identified as the awarded by a tender
      result.&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="CurrentVersion">
      &lt;SimpleValue>2.1&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextBusinessProcess">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextRegionGeopolitical">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextOfficialConstraints">
      &lt;SimpleValue>None&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextProduct">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextIndustry">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextRole">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextSupportingRole">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextSystemConstraint">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
&lt;/Row>
&lt;Row>&lt;!--2355-->
   &lt;Value ColumnRef="ModelName">
      &lt;SimpleValue>UBL-CommonLibrary-2.1&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="UBLName">
      &lt;SimpleValue>Rank&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="DictionaryEntryName">
      &lt;SimpleValue>Winning Party. Rank. Text&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ObjectClass">
      &lt;SimpleValue>Winning Party&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="PropertyTermPrimaryNoun">
      &lt;SimpleValue>Rank&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="PropertyTerm">
      &lt;SimpleValue>Rank&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="RepresentationTerm">
      &lt;SimpleValue>Text&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="DataType">
      &lt;SimpleValue>Text. Type&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="Cardinality">
      &lt;SimpleValue>0..1&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ComponentType">
      &lt;SimpleValue>BBIE&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="Definition">
      &lt;SimpleValue>Indicates the rank obtained in the 
      award.&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="CurrentVersion">
      &lt;SimpleValue>2.1&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextBusinessProcess">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextRegionGeopolitical">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextOfficialConstraints">
      &lt;SimpleValue>None&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextProduct">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextIndustry">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextRole">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextSupportingRole">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextSystemConstraint">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
&lt;/Row>
&lt;Row>&lt;!--2356-->
   &lt;Value ColumnRef="ModelName">
      &lt;SimpleValue>UBL-CommonLibrary-2.1&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="UBLName">
      &lt;SimpleValue>Party&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="DictionaryEntryName">
      &lt;SimpleValue>Winning Party. Party&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ObjectClass">
      &lt;SimpleValue>Winning Party&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="PropertyTerm">
      &lt;SimpleValue>Party&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="RepresentationTerm">
      &lt;SimpleValue>Party&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="AssociatedObjectClass">
      &lt;SimpleValue>Party&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="Cardinality">
      &lt;SimpleValue>1&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ComponentType">
      &lt;SimpleValue>ASBIE&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="Definition">
      &lt;SimpleValue>Information about an organization, sub-organization, or
      individual fulfilling a role in a business process.&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="CurrentVersion">
      &lt;SimpleValue>2.1&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextBusinessProcess">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextRegionGeopolitical">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextOfficialConstraints">
      &lt;SimpleValue>None&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextProduct">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextIndustry">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextRole">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextSupportingRole">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
   &lt;Value ColumnRef="ContextSystemConstraint">
      &lt;SimpleValue>In All Contexts&lt;/SimpleValue>
   &lt;/Value>
&lt;/Row></literal></literallayout>
    </section>
  </section>
  <section id="S-OPTIONAL-REPORTING">
    <title>Optional 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>
    <section id="S-RULES-FOR-REPORTING">
      <title>Rules for reporting</title>
      <para>There are no formal rules for reporting.</para>
    </section>
    <section id="S-UBL-REPORTING" role="non-normative">
      <title>UBL reporting</title>
      <section id="S-HTML-SUMMARY-REPORTS">
        <title>HTML summary reports</title>
        <para>The UBL distribution includes a number of HTML summary files
          reporting filtered content from the CCTS information. These files are
          found in the directory:</para>
        <blockquote>
          <para><ulink
              url="http://docs.oasis-open.org/ubl/os-UBL-2.1/mod/summary/"
            /></para>
          <itemizedlist>
            <listitem>
              <para>readme-Reports.html - report descriptions and usage, legend
                information, and a summary of links to all of the HTML summary
                files</para>
            </listitem>
            <listitem>
              <para><ulink
                  url="http://docs.oasis-open.org/ubl/os-UBL-2.1/mod/summary/reports/"
                /> - the subdirectory with all of the reports</para>
              <itemizedlist>
                <listitem>
                  <para>UBL-AllDocuments-2.1.html - an unfiltered report of the
                    entire CCTS information content</para>
                </listitem>
                <listitem>
                  <para>UBL-XXXX-2.1.html - a filtered report for the document
                    type "XXXX" as the component name of the ABIE of the object
                    class of the Document ABIE (e.g. OrderResponseSimple) in
                    which all common library CCTS information not found to be
                    used somewhere in the document type is not included</para>
                </listitem>
              </itemizedlist>
            </listitem>
          </itemizedlist>
        </blockquote>
      </section>
      <section id="S-MODEL-CHECK-REPORT">
        <title>Model check report</title>
        <para>Not included in the UBL distribution is a textual report the UBL
          TC utilizes as a "model check" that has analyzed the CCTS information
          reporting any violations of these Naming and Design Rules or any
          anomalies that may inadvertently interfere with the production of the
          validation artefacts. An example of such inadvertent interference is
          the use of a double-hyphen "--" in any description field. Such a
          sequence interferes with generating XML-based artefacts where some
          content might be, or later want to be, placed in an XML comment.
          Participants can be warned to revise field values so as not to
          include this or other sensitive character sequences.</para>
      </section>
    </section>
  </section>
  <section id="S-USER-DATA-VALIDATION-ARTEFACTS">
    <title>User data validation artefacts</title>
    <para>While the information bundles are described using CCTS principles, it
      is the document models that govern the structure of documents expressing
      in a machine-readable format the information described by the bundles.
      These NDR provide for expressing the model of an information bundle using
      validation artefacts that describe constraints on the structure and
      content of documents. Validation processes report violations of these
      model constraints found in a document.</para>
    <para>There are two types of validation artefacts. W3C XSD schemas are used
      to validate the structure of elements and the structure of data content.
      OASIS CVA expressions and OASIS genericode files are used to validate the
      values of data content.</para>
    <section id="S-RULES-FOR-CREATING-USER-DATA-VALIDATION-ARTEFACTS">
      <title>Rules for creating user data validation artefacts</title>
      <para>These rules do not constrain the organization of the validation
        artefacts in any particular directory structure.</para>
      <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>
      <section id="S-NAMESPACES">
        <title>Namespaces</title>
        <para>An important aspect of identifying and distinguishing the labels
          of information in information bundles is by using namespaces.
          Like-named constructs are distinguished by having different
          namespaces when using XML.</para>
        <note>
          <para>Namespace abbreviations (also used here as namespace prefixes)
            in this document 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>A minimum set of namespaces is required for that
                    information that is found in information bundles.</para>
                  <para>This set shall be as follows:</para>
                  <itemizedlist>
                    <listitem>
                      <para>one namespace for each document ABIE</para>
                      <itemizedlist>
                        <listitem>
                          <para>these namespaces are not abbreviated in this
                            document as they are not imported or
                            included</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>one namespace for all BBIE components</para>
                      <itemizedlist>
                        <listitem>
                          <para>abbreviated in this document as "cbc" for
                            "common basic components"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>one namespace for all ASBIE components (each
                        component corresponding to a library ABIE)</para>
                      <itemizedlist>
                        <listitem>
                          <para>abbreviated in this document as "cac" for
                            "common aggregate components"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>one namespace for the extension collection and
                        extension metadata elements</para>
                      <itemizedlist>
                        <listitem>
                          <para>abbreviated in this document as "ext"</para>
                        </listitem>
                      </itemizedlist>
                    </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>Each extension shall have a set of namespaces
                    defined.</para>
                  <para>This set shall be as follows:</para>
                  <itemizedlist>
                    <listitem>
                      <para>one namespace for the apex ABIE of the
                        extension</para>
                      <itemizedlist>
                        <listitem>
                          <para>abbreviated in this document as "myext1"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>one namespace for all BBIE extension components
                        that are not existing library components</para>
                      <itemizedlist>
                        <listitem>
                          <para>abbreviated in this document as "mycbc1"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>one namespace for all ASBIE extension components
                        (each corresponding to an extension ABIE) that are not
                        existing library components</para>
                      <itemizedlist>
                        <listitem>
                          <para>abbreviated in this document as "mycac1"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                  </itemizedlist>
                  <note>
                    <para>The structure of an extension parallels that of a
                      document with the distinct apex namespace, BBIE namespace
                      and ASBIE 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 labels of information
          bundles in documents, the description of the BBIE type information
          found in the bundles also is distinguished using namespaces. These
          namespaces are used only for labeling type information and not for
          labeling information items themselves and so are never found on XML
          elements in a document (thus they are never declared in an XML
          document governed by these NDR).</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>A minimum the following namespaces shall be defined for
                    identifying type information for BBIEs.</para>
                  <para>This set shall be as follows:</para>
                  <itemizedlist>
                    <listitem>
                      <para>one namespace for all qualified data types</para>
                      <itemizedlist>
                        <listitem>
                          <para>abbreviated in this document as "qdt"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>one namespace for all unqualified data types</para>
                      <itemizedlist>
                        <listitem>
                          <para>abbreviated in this document as "udt"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                    <listitem>
                      <para>one namespace for CCTS Core Component Type
                        definitions</para>
                      <itemizedlist>
                        <listitem>
                          <para>abbreviated in this document as
                            "ccts-cct"</para>
                        </listitem>
                      </itemizedlist>
                    </listitem>
                  </itemizedlist>
                  <note>
                    <para>These namespaces are used solely for describing the
                      BBIE type information and are not ever needed in the XML
                      document instances.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <para>Schema annotations describing CCTS information require the use of
          a namespace.</para>
        <blockquote id="NAM04" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>NAM04 Namespaces for schema annotations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>When needed, a namespace for CCTS documentation found
                    in schema annotations shall be defined as distinct from all
                    other namespaces.</para>
                  <para>This namespace is abbreviated in this document as
                    "ccts".</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <para>An implementation of these NDR may choose to have additional
          namespaces for the management of type information.</para>
      </section>
      <section id="S-XSD-IMPORT-INCLUDE-TREE">
        <title>XSD import/include tree</title>
        <para><xref
            linkend="F-POSSIBLE-IMPORT-INCLUDE-HIERARCHY-OF-XSD-SCHEMA-EXPRESSIONS"
          /> depicts the relationships between the W3C XSD fragments that are
          described in this section. There are no differences in the
          import/include hierarchy between the documented schemas and the
          runtime schemas. 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/UBL-2.1-NDR-allschema.png"
                contentwidth="750px"/>
            </imageobject>
            <textobject>
              <phrase>[XSD Schema Structure]</phrase>
            </textobject>
          </mediaobject>
        </figure>
        <para>In the diagram the unshaded boxes represent fragments created by
          the publishers of the schema. Once created there is no need for users
          of the schema to modify these fragments, and 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 modified and/or created by
          the users of the schema. The Extension Content Data Type is
          distinguished from other fragments in that it is initially created by
          the publishers of the schema and subsequently replaced by the users
          of the schema. This fragment defines which schemas are in play for
          the extension point of an extension item in the extension collection.
          The publishers of the schema </para>
      </section>
      <section id="S-SCHEMA-FRAGMENT-ANNOTATIONS">
        <title>Schema fragment annotations</title>
        <para>Provision is made in these NDR for annotating the schema
          fragments with model, housekeeping or maintenance information using
          XSD declaration annotations and XML comments. There are no
          constraints regarding which annotation information is added to the
          schema expressions. 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 schema documents.</para>
        <para>XSD annotation is typically defined for and with each of the many
          declarations in the file. Prudence suggests always providing a
          version of the published schema without XSD annotations so as not to
          burden runtime processing systems that provide no benefit having the
          information available. 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 XSD annotations are simple XML
          comments that annotate schema fragments for identification or
          copyright purposes. Such comments are ignored by schema processors
          and do not burden their processing. The information in these comments
          is useful to users and, in some cases, may be required for
          intellectual property reasons imposed by the publisher. Good practice
          suggests that such information include module identification, module
          revision metadata and copyright declarations.</para>
        <para>The built-in 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-LIBRARY-AND-DOCUMENT-ABIE-SCHEMA-DECLARATIONS">
        <title>Library and document ABIE schema declarations</title>
        <para>The schema fragment containing the definition of constraints for
          all common library ABIEs and each schema fragment containing the
          definition of constraints for a single document ABIE both have the
          same types of declarations.</para>
        <blockquote role="rule" id="DCL01">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL01 Element and type declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Every element and type declaration shall be
                    global.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="DCL02" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL02 Library ABIE schema contents</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The one library ABIE schema shall include an element
                    declaration for every library ABIE, every library ASBIE and
                    every document ASBIE. It also includes a type declaration
                    for every library ABIE.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="DCL03" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL03 Document ABIE schema contents</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each document ABIE schema shall include a single
                    element declaration, that being for the document ABIE. It
                    also includes a single type declaration, that being for the
                    document ABIE.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="DCL04" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL04 Library and document ABIE schema element
                  declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each ABIE element shall be declared with the component
                    name as the element name and the component name suffixed
                    with "Type" as the type.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:element name="WinningParty" type="WinningPartyType"/></programlisting>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="DCL05" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL05 Library and document ASBIE schema element
                  declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each ASBIE element shall be declared with the component
                    name as the element name and the component name of the ABIE
                    of the associated object class suffixed with "Type" as the
                    type.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:element name="AgentParty" type="PartyType"/></programlisting>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="DCL06" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL06 Library and document ABIE schema type
                  declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The library ABIE schema shall include a complex type
                    declaration for every library ABIE. The document ABIE
                    schema shall include a complex type declaration for the
                    document ABIE.</para>
                  <para>Each complex type name shall be declared with the
                    component name of the ABIE suffixed with "Type" as the
                    type.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:complexType name="WinningPartyType">
 &lt;xsd:sequence>
  &lt;xsd:element ref="cbc:Rank" minOccurs="0" maxOccurs="1"/>
  &lt;xsd:element ref="cac:Party" 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 ABIE schema type content declaration order</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The members of an ABIE shall be ordered as a sequence
                    with all BBIE element declarations first, followed by all
                    ASBIE declarations.</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="DCL08" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL08 Document ABIE schema type extension declaration</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The members of a document ABIE that is supporting
                    extensions shall be preceded by a reference to the
                    extension collection element declaration.</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 id="DCL09" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL09 ABIE schema type content declaration style</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The members of an ABIE shall be declared using
                    references to element declarations.</para>
                  <note>
                    <title>Example</title>
                    <programlisting>&lt;xsd:complexType name="ItemIdentificationType">
  &lt;xsd:sequence>
     &lt;xsd:element ref="cbc:ID" minOccurs="1" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:ExtendedID"
                     minOccurs="0" maxOccurs="1"/>
     &lt;xsd:element ref="cbc:BarcodeSymbologyID"
                      minOccurs="0" maxOccurs="1"/>
     &lt;xsd:element ef="cac:PhysicalAttribute"
                     minOccurs="0" maxOccurs="unbounded"/>
     &lt;xsd:element ref="cac:MeasurementDimension"
                     minOccurs="0" maxOccurs="unbounded"/>
     &lt;xsd:element ref="cac:IssuerParty"
                     minOccurs="0" maxOccurs="1"/>
  &lt;/xsd:sequence>
&lt;/xsd:complexType></programlisting>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <para>There are no constraints on the order of the declarations in the
          schema expression.</para>
        <note>
          <para>This lack of an order constraint may seem in conflict with the
            library constraint of alphabetical order of model components.
            Whereas the model components are organized for the benefit of the
            human reader, the order of the schema component declarations does
            not influence the behaviour of a schema processor. Choosing
            alphabetical order would be a convenience for the unexpected human
            reader of the schema expressions.</para>
        </note>
      </section>
      <section id="S-LIBRARY-BBIE-SCHEMA-DECLARATIONS">
        <title>Library BBIE schema declarations</title>
        <blockquote id="DCL10" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL10 Library BBIE schema</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The library BBIE schema shall have element declarations
                    for every BBIE referenced in all document ABIEs and all
                    library ABIEs.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="DCL11" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL11 Library BBIE schema</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The library BBIE schema shall have a complex type
                    declaration for every BBIE referenced in all document ABIEs
                    and all library ABIEs.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="DCL12" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL12 Library BBIE schema element declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each BBIE element shall be declared with the component
                    name as the element name and the concatenation of the
                    component 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="DCL13" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DCL13 Library BBIE schema element declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Each 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 id="S-EXTENSION-COLLECTION-SCHEMA-DECLARATIONS">
        <title>Extension collection schema declarations</title>
        <para>The validation artefacts may contain an extension collection in
          order to provide for the inclusion of extra-model information in a
          document. Such information includes content standardized by other
          organizations (e.g. signature information), and augmentations of the
          document models.</para>
        <para>The extension collection contains one or more extension items.
          Each extension item has extension metadata elements may reuse
          existing ABIEs or BBIEs from the common library or may contain
          specific metadata unrelated to concepts found in the common
          library.</para>
        <blockquote role="rule" id="EXT01">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT01 Extension collection cardinality</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>A document may be allowed to contain at most one
                    extension collection, and if it is, that extension
                    collection shall be optional and not repeated.</para>
                  <note>
                    <para>The rationale for the item being optional is that any
                      given instance of the document may not have any extension
                      information to augment the modeled business
                      objects.</para>
                  </note>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote role="rule" id="EXT02">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT02 Extension collection location</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The document's extension collection shall be realized
                    in the validation artefacts as the first child of the
                    document ABIE validation construct, before that of any BIE
                    modeled for the document ABIE.</para>
                  <note>
                    <para>The rationale is to support serial processing of the
                      information. All extension information is encountered,
                      and cached if necessary by a program, before encountering
                      any of the modeled document information. This ensures the
                      program has all information about a modeled business
                      object when encountering that object in the serial stream
                      of content, regardless of the presence or absence of
                      extension information.</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 content</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The document's extension collection shall require one
                    or more extension items as its content.</para>
                  <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 item content</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The extension item shall have a collection of metadata
                    information regarding the given instance of the item, plus
                    a mandatory single element being the extension point under
                    which extension information is added to the
                    document.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="EXT05" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT05 Extension point</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The extension point of each extension item shall
                    require a single element in some namespace other than the
                    extension namespace. There shall be no other constraints
                    imposed on the extension point element.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="EXT06" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT06 Extension collection and item schema fragment and
                  declarations</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The extension collection schema fragment shall include
                    the declarations of the extension collection element, the
                    extension item element, and the extension item metadata
                    elements and any required type information for
                    locally-defined elements.</para>
                  <para>The extension collection schema fragment shall include
                    the declaration of the mandatory extension point element,
                    but not the type information for the extension point
                    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 by a user of the schemas, 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 id="EXT07" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT07 Extension point data type schema fragment and
                  declaration</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The extension point 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 id="EXT08" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>EXT08 Extension point data type schema fragment import
                  directives</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>The extension point schema fragment may contain as many
                    import directives for extension point schemas as desired.
                    There is no order to the directives.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-QUALIFIED-DATA-TYPES-SCHEMA-DECLARATIONS">
        <title>Qualified Data Types schema declarations</title>
        <para>Any required qualified data types are declared in the Qualified
          Data Types module.</para>
        <blockquote role="rule" id="QDT01">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>QDT01 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="QDT02">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>QDT02 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>
                  <para>The resulting declaration shall be such that every
                    possible instance of the declared complex 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-DECLARATIONS">
        <title>Unqualified Data Types schema declarations</title>
        <para>All unqualified data types are declared in the Unqualified Data
          Types module. </para>
        <blockquote id="UDT01" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>UDT01 Unqualified Data Type declaration suite</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>An unqualified data type shall be declared for every
                    one of and only the 20 CCTS Primary Representation Terms
                    and Secondary Representation Terms defined in <xref
                      linkend="CCTS"/> Section 8-3 "Permissible Representation
                    Terms".</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="UDT02" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>UDT02 Unqualified Data Type declaration base</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>Every unqualified data type shall be based on one of
                    the 10 CCTS Core Component Type schema data types defined
                    in <xref linkend="CCTS"/> Section 8-2 "Approved Core
                    Component Type Content and Supplementary
                    Components".</para>
                  <para>This 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>
                  <para>The resulting declaration shall be such that every
                    possible instance of the declared complex type is also an
                    instance of the base type.</para>
                  <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>
      </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 a
                    schema fragment as published by UN/CEFACT.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
      <section id="S-DATA-TYPE-QUALIFICATIONS">
        <title>Data type qualifications</title>
        <para>Data type qualifications that are not expressed as qualified data
          types using XSD schema semantics are expressed using the OASIS
          Context Value Association <xref linkend="oasiscva"/> XML vocabulary.
          The CVA file provides for users to associate value evaluation
          expressions and OASIS genericode code lists with different CVA
          contexts.</para>
        <blockquote id="DTQ01" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DTQ01 Data type qualifications for element content</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>A CVA context shall be created for every BBIE with a
                    non-empty value in the CCTS information for the qualified
                    data type.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
        <blockquote id="DTQ02" role="rule">
          <informaltable frame="all" border="1" width="100%">
            <thead>
              <tr>
                <td>DTQ02 Data type qualifications for attribute content</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>
                  <para>A CVA context shall be created for every CCTS
                    supplementary component to be validated.</para>
                </td>
              </tr>
            </tbody>
          </informaltable>
        </blockquote>
      </section>
    </section>
    <section id="S-UBL-CREATION-OF-USER-DATA-VALIDATION-ARTEFACTS"
      role="non-normative">
      <title>UBL creation of user data validation artefacts</title>
      <para>The UBL distribution organizes the documented XSD schemas (with BIE
        XSD annotations) under the <literal>xsd/</literal> subdirectory and the
        runtime XSD schemas (without BIE XSD annotations) under the
          <literal>xsdrt/</literal> subdirectory:</para>
      <blockquote>
        <para><ulink url="http://docs.oasis-open.org/ubl/os-UBL-2.1/xsd/"
          /></para>
        <para><ulink url="http://docs.oasis-open.org/ubl/os-UBL-2.1/xsdrt/"
          /></para>
      </blockquote>
      <para>The CVA file and formatted report are distributed in the
          <literal>cva/</literal> subdirectory:</para>
      <blockquote>
        <para><ulink url="http://docs.oasis-open.org/ubl/os-UBL-2.1/cva/"
          /></para>
      </blockquote>
      <para>The genericode files referenced by the CVA file are distributed in
        the <literal>gc/</literal> subdirectories of both the UBL 2.1
        distribution and the UBL 2.0 distribution:</para>
      <blockquote>
        <para><ulink url="http://docs.oasis-open.org/ubl/os-UBL-2.1/cl/gc/"
          /></para>
        <para><ulink url="http://docs.oasis-open.org/ubl/os-UBL-2.0/cl/gc/"
          /></para>
      </blockquote>
      <para>The UBL CVA and genericode files are compiled into an XSLT
        stylesheet expression for runtime testing against XML instances that
        have been validated using the UBL XSD schemas. This stylesheet is named
          <literal>UBL-DefaultDTQ-2.1.xsl</literal> and is distributed in the
          <literal>val/</literal> subdirectory:</para>
      <blockquote>
        <para><ulink url="http://docs.oasis-open.org/ubl/os-UBL-2.1/val/"
          /></para>
      </blockquote>
      <section id="S-UBL-NAMESPACES">
        <title>UBL namespaces</title>
        <para>The following namespace URI strings are associated with the
          indicated documentary namespace prefixes:</para>
        <table frame="all" rowsep="1" colsep="1" id="T-UBL-NAMESPACES">
          <title>UBL Namespaces</title>
          <tgroup cols="2">
            <colspec colname="c1" colnum="1" colwidth="1.3*"/>
            <colspec colname="c2" colnum="2" colwidth="13.13*"/>
            <tbody>
              <row valign="top">
                <entry>(no prefix)</entry>
                <entry>Document ABIE namespaces use the component name of the
                  ABIE XXXXXXXX as
                      follows:<para><literal>urn:oasis:names:specification:ubl:schema:xsd:XXXXXXXX-2</literal></para></entry>
              </row>
              <row valign="top">
                <entry>cbc</entry>
                <entry><literal>urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2</literal></entry>
              </row>
              <row valign="top">
                <entry>cac</entry>
                <entry><literal>urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2</literal></entry>
              </row>
              <row valign="top">
                <entry>ext</entry>
                <entry><literal>urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2</literal></entry>
              </row>
              <row valign="top">
                <entry>sig</entry>
                <entry><literal>urn:oasis:names:specification:ubl:schema:xsd:CommonSignatureComponents-2</literal></entry>
              </row>
              <row valign="top">
                <entry>sac</entry>
                <entry><literal>urn:oasis:names:specification:ubl:schema:xsd:SignatureAggregateComponents-2</literal></entry>
              </row>
              <row valign="top">
                <entry>sbc</entry>
                <entry><literal>urn:oasis:names:specification:ubl:schema:xsd:SignatureBasicComponents-2</literal></entry>
              </row>
              <row valign="top">
                <entry>qdt</entry>
                <entry><literal>urn:oasis:names:specification:ubl:schema:xsd:QualifiedDataTypes-2</literal></entry>
              </row>
              <row valign="top">
                <entry>udt</entry>
                <entry><literal>urn:oasis:names:specification:ubl:schema:xsd:UnqualifiedDataTypes-2</literal></entry>
              </row>
              <row valign="top">
                <entry>ccts-cct</entry>
                <entry><literal>urn:un:unece:uncefact:data:specification:CoreComponentTypeSchemaModule:2</literal></entry>
              </row>
              <row valign="top">
                <entry>ccts</entry>
                <entry><literal>urn:un:unece:uncefact:documentation:2</literal></entry>
              </row>
            </tbody>
          </tgroup>
        </table>
      </section>
      <section id="S-UBL-XSD-IMPORT-INCLUDE-TREE">
        <title>UBL XSD import/include tree</title>
        <para><xref
            linkend="F-UBL-IMPORT-INCLUDE-HIERARCHY-OF-XSD-SCHEMA-EXPRESSIONS"
          /> depicts the UBL implementation of the import and include
          directives shown in <xref
            linkend="F-POSSIBLE-IMPORT-INCLUDE-HIERARCHY-OF-XSD-SCHEMA-EXPRESSIONS"
          />. </para>
        <figure id="F-UBL-IMPORT-INCLUDE-HIERARCHY-OF-XSD-SCHEMA-EXPRESSIONS">
          <title>UBL import/include hierarchy of XSD schema expressions</title>
          <mediaobject>
            <imageobject>
              <imagedata fileref="art/UBL-2.1-NDR-ublschema.png"
                contentwidth="750px"/>
            </imageobject>
            <textobject>
              <phrase>[XSD Schema Structure]</phrase>
            </textobject>
          </mediaobject>
        </figure>
      </section>
      <section id="S-UBL-COMMON-SCHEMA-FRAGMENT-ANNOTATIONS">
        <title>UBL common schema fragment annotations</title>
        <para>The documented XSD schemas include CCTS information in
          annotations of the Library and Document ABIE complex types (not of
          the element declarations). Only those values found in the columns
          referenced in <xref linkend="S-BIE-DEFINITION-CONVENTIONS"/> are
          included. An example of each of an ABIE, BBIE and ASBIE is as
          follows:</para>
        <programlisting>&lt;xsd:complexType name="WinningPartyType">
  &lt;xsd:annotation>
     &lt;xsd:documentation>
        &lt;ccts:Component>
           &lt;ccts:ComponentType>ABIE&lt;/ccts:ComponentType>
           &lt;ccts:DictionaryEntryName>Winning Party. 
           Details&lt;/ccts:DictionaryEntryName>
           &lt;ccts:Definition>A party that is identified as the awarded by
           a tender result.&lt;/ccts:Definition>
           &lt;ccts:ObjectClass>Winning Party&lt;/ccts:ObjectClass>
        &lt;/ccts:Component>
     &lt;/xsd:documentation>
  &lt;/xsd:annotation>
  &lt;xsd:sequence>
     &lt;xsd:element ref="cbc:Rank" minOccurs="0" maxOccurs="1">
        &lt;xsd:annotation>
           &lt;xsd:documentation>
              &lt;ccts:Component>
                 &lt;ccts:ComponentType>BBIE&lt;/ccts:ComponentType>
                 &lt;ccts:DictionaryEntryName>Winning Party. Rank.
                 Text&lt;/ccts:DictionaryEntryName>
                 &lt;ccts:Definition>Indicates the rank obtained in the
                 award.&lt;/ccts:Definition>
                 &lt;ccts:Cardinality>0..1&lt;/ccts:Cardinality>
                 &lt;ccts:ObjectClass>Winning Party&lt;/ccts:ObjectClass>
                 &lt;ccts:PropertyTerm>Rank&lt;/ccts:PropertyTerm>
                 &lt;ccts:RepresentationTerm>Text&lt;/ccts:RepresentationTerm>
                 &lt;ccts:DataType>Text. Type&lt;/ccts:DataType>
              &lt;/ccts:Component>
           &lt;/xsd:documentation>
        &lt;/xsd:annotation>
     &lt;/xsd:element>
     &lt;xsd:element ref="cac:Party" minOccurs="1" maxOccurs="1">
        &lt;xsd:annotation>
           &lt;xsd:documentation>
              &lt;ccts:Component>
                 &lt;ccts:ComponentType>ASBIE&lt;/ccts:ComponentType>
                 &lt;ccts:DictionaryEntryName>Winning Party.
                 Party&lt;/ccts:DictionaryEntryName>
                 &lt;ccts:Definition>Information about an organization,
                 sub-organization, or individual fulfilling a role in a
                 business process.&lt;/ccts:Definition>
                 &lt;ccts:Cardinality>1&lt;/ccts:Cardinality>
                 &lt;ccts:ObjectClass>Winning Party&lt;/ccts:ObjectClass>
                 &lt;ccts:PropertyTerm>Party&lt;/ccts:PropertyTerm>
                 &lt;ccts:AssociatedObjectClass>Party&lt;/ccts:Associated
ObjectClass>
                 &lt;ccts:RepresentationTerm>Party&lt;/ccts:RepresentationTerm>
              &lt;/ccts:Component>
           &lt;/xsd:documentation>
        &lt;/xsd:annotation>
     &lt;/xsd:element>
  &lt;/xsd:sequence>
&lt;/xsd:complexType></programlisting>
        <para>Every schema fragment generated for UBL 2.1 includes an XML
          comment at both the beginning of the document and the end of the
          document. These comments are present in both the documented schemas
          and the runtime schemas.</para>
        <para>The comment at the beginning of every schema fragment includes
          identification information and revision metadata, as in this example
          from the common aggregate components fragment:</para>
        <programlisting>&lt;!--
  Library:           OASIS Universal Business Language (UBL) 2.1 OS
                     http://docs.oasis-open.org/ubl/os-UBL-2.1/
  Release Date:      04 November 2013
  Module:            xsd/common/UBL-CommonAggregateComponents-2.1.xsd
  Generated on:      2013-10-31 17:17z
  Copyright (c) OASIS Open 2013. All Rights Reserved.
--></programlisting>
        <para>The comment at the end of the document is a detailed copyright
          notice as follows: </para>
        <programlisting>&lt;!-- ===== Copyright Notice ===== -->&lt;!--
  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's 
  procedures with respect to rights in OASIS specifications can be 
  found at 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 
  implementors or users of this specification, can be obtained from 
  the OASIS Executive Director.

  OASIS invites any interested party to bring to its attention any 
  copyrights, patents or patent applications, or other proprietary 
  rights which may cover technology that may be required to 
  implement this specification. Please address the information to the 
  OASIS Executive Director.
  
  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 
  paragraph are included on all such copies and derivative works. 
  However, this document itself may not be modified in any way, 
  such as by removing the copyright notice or references to OASIS, 
  except as needed for the purpose of developing OASIS 
  specifications, in which case the procedures for copyrights defined 
  in the OASIS Intellectual Property Rights document must be 
  followed, or as required to translate it into languages other than 
  English. 

  The limited permissions granted above are perpetual and will not be 
  revoked by OASIS or its successors or assigns. 

  This document and the information contained herein is provided on 
  an "AS IS" 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 RIGHTS OR ANY IMPLIED 
  WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 
  PARTICULAR PURPOSE.    
--></programlisting>
        <para>Throughout the fragments are short XML comments delineating
          sections with declarations for different purposes.</para>
        <para>The built-in version annotation of the schema document element is
          used to reflect the version of the UBL release. For example, this is
          used for every schema fragment in the UBL 2.1 release:</para>
        <programlisting>&lt;xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.1" ...</programlisting>
      </section>
      <section id="S-UBL-LIBRARY-AND-DOCUMENT-ABIE-SCHEMA-DECLARATIONS">
        <title>UBL library and document ABIE schema-declarations</title>
        <para>The UBL common ABIE library schema fragment is named
          UBL-CommonAggregateComponents-2.1.xsd in UBL 2.1.</para>
        <para>Each UBL document ABIE schema fragment is named UBL-XXXXX-2.1.xsd
          in UBL 2.1, where XXXXX is the component name of the document
          ABIE.</para>
        <para>There is only one addition in the UBL implementation of
          declarations as in <xref
            linkend="S-UBL-LIBRARY-AND-DOCUMENT-ABIE-SCHEMA-DECLARATIONS"/>.
          The element declaration in a document ABIE includes an annotation as
          follows:</para>
        <programlisting>&lt;xsd:annotation>
   &lt;xsd:documentation>This element MUST be conveyed as the root element 
in any instance document based on this Schema expression&lt;/xsd:documentation>
&lt;/xsd:annotation></programlisting>
      </section>
      <section id="S-UBL-LIBRARY-BBIE-DECLARATIONS">
        <title>UBL library BBIE declarations</title>
        <para>The UBL common BBIE library schema fragment is named
          UBL-CommonBasicComponents-2.1.xsd in UBL 2.1.</para>
        <para>There are no differences in the UBL implementation of
          declarations as in <xref linkend="S-LIBRARY-BBIE-SCHEMA-DECLARATIONS"
          />.</para>
      </section>
      <section id="S-UBL-EXTENSION-COLLECTION-SCHEMA-DECLARATIONS">
        <title>UBL extension collection schema declarations</title>
        <para>The UBL common extension library schema fragment is named
          UBL-CommonExtensionComponents-2.1.xsd in UBL 2.1.</para>
        <para>The UBL extension collection element is named "UBLExtensions" and
          its type is named "UBLExtensionsType". It is comprised of one or more
          UBL extension elements.</para>
        <para>The UBL extension element is named "UBLExtension" and its type is
          named " UBLExtensionType". It is comprised of the following elements,
          in order, each with a type named by the element name suffixed with
          "Type", each with a cardinality of 0..1, and those declared in the
          module are declared with the given unqualified data type:</para>
        <itemizedlist>
          <listitem>
            <para>cbc:ID (from the common library)</para>
            <itemizedlist>
              <listitem>
                <para>An identifier for the Extension assigned by the creator
                  of the extension.</para>
              </listitem>
            </itemizedlist>
          </listitem>
          <listitem>
            <para>cbc:Name (from the common library)</para>
            <itemizedlist>
              <listitem>
                <para>A name for the Extension assigned by the creator of the
                  extension.</para>
              </listitem>
            </itemizedlist>
          </listitem>
          <listitem>
            <para>ExtensionAgencyID (of unqualified data type "Identifier.
              Type")</para>
            <itemizedlist>
              <listitem>
                <para>An agency that maintains one or more Extensions.</para>
              </listitem>
            </itemizedlist>
          </listitem>
          <listitem>
            <para>ExtensionAgencyName (of unqualified data type "Text.
              Type")</para>
            <itemizedlist>
              <listitem>
                <para>The name of the agency that maintains the
                  Extension.</para>
              </listitem>
            </itemizedlist>
          </listitem>
          <listitem>
            <para>ExtensionVersionID (of unqualified data type "Identifier.
              Type")</para>
            <itemizedlist>
              <listitem>
                <para>The version of the Extension.</para>
              </listitem>
            </itemizedlist>
          </listitem>
          <listitem>
            <para>ExtensionAgencyURI (of unqualified data type "Identifier.
              Type")</para>
            <itemizedlist>
              <listitem>
                <para>A URI for the Agency that maintains the Extension.</para>
              </listitem>
            </itemizedlist>
          </listitem>
          <listitem>
            <para>ExtensionURI (of unqualified data type "Identifier.
              Type")</para>
            <itemizedlist>
              <listitem>
                <para>A URI for the Extension.</para>
              </listitem>
            </itemizedlist>
          </listitem>
          <listitem>
            <para>ExtensionReasonCode (of unqualified data type "Code.
              Type")</para>
            <itemizedlist>
              <listitem>
                <para>A code for reason the Extension is being included.</para>
              </listitem>
            </itemizedlist>
          </listitem>
          <listitem>
            <para>ExtensionReason (of unqualified data type "Text.
              Type")</para>
            <itemizedlist>
              <listitem>
                <para>A description of the reason for the Extension.</para>
              </listitem>
            </itemizedlist>
          </listitem>
          <listitem>
            <para>ExtensionContent (this type is declared in an included
              extension content data type schema fragment)</para>
            <itemizedlist>
              <listitem>
                <para>The definition of the extension content.</para>
              </listitem>
            </itemizedlist>
          </listitem>
        </itemizedlist>
        <para>The UBL implementation of the extension content data type schema
          fragment imposes "lax" processing on a single, mandatory element of
          type xsd:any. The schema fragment imports the UBL common digital
          signature extension in order to impose that extension's schema
          constraints when the signature extension element is used.</para>
        <para>The UBL common digital signature extension schema fragment is
          named UBL-CommonSignatureComponents-2.1.xsd in UBL 2.1.</para>
      </section>
      <section id="S-UBL-QUALIFIED-DATA-TYPE-SCHEMA-DECLARATIONS">
        <title>UBL Qualified Data Type schema declarations</title>
        <para>The UBL qualified data type schema fragment is named
          UBL-QualifiedDataTypes-2.1.xsd in UBL 2.1.</para>
        <para>The UBL implementation of qualified data types is empty. There
          are no qualified data types. Data type qualifications are validated
          solely through the expression of code list constraints using CVA
          expressions and genericode code list expressions.</para>
      </section>
      <section id="S-UBL-UNQUALIFIED-DATA-TYPE-SCHEMA-DECLARATIONS">
        <title>UBL Unqualified Data Type schema declarations</title>
        <para>The UBL unqualified data type schema fragment is named
          UBL-UnqualifiedDataTypes-2.1.xsd in UBL 2.1.</para>
        <para>The following modifications of the CCTS Core Component Types are
          implemented for the 20 CCTS Primary Representation Terms and
          Secondary Representation Terms defined in <xref linkend="CCTS"/>
          Section 8-3 "Permissible Representation Terms". The modifications are
          limited to changing the cardinality of an attribute from optional to
          required and imposing a particular lexical format in place of
          allowing a format identifier.</para>
        <table frame="all" rowsep="1" colsep="1"
          id="T-CORE-COMPONENT-TYPE-CONSTRAINTS-IN-UBL">
          <title>Core Component Type constraints in UBL</title>
          <tgroup cols="2">
            <colspec colname="c1" colnum="1" colwidth="1*"/>
            <colspec colname="c2" colnum="2" colwidth="3.08*"/>
            <tbody>
              <row>
                <entry>Amount Type</entry>
                <entry>Amount. Currency. Identifier required as
                    <literal>@currencyID</literal></entry>
              </row>
              <row>
                <entry>Binary Object Type</entry>
                <entry>Binary Object. Mime. Code required as
                    <literal>@mimeCode</literal></entry>
              </row>
              <row>
                <entry>Graphic Type</entry>
                <entry>Graphic. Mime. Code required as
                    <literal>@mimeCode</literal></entry>
              </row>
              <row>
                <entry>Picture Type</entry>
                <entry>Picture. Mime. Code required as
                    <literal>@mimeCode</literal></entry>
              </row>
              <row>
                <entry>Sound Type</entry>
                <entry>Sound. Mime. Code required as
                    <literal>@mimeCode</literal></entry>
              </row>
              <row>
                <entry>Video Type</entry>
                <entry>Video. Mime. Code required as
                    <literal>@mimeCode</literal></entry>
              </row>
              <row>
                <entry>Code Type</entry>
                <entry><emphasis>(unchanged)</emphasis></entry>
              </row>
              <row>
                <entry>Date Time Type</entry>
                <entry>Date Time. Format. Text omitted; Date Time. Type based
                  on <literal>xsd:dateTime</literal></entry>
              </row>
              <row>
                <entry>Date Type</entry>
                <entry>Date Time. Format. Text omitted; Date Time. Type based
                  on <literal>xsd:date</literal></entry>
              </row>
              <row>
                <entry>Time Type</entry>
                <entry>Date Time. Format. Text omitted; Date Time. Type based
                  on <literal>xsd:time</literal></entry>
              </row>
              <row>
                <entry>Identifier Type</entry>
                <entry><emphasis>(unchanged)</emphasis></entry>
              </row>
              <row>
                <entry>Indicator Type</entry>
                <entry>Indicator. Format. Text omitted; Indicator. Type based
                  on <literal>xsd:dateTime</literal></entry>
              </row>
              <row>
                <entry>Measure Type</entry>
                <entry>Measure. Unit. Code required as
                    <literal>@unitCode</literal></entry>
              </row>
              <row>
                <entry>Numeric Type</entry>
                <entry><emphasis>(unchanged)</emphasis></entry>
              </row>
              <row>
                <entry>Value Type</entry>
                <entry><emphasis>(unchanged)</emphasis></entry>
              </row>
              <row>
                <entry>Percent Type</entry>
                <entry><emphasis>(unchanged)</emphasis></entry>
              </row>
              <row>
                <entry>Rate Type</entry>
                <entry><emphasis>(unchanged)</emphasis></entry>
              </row>
              <row>
                <entry>Quantity Type</entry>
                <entry><emphasis>(unchanged)</emphasis></entry>
              </row>
              <row>
                <entry>Text Type</entry>
                <entry><emphasis>(unchanged)</emphasis></entry>
              </row>
              <row>
                <entry>Name Type</entry>
                <entry><emphasis>(unchanged)</emphasis></entry>
              </row>
            </tbody>
          </tgroup>
        </table>
      </section>
      <section id="S-UBL-CCTS-CORE-COMPONENT-TYPES-SCHEMA">
        <title>UBL CCTS Core Component Types schema</title>
        <para>The UBL CCTS Core Component Types schema fragment is named
          CCTS_CCT_SchemaModule-2.1.xsd in UBL 2.1.</para>
        <para>The CCTS Core Component Types schema fragment version 1.1,
          copyrighted in 2006 by UN/CEFACT, inspired the creation of the
          unqualified data types in UBL 2.0 and was included in the 2006 UBL
          distribution. These data types include content and supplementary
          components declared as normalized strings.</para>
        <para>For backward compatibility, UBL 2.1 bases the unqualified data
          types on the same version 1.1 schema fragment in its schema import
          hierarchy and not the version 2.0 schema fragment published in
          2007.</para>
        <note>
          <title>Important note regarding compatibility</title>
          <para>Version 2.0 of the XSD for Core Component Types is not backward
            compatible with version 1.1 of the XSD for Core Component Types. An
            example of being unable to replace version 1.1 with version 2.0 is
            the declaration of content and components as XSD tokens. Tokens are
            more restricted than the normalized strings used in version 1.1,
            thus a value expressed using 1.1 may not validate using 2.0
            schemas. Any schema import tree based on version 2.0 of the XSD for
            Core Component Types will not be backward compatible with the same
            import tree based on version 1.1.</para>
        </note>
        <para>The version 1.1 schema begins with the following metadata:</para>
        <programlisting>&lt;!-- ====================================================================== -->
&lt;!-- ===== CCTS Core Component Type Schema Module ===== -->
&lt;!-- ====================================================================== -->
&lt;!--
   Module of Core Component Type
   Agency: UN/CEFACT
   VersionID: 1.1
   Last change: 14 January 2005
   
   
   
   Copyright (C) UN/CEFACT (2006). All Rights Reserved.</programlisting>
        <note>
          <title>Important note regarding access</title>
          <para>This module is periodically revised by UN/CEFACT and archive
            copies of previous versions appear not to be available on the
            UN/CEFACT web site. A copy of version 1.1 of the XSD for Core
            Component Types cannot be found on the UN/CEFACT web site but is
            found in both of the UBL distributions at:</para>
          <blockquote>
            <para><ulink
                url="http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/CCTS_CCT_SchemaModule-2.0.xsd"
              /></para>
            <para><ulink
                url="http://docs.oasis-open.org/ubl/os-UBL-2.1/xsd/common/CCTS_CCT_SchemaModule-2.1.xsd"
              /></para>
          </blockquote>
        </note>
      </section>
      <section id="S-UBL-DATA-TYPE-QUALIFICATIONS">
        <title>UBL data type qualifications</title>
        <para>The data type qualifications in UBL 2.1 reference code lists
          whose name matches a name found in the Data Type Qualification
          information item of all BBIEs. These code lists are found in the
          following directories:</para>
        <itemizedlist>
          <listitem>
            <para>UBL 2.0 supplementary components</para>
            <itemizedlist>
              <listitem>
                <para><ulink
                    url="http://docs.oasis-open.org/ubl/os-UBL-2.0/cl/gc/cefact/"
                  /></para>
              </listitem>
            </itemizedlist>
          </listitem>
          <listitem>
            <para>UBL 2.0 qualifications</para>
            <itemizedlist>
              <listitem>
                <para><ulink
                    url="http://docs.oasis-open.org/ubl/os-UBL-2.0/cl/gc/default/"
                  /></para>
              </listitem>
            </itemizedlist>
          </listitem>
          <listitem>
            <para>UBL 2.1 qualifications</para>
            <itemizedlist>
              <listitem>
                <para><ulink
                    url="http://docs.oasis-open.org/ubl/os-UBL-2.1/cl/gc/default/"
                  /></para>
              </listitem>
            </itemizedlist>
          </listitem>
        </itemizedlist>
        <para>For completeness, the Binary Object. Mime. Code and Measure.
          Unit. Code lists, using the names "BinaryObjectMime" and
          "UnitOfMeasure" respectively, also are included from these
          directories:</para>
        <itemizedlist>
          <listitem>
            <para><ulink
                url="http://docs.oasis-open.org/ubl/os-UBL-2.0/cl/gc/cefact/"
              /></para>
          </listitem>
          <listitem>
            <para><ulink
                url="http://docs.oasis-open.org/ubl/os-UBL-2.1/cl/gc/default/"
              /></para>
          </listitem>
        </itemizedlist>
        <para>Instance metadata is described for the supplementary components
          as follows:</para>
        <programlisting>&lt;InstanceMetadataSets>
&lt;Annotation>
  &lt;Description>
    &lt;x:p>
      A supplementary component is a piece of metadata describing a
      property of the list of values in which a particular value is
      found.  For example, each code list of currency values has a
      version and when a currency value is specified in a UBL document
      it may be important to specify which version of the currency 
      code list that value is found.  By knowing the list from which a
      value is found, the semantics representated by that value are
      unambiguous.
    &lt;/x:p>
    &lt;x:p>
      These sets of supplementary components describe where instance-level
      metadata is found that contains values of list-level metadata from
      genericode files.  Each set is identified in a context using that
      set's unique &lt;x:samp>xml:id=&lt;/x:samp> attribute.
    &lt;/x:p>
    &lt;x:p>
      Each component pairs an XPath address of the supplementary component
      (specified in &lt;x:samp>address=&lt;/x:samp>) relative to the item with
      the code list value in the UBL document, with the XPath address of
      the corresponding list-level metadata item in the genericode file
      (specified in &lt;x:samp>identification=&lt;/x:samp>) relative to the
      &lt;x:samp>&amp;lt;Identification>&lt;/x:samp> element in the code
      list file.
    &lt;/x:p>
    &lt;x:p>
      All supplementary components in UBL are defined by the UN/CEFACT Core
      Component Technical Specification (CCTS) Version 2.01 dated
      15 November 2003
      &lt;x:a href="http://www.unece.org/cefact/ebxml/CCTS_V2-01_Final.pdf">
    &lt;x:samp>http://www.unece.org/cefact/ebxml/CCTS_V2-01_Final.
               pdf&lt;/x:samp>.&lt;/x:a>
      Table 8-2 "Approved Core Component Type Content
      and Supplementary Components" lists the various supplementary
      components available.  The UN/CEFACT 
      UnqualifiedDataTypeSchemaModule-2.0.xsd schema fragment specifies
      the names of the attributes for supplementary components.
    &lt;/x:p>
  &lt;/Description>
&lt;/Annotation>
&lt;InstanceMetadataSet xml:id="cctsV2.01-amount">
  &lt;Annotation>
    &lt;Description>
      &lt;x:p>
        The &lt;x:samp>Amount. Type&lt;/x:samp> supplementary component.
      &lt;/x:p>
    &lt;/Description>
  &lt;/Annotation>
  &lt;InstanceMetadata address="../@currencyCodeListVersionID"
                    identification="Version"/>
&lt;/InstanceMetadataSet>
&lt;InstanceMetadataSet xml:id="cctsV2.01-binary">
  &lt;Annotation>
    &lt;Description>
      &lt;x:p>
        There are no supplementary components for the
        &lt;x:samp>Binary Object. Type&lt;/x:samp>.
      &lt;/x:p>
    &lt;/Description>
  &lt;/Annotation>
&lt;/InstanceMetadataSet>
&lt;InstanceMetadataSet xml:id="cctsV2.01-code">
  &lt;Annotation>
    &lt;Description>
      &lt;x:p>
        The &lt;x:samp>Code. Type&lt;/x:samp> supplementary components.
      &lt;/x:p>
    &lt;/Description>
  &lt;/Annotation>
  &lt;InstanceMetadata address="@listName"
                    identification="LongName[not(@Identifier='listID')]"/>
  &lt;InstanceMetadata address="@listID"
                    identification="LongName[@Identifier='listID']"/>
  &lt;InstanceMetadata address="@listVersionID"
                    identification="Version"/>
  &lt;InstanceMetadata address="@listSchemeURI"
                    identification="CanonicalUri"/>
  &lt;InstanceMetadata address="@listURI"
                    identification="LocationUri"/>
  &lt;InstanceMetadata address="@listAgencyName"
                    identification="Agency/LongName"/>
  &lt;InstanceMetadata address="@listAgencyID"
                    identification="Agency/Identifier"/>
&lt;/InstanceMetadataSet>
&lt;InstanceMetadataSet xml:id="cctsV2.01-identifier">
  &lt;Annotation>
    &lt;Description>
      &lt;x:p>
        The &lt;x:samp>Identifier. Type&lt;/x:samp> supplementary components.
      &lt;/x:p>
    &lt;/Description>
  &lt;/Annotation>
  &lt;InstanceMetadata address="@schemeName"
                    identification="LongName[not(@Identifier='listID')]"/>
  &lt;InstanceMetadata address="@schemeID"
                    identification="LongName[@Identifier='listID']"/>
  &lt;InstanceMetadata address="@schemeVersionID"
                    identification="Version"/>
  &lt;InstanceMetadata address="@schemeURI"
                    identification="CanonicalUri"/>
  &lt;InstanceMetadata address="@schemeDataURI"
                    identification="LocationUri"/>
  &lt;InstanceMetadata address="@schemeAgencyName"
                    identification="Agency/LongName"/>
  &lt;InstanceMetadata address="@schemeAgencyID"
                    identification="Agency/Identifier"/>
&lt;/InstanceMetadataSet>
&lt;InstanceMetadataSet xml:id="cctsV2.01-measure">
  &lt;Annotation>
    &lt;Description>
      &lt;x:p>
        The &lt;x:samp>Measure. Type&lt;/x:samp> supplementary component.
      &lt;/x:p>
    &lt;/Description>
  &lt;/Annotation>
  &lt;InstanceMetadata address="../@unitCodeListVersionID"
                    identification="Version"/>
&lt;/InstanceMetadataSet>
&lt;InstanceMetadataSet xml:id="cctsV2.01-quantity">
  &lt;Annotation>
    &lt;Description>
      &lt;x:p>
        The &lt;x:samp>Quantity. Type&lt;/x:samp> supplementary components.
      &lt;/x:p>
    &lt;/Description>
  &lt;/Annotation>
  &lt;InstanceMetadata address="../@unitCodeListID"
                    identification="LongName[@Identifier='listID']"/>
  &lt;InstanceMetadata address="../@unitCodeListAgencyName"
                    identification="Agency/LongName"/>
  &lt;InstanceMetadata address="../@unitCodeListAgencyID"
                    identification="Agency/Identifier"/>
&lt;/InstanceMetadataSet>
&lt;/InstanceMetadataSets></programlisting>
        <para>The following contexts are described for attributes:</para>
        <itemizedlist>
          <listitem>
            <para>every <literal>currencyID</literal> attribute is a context
              for the currency code lists</para>
          </listitem>
          <listitem>
            <para>every <literal>mimeCode</literal> attribute is a context for
              the binary object mime code lists</para>
          </listitem>
          <listitem>
            <para>every <literal>unitCode</literal> attribute of those BBIEs
              with a Data Type value of "Measure" is a context for the unit of
              measure code lists</para>
          </listitem>
          <listitem>
            <para>every <literal>unitCode</literal> attribute of those BBIEs
              with a Data Type value of "Quantity" is a context for the unit of
              measure code lists</para>
          </listitem>
        </itemizedlist>
        <para>The following contexts are described for elements:</para>
        <itemizedlist>
          <listitem>
            <para>every element of those BBIEs with a Qualified Data Type value
              is a context for a code list with the same name as the
              value</para>
          </listitem>
        </itemizedlist>
      </section>
    </section>
  </section>
  <section id="S-CONFORMANCE">
    <title>Conformance</title>
    <para>A set of information bundle definitions and their associated user
      data 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 word <emphasis>shall</emphasis> is used
      in the context for which the user is utilizing these rules. </para>
    <note>
      <para>The different contexts referenced here relate to the different
        examples described in <xref linkend="S-INTRODUCTION"/> of how users may
        wish to utilize this specification.</para>
    </note>
    <note>
      <para>The non-normative sections of this specification that document the
        tools and techniques the UBL Technical Committee used to produce the
        UBL 2.1 validation artefacts do not govern conformance. There is no
        obligation for users of this specification to use the same tools and
        techniques. There is only the obligation to produce information bundle
        definitions and associated user data validation artefacts in such a way
        as not to violate any normative rule for the context the user wishes to
        utilize. </para>
    </note>
  </section>
  <appendix role="non-normative" 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 beginning 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>
        <para>
          <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>
          </variablelist>
          <variablelist>
            <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>
        </para>
      </blockquote>
      <para>These are the subdirectories in the package:</para>
      <blockquote>
        <para>
          <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>
        </para>
      </blockquote>
    </section>
  </appendix>
  <appendix id="A-ACKNOWLEDGEMENTS" role="non-normative">
    <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="non-normative" id="A-SUMMARY-OF-RULES">
    <title>Summary of rules</title>
    <para>The following is an alphabetical list of all rules expressed in this
      document. 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. Only the first paragraph of
      each rule is copied here. 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 role="non-normative" 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>csprd01</entry>
            <entry>&pubdate;</entry>
            <entry>GKH</entry>
            <entry>Public review draft</entry>
          </row>
        </tbody>
      </tgroup>
    </informaltable>
  </appendix>
</article>
