There is a slight difference between how instance-identifiers are encoded in https://tools.ietf.org/html/draft-lhotka-netmod-yang-json-02 (used by draft-bierman-netconf-restconf-02) and https://tools.ietf.org/html/rfc7951 (used by RFC8040).
For RFC8040 we need to use a different JSON codec to handle prefixes.
While we are in the area, I suspect key encoding does not work correctly (for both XML and JSON) with respect to complex types – i.e. when we are encoding an instance identifier which uses one of:
- empty
- identityref
- instance-identifier
as type of a key leaf.
- blocks
-
NETCONF-494 Fix RFC8040 instance identifier formatting
- Resolved
- is blocked by
-
YANGTOOLS-758 yang-data-codec-xml: reuse codecs across documents
- Resolved
-
YANGTOOLS-759 yang-data-codec-gson: fix JSONCodecFactory caching
- Resolved
- is duplicated by
-
YANGTOOLS-782 JSONStringInstanceIdentifierCodec fails to lookup subsequent module prefix if not explicitly given
- Resolved
- relates to
-
YANGTOOLS-678 [Yang 1.1] Allow type "empty" in a key
- Resolved