Skip to content
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.

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

edits to reflect that we are defining two models, not one #71

Merged
merged 1 commit into from Jun 13, 2023

Conversation

boucadair
Copy link
Contributor

and other minor fixes

@boucadair boucadair added WGLC comment received during WGLC editorial labels May 30, 2023
@fno2010
Copy link
Member

fno2010 commented May 30, 2023

Is there any guideline about the usage of the term "data model"? Is it equivalent to a "YANG module" or a top-level container in YANG? Although this document defines two YANG modules, they share a single top-level container.

@boucadair
Copy link
Contributor Author

Is there any guideline about the usage of the term "data model"? Is it equivalent to a "YANG module" or a top-level container in YANG?

I'm not aware of any, other than the entries in RFC6020:

RFC 6020 defines:

    o  data model: A data model describes how data is represented and
       accessed.

    o  module: A YANG module defines a hierarchy of nodes that can be
       used for NETCONF-based operations.  With its definitions and the
       definitions it imports or includes from elsewhere, a module is
       self-contained and "compilable".

That's said, we need to be consistent in our use. For example, we do already have this in the title:

"YANG Data Models for the Application-Layer Traffic Optimization (ALTO).."

@fno2010 fno2010 merged commit f3b5ef9 into main Jun 13, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial WGLC comment received during WGLC
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants