ISSUE-162: Michael Pizzo: Attempt to converge markup mechanisms for OData and JSON-LD
OData/JSON-LD Convergence
Michael Pizzo: Attempt to converge markup mechanisms for OData and JSON-LD
- State:
- CLOSED
- Product:
- JSON-LD Candidate Recommendation
- Raised by:
- Manu Sporny
- Opened on:
- 2013-10-22
- Description:
- This issue was raised by Michael Pizzo, from Microsoft:
JSON-LD, OData’s JSON format, and other formats built on JSON are trying to do very similar things (add “markup” to a JSON payload for things like ids, types, etc.). Unfortunately, since JSON doesn’t define a way to differentiate properties from markup, each specification invents its own naming conventions to differentiate properties from markup.
We have a real opportunity to align efforts here in defining a common convention for marking up JSON payloads.
The rest of the request can be found here:
http://lists.w3.org/Archives/Public/public-linked-json/2013Aug/0107.html - Related Actions Items:
- No related actions
- Related emails:
- Official response to ISSUE-162: Attempt to converge markup mechanisms for OData and JSON-LD (from msporny@digitalbazaar.com on 2013-10-22)
- RDF-ISSUE-162 (OData/JSON-LD Convergence): Attempt to converge markup mechanisms for OData and JSON-LD [JSON-LD Candidate Recommendation] (from sysbot+tracker@w3.org on 2013-10-22)
Related notes:
Michael Pizzo joined the JSON-LD CG telecon to discuss the OData/JSON-LD alignment and it was agreed that no changes to JSON-LD 1.0 are necessary at this stage. Community members will try come up with a proof-of-concept that shows a JSON-LD document using OData keywords that can be interpreted by either system.
http://json-ld.org/minutes/2013-10-08/#topic-1
Display change log