Re: proposal: collapse To and From elements

[christopher ferris <chris.ferris@east.sun.com>]

Yet again, David and I agree on something;-)

I think that since InternalRouting is optional in RNIF
and given what David describes should be more than
adequate.

Cheers,

Chris

Chris

"Burdett, David" wrote:
> 
> You should be able to devise a URN scheme that includes, DUNS+4 or Internal
> Routing, for example:
>         "urn:duns.com:baseid:123456789+4321:InternalRoute:Columbus_Office"
> 
> The point is we (i.e. ebXML) cannot hope to define all identifier/numbering
> schemes that will be required. This way, if the RosettaNet folks want to
> include some Internal Routing inside the Message Header, then they can
> without overloading the base definition of a party, for those folks that
> don't need it.
> 
> David
> -----Original Message-----
> From: christopher ferris [mailto:chris.ferris@east.sun.com]
> Sent: Wednesday, December 13, 2000 4:28 AM
> To: ebXML Transport (E-mail)
> Subject: Re: proposal: collapse To and From elements
> 
> William,
> 
> I'm not sure what you mean by "pretty". No one ever said
> angle brackets were "pretty";-)
> 
> You do raise an interesting point. However, isn't
> this sort of "internal" routing supposed to be
> addressed with DUNS+4 (assuming that DUNS is used as
> a Party identifier)?
> 
> Cheers,
> 
> Chris
> 
> "William J. Kammerer" wrote:
> >
> > What if some day you wanted to add internal routing specifications to
> > either the <From> or <To> specifications, a 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"
begin:vcard 
n:Ferris;Christopher
tel;cell:508-667-0402
tel;work:781-442-3063
x-mozilla-html:FALSE
org:Sun Microsystems, Inc;XTC Advanced Development
adr:;;;;;;
version:2.1
email;internet:chris.ferris@east.sun.com
title:Sr. Staff Engineer
fn:Christopher Ferris
end:vcard