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


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

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

Subject: [OASIS Issue Tracker] Commented: (ODATA-204) Define namespace versioning policy for XML namespaces

    [ http://tools.oasis-open.org/issues/browse/ODATA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32495#action_32495 ] 

Stefan Drees commented on ODATA-204:

I second the proposal from Mike to **not** version the namespace. Amending a namespace label by dates and/or version numbers to me looks like an irritating additional dimension in "semantic negotiation space". 
Each communication link between server and client negotiates a version. 
This version is defined in versioned schema files. 
After some thoughts about this, versioning our namespace labels feels a bit like wanting to define types indirectly like eg. <abc_v4.Integer/>, instead of A) an instance <abc.Integer> plus B) a schema/vocabulary ruling namespace abc by defining for that version 4.0 what an instance of that type is meant to "be" in that version. 
For v4.1 some minor changes may apply, which should not break clients with same major but lesser minor version number. 
For v5.0 abrupt changes may apply. 
In either case the label called "namespace" should not be ammended. 
The version vector negotiated for the client server link and its corresponding schema versions should be necessary and sufficient.

Does this sound compatible with the usual versioning semantics?

> Define namespace versioning policy for XML namespaces
> -----------------------------------------------------
>                 Key: ODATA-204
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-204
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol v1.0
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_WD01
> http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives-v1.3.html#xml-namespaces requires that:
> TCs must define a namespace versioning policy for any XML namespace declared in a specification, and must communicate the text expressing such policy to the TC Administrator for incorporation into the appropriate namespace document.
> The requirement refers to http://www.w3.org/TR/webarch/#versioning-xmlns.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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