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

[Andy Bierman <[e-mail]>]

On Thu, Feb 5, 2026 at 7:27 AM Carsten Bormann <[e-mail]> wrote:

> On Feb 5, 2026, at 16:23, Andy Bierman <[e-mail]> wrote:
> >
> > Using strings means only the local-name (or modname:local-name) is used
> in the identifier.
> > This has the same property as XML and JSON (identifier is only
> meaningful within a parent node).
>
> Since the parent node is not necessarily identified, the name actually
> does include the (global) module name; this can only be elided for a name
> path component if it is the same as a preceding name path component.
> I’m not sure I fully understand what a local name is (a name involving a
> module prefix?  These aren’t used in YANG-CBOR).
>
>
The term is used in XML.  The name format uses 'node-identifier' from RFC
7950
except prefix is really module-name.


   absolute-schema-nodeid = 1*("/" node-identifier)

   node-identifier     = [prefix ":"] identifier

Does anybody implement the first 2 forms of the media-type?

application/yang-data+cbor; id=sid
application/yang-data+cbor; id=name

We only implement application/yang-data+cbor.
If a schema node has a SID assigned then send it, otherwise send the name.
If a SID is received, look it up, otherwise expect a name and find the
child of the current parent.

If the sender uses id-sid and sends a name, is the receiver supposed to
reject the message as not valid?


Andy




> Grüße, Carsten
>
>