[YANGTOOLS-993] Separate Normalized and Opaque metadata Created: 21/May/19  Updated: 27/May/19  Resolved: 27/May/19

Status: Resolved
Project: yangtools
Component/s: data-impl
Affects Version/s: None
Fix Version/s: 3.0.1

Type: New Feature Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: Anydata Support

 Description   

Opaque metadata needs slightly different translation than NormalizedMetadata, due to two reasons:

  • 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
  • values for NormalizedMetadata are required to be native, whereas opaque metadata holds either Strings or Numbers

Refactor current definitions to account for this difference.

 

 Comments   
Comment by Robert Varga [ 23/May/19 ]

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.

The mechanism to normalize such anydata nodes is subject of YANGTOOLS-995.

Generated at Wed Feb 07 20:54:53 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.