OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: proposal: collapse To and From elements


What if some day you wanted to add internal routing specifications to
either the <From> or <To> specifications,  la RosettaNet's (V2)
optional <locationID> within <PartnerIdentification>?

 <To>
      <Party context="uri">urn:duns:123456789</Party>
       <InternalRouting>Columbus office</InternalRouting>
 </To>

I suppose <InternalRouting> could be made another attribute of the newly
"collapsed" <To> and <From> elements, but...

Also, I've got a gut feel against having different leaf-node elements
which are a whole lot like other elements (even if they're easy enough
to define in a schema).  If and when we ever got Core Component Design
Rules, would the type of collapsing described by Christopher Ferris be
considered pretty?

William J. Kammerer
FORESIGHT Corp.
4950 Blazer Memorial Pkwy.
Dublin, OH USA 43017-3305
+1 614 791-1600

Visit FORESIGHT Corp. at http://www.foresightcorp.com/
"Commerce for a New World"





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC