Re: "DOM" for RDF?

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? If this is the case it could be 
> interesting from my point of view an approach similar to the current 
> implmentation of the Sail interface.
>
Alfredo,

I think a query language on its own isn't enough.  I would like to see 
an environment in which I can create an in-memory graph, load it with 
one or more graphs and/or query results, create, delete and edit graph 
nodes and triples within it, query it, and serialize all or part of the 
result to any of the popular serialization formats, plus (X)HTML, 
ideally using a tool as powerful as XSLT. :-)

Looking up LDPath I came across Marmotta [1], which seems rather closer 
to what I have in mind.

Richard

[1] http://marmotta.apache.org/

> My 2 cents
>
> Alfredo Serafini
>
>
> 2013/12/2 Richard Light <richard@light.demon.co.uk 
> <mailto:richard@light.demon.co.uk>>
>
>     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 variety of environments and applications. The
>     [RDF] DOM is designed to be used with any programming language".
>     (Quotes taken from [1])
>
>     A quick search turns up a number of PHP-based libraries, and the
>     odd one for javascript, Delphi, Python and Ruby, but as far as I
>     can see there is little, or no, commonality of approach or
>     functionality amongst these offerings.  This means that a
>     programmer (a) has to decide which of these widely varying
>     approaches to adopt, (b) only gets whatever documentation each
>     chooses to provide and (c) is faced with a complete rewrite,
>     should they decide to switch RDF platform.
>
>     Might this situation be a significant factor in the slow take-up
>     of RDF by mainstream developers?
>
>     Richard
>
>     [1] http://www.w3.org/TR/REC-DOM-Level-1/introduction.html
>
>     -- 
>     *Richard Light*
>
>

-- 
*Richard Light*