Changes between UBL-1.0-SBS first (June 2005) and second (January 2006)
public review drafts
1. Normative Subset Content Change:
RegistrationName added to PartyTaxScheme
2. Normative Subset Content Change:
Percent added to TaxCategory
3. Change in Section 1, "Introduction" from:
"To allow trading parties to unambiguously state adherence to the subset where
one or more of the partners does not wish to use a full implementation of UBL,
this specification provides references (in the form of URIs) that can be
included in trading partner agreements."
changed to:
"To allow trading parties to unambiguously state adherence to the subset where
one or more of the partners does not wish to use a full implementation of UBL,
this specification provides references (in the form of URNs) that can be
included in trading partner agreements."
4. Change in Section 2, "Intended Use of the Small Business Subset" from:
"It is intended that any party wishing to limit their own UBL implementation
to the Small Business Subset (SBS) SHOULD indicate this in their trading partner
agreements (or the equivalent) with the relevant UBL schema URI and URL and
with the URI and URL associated with the respective Small Business Subset
definition document.
...
The subset URL used SHOULD be the persistent URL provided with this
documentation but a more convenient alternative persistent URL might be used
where this is more desirable, say to assist in automation of the trading partner
discovery process. One might have something like the following as part of an
business process specification schema (here using ebBPSS 2.0):"
changed to:
"It is intended that any party wishing to limit their own UBL implementation to
the Small Business Subset (SBS) should indicate this in their trading partner
agreements (or the equivalent) with the relevant UBL schema namespace and URL
and with the URN and URL associated with the respective Small Business Subset
definition document.
...
The subset URL used should be the persistent URL provided with this documentation.
Another persistent URL may be used such as those intended to assist in automation
of the trading partner discovery process or composition of business documents as
defined in a business process.
When a business process is used in conjunction with the Small Business Subset
(such as OASIS ebXML Business Process Specification Schema or ebBP), the logical
business document and business rules may be specified to enable their use, as in
the following example:"
5. Change to ebBP example fragment in Section 2, "Intended Use of the Small
Business Subset", from:
"...
The documents are an XSD file and a subset definition that specify
the rules for creating the XML document for the business action of invoicing the
buyer. For further explanation see http://docs.oasis-open.org/ubl/.../index.html .
...
"
changed to:
"...
The documents are an XSD file and a subset definition that specify
the rules for creating the XML document for the business action of invoicing the buyer.
...
"
[This is to conform to public review draft 4 of OASIS ebBP 2.0.2]
6. Change in Section 2.1, Normative Business Rules, from:
"2.1 Normative Business Rules
Unless otherwise specified in a trading partner agreement, the default use of a
UBL 1.0 Small Business Subset SHOULD be in accordance with the following two
business rules:"
changed to:
"2.1 Normative Business Rules
Unless otherwise specified in a trading partner agreement, the default use of a
UBL 1.0 Small Business Subset MUST be in accordance with the following two
business rules:"
7. Change in prose of Section 3.1, "Normative Material", from:
"Each of these document subset definition files contains its own Uniform
Resource Identifier (URI). The URI is located in the subset definition file in
the contents of the attribute named "id" of the root element named "xpath"
These URIs SHOULD be used as formal identifiers of the SBS version of the
appropriate document in a trading partner agreement and business process
specification. Typically this would be in addition to the corresponding (and
unchanging by this specification) use of the standard UBL namespace URI strings
for the purposes of the XML namespace of the UBL vocabulary in instances."
changed to:
"Each of these document subset definition files contains its own Uniform
Resource Name (URN). The URN is located in the subset definition file in the
contents of the attribute named "id" of the root element named "xpath".
These URNs should be used as formal identifiers of the SBS version of the
appropriate document in a trading partner agreement and business process
specification.
Typically this would be in addition to the corresponding (and unchanging by
this specification) use of the standard UBL namespaces for the purposes of the
XML namespace of the UBL vocabulary in instances."
8. Addition of supplementary packages of material allowing use of ebXML ebBP
(2.0.2) and ebCPPA (2.0b) with UBL 1.0 SBS (and UBL 1.0 without a subset):
"A complete set of ebXML Business Process (ebBP 2.0.2) definitions for the
business context of Procurement for use with UBL 1.0 (both definitions with
and definitions without the Small Business Subset) is provided here in the
universal-business-process-1.0-ebBP/ directory and called 'Universal Business
Process 1.0 Part 1: ebBP'. A corresponding set of ebXML Collaboration Protocol
Agreement (ebCPPA 2.1) templates has been produced and can be found in the
universal-business-process-1.0-ebCPPA/ directory and is called 'Universal
Business Process 1.0 Part 2: ebCPPA'." This accompanying prose is added to
section 2 and section 3.2.
9. Addition of UML diagrams (Non-Normative) outlining each subset, with
accompanying prose added to section 3.2:
"A further set of UML model diagrams identify the elements and datatypes which
are included in the subset. These diagrams are located in the uml/ directory."
10. Addition of example instances with simulated content (Non-Normative) for each
subset, with accompanying prose added to section 3.2:
"Valid UBL example instances of each UBL 1.0 document type conforming to the
Small Business Subset with simulated content are provided in the directory
xml/filled-examples/. These are provided both with fully qualified URLs (located
in the directory xml/filled-examples/with-urls/) and with the names of the XSD
schema files only (located in the directory xml/filled-examples/without-urls/)."
11. Changes to Section 3.2, "Non-Normative Material", (accompanying prose), from:
"Model files are provided in the format of the data model spreadsheets in the
UBL 1.0 Standard, with an extra column R in which "Y" indicates that the
corresponding UBL Business Information Entity (BIE) is included in the Small
Business Subset. These spreadsheets are located in the model/ subdirectory.
Note that for each document spreadsheet a separate copy of the Reusable
spreadsheet is required since the subset of reusable BIEs is different for
each SBS document model.
...
Valid UBL example instances of each UBL 1.0 document type conforming to the Small
Business Subset are provided in the directory xml/filled-examples/.
...
"
changed to:
"A model file is provided in a format similar to the data model spreadsheets in
the UBL 1.0 Standard, with an extra column for each subset document, in which "Y"
indicates that the corresponding UBL Business Information Entity (BIE) is
included in the Small Business Subset. This spreadsheet is located in the model/
subdirectory.
...
Valid UBL example instances of each UBL 1.0 document type conforming to every
attribute and element of the Small Business Subset but with generated data are
provided in the directory xml-generated/filled-examples/. These are provided
both with fully qualified URLs (located in the directory
xml-generated/filled-examples/with-urls/) and with the names of the XSD schema
files only (located in the directory xml-generated/filled-examples/without-urls/).
...
"