-
Type:
Story
-
Status: Implemented (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Labels:
Should we really change the namespace URI for minor versions?
This makes use of prerelease attributes simply by selecting a new schema very different.
Looking at what "the community" is doing, e.g. for xpath or xsl, they seem to retain the namespaces in order NOT to invalidate existing solutions. We can keep multiple schema versions that can be selected by location.
Note: this implies that we never do backwards incompatible changes within a minor version.
Same procedure also for PTK...
1.3.7 Compatibility with JDF and prior versions of XJDF
Backwards compatibility within versions that belong to a major release is a design goal for all CIP4 standards. XJDF was
a major revision and therefore is aligned with JDF but is not backwards compatible with JDF.
This specification - XJDF 2.1 is designed to be backwards compatible with XJDF 2.0. Therefore any valid XJDF 2.0 document will also be a valid XJDF 2.1 document. The namespace URI for XJDF remains the same as for XJDF 2.0: "http://www.CIP4.org/JDFSchema_2_0". The version of an XJDF or XJMF document SHOULD be specified in XJDF/@Version or XJMF/@Version.
can be transformed into a valid XJDF 2.1 document simply by updating the namespace URI for the xjdf namespace
from "http://www.CIP4.org/JDFSchema_2_0" to "http://www.CIP4.org/JDFSchema_2_1".
Table 3.1: XJDF
| Version ? New in XJDF 2.1 |
enumeration | @Version SHALL define the version of the XJDF document. The value of @Version SHALL be "2.1" for documents that comply to this specification. A value of "2.0" MAY be specified for XJDF elements that comply with XJDF 2.0 in all aspects except for the presence of @Version. |
Table 7.1: XJMF
| Version ? New in XJDF 2.1 |
enumeration | @Version SHALL define the version of the XJMF document. The value of @Version SHALL be "2.1" for documents that comply to this specification. A value of "2.0" MAY be specified for XJMF elements that comply with XJDF 2.0 in all aspects except for the presence of @Version. |
