[yang-tooling] Re: SID file issues / .sid file differences in pyang and core-wg/pyang

[Carsten Bormann <[e-mail]>]

On Feb 5, 2026, at 11:03, Esko Dijk <esko.dijk=[e-mail]> wrote:
> 
> I was trying to confirm that this is correct and that the sender can arbitrarily select which names to substitute, e.g. a subset.

Section 7 of RFC 9254 defines three content types (parameterized media types):

   *  application/yang-data+cbor; id=sid -- for use by applications that
      need to be frugal with encoding space and text string processing
      (e.g., applications running on constrained nodes [RFC7228] or
      applications with particular performance requirements);

   *  application/yang-data+cbor; id=name -- for use by applications
      that do not want to engage in SID management and that have ample
      resources to manage text-string-based item identifiers (e.g.,
      applications that directly want to substitute application/
      yang.data+json with a more efficient representation without any
      other changes); and

   *  application/yang-data+cbor -- for use by more complex applications
      that can benefit from the increased efficiency of SID identifiers
      but also need to integrate databases of YANG modules before SID
      mappings are defined for them.

   All three content-types are based on the same representation
   mechanisms, parts of which are simply not used in the first and
   second cases.


I think your arbitrary selection fits with the third case (note that the text behind the dashes are use cases and not the defining characteristics of these content types). 

Grüße, Carsten