https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/YANGTOOLS-783 yangtools <p>While <a href="https://tools.ietf.org/html/rfc6020#section-9.13" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/rfc6020#section-9.13</a> requires instance identifiers to have keys,<br/> it would be useful to be able to parse unkeyed ids to YII and then II (both support wildcards).</p> <p>Simplest solution would be to make JSONStringInstanceIdentifierCodec accept<br/> wildcard instance identfiers.</p> <p>Example use case would be to define processing order for yang nodes in human friendly format, e.g.:</p> <p>/ietf-interfaces:interfaces/interface -&gt; /v3po:bridge-domains/bridge-domain</p> <p>Operating System: All<br/> Platform: All</p> YANGTOOLS-783

Add support for parsing wildcard instance identifiers to JSON codec

New Feature Confirmed Unresolved Unassigned Marek Gradzki Wed, 7 Jun 2017 09:57:42 +0000 Sun, 10 Apr 2022 18:35:59 +0000 0 3 <p>Would Boron-SR4 be possible provided:</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/58386/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/58386/</a></p> <p>does the right job?</p> <p>Right, but where would that be used? Note that wildcards are an accidental feature and we certainly do not want to break compliance here.</p> <p>We need such utility in honeycomb (we want to let users define node processing order via text files). <br/> JSON format is simplest one.</p> <p>In my opinion this change does not break compliance with RFC, just extends it.</p> <p>But I agree that perhaps JSONStringInstanceIdentifierCodec is not the best place for adding this functionality. </p> <p>After closer look at RFC, absolute schema node identifier to wildcard InstanceIdentifier is something we need. And it looks like yangtools provides some utils for parsing them...</p> Development External issue ID 8616 External issue URL Issue Type ODL SR Target Milestone Rank 0|i029cv: