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=32496#action_32496 ] 

Ralf Handl commented on ODATA-204:

Answering my first question: I believe we should NOT include xsd:any or xsd:anyAttribute "extension points" for versioning purposes.

Version 4.0 of our schema files will only allow the value "4.0" for the (one and only surviving) version attribute and only define elements and attributes for 4.0.

Version 4.1 will allow the two values "4.0" and "4.1" for the version attribute and may contain additional elements and attributes.

If we need breaking changes in version 5.0 we can either 
- continue the additive approach and just document unwanted features as "deprecated", or
- hope that the next version of XML Schema adds a "deprecated" attribute, or 
- restrict the schema to the 5.0 view of the world, forcing "naive" 5.0 tools to refuse 4.x documents. "Intelligent" tools will look at the version attribute inside a CSDL document and feed the right schema definition version into the schema validation.

> 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]