- From: Sergey Beryozkin <sergey.beryozkin@iona.com>
- Date: Thu, 15 Feb 2007 17:42:15 -0000
- To: "Paul Cotton" <Paul.Cotton@microsoft.com>, <public-ws-policy@w3.org>
Thanks for the explanation, it does help...So the namespace will likely be changed by appending or replacing the version number at the end of the namespace... Cheers, Sergey Case 1: We do a minor revision (aka WS-Policy 1.6). There might be no need to change the namespace if it was backwards compatible with the WS-Policy 1.5 semantics. Case 2: We do a major revision (aka WS-Policy 2.0) and it is NOT backwards compatible with the WS-Policy 1.5 semantics. In this case I would imagine the new namespace might be http://www.w3.org/ns/ws-policy20 There are of course other scenarios but I think these are enough to answer your question. Does this help? /paulc Paul Cotton, Microsoft Canada 17 Eleanor Drive, Ottawa, Ontario K2E 6A3 Tel: (613) 225-5445 Fax: (425) 936-7329 mailto:Paul.Cotton@microsoft.com > -----Original Message----- > From: public-ws-policy-request@w3.org [mailto:public-ws-policy- > request@w3.org] On Behalf Of Sergey Beryozkin > Sent: February 15, 2007 12:20 PM > To: public-ws-policy@w3.org > Subject: WS-Policy schema naming pattern > > > Hi > > This is somewhat off-topic, but I'm curious as to why the typical naming > convention of the namespaces which includes /yyyy/dd > pattern has been dropped in favour of the new pattern : > > from http://www.w3.org/2006/07/ws-policy > to http://www.w3.org/ns/ws-policy... > > Suppose we have http://www.w3.org/ns/ws-policy in the REC spec...What > would the namespace look like then in the next version of the > WS-Policy spec ? > > Thanks, Sergey >
Received on Thursday, 15 February 2007 17:40:52 UTC