Thanks Paulo - I know that tdbloader2 can handle n3 files, however the particular files I was using had some issues with malformed URIs, as well as the ------------------- lines you spotted, so the conversion step helped clean these up. This step wouldn't have been necessary if the files had been properly formatted in the first place ...
Regards Glenn. On Tue, Feb 28, 2012 at 4:01 PM, Paolo Castagna <[email protected]> wrote: > Glenn Proctor wrote: >> Hi folks >> >> Thanks for the helpful replies. In the end I used rapper to convert >> the n3/nq files to rdf/xml, and then tdbloader2 to bulk load the >> resulting files into TDB. As Andy suggested this was much quicker than >> doing everything via Fuseki. > > You can load N-Triples | N-Quads with tdbloader|tdbloader2, > that should even be faster. > > Paolo > >> >> I've now started a Fuseki server on top of the TDB I created and it's >> working very well. >> >> Thanks for the help >> >> Glenn. >> >> >> On Mon, Feb 27, 2012 at 3:47 PM, Paolo Castagna >> <[email protected]> wrote: >>> Paolo Castagna wrote: >>>> Next step (mine or your) is to check in the Fuseki source code if the >>>> PUT handles other RDF serializations (and if not, this could be a good >>>> candidate to open a new feature request). >>>> >>>> I found the parseBody method in Fuseki, but I'll look in details later, >>>> here it is, just in case another pair of eyes is faster than mine: >>>> http://svn.apache.org/repos/asf/incubator/jena/Jena2/Fuseki/trunk/src/main/java/org/apache/jena/fuseki/servlets/SPARQL_REST.java >>> After having seen Andy's reply... oh, yes! >>> >>> No problem in Fuseki, this also works: >>> curl -X PUT -H "Content-Type: application/n-triples" -d@/tmp/hgnc-100.nt >>> http://localhost:3030/dataset/data?default >>> >>> Andy, do we have a problem in soh [1], line 47? >>> $fileMediaTypes['n3'] = 'text/rdf+n3application/rdf+n3' >>> >>> I am not sure which one is the correct one. >>> >>> Paolo >>> >>> [1] http://svn.apache.org/repos/asf/incubator/jena/Jena2/Fuseki/trunk/soh >
