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

When do we use "sdfXxx", when do we use "xxx"? #11

Open
cabo opened this issue Dec 21, 2020 · 5 comments
Open

When do we use "sdfXxx", when do we use "xxx"? #11

cabo opened this issue Dec 21, 2020 · 5 comments

Comments

@cabo
Copy link
Member

cabo commented Dec 21, 2020

To get a consistent usage of terms, we probably should describe when we are prefixing new terms with "sdf" and when we don't.

@WAvdBeek
Copy link
Contributor

a long time ago we decided to prefix new things that are not available in JSON schema. I think this still holds.

@cabo
Copy link
Member Author

cabo commented Jan 12, 2021

That would be one way to do this, but if we wanted to do this consistently, we'd have to prefix

unit scaleMinimum scaleMaximum readable writable observable nullable contentFormat subtype

as well.

@WAvdBeek
Copy link
Contributor

maybe we should not have a mechanism, but just list what the deviations are with JSON
we could add another column in here:
https://onedm.org/terminology/

@nwidell
Copy link
Member

nwidell commented Mar 14, 2022

Consistency rule, needed for 2.0 but not now

AK: what if JSON schema reuses any of our terms? eg things that might have different semantics.
CB: we are very specific with the terms we used
MJK: might be a conflict later

@cabo cabo added the 1.next label Apr 20, 2022
@akeranen
Copy link
Collaborator

Out of the list above seems contentFormat might be (future?) conflict. Need to check status of that with JSO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants