abierman
commented
8 years ago On Sat, Jun 11, 2016 at 1:17 PM, Sean Leonard dev+ietf@seantek.com wrote:
YANG is not an encoding format. It is a schema language. Instance documents conforming to YANG schema are encoded in XML or JSON.
That confirms my suspicion. So, these proposed media type(s) should have +xml, +json, or nothing (as structured syntax suffixes are optional, they are really intended more as a hint to intermediate decoders such as debugging tools). They should not have +yang.
Yah, having just spent some quality time with RFC 6090 over the weekend, I concur.
And to answer mnot's question, yep, the period needs to go.
YANG is attempting to register a number of media types that begin with "application/yang."; see: https://tools.ietf.org/html/draft-ietf-netconf-yang-patch-08#section-4.2 https://tools.ietf.org/html/draft-ietf-netconf-restconf-13#section-11.3
E.g., it calls "application/yang.api" a "subtype" of "application/yang".
I read RFC6838 to prohibit this, because the portion of a subtype preceded by the first "." indicates the registration tree in a facet, and faceted media types are prohibited from being registered in the standards tree (unless they're grandfathered in in Appendix A). Furthermore, the drafts' use of "subtype" is erroneous.
Is that understanding correct? If so, should they be using different media types, or is there some other way to accommodate what they want?