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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wss message

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


Subject: Proposal re: Issue 31 (persistent OASIS namespaces)


My response to Frederick last month didn't get any additional response from anyone on the TC, so I thought I'd resend it.  As I mentioned on the call today, I had a separate exchange with Karl where he stated that OASIS can't accept a spec that uses a non-OASIS namespace.  As I stated below, I happen to personally agree with that policy. Anyway, I believe this issue will be a showstopper when submitting our Committee Specifications. 

 

As I understand it, we've asked OASIS to set up a general URL scheme such as http://www.oasis-open.org/schemas/<document-name> that is resolvable to the actual document.  I don't understand how hard it can be for OASIS to set up a URL like that for us to use, but that appears to be a problem.

 

However, this does NOT have to block us for V1 of the specs since we can use an OASIS-approved namespace. At the moment, the OASIS-approved namespaces either need to be urn-based (which no one wants including me) or HTTP-based URL's that are within our TC's OASIS namespace (ala ebXML - see below). 

 

I recommend that, at least for V1.0, if OASIS cannot come through with a general namespace location, we use a namespace such as "http://www.oasis-open.org/committees/wss/schemas/<our-schema-file>.xsd".  OASIS can set up a URL redirect for us that provides us persistence and points to the current document so we don't have to use the wierd PHP/number-based paths in the NS.

 

Actually, I don't know that they wouldn't be willing to use a URL such as http://www.oasis-open.org/schemas/<our-schema-file> (i.e. without the "/wss" embedded). It they can set up a redirect for the former URL, they should be able to set it up using the latter one.  Why don't we make a specific proposal such as this to Karl?

 

 

Rob Philpott

RSA Security Inc.

The Most Trusted Name in e-Security

Tel: 781-515-7115

Mobile: 617-510-0893

Fax: 781-515-7020

mailto:rphilpott@rsasecurity.com

 

 

-----Original Message-----
From: Philpott, Robert
Sent: Wednesday, July 16, 2003 10:43 AM
To: 'Frederick.Hirsch@nokia.com'; 'wss@lists.oasis-open.org'
Subject: RE: [wss] namespace stability issue

 

Issue 31 re: the schema namespaces has been pending for months now. It was

first raised by Time Moses in October.  The status says that Karl Best is

working on it and it should be resolved in "2 or 3 months".

 

We ARE an OASIS TC attempting to produce an OASIS standard. I personally do

not think we should produce schemas defined with namespaces that have

nothing to do with OASIS **unless** OASIS TC Administration signs off on it.

I am particularly against using a namespace that is owned by a specific

company (i.e. According to whois, that is Microsoft in the case of

xmlsoap.org).  We agreed to defer this issue until after the interop draft,

but I personally am opposed to dropping it for the committee specification

draft.

 

The OASIS TC Guidelines describe the allocation of a URN namespace for OASIS

TC's.  Some OASIS standards (SAML, XACML) use this URN format for the XML

schema namespaces. Most of us, I think, feel that a resolvable URL-based

namespace is preferable.  Another OASIS TC (ebXML) uses such a resolvable

URL namespace based at OASIS; namely

http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd.

Note that we certainly could pick an oasis-based URL namespace as well.

 

In our case, since we've asked Karl to help get this resolved, I feel that

WSS should make an explicit statement to the OASIS TC Administrator

indicating that the TC is going to use XML namespaces <list them> unless we

hear an official objection from OASIS by <pick a date>.

 

My preferences in order:

1. OASIS resolves the issue and provides us a resolvable URL namespace root.

2. We pick a resolvable URL based at OASIS ala ebXML (i.e. in our TC's URL

namespace)

 

I am opposed to using the schemas.xmlsoap.org based URL even as a last

resort.

 

Rob Philpott

RSA Security Inc.

The Most Trusted Name in e-Security

Tel: 781-515-7115

Mobile: 617-510-0893

Fax: 781-515-7020

mailto:rphilpott@rsasecurity.com

 

 

> -----Original Message-----

> From: Frederick.Hirsch@nokia.com [mailto:Frederick.Hirsch@nokia.com]

> Sent: Wednesday, July 16, 2003 9:38 AM

> To: wss@lists.oasis-open.org

> Subject: [wss] namespace stability issue

>

> I would like to confirm the expectation that the wsse and wsu namespaces

> are now determined and stable, as follows:

>

> http://schemas.xmlsoap.org/ws/2003/06/secext

> http://schemas.xmlsoap.org/ws/2003/06/utility

>

> Is it true that the namespaces in the document are not expected to change

> any more, even when these become Oasis specifications?

>

> The question is a concern regarding stability of the namespaces for

> development and interop.

>

> Is this correct?

>

> regards, Frederick

>

> Frederick Hirsch

> Nokia Mobile Phones

>

>

>

> You may leave a Technical Committee at any time by visiting

> http://www.oasis-

> open.org/apps/org/workgroup/wss/members/leave_workgroup.php

 

You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/wss/members/leave_workgroup.php



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