NDR algorithm for converting BIEs to XML Schema components

[kenneth.sall@gsa.gov]

Hello,

I've just joined ubl-dev and ubl-comment, so pardon me if this has been
discussed here or on ubl-ndrsc. Couldn't find a subject that indicated so.

I cannot find in the November Naming and Design Rules draft a nice,
straight-forward algorithm for converting BIEs (as well as ABIEs and
ASBIEs) to XML Schema components as there was in Eve Maler's summer UBL
presentation (relevant excerpt below). Is this intentional? I realize there
are many more specific rules now, but explaining what "magic" happens in
the spreadsheet formuli would be very helpful, IMHO.

   Object classes (such as Person. Details) become complex types
   Properties (such as Person. Name. Text etc.) become elements in those
   types' content models
   Representation terms (such as Text, Date, and Address ? or Address.
   Details, actually) become the types bound to the property elements
   Remove redundant and nearly redundant words in the property field (as in
   *. Identification. Identifier)
   Remove periods, spaces, and underscores
   Replace "Details" with "Type"
   When the representation term is "Text", remove it
   When the representation term is "Identifier", truncate it to "ID"
   Remove the object class name on properties, as the XML parent labels it
   sufficiently

Kenneth Sall
XML Specialist
GSA IAE Program Management Office
U.S. General Services Administration
1 Crystal Park, Mail Stop IAA
2011 Crystal Drive, Suite 911
Arlington, VA 22202
Phone: 703.872.8589
Cell: 301-672-3269
Fax: 703.872.8598


The President's Management Agenda:
"Implementation of E-Government is important in making Government more
responsive and cost-effective."
http://www.whitehouse.gov/omb/egov/
(Embedded image moved to file: pic17964.jpg)

pic17964.jpg