[ubl-ndrsc] release notes

[Lisa-Aeon <lseaburg@aeon-llc.com>]

I am attaching the html file of release notes that the LCSC QA Team put together this morning.  It will be a separate file from the Release publication.  Please look at this and give me some help getting this accurate.  I have added a heading for naming rules truncation problem, can we put something in here?

 

Lisa

 

++++++++++++++++++++++++++++++++++++++++++++++++++++
Lisa Seaburg
AEON Consulting
Website: http://www.aeon-llc.com
Email:  lseaburg@aeon-llc.com
Alternative Email: xcblgeek@yahoo.com
Phone: 662-562-7676
Cellphone: 662-501-7676

 

"If you obey all the rules, you miss all the fun."
                       -Katharine Hepburn
++++++++++++++++++++++++++++++++++++++++++++++++++++

 

 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.441 / Virus Database: 247 - Release Date: 1/9/2003

Attachment: Lisa Seaburg.vcf
Description: text/vcard

Title: 0p70 Release Notes

Universal Business Language -  0p70 Release Notes

Dated: January 17, 2003

1. A Note on the UBL Extension Methodology

The UBL TC has not yet come to a final decision on all the details of the extension methodology to be followed by those using and customizing the UBL core libraries. It is anticipated that there will be a need for users to customize the core library, however, and much work has been done in this area. The following points should be borne in mind during review of this UBL Library release, as being probable features of future releases:

1. All customizations (extensions and restrictions) are/will utilize XML namespaces owned by the customizing user, into which the core UBL libraries will be imported and referenced.
2. All extensions and refinements are/will be expressed as XSD extensions in the resulting XML schemas.
3. The business need for extensions and refinements are/will be described using a "context mechanism" based on that found in the UN/CEFACT Core Components Technical Specification, and earlier in the ebXML Core Components work. This mechanism provides for a rules language that lets machines determine the appropriateness of a specific extension for a given business purpose.
4. An "Ur Library" of XML types will be published in future as part of the UBL deliverables, in its own set of namespaces, from which everything in the UBL library will itself be a refinement. This should have little or no effect on the direct use of the document types and components found in this library release - they will have the same types and names - but will affect how they are expressed in the schemas. The reason for having such a mechanism has to do with the ability to express some types of customizations within the capabilities of XSD syntax.

Those interested in further understanding of the anticipated extension methodology should see the white papers found at the naming and Design Rules section of the UBL portal (www.oasis-open.org).

2. Truncation of Naming Rules

We need something here to go through why this is not following the NDR.