Search RFCs

RFC Editor

Found 1 record.

Status:Verified (1)

RFC 6110, "Mapping YANG to Document Schema Definition Languages and Validating NETCONF Content", February 2011

Note: This RFC has been updated byRFC 7952

Errata ID:3362
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Jernej Tuljak
Date Reported: 2012-09-21
Verifier Name: Benoit Claise
Date Verified: 2012-10-22

Throughout the document, when it says:

Table of Contents-----------------OLD      12.16. The @nma:unique Annotation ..............................74Sec. 5.3, entry in Table 2:---------------------------OLD        | @nma:unique               | 10.55              |      |Sec. 10.55:-----------OLD   This statement is mapped to the @nma:unique attribute.  ARGUMENT MUST   be translated so that every node identifier in each of its components   is prefixed with the namespace prefix of the local module, unless the   prefix is already present.  The result of this translation then   becomes the value of the @nma:unique attribute.   For example, assuming that the local module prefix is "ex",   unique "foo ex:bar/baz"   is mapped to the following attribute/value pair:   nma:unique="ex:foo ex:bar/ex:baz"Sec. 11.2, second paragraph:----------------------------OLD   In a Schematron schema generated by the second mapping step, the   basic unit of organization is a rule represented by the <sch:rule>   element.  The following NETMOD-specific annotations from the hybrid   schema (henceforth called "semantic annotations") are mapped to   corresponding Schematron rules: <nma:must>, @nma:key, @nma:unique,   @nma:max-elements, @nma:min-elements, @nma:when, @nma:leafref, @nma:   leaf-list, and also @nma:mandatory appearing as an attribute of <rng:   choice> (see Section 11.2.1).Sec. 12.16 (including its title):---------------------------------OLD12.16.  The @nma:unique Annotation   The mapping of this annotation is almost identical as for @nma:key,   see Section 12.8, with two small differences:   o  The value of @nma:unique is a list of descendant schema node      identifiers rather than simple leaf names.  However, the XPath      expressions specified in Section 12.8 work without any      modifications if the descendant schema node identifiers are      substituted for k_1, k_2, ..., k_n.   o  The message appearing as the text of <sch:report> is different:      "Violated uniqueness for list CONTELEM".Appendix A:-----------OLD  <define name="unique-attribute">    <optional>      <attribute name="nma:unique">        <list>          <data type="token"/>        </list>      </attribute>    </optional>  </define>

It should say:

Table of Contents-----------------NEW      12.16. The <nma:unique> Annotation ..............................74Sec. 5.3, entry in Table 2:---------------------------NEW        | <nma:unique>              | 10.55              |      |Sec. 10.55:-----------NEW   This statement is mapped to the <nma:unique> element.  ARGUMENT MUST   be translated so that every node identifier in each of its components   is prefixed with the namespace prefix of the local module, unless the   prefix is already present.  The result of this translation then   becomes the value of the @tag attribute which is attached to the   <nma:unique> element.   For example, assuming that the local module prefix is "ex",   unique "foo ex:bar/baz"   is mapped to the following annotation element:   <nma:unique tag="ex:foo ex:bar/ex:baz"/>Sec. 11.2, second paragraph:----------------------------NEW   In a Schematron schema generated by the second mapping step, the   basic unit of organization is a rule represented by the <sch:rule>   element.  The following NETMOD-specific annotations from the hybrid   schema (henceforth called "semantic annotations") are mapped to   corresponding Schematron rules: <nma:must>, <nma:unique>, @nma:key,   @nma:max-elements, @nma:min-elements, @nma:when, @nma:leafref, @nma:   leaf-list, and also @nma:mandatory appearing as an attribute of <rng:   choice> (see Section 11.2.1).Sec. 12.16 (including its title):---------------------------------12.16.  The <nma:unique> Annotation   The mapping of this annotation is similar to @nma:key,   see Section 12.8, with two small differences:   o  The value of the @tag attribute of <nma:unique> is a list of      descendant schema node identifiers rather than simple leaf names.      However, the XPath expressions specified in Section 12.8 work      without any modifications if the descendant schema node      identifiers are substituted for k_1, k_2, ..., k_n.   o  The message appearing as the text of <sch:report> is different:      "Violated uniqueness of NODES", where NODES is the value of the      @tag attribute.Appendix A:-----------NEW  <define name="unique-element">    <element name="nma:unique">      <attribute name="tag">        <list>          <data type="token"/>        </list>      </attribute>    </element>  </define>

Notes:

The 'unique' YANG statement, which is a substatement of 'list', has the cardinality of "0..n". Multiple sibling 'unique' statements cannot be mapped to a single @nma:unique attribute in the hybrid schema. Therefore, an XML element, <nma:unique>, has to be used for mapping the 'unique' statement instead of the attribute, much like the it is done for the 'must' statement.

This change to the mapping of the 'unique' statement is realized by changing the text of Section 10.55. Several other sections are also affected by this change.

Report New Errata