I agree with the solution of the mandatory URN and optional URI. This
will allow for de-confliction of "names" by having the capability
(albeit optional) to go back to the source URI.
Regards,
Tom Merkle
CapWIN: www.capwin.org
Phone: (301) 614-3720
Cell Phone: (240) 375-1966
Fax: (301) 614-0581
e-mail:
CapWIN
6305 Ivy Lane Suite 300
Capital Office Park
Greenbelt, MD 20770
-----Original Message-----
From: Art Botterell [mailto:]
Sent: Wednesday, June 08, 2005 2:53 AM
To: Emergency_Mgt_TC TC
Subject: Re: [emergency] valueListURN
On Jun 7, 2005, at 6/7/05 11:33 PM, Renato Iannella wrote:
> Q1: Do we want to use real URN syntax?
It's the same dilemma as with XML namespaces: if it's a URI, folks tend
to assume the schema will actually appear at that network location, and
if it's a URN it begs the question of whether the referenced document is
published online and if so, where.
Seems to me like we could consider a mandatory valueList URN and a
optional valueListLocation URI.
> Q2: Do we want to use a hybrid system where we identify the authority
> that manages the vocabulary list (with a URI) and then indicate the
> value?
The atomic identity of the list is what we really care about... but that
implies a managing authority. What we definitely don't want is multiple
lists with the same "name." URIs and URNs are nice in that they provide
at least a clue as to the authority on the way to uniqueness.
- Art
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
