Yes, I use jena (and could use cwm even!) usually to convert from n3 to rdf. However, I am trying *not* to do all the work - for example, many of the namespaces are missing in chime's inline text. Missing namespaces and "live" files require complete RDF/XML. Dan Connolly wrote: > On Sun, 2007-02-11 at 20:43 -0500, Harry Halpin wrote: > >> The primer has now checked in Chime's HL7 use-case. However, until we >> get a RFC out of the IETF (which should happen!), we cannot use N3 >> notation inline in the primer. >> > > Hmm... I'm not sure why not? The SPARQL spec uses turtle > as an editorial device. Why can't the GRDDL primer? > > >> Therefore, Chime - can you convert all >> your examples in n3 into RDF/XML files and send me them, not as text in >> line, but as files. >> > > Yes, I suppose any files we use as live primer data should > be RDF/XML. Do you not have a tool to convert from turtle > to RDF/XML, Harry? cwm will do it, as will any number > of Jena/redland/rdflib/4suite tools. > > >> Also, since this is a health care case John Madden - do you mind >> checking this out and seeing if it's works? I.e. read the text and then >> try to *run* the example. It's important to have running code in the >> primer. >> >> Also, Chime - we need references. Could you please send IanD and me the >> markup for the references >> that have @@TODOs in the file. >> >> It would be good if there was some *problem* that this solved via usage >> of OWL entailment, but I can't think of one. >> >> [1] http://www.w3.org/2001/sw/grddl-wg/doc29/primer.html#hl7 >> >> -- -harry Harry Halpin, University of Edinburgh http://www.ibiblio.org/hhalpin 6B522426Received on Monday, 12 February 2007 17:03:05 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:11:47 GMT