- From: Jose M. Alonso <josema.alonso@fundacionctic.org>
- Date: Fri, 26 Nov 2010 08:37:41 +0100
- To: Jim Hendler <hendler@cs.rpi.edu>
- Cc: Ed Summers <ehs@pobox.com>, Chris Beer <chris@e-beer.net.au>, "public-egov-ig@w3.org" <public-egov-ig@w3.org>
Same here at CTIC various Open Data projects in Spain. I don't see any problem with adding JSON. Probably the only issue is that the document dates already back to more than a year ago, it's still a WD in progress (so to say since we didn't update it at all since then) and needs a review, an update and to be published as a Group Note. As usual, we would need IG volunteers to do so. -- Josema El 26/11/2010, a las 04:16, Jim Hendler escribió: > 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 07:38:19 UTC