If you have been paying attention to work being done at the W3C regarding RDF and JSON, you are probably confused. We would be surprised if you weren’t! This post will hopefully clarify the state of RDF and JSON at W3C and suggest what will likely happen next.
The RDF Working Group was chartered to publish an “RDF JSON Syntax Specification” as a W3C Recommendation. The working group subsequently established the JSON RDF Task Force to fulfill that requirement. A number of input documents were identified for that task force, including the RDF JSON specification by Talis and JSON-LD originally by Manu Sporny.
However, JSON-LD matured significantly over the summer and work on the new document based on RDF JSON was not rapid. Thus, we decided in August to reverse our earlier decision and stop work on an RDF JSON-based document for the time being. Specifically, we resolved to “remove the words ‘make a REC on something like Talis RDF/JSON’ from this resolution to allow JSON-LD to further incubate.”
The RDF Working Group is currently waiting in order to let JSON-LD mature. We believe that we have sufficient time in our charter to delay our work on JSON in the hopes that an eventual Recommendation will be useful to the broader developer community. We also do not believe that the RDF Working Group is the best place to work on JSON-LD; the JSON for Linking Data Community Group is already doing a fine job of that.
As always, feedback is welcome on this and other actions by the RDF Working Group by sending mail to email@example.com.
3 thoughts on “The State of RDF and JSON”
Thanks for this update, it’s helpful as the state of things was confusing indeed.
It would be great if you could at some point post a summary of the blocker issues, too. What needs to happen to JSON-LD to be considered official?
Comments are closed.