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: Trading Partner Logical Identification based on EDIFACT or X12qualifiers

Any individual company in the U.S., or even the world, is likely to have
one of the identifiers supported by the EDIFACT UNB or X12 ISA receiver
qualifiers.  It doesn't matter which one, or ones, are used to identify
a trading partner, as they are unique and (usually) unchanging. And you
usually know your own numbers which you can share with your TPs.  Even
if you don't share them, they are easily discoverable, as I demonstrated
with the DUNS.  Some, like the DOD according to Mark Nobles, prefer
their trading partners to identify themselves by a DUNS.  But clearly,
even the DOD can handle TPs who chose to identify themselves by SCAC,
UCC Comm ID, or others.

So, what provisions will ebXML have for addressing by common logical
IDs?  Ultimately, I want send a gob o' messages, each intended for a
different recipient whom I only know by logical ID;  how will the
logical ID be transmogrified into whatever information is needed for
transport over the internet (e.g., HTTP URLs, SMTP e-mail addresses,
etc.).  Is this a job for the repository?  And no, I don't want to jack
around at my end with URLs or e-mail addresses to correlate with logical
ID.   Further, how can X.509 Public key certificates be used to ensure
that if someone says they're DUNS 895678912 that they really are?

William J. Kammerer
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