Re: RDF MV* frameworks

So you want to take an RDF resource and format it as HTML, and vice versa?
Correct?

For the latter case, this is easy: RDFa can be used to read an RDF graph
out of an HTML document and write it to an RDF database.

However for out first case, there's not much in the way of generating HTML
from RDF. Which is rather curious, no?

I have some software I'm working on that ultimately hopes to do exactly
this, <http://magnode.org/>. It's not dealing with RDF data quite yet,
however. But I do have an idea for what I call "RDFa Templates",
essentially RDFa documents with explicit variables, as well as the standard
implicit variables (i.e. subgraph-matching bnodes), and some XSLT-like
control tags for doing things like iterating over multiple result matches,
and if-then-else conditions. I have a bad TR-like draft written up: <
http://magnode.org/rdfa-templating/>. I had an implementation, but it only
worked with Jade (the XML/HTML template language) and my own in-memory
SPARQL engine.

The upshot of this is you can parse the generated XML/HTML and get out the
exact same RDF graph that went into it. This also means that you can modify
the HTML, and know exactly what RDF data has been modified, satisfying your
MV* framework criteria.

I do believe someone has written an implementation of something similar to
this, but I forget the link. Anyone know what I'm talking about?

Austin Wright.


On Sat, Oct 12, 2013 at 3:35 AM, Henry Story <henry.story@bblfish.net>wrote:

> Hi,
>
>    In order to write professional JS applications one requires
> a good MV* framework [1], such as those provided by backbone
> for the modelling, and views, Handlebars.js [3] for templating, ...
>
>    What frameworks exist in RDF land to make the model be
> RDF/Linked Data based?
>
>   I know of Antonio Garrote's rdfstore-js [4] and his
> semantic-ko [5] MV* framework. the semantic-ko has not
> been developed for a while.
>
>   What other frameworks are there? What feedback do
> people have about them?
>
>   Here are some things that I think would be important for
> RDF Linked Data Protocol compliant framework:
>
> 1. One should be able to follow through links accross graphs.
>  That is: imagine I have some graph <doc1> which contains
>
>   { <doc1#me> foaf:knows <doc2#her> . }
>
>   and I have a PNG(<doc1>,<doc1#me>,doc1graph), pointing
> into the gr graph at <doc1#me>, then following pg1.find(foaf.knows)
> should give me a PointedGraph where the graph comes from <doc2> and the
> pointer is <doc2#her> in that graph, that is
>
>      PNG(<doc2>,<doc2#me>,doc2graph)
>
> This should be done transparently.
>
>    The advantage of this over usual JSon systems is very big as
> it makes it easy to split information up, using cashes.
>
> 2. It should be very easy for the client to know what the access
> rights are for each MVP ( so it can decide for example wether it
> can allow editing of it, or whether it needs to have a error correction
> mode on a different view.
>
> 3. Local storage would be important
>
> 4. the system should be LDP based [6] ( core implementation of LDP only,
> some
> pieces like propertyXXX are still up for discussion on that list )
>
> 5. because of CORS there needs to be a way to work with remote resource by
> going through
> the server
>
>   We have a lot of code using backbone and so ideally are looking
> for something that would work better with that framework. If someone
> wishes to work on this please let me know.
>
>    Henry
>
> [1] very good article on this
>
> http://addyosmani.com/blog/understanding-mvc-and-mvp-for-javascript-and-backbone-developers/
> [2] http://backbonejs.org/
> [3] http://handlebarsjs.com/
> [4] https://github.com/antoniogarrote/rdfstore-js
> [5] https://github.com/antoniogarrote/semantic-ko
> [6] https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html
>
> Social Web Architect
> http://bblfish.net/
>
>
>