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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsn message

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


Subject: RE: [wsn] [Namespace URIs] Proposal to split the existing namespaces


Title: Message
 
I am not sure I understand fully the consequences of the decision here.
 
I guess there were valid reasons for using the same namespace for the related set of WSDL and XSD instances. The simplest and perhaps most significant advantage of using the same namespace IMHO was that - tools could easily recognize and build on the fact that the WSDL, XSD (and perhaps some other artifacts in  future) instances tagged with the same namespace are closely related. For example, if one of the artifacts changes, I could possibly use the knowledge of the relationship to analyze the impact of the change.
 
With separate namespaces for the WSDL and XSD, I suppose the relationships between them have to be captured explicitly and the mechanisms for doing so may not be equivalent to using the same namespace (I am not sure).
 
I never felt comfortable about the fact that  namespace URLs are not required to be resolvable. But having some how accepted this fact, now I am not sure why we want to adopt resolvability (specifically when there are no guarantees) and is the cost of the same (requiring separate namespaces for each related artifact) worth it?  I think I may have missed some big debate somewhere about the benefits of making namespaces resolvable, while the namespace specification may continue to not require the same!
 
Can somebody closely familiar with this issue shed some light here please!
 
Thanks,
Sanjay
-----Original Message-----
From: Steve Graham [mailto:sggraham@us.ibm.com]
Sent: Tuesday, May 11, 2004 12:59 PM
To: wsn@lists.oasis-open.org
Subject: [wsn] [Namespace URIs] Proposal to split the existing namespaces


Folks:
In [1] I proposed a mapping from the namespace URI convention used in version 1.1 of WS-notification specs to one based on the OASIS file naming and related URI namespace conventions.

The submitted version of WS-Notification used a single URI namespace per specification for both the XSD and WSDL.  Given that we are trying to adopt a direct mapping from URI to URL for our XSD and WSDL, we should change this pattern to having separate URI namespaces for the XSD and WSDL.

Does anyone object to adopting this change in namespace URIs for the 0.1 draft of the OASIS work on WS-Notification?


[1]http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/6710/Proposed%20WS-Notification%20URIs.2.doc

sgg
++++++++
Steve Graham
(919)254-0615 (T/L 444)
STSM, On Demand Architecture
Member, IBM Academy of Technology
<Soli Deo Gloria/>
++++++++


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