This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
We need to specify the policy that the WG will use to create namespaces for all the RA specification documents, created during the standardization process. The W3C namespace URI policy is at: http://www.w3.org/2005/07/13-nsuri The suggested policy, defined in Section 1.1, recommends using the following syntax: http://www.w3.org/YYYY/MM/ssss Where: YYYY = year, MM = Month, ssss=a short string Proposal: We propose we follow the W3C recommendation for namespace URIs and use the following URIs for our first working drafts. http://www.w3.org/2009/02/ws-t http://www.w3.org/2009/02/ws-mex http://www.w3.org/2009/02/ws-en http://www.w3.org/2009/02/ws-ev http://www.w3.org/2009/02/ws-rt This is based on our intension to deliver them in February. Also, we propose using the following change policy in both the specs and namespace document (based on http://www.w3.org/ns/ws-policy/): It is the intent of the W3C Web Services Resource Access Group that the WS-Transfer, WS-Eventing, WS-Enumeration, WS-MetadataExchange and WS-ResourceTransfer namespace URIs will not change arbitrarily with each subsequent revision of the corresponding XML Schema documents but rather change only when a subsequent revision, published as a WD, CR or PR draft results in non-backwardly compatible changes from a previously published WD, CR or PR draft of the specification. Under this policy, the following are examples of backwards compatible changes that would not result in assignment of a new XML namespace URI: Addition of new global element, attribute, complexType and simpleType definitions. Addition of new elements or attributes in locations covered by a previously specified wildcard. Modifications to the pattern facet of a type definition for which the value-space of the previous definition remains valid or for which the value-space of the vast majority of instances would remain valid. Modifications to the cardinality of elements (i.e. modifications to minOccurs or maxOccurs attribute value of an element declaration) for which the value-space of possible instance documents conformant to the previous revision of the schema would still be valid with regards to the revised cardinality rule.
Resolved on 2009-02-03: Format of Namespaces for the specifications being worked in WS-Resource Access: http://www.w3.org/YYYY/MM/ws-tra for WS-Transfer http://www.w3.org/YYYY/MM/ws-mex for WS-Metadata Exchange http://www.w3.org/YYYY/MM/ws-enu for WS-Enumeration http://www.w3.org/YYYY/MM/ws-evt for WS-Eventing http://www.w3.org/YYYY/MM/ws-rst for WS-Resource Transfer Namespace Policy to be contained in specs and re-referenceable namespace document: The working group intends to update the value of the Web Services XXXX namespace URI each time a new version of this document is published until such time that the document reaches Candidate Recommendation status. Once it has reached Candidate Recommendation status, the working group intends to maintain the value of the Web Services XXXX namespace URI that was assigned in the Candidate Recommendation unless significant changes are made that impact the implementation or break post-CR implementations of the specification. Reference http://www.w3.org/2001/tag/doc/namespaceState.html and http://www.w3.org/2005/07/13-nsuri
In specs.
Please make my changes