[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=31968#action_31968 ] Michael Pizzo commented on ODATA-204: ------------------------------------- More context from Stefan Drees in 2012-13-12 meeting: Look at http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives-v1.3.html#xml-namespaces Defines format: http://docs.oasis-open.org/[tc-shortname]/ns/xxxx It also states there: 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. This refers to http://www.w3.org/TR/webarch/#versioning-xmlns where it says: 4.2.1. Versioning There is typically a (long) transition period during which multiple versions of a format, protocol, or agent are simultaneously in use. Good practice: Version information A data format specification SHOULD provide for version information. > 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: WD01 > Reporter: Ralf Handl > Fix For: 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]