OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [regrep] Re: [ebxml-cppa] CPPA version 1.10


I brought the issue up to Dale Moberg for a separate document describing
the oasis:names:tc:ebxml-cppa:partyid-type URN.  It can be maintained
independently of the CPP/A specification, and referred to from any of
the CPP/A, Registry and Messaging Services specs.  If someone would ask
me nicely to devise the document, I might consider volunteering!

William J. Kammerer
Novannet, LLC.
+1 (614) 487-0320
+1 (614) 638-4384 (c)
+1 (928) 396-6310 (FAX)


----- Original Message -----
From: "Christopher Ferris" <chris.ferris@sun.com>
To: "William J. Kammerer" <wkammerer@novannet.com>
Cc: "OASIS ebxml-cppa" <ebxml-cppa@lists.oasis-open.org>
Sent: Monday, 18 March, 2002 11:17 AM
Subject: Re: [ebxml-cppa] CPPA version 1.10


Where are the normative URN's for the various types defined?
The spec just cites as an example the use of the URN you cite.
It seems clear to me that these URN's need to be formally
declared and assigned specific an unambiguous definitions.

Cheers,

Chris






The ebxml-cppa TC already has an OASIS URN namespace defined for
describing ID domains: urn:oasis:names:tc:ebxml-cppa:partyid-type.
There's no need for the registrar of a particular domain (e.g., D & B
for DUNS, or the IRS for Federal Tax IDs) to define URNs.  Currently,
the CPP URN describes the use of a DUNS, e.g.,

<tp:PartyId tp:type="urn:oasis:names:tc:ebxml-cppa:partyid-type:duns">
        123456789</tp:PartyId>

I've asked the CPP/A group to define a few additional domains.  HIPAA
EDI will require a number of domains available in the X12 Interchange ID
Qualifier, in addition to the already existing DUNS.  I've listed the
X12 qualifier code, the description, and examples, if available:

   01 Duns (Dun & Bradstreet), e.g., DUNS 072930527 is Novannet, LLC
   14 Duns Plus Suffix DUNS+4, e.g.,1465226281601  Kroger Distribution
Center at 4450 Poth Road Columbus, OH 43213
   20 Health Industry Number (HIN), http://www.hibcc.org/hin.htm
(602-553-8552), .e.g., G8TT9DW00 is Novation
   27 Carrier Identification Number as assigned by Health Care Financing
Administration (HCFA), e.g., 30002 is Aetna Life and Casualty Co.
   28 Fiscal Intermediary Identification Number as assigned by Health
      Care Financing Administration (HCFA)
   29 Medicare Provider and Supplier Identification Number as assigned
      by Health Care Financing Administration (HCFA)
   30 U.S. Federal Tax Identification Number, e.g, UCLA Orthopaedic
Surgery Medical Group is 954505291
   33 National Association of Insurance Commissioners Company Code
(NAIC), e.g, Prudential is NAIC # 68241, and Highmark is 54771.

It would make sense if the other ebXML groups (Messaging Services and
Registry) used this same URN: The OASIS/ebXML Registry Information Model
v2.0 uses a text string (e.g., "DUNS", "Social Security #") in section
7.9 Class ExternalIdentifier, and the Message Service Specification
Version rev C uses an "imaginary" URN in PartyId type.

William J. Kammerer
Novannet, LLC.
+1 (614) 487-0320
+1 (614) 638-4384 (c)
+1 (928) 396-6310 (FAX)

----- Original Message -----
From: "Christopher Ferris" <chris.ferris@sun.com>
To: "Duane Nickull" <duane@xmlglobal.com>
Cc: "Martin W Sachs" <mwsachs@us.ibm.com>; "David Fischer"
<david@drummondgroup.com>; "CPPA" <ebxml-cppa@lists.oasis-open.org>
Sent: Friday, 15 March, 2002 06:15 PM
Subject: Re: [ebxml-cppa] CPPA version 1.10


again, it wasn't my intent that the ssn or ein be used, but
it was an example of an authority that had an identification
scheme with a managed namespace. It was just an example.

The point is that D&B has such a namespace and if they
would simply register a URN scheme with IANA then the
issue would be moot. In the absense of a URI/URN scheme
we and many before us have resorted to code sets (like
'DUNS') that in reality are just another value in a namespace
which is not identified.

Maybe OASIS should simply use its namespace (the regrep team
maybe) to establish a branch that could be used to assign
identifiers for codes like 'DUNS'...
e.g. urn:oasis-open.org:tc:regrep:foriegn-namespaces:duns
which we could use as values for the 'type' attribute
and then make the 'type' attribute of type xsi:anyURI and
be done with it.

Cheers,

Chris



----------------------------------------------------------------
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