-
Notifications
You must be signed in to change notification settings - Fork 25
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
Disallow changing prefix of binding ontology #239
Comments
I was wondering if there is some kind of registry for well-known prefixes for JSON-LD. If not, maybe it would make sense to at least define a WoT-specific registry to keep track of all defined prefixes and to avoid conflicts in the future? |
I think it would make sense to at least track the ones we are specifying in our deliverables. Then, I would say that we can track the popular ones separately and avoid using them. |
I think here is where we see the limitations of thinking that "JSON-LD is just JSON". Forcing a specific prefix limits the flexibility of our TDs as a JSON-LD processor would happily understand another naming, but we can't allow for this flexibility otherwise all other JSON-only parsers will fail. I'm definitely in favor of this, I also don't know if any of the current implementations are really able to treat a Thing Description as a JSON-LD document. For example, node-wot doesn't (he wouldn't understand |
I have checked with the WoT developers inside Siemens and this direction is also appreciated. The ontologies we specify can have this rule but of course, other ontologies should be allowed and stay flexible. |
Call of 22.02:
|
Also see w3c/wot-charter-drafts#57 |
Call of 05.04:
|
Call of 08.02:
In order to allow TD parsers that do not have JSON-LD processing capability, it would be good to make sure that a binding is always declared with the same prefix. This would allow the parser to simply check for "
htv:methodName"
instead of resolving the context.Everyone in the call seems to be in favor of this, any other opinions?
The text was updated successfully, but these errors were encountered: