Re: [xacml] OASIS namespace documents

If the TC would like to use HTTP scheme URIs as identifiers for XML
namespace names, we will assist in the creation and maintenance

of a namespace document -- such that the dereferenced URIs

will resolve under DNS and HTTP to fetch the namespace document.

Where, of course, the namespace document documents the namespace.

See examples below.

In a recent discussion with the TAB, we decided to adopt the

pattern you see below for BIAS and Genericode (rather than

the pattern used by the ICOM TC): that is:  /tc-shortName/ns/[...]

( not /ns/tc-shortName/[...]  ).

Just let me know if you would like to pursue this in connection

with one or more of your Work Products.  URN-based names

are still allowed, but without resolution support, we're not able

to use namespace documents in any obvious way.

Examples:

Biometric Identity Assurance Services (BIAS) SOAP Profile Version 1.0

http://docs.oasis-open.org/bias/soap-profile/v1.0/csprd03/biasprofile-v1.0-csprd03.html

Declared XML namespaces:

http://docs.oasis-open.org/bias/ns/bias-1.0/

http://docs.oasis-open.org/bias/ns/biaspatronformat-1.0/

Code List Representation (Genericode) Version 1.0

(2007)

http://docs.oasis-open.org/codelist/genericode/doc/oasis-code-list-representation-genericode.html

Declared XML Namespace(s):

http://docs.oasis-open.org/codelist/ns/genericode/1.0/

http://docs.oasis-open.org/codelist/ns/rule/1.0/

Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0

http://docs.oasis-open.org/icom/icom-ics/v1.0/csprd01/icom-ics-v1.0-csprd01.html

Declared XML Namespace(s):

http://docs.oasis-open.org/ns/icom/core/201008

http://docs.oasis-open.org/ns/icom/accesscontrol/201008

http://docs.oasis-open.org/ns/icom/metadata/201008

http://docs.oasis-open.org/ns/icom/content/201008

http://docs.oasis-open.org/ns/icom/document/201008

http://docs.oasis-open.org/ns/icom/message/201008

http://docs.oasis-open.org/ns/icom/presence/201008

http://docs.oasis-open.org/ns/icom/addressbook/201008

http://docs.oasis-open.org/ns/icom/calendar/201008

http://docs.oasis-open.org/ns/icom/forum/201008

http://docs.oasis-open.org/ns/icom/conference/201008

On Fri, Dec 2, 2011 at 1:16 PM, Chet Ensign <> wrote:

It does and in fact TC Admin has been creating the namespace documents

that accompany specs.

I'm cc'ing Robin - he can help you with the ns definitions, etc.

/chet

On Fri, Dec 2, 2011 at 1:53 PM, Bill Parducci <> wrote:

> Interesting. I suspect that it requires the traditional promotion process (relying upon TC-ADMIN) to deploy it.

>

> b

>

> On Dec 2, 2011, at 9:38 AM, Tyson, Paul H wrote:

>

>> http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#xml-namespaces

>>

>> It looks like we are free to define http-style namespace URIs and maintain namespace description documents at http://docs.oasis-open.org/ns/xacml/...

>>

>> Regards,

>> --Paul

>

>

> ---------------------------------------------------------------------

> To unsubscribe, e-mail: 

> For additional commands, e-mail: 

>

--

/chet

----------------

Chet Ensign

Director of Standards Development and TC Administration

OASIS: Advancing open standards for the information society

http://www.oasis-open.org

Primary: +1 973-378-3472

Mobile: +1 201-341-1393

Follow OASIS on:

LinkedIn:    http://linkd.in/OASISopen

Twitter:        http://twitter.com/OASISopen

Facebook:  http://facebook.com/oasis.open

-- 
Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: 

Staff bio: http://www.oasis-open.org/people/staff/robin-cover
Cover Pages: http://xml.coverpages.org/

Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783