[YANGTOOLS-862] yang.common.QName is a YANG identifier Created: 12/Mar/18  Updated: 20/Jul/21  Resolved: 25/Feb/19

Status: Resolved
Project: yangtools
Component/s: parser
Affects Version/s: None
Fix Version/s: 3.0.0

Type: Bug 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


 Description   

This has cropped up from MDSAL-309 and MDSAL-300, when Binding V1 is creating Java identifiers from QName.localName(). Due to historic reasons coming from SchemaNode design, localName() is quite permissive in what it accepts and hence MD-SAL considers a lot of crud, line spaces in BindingMapping.getClassName() – which is fed solely through YANG Identifiers.

Clarifying a YANG Identifier localName() contract, it's relationship to XML localNames used by XML parser would be useful – especially in the are of anyxml/anydata content.



 Comments   
Comment by Robert Varga [ 12/Jun/18 ]

QName should represent a YANG identifier, with JSON/XML parsers using a different construct if they really need to.

Comment by Robert Varga [ 03/Aug/18 ]

With the question resolved, this becomes a Bug to be addressed in 3.0.0.

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