- From: Charles McCathieNevile <charles@w3.org>
- Date: Thu, 10 Oct 2002 04:21:47 -0400 (EDT)
- To: Emmanuel Pietriga <epietriga@yahoo.fr>
- cc: Diego Garcia <diego_garcia77@hotmail.com>, <www-rdf-interest@w3.org>
As well as IsaViz, and Danny's work, RDFAuthor uses this kind of approach. I proposed a bit of metadata that could be added to SVG to ensure that it represents RDF in a way that would allow for round-trip of the data - http://lists.w3.org/Archives/Public/www-rdf-interest/2002May/0095 - based on ideas put forward by Damian Steer (author of RDF Author) and Danny Ayers, among others. And yes, what Danny says about seperating the model from the view and control of the data is important - not least for accessibility. There has been work on an XSLT-based RDF parser, so presumably it can be used (XSLT is Turing-complete) if you want. Implementation details are to some extent up to the implementor, although there are some design principles that are generally valuable. Cheers Chaals On Thu, 10 Oct 2002, Emmanuel Pietriga wrote: > >I tend to agree with Danny on the side of adopting an MVC approach. >[snip] >Why not adopt an approach similar to IsaViz [1] ? The environment is >RDF-aware ; the graph is represented in a purely abstract (close to >RDF/Jena model) way. This representation can be manipulated and >imported/exported from/to RDF or NTriples, but also exported as SVG >graphics. And it can be modified directly from the graphical view. > >Emmanuel > >[1] http://www.w3.org/2001/11/IsaViz/ > >
Received on Thursday, 10 October 2002 04:21:54 UTC