Re: [media-types] Subtypes and registration trees

[Benoit Claise <[e-mail]>]

On 6/17/2016 2:59 PM, Sean Leonard wrote:
> On 6/17/2016 4:42 AM, Andy Bierman wrote:
>>
>>
>> On Fri, Jun 17, 2016 at 12:36 AM, Benoit Claise <[e-mail] 
>> <mailto:[e-mail]>> wrote:
>>
>>     I'm not sure what the conclusion is regarding this email thread?
>>     Also, it should be time to include the NETCONF community on this
>>     topic.
>>     Why not an email thread with both netconf and media-types?
>>
>>
>> I am changing the media type name so that faceted names are not used.
>>
>> yang.foo becomes yang-foo
>>
>> The IANA registration section is being redone to conform to RFC 6838
>>
>
> application/yang.foo -> application/yang-foo
>
> corrects the faceted name problem, yes.
>
> However, the other point has not been addressed. I do not see a 
> technical reason or justification for registering 8 media types, when 
> application/yang; yangtype="foo" (api, data, datastore, errors, 
> operation, stream, patch, patch-status) suffices. Please address.
Is this a constraint imposed by the media-type designated expert or a 
preference?
Maybe this is mentioned by one of the RFCs at 
http://www.iana.org/assignments/media-types/media-types.xhtml? Sorry I 
have not read them all.
If a preference, then it should be discussed on the NETCONF mailling list.

Regards, Benoit


>
> Best regards,
>
> Sean
>
>>
>>
>>     Regards, B.
>>
>>
>> Andy
>>
>>>
>>>
>>>     On Thu, Jun 9, 2016 at 7:34 PM, Mark Nottingham <[e-mail]>
>>>     wrote:
>>>
>>>
>>>         > On 10 Jun 2016, at 12:15 PM, Sean Leonard
>>>         <[e-mail] <mailto:[e-mail]>> wrote:
>>>         >
>>>         > When it comes to Internet media types, "subtype" refers to
>>>         everything after the "/" and "type" refers to everything
>>>         prior to the "/".
>>>         >
>>>         > The field "Subtype name" is a field in the media type
>>>         registration template--its usage in those drafts is correct.
>>>
>>>         Even:
>>>
>>>         """
>>>         The parent MIME media type for RESTCONF resources is
>>>         application/yang, which is defined in [RFC6020].  This
>>>         document defines the following sub-types for this media type.
>>>         """
>>>
>>>         ? That seems to read as if "application/foo.bar" is a
>>>         subtype of "application/foo".
>>>
>>>
>>>
>>>     I can see from RFC 6838, 4.2 that we named all of our media
>>>     types incorrectly.
>>>
>>>     The media type application/yang just refers to UTF-8 text that
>>>     represents a YANG
>>>     module or submodule. It is expected to conform to the YANG syntax.
>>>
>>>     https://tools.ietf.org/html/rfc6020#section-14.1
>>>
>>>     We are incorrectly using this as a tree root for adding subtypes.
>>>
>>>     We want to create media types that conform to a particular YANG
>>>     schema.
>>>     We defined a YANG extension hack to define YANG data structures
>>>     for a media type
>>>     https://tools.ietf.org/html/draft-ietf-netconf-restconf-13#section-8
>>>     (see restconf-media-type)
>>>
>>>     Our IANA section for Media Sub Types is wrong
>>>
>>>     https://tools.ietf.org/html/draft-ietf-netconf-restconf-13#section-11.3
>>>
>>>     It appears we have to make a Media Type registration similar to
>>>     RFC 6020 14.1
>>>     for each of (what we call) the sub-types.
>>>
>>>          application/yang-api
>>>          application/yang-data
>>>          application/yang-datastore
>>>          application/yang-errors
>>>          application/yang-operation
>>>          application/yang-stream
>>>
>>>          application/yang-patch
>>>          application/yang-patch-status
>>>
>>>
>>>     Andy
>>>
>>>
>>>
>>>         >
>>>         > When referring to the construct as a whole, the term
>>>         "media type" is generally used, not "media subtype" or
>>>         "subtype". However, I suppose that "subtype" would be
>>>         technically correct (although not preferred) because
>>>         application/xml (for example) is actually a subtype of
>>>         application. Stylistically it should be called the media
>>>         type application/xml, etc.
>>>         >
>>>         > They should be called application/yang-api,
>>>         application/yang-patch, application/yang-patch-status, etc.
>>>         >
>>>         > I am assuming that YANG is referring specifically to the
>>>         language (akin to saying "C++" or "JavaScript"), and not
>>>         referring specifically to the structured syntax (akin to
>>>         saying "JSON"). If YANG is referring specifically to a
>>>         structured syntax, then the media types should end in +yang.
>>>         My knowledge of YANG is not deep enough to opine further on
>>>         this point.
>>>         >
>>>         > Regards,
>>>         >
>>>         > Sean
>>>         >
>>>         > On 6/9/2016 4:45 PM, Mark Nottingham wrote:
>>>         >> 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?
>>>         >>
>>>         >> Cheers,
>>>         >>
>>>         >>
>>>         >> --
>>>         >> Mark Nottingham https://www.mnot.net/
>>>         >>
>>>         >> _______________________________________________
>>>         >> media-types mailing list
>>>         >> [e-mail] <mailto:[e-mail]>
>>>         >> https://www.ietf.org/mailman/listinfo/media-types
>>>         >
>>>         >
>>>         >
>>>         > _______________________________________________
>>>         > media-types mailing list
>>>         > [e-mail] <mailto:[e-mail]>
>>>         > https://www.ietf.org/mailman/listinfo/media-types
>>>
>>>         --
>>>         Mark Nottingham https://www.mnot.net/
>>>
>>>
>>
>>
>>
>>
>> _______________________________________________
>> media-types mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/media-types
>
>