Move normative XML encoding rules into its own RFC

netmod-wg / yang-next

Feature requests for future versions of YANG

6 stars 0 forks source link

Move normative XML encoding rules into its own RFC #10

Open kwatsen opened 7 years ago

kwatsen commented 7 years ago

The YANG RFC is littered with XML encoding rules (see table of contents).

These should be factored out into another document like RFC 7951.

schoenw commented 6 years ago

See my comment on a related issue.

kwatsen commented 6 years ago

Idea is to convert examples from NC/RC to XML/JSON

schoenw commented 6 years ago

This last comment does not make sense. Yes, perhaps there are situations where NETCONF details can be removed, but you do not convert from NC to XML/JSON (and there is no RC anyway). I am also against using different encodings in examples or worse to duplicate examples. This adds noise but not value.

mbj4668 commented 5 years ago

See also #56. The lexicographic representation of instance-identifiers are defined only in terms of XML.

abierman commented 1 month ago

I do not think this rewrite is an improvement at all.

https://www.ietf.org/archive/id/draft-yn-netmod-rfc7950bis-00.html

https://datatracker.ietf.org/doc/html/draft-yn-netmod-yang-xml-00

the base doc is harder to understand
the XML examples seem to cut-and-paste a lot from 7950

No need to refactor at all. Add explanation that JSON and CBOR encoding are supported in other RFCs