On 04/12/2013 10:42, Armando Stellato wrote:
http://www.w3.org/TR/rdf-api/
Why did it die?
Lack of interest:-( There were no real uptake in the idea neither by users
nor
by implementers. It really was heading for a paper-only specification. It
seems that this direction was not what the commu
> >> http://www.w3.org/TR/rdf-api/
> > Why did it die?
>
> Lack of interest:-( There were no real uptake in the idea neither by users
nor
> by implementers. It really was heading for a paper-only specification. It
> seems that this direction was not what the community wanted at large.
..though ma
On 02 Dec 2013, at 15:22 , Richard Light wrote:
>
> On 02/12/2013 11:10, Karl Dubost wrote:
>> Le 2 déc. 2013 à 06:00, Richard Light
>> a écrit :
>>
>>> By this, I mean "an application programming interface (API) for [RDF
>>> graphs]", which will be "a standard programming interface that ca
On 02/12/2013 11:10, Karl Dubost wrote:
Le 2 déc. 2013 à 06:00, Richard Light a écrit :
By this, I mean "an application programming interface (API) for [RDF graphs]", which
will be "a standard programming interface that can be used in a wide variety of
environments and applications.
http://
On 02/12/2013 11:23, Tim Berners-Lee wrote:
I think my conclusion from the DOM experience was that actually
people wanted jQuery -- something optimized for the language.
My own RDF APIs have been optimized for js and python respectively,
though they share style and many calls.
See undocumente
Yes Richard, i agree and mybe my reply ws not so clear regarding what i
mean. I like the ld-api (such as Elda) which uses ldpath much like xpath is
used in the XSLT or DOM context... the next step in that direction could be
marmotta, i agree on that.
I also love very much Sail or the gremlin lang
Richard,
I think Graphity is close to what you're looking for:
https://github.com/Graphity/graphity-browser
It supports SPARQL Protocol and Graph Store Protocol, content
negotiation, XSLT transformations of RDF output and RDF input user
interface using RDF/POST (http://www.lsrn.org/semweb/rdfpost.
On 02/12/2013 11:10, Alfredo Serafini wrote:
Hi Richard
from my point of view the DOM-like approach does exists yet, and it's
by SPARQL and LDpath. What are them lacking? Do you feel there should
be an object-oriented approach? As for the Jena model or Sesame
internal Graph representation? I
I think my conclusion from the DOM experience was that actually
people wanted jQuery -- something optimized for the language.
My own RDF APIs have been optimized for js and python respectively,
though they share style and many calls.
See undocumented rdflib.js https://github.com/linkeddata/rdf
Hi Richard
from my point of view the DOM-like approach does exists yet, and it's by
SPARQL and LDpath. What are them lacking? Do you feel there should be an
object-oriented approach? As for the Jena model or Sesame internal Graph
representation? If this is the case it could be interesting from my
Le 2 déc. 2013 à 06:00, Richard Light a écrit :
> By this, I mean "an application programming interface (API) for [RDF
> graphs]", which will be "a standard programming interface that can be used in
> a wide variety of environments and applications.
http://www.w3.org/TR/rdf-api/
--
Karl Dub
Hi,
I'm sure this has been discussed many times and/or ages ago, but I am
struck by the absence of a DOM-like W3C framework for RDF. By this, I
mean "an application programming interface (API) for [RDF graphs]",
which will be "a standard programming interface that can be used in a
wide variet
12 matches
Mail list logo
