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

Move more properties to the "Glossary"; rename to "Core Concepts"? #948

Open
roll opened this issue Jun 25, 2024 · 2 comments
Open

Move more properties to the "Glossary"; rename to "Core Concepts"? #948

roll opened this issue Jun 25, 2024 · 2 comments
Labels

Comments

@roll
Copy link
Member

roll commented Jun 25, 2024

Overview

As a consequence of the organic growth of the Standard usage we got a situation where we reference some properties from other specs e.g.:

We just need to move common ones into the Glossary and reference them from there

@roll roll added the docs label Jun 25, 2024
@roll roll modified the milestone: v2.1 Oct 28, 2024
@nichtich
Copy link
Contributor

nichtich commented Dec 13, 2024

The formal role of the glossary should be made more clear. Is it documentation to explain basic concepts? Is it specification with formal definition of data elements? For the latter the term "glossary" should better be replaced by some other name, e.g. "Core Concepts".

@roll
Copy link
Member Author

roll commented Dec 16, 2024

@nichtich
The "Glossary" is intended to be a spec as it defines building blocks for other specs that requires to be on the same level of formality (e.g. regarding changes etc)

I agrees that "Core Concepts" or similar might be a better name

@roll roll changed the title Move more properties to the Glossary Move more properties to the "Glossary"; rename to "Core Concepts"? Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants