ISSUE-22: Need to normatively reference and recommend JSON-LD
json-ld
Need to normatively reference and recommend JSON-LD
- State:
- CLOSED
- Product:
- Linked Data Platform Spec
- Raised by:
- Steve Speicher
- Opened on:
- 2012-10-08
- Description:
- Consider making JSON-LD [1] a SHOULD for all operations.
[1] http://www.w3.org/TR/json-ld-syntax/ - Related Actions Items:
- No related actions
- Related emails:
- LDP Rec (from eric@w3.org on 2015-02-20)
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from ashok.malhotra@oracle.com on 2013-04-05)
- Re: Review and Comments for Linked Data Platform FPWD (from david@3roundstones.com on 2013-03-05)
- Re: Review and Comments for Linked Data Platform FPWD (from sspeiche@gmail.com on 2013-03-04)
- Edits done for: ISSUE-22, ISSUE-23: changed sections 4.2.3 and 5.4.7. Removed closed issues. (from sspeiche@us.ibm.com on 2012-11-03)
- Review and Comments for Linked Data Platform FPWD (from david@3roundstones.com on 2012-10-28)
- ldp-ISSUE-22 (json-ld): Need to normatively reference and recommend JSON-LD [Linked Data Platform core] (from sysbot+tracker@w3.org on 2012-10-08)
Related notes:
<cygri> RESOLVED: Servers MUST support Turtle; servers MAY deliver other formats using standard HTTP content negotiation; If the client doesn't indicate a preference, Turtle MUST be returned
http://www.w3.org/2012/ldp/meeting/2012-11-01#ISSUE__2d_22_and_ISSUE__2d_23___28_RDF__2f_XML_and_JSON__2d_LD__29_
Display change log
