Re: APIs to work with data on the web

+1 Steven

I think we SHOULD include not just JSON-LD, but ALSO the others RDF
serialization proposals, like Turtle's based languages, RDFa and RDF/XML.

Best,
Ig


2014-03-19 11:57 GMT-03:00 Steven Adler <adler1@us.ibm.com>:

> I agree and support these specifications.  Could we ALSO include JSON-LD
> in our recommendations since many developers prefer to use JSON with Linked
> Data to store data in MongoDB?  In fact, for most Open Data applications
> this is what is used.
>
> http://json-ld.org/
>
>
> Best Regards,
>
> Steve
>
> Motto: "Do First, Think, Do it Again"
>
>
>  From: Ig Ibert Bittencourt <ig.ibert@gmail.com> To: Steven
> Adler/Somers/IBM@IBMUS Cc: Laufer <laufer@globo.com>, "deirdre.lee" <
> Deirdre.Lee@deri.org>, Makx Dekkers <mail@makxdekkers.com>,
> "manuel.carrasco-benitez" <Manuel.CARRASCO-BENITEZ@ec.europa.eu>, Newton
> Calegari <newton@nic.br>, DWBP WG <public-dwbp-wg@w3.org> Date: 03/19/2014
> 10:49 AM Subject: Re: APIs to work with data on the web
> ------------------------------
>
>
>
> Hi Laufer and Steven,
>
> There are two specifications that I think is very interesting to take a
> look. The first one if the Linked Data Platform 1.0 [1], with the Working
> Draft from this month which brings two concepts: The Linked Data Platform
> Container [2], which group several concepts in a container and it can be
> retrieved with only one URI (or IRI) and the Linked Data Platform Paging
> [3] (and editor draft from today), which is exactly for large resources.
>
> Another specification is RDF 1.1 [4] Specification, which provides the
> concept of RDF Dataset and I can combine diferent resources and datasets
> with only one IRI (loog this example [5] in the spec). It is also possible
> to increment new resources to the RDF Dataset by using TriG [6].
>
> [1] *http://www.w3.org/TR/ldp/#bib-LDP-PAGING*<http://www.w3.org/TR/ldp/#bib-LDP-PAGING>
> [2] *http://www.w3.org/TR/ldp/#ldpc* <http://www.w3.org/TR/ldp/#ldpc>
> [3] *https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html*<https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html>
> [4] *http://www.w3.org/TR/2014/NOTE-rdf11-primer-20140225/*<http://www.w3.org/TR/2014/NOTE-rdf11-primer-20140225/>
> [5]
> *http://www.w3.org/TR/2014/NOTE-rdf11-primer-20140225/#section-multiple-graphs*<http://www.w3.org/TR/2014/NOTE-rdf11-primer-20140225/#section-multiple-graphs>
> [6] *http://www.w3.org/TR/2014/REC-trig-20140225/Overview.html*<http://www.w3.org/TR/2014/REC-trig-20140225/Overview.html>
>
> Best,
> Ig
>
>
> 2014-03-19 10:17 GMT-03:00 Steven Adler <*adler1@us.ibm.com*<adler1@us.ibm.com>
> >:
> Laufer,
>
> You raise a very good point.  It would become extremely complex to have to
> access large datasets via URI's, but is SPARQL the only way to do this?  I
> ask because IBM just discontinued RDF support in DB2 due to inadequate
> customer demand.  I am not personally biased against RDF because there may
> be many reasons for IBM's decision:
>
> 1.  We may not have marketed this capability.
> 2.  DB2 may be too expensive or heavy for RDF use cases.
> 3.  RDF users may not think about DB2 as their first choice in databases,
>  etc.
>
> But I also have anecdotal developer stories that they do not like working
> with RDF.  So even though SPARQL is a very elegant way to gather up and
> represent many URI's I would prefer if we also had other non-RDF methods
> highlighted in our recommendations.
>
> Is that possible?
>
>
> Best Regards,
>
> Steve
>
> Motto: "Do First, Think, Do it Again"
>
>   From: Laufer <*laufer@globo.com* <laufer@globo.com>>  To: "manuel.carrasco-benitez"
> <*Manuel.CARRASCO-BENITEZ@ec.europa.eu*<Manuel.CARRASCO-BENITEZ@ec.europa.eu>
> >  Cc: Steven Adler/Somers/IBM@IBMUS, "deirdre.lee" <
> *Deirdre.Lee@deri.org* <Deirdre.Lee@deri.org>>, Makx Dekkers <
> *mail@makxdekkers.com* <mail@makxdekkers.com>>, Newton Calegari <
> *newton@nic.br* <newton@nic.br>>, DWBP WG <*public-dwbp-wg@w3.org*<public-dwbp-wg@w3.org>
> >  Date: 03/19/2014 08:19 AM  Subject: Re: APIs to work with data on the
> web
>
>  ------------------------------
>
>
>

Received on Wednesday, 19 March 2014 15:10:44 UTC