RFC9595: More exotic `identifier`s format

[vvilimek]

For given module:

module example {
  yang-version 1.1;
  prefix e;
  namespace "http://example.com";

  import ietf-restconf {
    prefix rc;
  }

  rc:yang-data ydata {
    container msg {
      leaf proto-version { type uint16; }
      leaf payload-len { type uint32; }
    }
  }
}

Should the item identifier look like:

{
  "ietf-sid-file:sid-file": {
    "name": "example"
    "item": [
      {
        "namespace": "data",
        "identifier": "/example:ydata/msg",
        "sid": "60000",
      }
    ]
  }
}

or like this:

{
  "ietf-sid-file:sid-file": {
    "name": "example"
    "item": [
      {
        "namespace": "data",
        "identifier": "/example:msg",
        "sid": "60000",
      }
    ]
  }
}

[vvilimek]

Based on email from Kent Watsen:

The rc:yang-data is not part of the schema tree, and also:

RFC7950: The YANG 1.1 Data Modeling Language; section 6.5

6.5. Schema Node Identifier

A schema node identifier is a string that identifies a node in the
schema tree. It has two forms, "absolute" and "descendant", defined
by the rules "absolute-schema-nodeid" and "descendant-schema-nodeid"
in Section 14, respectively. A schema node identifier consists of a
path of identifiers, separated by slashes ("/"). In an absolute
schema node identifier, the first identifier after the leading slash
is any top-level schema node in the local module or in an imported
module.

References to identifiers defined in external modules MUST be
qualified with appropriate prefixes, and references to identifiers
defined in the current module and its submodules MAY use a prefix.

For example, to identify the child node "b" of top-level node "a",
the string "/a/b" can be used.

Right now, it looks like the option with "identifier": "/example:msg", is correct.

The question is what to do with sx:structure struct because the RFC8791: YANG Data Structure Extensions does not meantion "schema tree" anywhere.

[vvilimek]

An example with rc:yang-data and sx:structure would be great.

[vvilimek]

ML discussion