-
Notifications
You must be signed in to change notification settings - Fork 11
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
Comments
a long time ago we decided to prefix new things that are not available in JSON schema. I think this still holds. |
That would be one way to do this, but if we wanted to do this consistently, we'd have to prefix
as well. |
maybe we should not have a mechanism, but just list what the deviations are with JSON |
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. |
Out of the list above seems contentFormat might be (future?) conflict. Need to check status of that with JSO. |
To get a consistent usage of terms, we probably should describe when we are prefixing new terms with "sdf" and when we don't.
The text was updated successfully, but these errors were encountered: