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

add discussion of name registry to the following sections

    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
    • Draft:
      Hide

      1.11.3.2 NMTOKEN data types
      The data type in the tables is either ‘NMTOKEN’ or ‘NMTOKENS’.
      These are designed to be machine readable values with a limited set of recommended values but an an unlimited set of
      valid values. NMTOKEN data types SHOULD NOT be localized. As the list of values is an open list, implementers cannot
      rely on the values of these data types to be from a predetermined list.
      If, in a later version of JDF XJDF, recommended values are added or deprecated from an NMTOKEN data type, this will
      be not called out in a modification note. Modification to the list of suggested values will be provided at ##ref CIP4Namesthe CIP4 technical
      website
      and updated with every specification release.
      <2.1>
      3.15.6 Extending NMTOKEN Lists
      Some elements contain attributes of type NMTOKEN and some of these have a set of predefined suggested values. These
      sets are open by design and MAY be extended with other values providing such additional values do not conflict with the
      usage of those already defined in this specification.
      If an ICS requires new NMTOKEN values or a work group has agreed upon new recommended NMTOKEN values, these will be published at ##ref CIP4Names prior to being added to the specification.
      ...
      </2.1>

      <1.7>
      3.15.10 Extending NMTOKEN Lists
      Many resources contain attributes of type NMTOKEN. Some of these have a set of predefined, suggested enumerative
      values. These lists MAY be extended with private keywords. If an ICS requires new NMTOKEN values or a work group has agreed upon new recommended NMTOKEN values, these will be published at ##ref CIP4Names prior to being added to the specification.
      In order to identify private keywords, it is strongly RECOMMENDED
      to prefix these keywords with a namespace like syntax (i.e., a namespace prefix separated by a single colon
      “:”). Such a namespace prefix SHOULD be defined in the JDF ticket with the standard xmlns:Prefix=“someURI” notation,
      even if no extension elements or attributes from that namespace occur in the JDF ticket. Implementations that find an
      unknown NMTOKEN prefixed by a namespace prefix MAY then attempt to use the default value of that attribute if the
      value of @SettingsPolicy in effect is "BestEffort".</1.7>

      A.4 Preferred NMTOKEN Values
      This section contains the preferred values for items of NMTOKEN. Although these types are open lists, the values in these
      tables SHOULD be used where possible.
      If an ICS requires new NMTOKEN values or a work group has agreed upon new recommended NMTOKEN values, these will be published at ##ref CIP4Names prior to being added to the specification and SHOULD be used where appropriate.
      ...
      <Add reference to appendix>

      [CIP4Names] <copy from cip3-ppf>
      CIP4 Name registry
      https://confluence.cip4.org/display/PUB/Name+Registry
      Show
      1.11.3.2 NMTOKEN data types The data type in the tables is either ‘NMTOKEN’ or ‘NMTOKENS’. These are designed to be machine readable values with a limited set of recommended values but an an unlimited set of valid values. NMTOKEN data types SHOULD NOT be localized. As the list of values is an open list, implementers cannot rely on the values of these data types to be from a predetermined list. If, in a later version of JDF XJDF, recommended values are added or deprecated from an NMTOKEN data type, this will be not called out in a modification note. Modification to the list of suggested values will be provided at ##ref CIP4Names the CIP4 technical website and updated with every specification release. <2.1> 3.15.6 Extending NMTOKEN Lists Some elements contain attributes of type NMTOKEN and some of these have a set of predefined suggested values. These sets are open by design and MAY be extended with other values providing such additional values do not conflict with the usage of those already defined in this specification. If an ICS requires new NMTOKEN values or a work group has agreed upon new recommended NMTOKEN values, these will be published at ##ref CIP4Names prior to being added to the specification. ... </2.1> <1.7> 3.15.10 Extending NMTOKEN Lists Many resources contain attributes of type NMTOKEN. Some of these have a set of predefined, suggested enumerative values. These lists MAY be extended with private keywords. If an ICS requires new NMTOKEN values or a work group has agreed upon new recommended NMTOKEN values, these will be published at ##ref CIP4Names prior to being added to the specification. In order to identify private keywords, it is strongly RECOMMENDED to prefix these keywords with a namespace like syntax (i.e., a namespace prefix separated by a single colon “:”). Such a namespace prefix SHOULD be defined in the JDF ticket with the standard xmlns:Prefix=“someURI” notation, even if no extension elements or attributes from that namespace occur in the JDF ticket. Implementations that find an unknown NMTOKEN prefixed by a namespace prefix MAY then attempt to use the default value of that attribute if the value of @SettingsPolicy in effect is "BestEffort".</1.7> A.4 Preferred NMTOKEN Values This section contains the preferred values for items of NMTOKEN. Although these types are open lists, the values in these tables SHOULD be used where possible. If an ICS requires new NMTOKEN values or a work group has agreed upon new recommended NMTOKEN values, these will be published at ##ref CIP4Names prior to being added to the specification and SHOULD be used where appropriate. ... <Add reference to appendix> [CIP4Names] <copy from cip3-ppf> CIP4 Name registry https://confluence.cip4.org/display/PUB/Name+Registry

      Description

      1.9.3.2 NMTOKEN data types

      3.5.5 Extending NMTOKEN Lists

      A.3 Preferred NMTOKEN Values

        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: