Title: Re: [ebcore] Groups - PartyIdType-1.0 v0_4.odt uploaded
Hi Pim,
You write that the different notations for the ISO6523 are historically grown. But since we define a new prefix here using “ebcore” instead of “ebxml-cppa" I would think this only applies to the old prefix. With the new prefix we can define just one notation to make it easier to construct URN’s for ISO6523 registered catalogs and make the URN’s more consistent with the general scheme used for the other registries.
Of course other catalogs and schemes can be defined using the “unregistered” prefix or register their own URN namespace. But doesn’t that also apply for the three schemes in the spec. If there is a need to have a formal URN for these registries shouldn’t they apply for a formal namespace with IANA?
Regards
Sander
On 31-03-10 09:55, "Pim Eijk, van der" <> wrote:
Comments inline.
From: Sander Fieten [mailto:]
Sent: 31 March 2010 09:12
To:
Subject: Re: [ebcore] Groups - PartyIdType-1.0 v0_4.odt uploaded
From the earlier e-mails I understand that (part of) the purpose of this spec is to provide a formal URN notation for PartyId type. I already noted earlier that the oasis NID is formally to used for identifying document from OASIS TC’s. When we discussed this earlier it was said the proposed urn are acceptable for OASIS, but is this still the case If the formal aspect is important?
Why are different notations used for the ISO6523 scheme? Why not only specifiy urn:oasis:names:tc:ebcore:partyid-type:iso6523:<ICD of catalog> ? I think this would make the specification clearer as there’s only one notation for each catalog.
This is because of the history of this spec. There are communities that use the variants. We want to continue to support them, although the notation based "iso6523" is the most concise one.
And also mentioned earlier I would prefer the scheme part of the urn not to be restricted to the three registries now described but just leave it open to users.
This is fully supported via branches of the "unregistered" case. It is important to distinguish the three internationally standardized catalogues from arbitrary other homegrown or proprietary catalogues. If communities want a formal URN and want to use this spec but don't like to be in an "unregistered" branch, let them go to IANA themselves and register their own NID.
Regards,
Sander
On 31/03/2010 01:12, "Breininger, Kathryn R" <> wrote:
Next ebCore telecon is this Friday, April 2nd. Please review prior to our meeting.
Kathryn Breininger
Manager, Document Authoring & Release
Product Standards Office
Boeing Research & Technology
The Boeing Company
MC 62-LC
425-965-0242 desk
425-512-4281 cell
425-237-4582 fax
-----Original Message-----
From: [mailto:]
Sent: Monday, March 29, 2010 12:56 PM
To:
Subject: [ebcore] Groups - PartyIdType-1.0 v0_4.odt uploaded
Please review for the next ebCore TC meeting and send any comments to the list. I do hope we can vote this as (cd2) and as PRD1.
-- Mr. Pim van der Eijk
The document revision named PartyIdType-1.0 v0_4.odt has been submitted by Mr. Pim van der Eijk to the OASIS ebXML Core (ebCore) TC document repository. This document is revision #2 of OASIS ebCore Party Type v0_1.odt.
Document Description:
View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=37116
Download Document:
http://www.oasis-open.org/committees/download.php/37116/PartyIdType-1.0%20v0_4.odt
Revision:
This document is revision #2 of OASIS ebCore Party Type v0_1.odt. The document details page referenced above will show the complete revision history.
PLEASE NOTE: If the above links do not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.
-OASIS Open Administration
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
