-
Notifications
You must be signed in to change notification settings - Fork 63
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
7.2 Transformation to JSON-LD & RDF seems unnecessary #444
Comments
Thank you, @msporny, for your review and apologies for not attending today's call. Looking back at the section, it deserves further case. Yet, I don't think we should completely remove it from the spec.
The algorithm presented in Section 7.2 is a transformation from JSON to RDF, not the contrary. The main use case is the integration of TD documents with contextual info in a large RDF store. I can remove references to the "bidirectionality" of the transformation. We haven't tested it in fact.
Is there a way to keep |
In tomorrow's TD web conference we should discuss the new option that @msporny was recommended to us:
Pro:
Con:
Something else? |
To add to the Con list:
The bidirectionality of the transformation is important for serving TD documents from the Thingweb Directory. Of course, I can live without and implement something non-standard to fit the Directory's needs but I do think it is a good practice to make every bit of a TD identifiable. I would thus suggest to keep this section, at least for the JSON Pointer part. |
A side note:
This assertion may remain in the spec, I think its main purpose is to simplify the implementation work and avoid confusion with standard terms. It is not exactly a JSON-LD limitation. |
also see discussion within JSON-LD 1.1 repo w3c/json-ld-api#65 |
During 3/1 Thing Description TF teleconference, in order to hedge against potential risks, the TD TF noted we should probably keep this section. At the same time, the followings were suggested.
|
You'll find a transcript of our discussion with the JSON-LD group here. In summary: the feature we were asking for will be added to the JSON-LD syntax spec in the coming weeks (first as a draft). |
TD spec was updated by @vcharpenay and introduced the usage of JSON-LD 1.1 as serialization option. Please review. |
The entirety of Section 7.2 Transformation to JSON-LD & RDF feels unnecessary for at least one of these reasons:
I suggest an immediate review by the JSON-LD WG for the spec as there are a number of areas in the specification that could benefit from their input, AFAICT.
The text was updated successfully, but these errors were encountered: