Hi Jürgen, > On 2020-04-08, at 08:57, Juergen Schoenwaelder > <[email protected]> wrote: > > COMI defines: > > application/yang-data+cbor > application/yang-identifiers+cbor > application/yang-instances+cbor > > It seems that yang-data+cbor really is yang-data+cbor+sid
(We couldn’t use that syntax for the media type name, as +sid is not a structured syntax suffix, but I get the point.) One way to build a content-type from a media-type name is to add a parameter: application/yang-data+cbor; id=name application/yang-data+cbor; id=sid (In the CoAP content-format those content types would just be two different content-format numbers.) But we could also encode that parameter in the media type name. We would have to end the media type name with “+cbor”, because that is the structured syntax suffix that applies. > and it seems > there is no media type for yang-data+cbor+names (i.e., the CBOR > encoding that uses names instead of SIDs as keys). The other two media > types yang-identifiers+cbor and yang-instances+cbor seem to be COMI > specific. Hence, me preference would be to define something like > > application/yang-data+cbor+sid > application/yang-data+cbor+name > > in YANG-CBOR That would put the normative reference to -sid back into YANG-CBOR. Yes, we could do that. Grüße, Carsten PS.: The terminology for media types is a mess^W^W underdeveloped; see the expired https://tools.ietf.org/html/draft-bormann-core-media-content-type-format-01.txt for more info. > and to leave the other two > > application/yang-identifiers+cbor > application/yang-instances+cbor > > for COMI. _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
