Re: [ebxml-cppa] PartyId proposal, modifications of ECOM proposal to consider.

["Yukinori Saito" <y-saito@ecom.jp>]

Dear Dale Moberg,

Thank you very much for your assembling a new draft on PartyId.
Mr. Kazuhiko Wakaizumi and I checked your draft.
The followings are our comments.

1. We agree with your draft.

2. But We have noticed some minor editing comments.
(1) at the 4th line of Item No. 1
In the clause of "and appending a colon ":" followed by the the ICD
numerical identifier value.", the word "the" is doubled. We think that this
is mistaken.

(2) at the 2nd sentence of Item No. 3
The original sentence is "In the latter event, the hex escaping convention
for restricted characters should be followed."
We cannot understand this sentence clearly.
-What does the clause "In the latter event" mean?
-What is "hex"? Is this the mistake of "hexa"?

Best Regards,
Yukinori Saito
------------------------------------------------------
Yukinori Saito
Electronic Commerce Promotion Council of Japan (ECOM)
E-mail: y-saito@ecom.jp
Tel: +81-3-3436-7542    Fax: +81-3-3436-7570
------------------------------------------------------

----- Original Message ----- 
From: "Dale Moberg" <dmoberg@cyclonecommerce.com>
To: <ebxml-cppa@lists.oasis-open.org>
Sent: Thursday, August 28, 2003 1:03 AM
Subject: [ebxml-cppa] PartyId proposal, modifications of ECOM proposal to
consider.


Hi,

I am assembling a new draft on PartyID/@type values from William
Kammerer's contributions and the ECOM proposal sent by WAKAIZUMI
Kazuhiko of the Electronic Commerce Promotion Council of Japan,
JEITA/EDI-Center Technology working group.


The essence of the integrated proposal is:

1. Retain urn:oasis:names:tc:ebxml-cppa:partyid-type:duns as a type
identifier for duns, as it is used in the version 2.0 CPPA
specification.
2. Adopt, with some minor changes, most of the ECOM proposal.
3. Continue seeking consensus for how to align with the following ebXML
Messaging idea:

"It is RECOMMENDED that the value of the type attribute be a URI. It is
further recommended that these values be taken from the EDIRA (ISO
6523), EDIFACT ISO 9735 or ANSI ASC X12 I05 registries."

While the ECOM proposal handles the ISO 6523 value question,
neither the EDIFACT nor X12 registries have values that immediately
satisfy the URI syntax. If we wish to create identifiers, we can adapt
the ECOM constructions to these cases. Does anyone wish to send a
proposal to me?

When we start teleconferences again in September, this PartyId issue
will need TC discussion and consensus resolution, please.


Here is the ECOM proposal, amended in some minor details. The entire
draft should be available before the first September teleconference.


A  method to generate values fo the "type" attribute from information
described in ICD list [ISO 6523].

1.If an abbreviated name is described in the item titled "Name of Coding
System" within the ICD list, a "type" attribute can be constructed by
prepending "urn:oasis:names:tc:ebxml-cppa:partyid-type:" to the
abbreviated name and appending a colon ":" followed by the the ICD
numerical identifier value.

Example  Using abbreviated name D-U-N-SNumber
      tp:type="
urn:oasis:names:tc:ebxml-cppa:partyid-type:D-U-N-SNumber:0060"

       Note: "0060" is ICD value of D-U-N-S Number.

2.If an abbreviated name is not described in the ICD list, the "type"
attribute should contain the string derived from "Name of Coding System"
into upper-camel-case. An allowable value can always be constructed by
by prepending "urn:oasis:names:tc:ebxml-cppa:partyid-type:" to the
upper-camel-case name and appending a colon ":" followed by the ICD
numerical identifer value.

Example:
     Name of Coding System: "Data Universal Numbering System"
     Transformed Camel-case: "DataUniversalNumberingSystem"
     Example A  Using formal name:

tp:type="urn:oasis:names:tc:ebxml-cppa:partyid-type:DataUnivaersalNumber
ingSystem:0060"

3.Punctuation marks in these formal names (such as, "/", "-" or "'" )
should be included unless they are restricted in URNs  (RFC 2121). In
the latter event, the hex escaping convention for restricted characters
should be followed. Spaces are not allowed in URNs, since they should be
consumed in the concatenation process forming the upper-camel-case
string. If values are already in all upper case, they should be left in
all upper-case, and concatenated into the upper-camel-case string.

3. The ICD value should be appended as the last field of the URN so that
any collision between formal or abbreviated names is avoided.




To unsubscribe from this mailing list (and be removed from the roster of the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/ebxml-cppa/members/leave_workgroup.php.