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

type should be provided always in TD #258

Closed
jmcanterafonseca opened this issue Oct 23, 2018 · 1 comment
Closed

type should be provided always in TD #258

jmcanterafonseca opened this issue Oct 23, 2018 · 1 comment
Labels
Propose closing Problem will be closed shortly if there is no veto.

Comments

@jmcanterafonseca
Copy link

jmcanterafonseca commented Oct 23, 2018

I think that for a matter of cleanliness "type" term should be provided not only in TD expressed in JSON-LD but also in JSON.

Also it would be good to define a mapping in the @context "type": "@type".

By the way it seems that in certain JSON-LD serialisation examples is included

https://www.w3.org/TR/wot-thing-description/#ex-19-mylampthing-with-semantic-annotations-based-on-a-valid-json-ld-1-1-representation

but not in others

https://www.w3.org/TR/wot-thing-description/#thing-description-as-json-ld-1-1-serialization

so there is some lack of consistency in the current published draft.

Recommendation: Define a mapping "type": "@type" in the @context. Use "type" always, both in the JSON and JSON-LD Representation of a Thing Descriptor.

@sebastiankb
Copy link
Contributor

Based on the Lyon meeting we cannot follow JSON-LD 1.1 anymore. The TD offers now an own format with the opportunity of a transformation to JSON-LD 1.0.

The type term in the TD is based on JSON Schema and has a different meaning as the @type from JSON-LD.

@sebastiankb sebastiankb added the Propose closing Problem will be closed shortly if there is no veto. label Mar 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Propose closing Problem will be closed shortly if there is no veto.
Projects
None yet
Development

No branches or pull requests

2 participants