- From: Jim Hendler <hendler@cs.rpi.edu>
- Date: Thu, 25 Nov 2010 22:16:06 -0500
- To: Ed Summers <ehs@pobox.com>
- Cc: Chris Beer <chris@e-beer.net.au>, "public-egov-ig@w3.org" <public-egov-ig@w3.org>
In fact, Data.gov also does this through the linked data stuff hosted at RPI - we use various combinations of JSON, HTML and straight RDF in the various mashups, Sent from my iPhone On Nov 25, 2010, at 22:09, Ed Summers <ehs@pobox.com> wrote: > On Thu, Nov 25, 2010 at 6:36 PM, Chris Beer <chris@e-beer.net.au> wrote: >> True - should get a mention. Open standard too so no issues there. Example use case would be good too. > > I agree. JSON is another good example of a widely deployed web > standard for data (RFC 4627) that really ought to be discussed in the > context of best practices for web access to egov data. Some of the > folks involved in data.gov.uk effort have worked specifically on using > JSON to provide more familiar access to pools of RDF made available at > SPARQL endpoints [1]. > > """ > For some web developers the need to understand the RDF data model and > associated serializations and query language (SPARQL) has proved a > barrier to adoption of linked data. This project seeks to develop > APIs, data formats and supporting tools to overcome this barrier. > Including, but not limited to, accessing linked data via a > developer-friendly JSON format. > """ > > //Ed > > [1] http://purl.org/linked-data/api/project >
Received on Friday, 26 November 2010 03:18:04 UTC