[on-listing Alexandre's mail on his green light] [On contexts] On Wed, Aug 24, 2011 at 18:10, Alexandre Passant <alex@seevl.net> wrote: > I guess that the link to an external @context could do the job. You > can also have this context automatically generated by the app, that's > how we're doing it in Seevl. > From my POV, removing all CURIES from the JSON itself, and > keeping namespaces only in the context (ideally in an external > document, so that the "data file" is completely namespace-less, as > RDFa profiles) is the best way to reach Web-dev that are not semweb > geeks. And the way RDF should go to have a JSON serialisation (and RDF > data !) that can reach the masses. I also have brain stormed the following idea, documented in a tweet [1]: "Link headers, the mullet of the Web: business in the front, party in the back. Idea: serve #JSON, make it #jsonLD by a @context Link header." > NB: This reply can be public if needed I think it makes sense to have this discussion on-list. Best, Tom [1] http://twitter.com/tomayac/status/106304670464606208 -- Thomas Steiner, Research Scientist, Google Inc. http://blog.tomayac.com, http://twitter.com/tomayacReceived on Wednesday, 24 August 2011 16:20:06 UTC
This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:02:00 UTC