[MDSAL-675] Generate structures for RFC8040 yang-data extensions Created: 09/Jul/21 Updated: 14/Feb/23 Resolved: 01/Feb/23 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | Binding codegen |
| Affects Version/s: | None |
| Fix Version/s: | 11.0.5 |
| Type: | New Feature | Priority: | High |
| Reporter: | Robert Varga | Assignee: | Ruslan Kashapov |
| Resolution: | Done | Votes: | 0 |
| Labels: | pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Epic Link: | MD-SAL patch | ||||||||||||||||||||||||||||||||||||
| Description |
|
RFC8040 has defined a new language extension, yang-data, which allows defining free-standing structures in YANG. Add a mapping of these structures to Java, similar to other YANG constructs. The result should be similar to a top-level container, except it should not use 'ChildOf', but rather be a free-standing. In terms of namespace collision handling, this construct should be secondary only to schema tree statements, i.e. in case of a conflict with grouping/identity, those should be displaced. A reasonable suffix needs to be assigned as well. Note that these extensions are superseded with more flexible RFC7891 Yang Structure extensions – and when we implement them, they should map to the same Java construct. |
| Comments |
| Comment by Robert Varga [ 29/Aug/21 ] |
|
While we can package RFC8639 model, we really need the structures defined as yang-data to be able to implement this in a reasonable fashion. |
| Comment by Robert Varga [ 16/Dec/22 ] |
|
Runtime parts need to be delivered separately, as they depend on |