Uploaded image for project: 'XJDF / JDF'
  1. XJDF / JDF
  2. JDF-527

Add section on backwards compatibility to XJDF Spec

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Implemented (View Workflow)
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1
    • Component/s: Introduction
    • Labels:
      None
    • Draft:
      Hide

      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 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 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".

      3.5.6.1 Rules about Process Extension
      The use of namespace prefixes in the @Types attribute is for extensions only. Standard XJDF process types SHALL be
      specified without a prefix in XJDF/@Types. If a process is simply an extension of an existing process, it is possible to describe
      the private data by extending the existing resource types. This is described in greater detail in the sections below.

      Show
      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 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 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". 3.5.6.1 Rules about Process Extension The use of namespace prefixes in the @Types attribute is for extensions only. Standard XJDF process types SHALL be specified without a prefix in XJDF/@Types. If a process is simply an extension of an existing process, it is possible to describe the private data by extending the existing resource types. This is described in greater detail in the sections below.

      Description

      Discuss that XJDF 2.1 tickets need to be XJDF 2.0 tickets

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              prosi Rainer Prosi
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: