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-993 yangtools <p>Opaque metadata needs slightly different translation than NormalizedMetadata, due to two reasons:</p> <ul> <li>the exact QNameModule binding is not necessarily available in the SchemaContext which is parsing opaque anydata – XML has URI reference and JSON has module name, thus complicating addressing</li> <li>values for NormalizedMetadata are required to be native, whereas opaque metadata holds either Strings or Numbers</li> </ul> <p>Refactor current definitions to account for this difference.</p> <p> </p> YANGTOOLS-993

Separate Normalized and Opaque metadata

New Feature Medium Resolved Done Robert Varga Robert Varga Tue, 21 May 2019 14:27:51 +0000 Mon, 27 May 2019 12:26:56 +0000 Mon, 27 May 2019 12:26:56 +0000 3.0.1 data-impl 0 1 <p>This rework actually shows that opaque anydata node is not feasible, as interpreting QNames and InstanceIdentifiers requires XML parsing context. The focus of this issue is to refactor the code so that opaque anydata nodes are captured in DOMSource, just like anyxml nodes.</p> <p>The mechanism to normalize such anydata nodes is subject of <a href="https://jira.opendaylight.org/browse/YANGTOOLS-995" title="Add support for normalizing Anydata" class="issue-link" data-issue-key="YANGTOOLS-995"><del>YANGTOOLS-995</del></a>.</p> Development Epic Link YANGTOOLS-777 Rank 0|i03nwn: