MHonArc v2.5.2 -->
ubl-ndrsc message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: RE: [ubl-ndrsc] Draft Partial Document Use Case - Justification f orDocument at the Top Level Tag Name
Title: RE: [ubl-ndrsc] Draft Partial Document Use Case - Justification f or Document at the Top Level Tag Name
Ron,
After looking at your paper, I am not convinced that adding the word document in the tag is necessary. I understand what you are saying when you talk about ECP's, etc, but fail to see how the use of the word document makes it any clearer. Under your scenario, we would have a UBL schema with a differentiated top level tag name for every possible engineering data element. A much simpler approach would be to create a single schema for <SharedEngineeringData> with a host of optional data elements. No need to use document in the top level tag, as (1) it is not a document, (2) the concept of documents is what we are trying to get away from, and (3) I can certainly garner the intent of the transaction from the proposed tag.
On a separate note, please remember that the UBL community and ebXML community are not necessarily one in the same. There is a clear overlap in interest, especially vis a vis the use of the core components specification, but we in UBL are not defining document structures for ebXML. No one has taken on that task yet.
Mark
>