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

Add discussion of no modifications of NMTOKEN values to spec reading section

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Implemented (View Workflow)
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.7, 2.1
    • Component/s: all
    • Labels:
      None

      Description

      NMTOKEN lists are open lists of suggested values and adding or removing values is not technically a schema change. They can even happen between versions in the CIP4 website.

        Draft

        <revive 1.3.4 for XJDF and modify appropriately to reference XJDF>

        1.9.3 Human and Machine readable strings and tokens.
        Tokens and strings are provided in 3 different facettes within (X)JDF:
        1) enumeration data types are designed to be machine readable values with a limited and well-defined set of valid values. enumeration data types can not be localized. Thus implementers can rely on the values of these data types to be from a known list. If values are added or deprecated from an enumeration data type, this will be called out in a ##ref modification note.
        2) NMTOKEN data types are designed to be machine readable values with a limited set of suggested values but an an unlimited set of valid values. NMTOKEN data types should not be localized. Thus implementers cannot rely on the values of these data types to be from a known list. If values are added or deprecated from an NMTOKEN data type, this will be not called out in a ##ref modification note. Additions to the list of suggested values will be provided at the CIP4 technical website and updated with every specification release.
        3) String data types are designed to be human readable values with an unlimited set of valid values. String data types may be localized. Thus implementers cannot rely on the values of these data types to be from a known list. No attempt is made to provide a list of valid string values. Note: In some cases, string data types are also designed to be machine readable. This is typically the case when the value set is not defined by CIP4 and therefore a limitation to NMTOKEN is not possible without reducing functionality.

         

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: