- From: Danny Ayers <danny.ayers@gmail.com>
- Date: Mon, 19 Sep 2005 15:31:09 +0200
- To: Damian Steer <damian.steer@hp.com>
- Cc: Hans Teijgeler <hans.teijgeler@quicknet.nl>, semantic-web-request@w3.org, semantic-web@w3.org
On 9/18/05, Damian Steer <damian.steer@hp.com> wrote: > I know what you mean. Currently I think the best approaches are as follows: > > 1) XML -> RDF: XSLT or XQuery to RDF/XML (although I've also gone to n3) Yep. If you've got any control over the original XML then it might be worth considering making it "coincidentally" RDF/XML, see: http://www.xml.com/lpt/a/2002/10/30/rdf-friendly.html > 2) RDF -> RDF: Rules language, eg n3, jena rules, swrl. Stay out of xml > here. Yep. The n3/cwm tutorial is pretty good on this: http://www.w3.org/2000/10/swap/doc/ You may be able to do the logic using *standard* RDFS/OWL inference - cwm, Euler, Jena, Pellet, one of the DL reasoners. Depending on what you're trying to do SPARQL may be an option here too, using CONSTRUCT. A twisty possibility might also be to follow the route - [RDF] SPARQL -> xml results -> xslt/xquery -> RDF/XML I'm only guessing, but I think this would probably be straightforward for simple transformations/mappings but would probably get hard to control for anything beyond those. > 3) RDF -> XML: SPARQL -> xml results -> xslt/xquery -> xml. Yep. This works wonders ;-) Cheers, Danny. -- http://dannyayers.com
Received on Monday, 19 September 2005 13:31:32 UTC