[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-cppa] Party Details
Thanks for your clear restatement of one concrete proposal to deal with the problem of enumerated values for type fields. Tony, I searched but did not find an issue number for this problem. Perhaps we can arrive at a convention for dealing with these values before the next version of the specification goes for approval. I will also check up the ladder with Oasis and the "Joint Committee" to see whether they have any ideas on best practices for these identifiers. This seems like it might have been a job that Core Components might have dealt with. Duane, please comment on whether William Kammerer's convention seems suitable for the usages you have in mind. OIDs are certainly widely used in other standards-- cryptography, SNMP, the old X.400 email system, some telecommunications stuff, and anywhere that ASN.1 goes. Dotted integer strings are probably not high on the XML human readability chart, but URNs are to me about at the same height. It seems to me that a standards body like Oasis promoting XML would have decided on best practices for identifiers like this. Oasis does have a URN that it has registered. Arvola research its use for values in Messaging. Next meeting we can perhaps review this under the unassigned issues. Dale Moberg -----Original Message----- From: William J. Kammerer [mailto:wkammerer@novannet.com] Sent: Tuesday, January 08, 2002 3:14 PM To: ebxml-cppa@lists.oasis-open.org Subject: Re: [ebxml-cppa] Party Details Dale Moberg agrees with Duane that it would be good if we had an enumerated list [of PartyId types], with option to extend it. It would be good if these list values were at least standardized to URIs, probably URNs. But last time [Dale] checked, there was little agreement even on how to get an official URN for DUNS or whether it might need to get some official (read legal) approval to use it. Dale asks if there are "some candidate values that could help standardization in this area? ....what [could we] use as enumerated values?" He wants a list of all commonly used identifier schemes. Dale further suggests "we might then use an oasis urn prefix to rig up enumerated values." All URN prefixes or domains are defined at http://www.iana.org/assignments/urn-namespaces. Dun & Bradstreet still hasn't requested one since we first discussed this a year ago, and I wouldn't hold my breath waiting for this to happen at all. In the meantime, I would be quite satisfied using the OID (Object Identifier) scheme to indicate PartyId types. "urn:oid:1.3.60" uniquely says Dun & Bradstreet D-U-N-S. Use "urn:oid:1.3.60" to qualify the code 081466849, and you instantly know I'm talking about the Microsoft Corporation. As another example using the OID URN, an EAN Location Code would be qualified it with a PartyId type of "urn:oid:1.3.88". The OID structure itself is cataloged at http://www.alvestrand.no/objectid. I addressed this use of OIDs (for the PartyId type) in detail within a thread of messages to the ebXML Transport mailing list back in December 2000 and subsequent months. William J. Kammerer Novannet, LLC. ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC