Skip to content

Add section about derived types #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vvilimek wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add section about derived types #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions draft-bormann-cbor-yang-standin.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -377,6 +377,21 @@ otherwise it SHOULD keep the legacy representation.
If a decoder receives data for a union-typed node, it MUST accept any data type
of the union, even though it may violate additional constraints outside the schema.

## Derived types and indirection

When a stand-in tag type is used as a base type of some derived type
the rules for stand-in tag apply. If the derived type has some restrictions those
restrictions also apply.

If the target type of leafref is a stand-in tag typed the stand-in tag rules also apply.

TO DO: Is the following section useful? Doesn't it make the specification too complex?

The author YANG model may require to use the legacy representation over the efficient
stand-in representation. Then the description of the specific place, where this applies,
needs to clearly and explicitly state that this derived type should not be encoded according
to the stand-in rules.

# Using Stand-In Tags

## Defining Stand-In Usage in Schema
Expand Down