Andy Seaborne wrote:
Lewis,

13:53:28 WARN riot :: {W136} Relative URIs are not permitted in RDF: specifically<section6energydomestic2010rdf.owl> 13:53:28 WARN riot :: {W124} Non-ascii characters in a namespace URI may not be completely portable:<http://www.semanticweb.org/ontologies/2010/11/section6energydomestic2010.owl#hasMaximumAreaWeightedAverageUvalueForAllElementsOfTheSameTypeWhereParametersForColumnADoNotApplyWperm²>. Resulting RDF URI references are legal. 13:53:28 WARN riot :: {W124} Non-ascii characters in a namespace URI may not be completely portable:<http://www.semanticweb.org/ontologies/2010/11/section6energydomestic2010.owl#hasMaximumAreaWeightedAverageUvalueForAllElementsOfTheSameTypeWperm²>. Resulting RDF URI references are legal. 13:53:28 WARN riot :: {W124} Non-ascii characters in a namespace URI may not be completely portable:<http://www.semanticweb.org/ontologies/2010/11/section6energydomestic2010.owl#hasMaximumIndividualElementUvalueWperm²>. Resulting RDF URI references are legal.

Warnings do not stop data being loaded.  They are just "helpful" messages.

I don't know what the state of full IRI handling in other systems but "Wperm²" may get you into trouble, even if correct.


with control-panel.jsp showing as below when I attempt to enter the control panel to form queries
-------------------------------------------------------------------------
Error 404: Not Found

I suspect this is something else.

Did you see the datasset in the control panel to select?

It happened to me as well. :-)

(You can't jump straight to the query form as it knows the dataset your working on - suggestions on better design of HTML forms welcome)

Fuseki SPARQL endpoints follow all this pattern:
http://{host}:{port}/{dataset}/{data|query|update}

Why not to serve JSP and/or HTML pages which act on a specific
dataset via: http://{host}:{port}/{dataset}/sparql.jsp?
If at all possible (I haven't tried yet).

Paolo




Fuseki - version 0.2.0 (Date: 2011-04-21T10:29:50+0100)
-------------------------------------------------------------------------
Have the riot's above only to do with the non-ASCII characters, as these can be easily changed. Luckily these appear to be the only instances of possible riot's which I have within my dataset.
Thanks for any help

Lewis

    Andy

Reply via email to