RE: [ubl-ndrsc] Tag structure discussion kickoff

["Schuldt, Ron L" <ron.l.schuldt@lmco.com>]

NDR-SC,

Using the phase "a picture is worth a thousand words",perhaps a few examples
will do likewise to help clear the air regarding the UDEF UIDs.

The following are example UDEF name constructs plus their associated UDEF
IDs.

<ProductScheduledDeliveryDate UID="9_3.29.6">
<ProductActualDeliveryDate UID="9_2.29.6">
<ProductLastPossibleDeliveryDate UID="9_2.1.29.6">
<ProductFirstPossibleDeliveryDate UID="9_1.1.29.6">
<ReplacementProductScheduledDeliveryDate UID="m.9_3.29.6">
<NewProductScheduledDeliveryDate UID="h.9_3.29.6">
<NewProductWholesalePriceAmount UID="h.9_5.2.1">
<NewProductRetailPriceAmount UID="h.9_4.2.1">
<ReplacementProductRetailPriceAmount UID="m.9_4.2.1">

<InvoiceDocumentTotalTaxAmount UID="bd.2_1.3.1">
<InvoiceDocumentTotalDueAmount UID="bd.2_2.12.1">
<InvoiceDocumentMinimumDueAmount UID="bd.2_1.12.1">

<ContractDocumentRevisionIdentifier UID="e.2_9.8">
<PurchaseOrderDocumentRevisionIdentifier UID="d.t.2_9.8">
<WorkOrderDocumentRevisionIdentifier UID="a.t.2_9.8">

<RealEstateAssetListPriceAmount UID="c.1_3.2.1">
<EquipmentAssetCostAmount UID="d.1_1.1">
<CashAssetBalanceAmount UID="a.1_6.1">

<EnterpriseName UID="3_10">
<SupplierEnterpriseName UID="y.3_10">
<PaymentRemitterEnterpriseName UID="a.w.3_10">
<PaymentReceiverEnterpriseName UID="a.x.3_10">
<CarrierEnterpriseName UID="ae.3_10">
<ManufacturerEnterpriseName UID=ah.3_10">

<SupplierEnterprisePurchaserAssignedIdentifier UID="y.3_2.35.8">
<ProductVendorAssignedIdentifier UID="9_1.35.8">

<DestinationPlaceCountryName UID="i.7_1.10">
<AddressPlaceCountryName UID="k.7_1.10">
<HomeAddressPlaceCountryName UID="a.k.7_1.10">
<DeliveryAddressPlaceCountryName UID=d.k.7_1.10">
<DeliveryAddressPlaceCityName UID="d.k.7_10.10">

I hope these illustrations provide insight to the possibilities that a
structured UID might offer.

Ronald L. Schuldt
Senior Staff Systems Architect
Lockheed Martin Enterprise Information Systems
11757 W. Ken Caryl Ave. #F521 MP DC5694
Littleton, CO 80127
303-977-1414
ron.l.schuldt@lmco.com









-----Original Message-----
From: Eve L. Maler [mailto:eve.maler@sun.com]
Sent: Wednesday, December 12, 2001 2:06 PM
To: ubl-ndrsc@lists.oasis-open.org
Subject: [ubl-ndrsc] Tag structure discussion kickoff


 From the latest minutes:

			*		*		*
    Outstanding issues:

    - Do we use highly structured names (option 1) or slightly structured
      names (option 2)?

    - Do we use fully qualified structured names (option 1a) or abbreviated
      structured names (option 1b)?  How much abbreviation do we want
      to allow?

    - Do we use ebXML/11179-style names (option 1E) or UDEF-style names
      (option 1U)?

    - Do we add attributes to UBL elements that link them to the UDEF
      structured UIDs?

    ACTION: Everybody to discuss this on the list!
			*		*		*

Okay folks, have at it!  I will be on vacation from tomorrow through next 
Tuesday, so won't be able to participate during that time.  Here are my 
thoughts on the matter, as unformed as they may be:

- I think regularity is important, and can't see much "intuition-affecting" 
difference between Mark's xCBL example and his modified option #1 version 
(which uses 1b, by the way).  So I'm in favor of option 1.

- I prefer option 1b, so that we give reusability some amount of 
importance.  I think we should try to come up with an algorithm (not a 
heuristic), if we can, to ensure that our regularity stays regular.

- I prefer option 1E, so that we can more easily align with semantics that 
we know are important to us and so that the Library Content SC can continue 
to work in the effective way that they've been using so far (working off of 
CC semantics).  I see nothing inherently wrong in the UDEF semantic trees 
(though I don't know them very well yet), but do have some questions about 
the object words that are aligned with context drivers -- how would that 
work against the context methodology that needs to be developed?  It sounds 
a bit weird to be baking context into base UBL.

- I don't, in principle, have a problem with adding UDEF UIDs to our leaf 
elements.  I see this as very much an adjunct, however, and it could 
possibly be done at a later stage.  Perhaps because I'm not entirely 
familiar with the usage/processing situations envisaged for these "hub" 
semantic sets, I have some doubts about how helpful it really is to link up 
to a standard semantic when the internal structure of the so-marked element 
can possibly be arbitrarily different from any other such element on the 
planet.  (Or maybe this is solved only by linking from leaf nodes?)

	Eve
--
Eve Maler                                    +1 781 442 3190
Sun Microsystems XML Technology Center   eve.maler @ sun.com


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>