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: TC154 vote on NWI - your approval needed

A couple of points of clarification.

1. ebXML TRP will probably use a URI (which can be either a URN or a URL)
for the content of PartyId unless the PartyId contains "type='UserDefined'"
in which case the content of PartyId will rely on a mutual understanding by
the sender and recipient of the message.
2. Using a URL means that you can, if you want, use an email address as the
From and To Party, e.g. "smtp:myname@example.com", which is nice for
lightweight messaging situations.
3. It can also be a URN, which would allow, codes along the lines of
"urn:duns.com:id:123456789", or "urn:iso.org:std:6523:code:12345".

In the last example I've made up the structure of the URNs, the structures
actually need to be registered with Iana (www.iana.org). But using URIs
allows us to support both the Internet and EDI worlds.



-----Original Message-----
From: William J. Kammerer [mailto:wkammerer@foresightcorp.com]
Sent: Tuesday, December 12, 2000 8:47 AM
To: ebxml-transport@lists.ebxml.org
Cc: tc154TAG@disa.org; sc32-1TAG@disa.org
Subject: Re: TC154 vote on NWI - your approval needed

Dear David:

The entire service code list for D.E. 0007 (2000/11/05) is at the ISO/TC
154-UN/CEFACT Joint Syntax Working Group (JSWG) web site at
http://www.gefeg.com/jswg/cl/s4/40004/cl3.htm.  The code list is only
aligned with ISO 6523 in a hodge-podge fashion for only the recently
added codes.  The whole point of using ISO 6523 is to avoid having to
maintain the service codes for EDIFACT's D.E. 0007.

My impression is that if D.E. 0007 is "30" (ISO 6523: Organization
identification), then the corresponding receiver (D.E. 0010) or sender
(D.E. 0004) code would be the ICD followed by the organization ID.  For
example, a receiver ID as an ISO 8523 structure of "0060835471095" is
instantly recognized as CommerceOne, where the 0060 says "(D-U-N-S
Number)" and 835471095 is their DUNS.

In any case, I'm relieved to hear that ISO 6523 is alive and well.

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"

----- Original Message -----
From: DDOBBING <ddobbing@attmail.com>
To: <ebxml-transport@lists.ebxml.org>
Cc: <tc154TAG@disa.org>; <sc32-1TAG@disa.org>; <fvuille@attglobal.net>
Sent: Tuesday, December 12, 2000 5:32 AM
Subject: RE: TC154 vote on NWI - your approval needed

Henry and William,

By way of background, and to let you know the that ISO 6523 is alive and
well.  For EDIFACT, the UNB (Interchange header) uses data element 0007
(Identification code qualifier) to qualify 0004 (Interchange sender
identification) and 0010 (Interchange recipient identification).

The point here is that the code list for 0007 (see below) is aligned
with ISO 6523, and as part maintenance process has its code values
assigned by the Maintenance Agency (MA) for ISO 6523.  As you will see
in the latest EDIFACT code list below (Oct 2000), there are number of
new values (designated with a "+").  These were assigned by the ISO 6523
MA within the last four months.


--- David Dobbing, Data Logistics, ddobbing@attmail.com

[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