openRDF.org Issue Tracker

[RIO-76] RdfParserRegistry prints error to logs when it doesn't find a built-in parser factory

Fri, 24 Jun 2011 13:22:19 +0200 (CEST)

I have only imported the rio packages that I require using Maven, however, there are errors printed for the missing packages, ie, Trig and Trix. These should be warnings or informational at most, as the package still operates properly without the missing parser factories.

See below for a stack trace.

ERROR (org.openrdf.rio.RDFParserRegistry:58) Failed to instantiate service
sun.misc.ServiceConfigurationError: org.openrdf.rio.RDFParserFactory: Provider org.openrdf.rio.trig.TriGParserFactory not found
at sun.misc.Service.fail(Service.java:129)
at sun.misc.Service.access$000(Service.java:111)
at sun.misc.Service$LazyIterator.next(Service.java:273)
at info.aduna.lang.service.ServiceRegistry.<init>(ServiceRegistry.java:42)
at info.aduna.lang.service.FileFormatServiceRegistry.<init>(FileFormatServiceRegistry.java:20)
at org.openrdf.rio.RDFParserRegistry.<init>(RDFParserRegistry.java:33)
at org.openrdf.rio.RDFParserRegistry.getInstance(RDFParserRegistry.java:26)
at org.openrdf.rio.Rio.createParser(Rio.java:167)
at org.openrdf.rio.Rio.createParser(Rio.java:188)
at org.openrdf.repository.base.RepositoryConnectionBase.addInputStreamOrReader(RepositoryConnectionBase.java:373)
at org.openrdf.repository.base.RepositoryConnectionBase.add(RepositoryConnectionBase.java:277)

I would prefer not to have to filter these messages, as I would like to see Sesame/Rio errors in my logs if they are legitimate.

[RIO-46] rdf:about not allowed

Thu, 3 Apr 2008 13:36:00 +0200 (CEST)

When trying to add the following file in Sesame2CVS, I got the following error:

http://apassant.net/blog/sioc.php

Yet, the file runs well on the RDF Validator

Trace:

'rdf:about' not allowed as attribute name
org.openrdf.rio.ParseException: 'rdf:about' not allowed as attribute name
        at org.openrdf.rio.helpers.RDFParserBase._reportError(RDFParserBase.java:476)
        at org.openrdf.rio.rdfxml.RDFXMLParser._reportError(RDFXMLParser.java:1093)
        at org.openrdf.rio.rdfxml.RDFXMLParser._checkRDFAtts(RDFXMLParser.java:1018)
        at org.openrdf.rio.rdfxml.RDFXMLParser._processPropertyElt(RDFXMLParser.java:692)
        at org.openrdf.rio.rdfxml.RDFXMLParser.emptyElement(RDFXMLParser.java:394)
        at org.openrdf.rio.rdfxml.SAXFilter.endElement(SAXFilter.java:385)
        at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
        at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:221)
        at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:322)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
        at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
        at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
        at org.openrdf.rio.rdfxml.RDFXMLParser._parse(RDFXMLParser.java:280)
        at org.openrdf.rio.rdfxml.RDFXMLParser.parse(RDFXMLParser.java:231)
        at org.openrdf.sesame.repository.DefaultTransaction._addInputStreamOrReader(DefaultTransaction.java:248)
        at org.openrdf.sesame.repository.DefaultTransaction._add(DefaultTransaction.java:194)
        at org.openrdf.sesame.repository.DefaultTransaction.add(DefaultTransaction.java:172)
        at org.openrdf.sesame.repository.Repository.add(Repository.java:899)
        at List.main(List.java:21)

[RIO-42] N3 writer not up-to-date with grammar: uses '-' as language prefix instead of '@'

Tue, 7 Feb 2006 11:57:07 +0100 (CET)

Rio's N3 writer still uses '-' as the prefix for a literal language tag instead of '@'.

[RIO-41] double quotes in long strings must not be parsed greedily

Tue, 7 Feb 2006 11:57:17 +0100 (CET)

Characters in long strings ending in more than 3 double quotes (e.g. """Jim said: "Hello!""""") should not be parsed greedily. The long string terminates upon parsing the first sequence of 3 (unescaped) double quotes, making the mentioned example illegal. The 2006-01-02 spec accomodates for this by allowing double quotes to be escaped.

[RIO-40] support double quote escaping (\") in long strings

Tue, 7 Feb 2006 11:57:26 +0100 (CET)

Double quote escapes (\") are now allowed in the new 2006-01-02 Turtle spec.

[RIO-39] add decimal support

Tue, 7 Feb 2006 11:57:35 +0100 (CET)

Revision 2006-01-02 adds decimal support to Turtle. Decimal numbers without an exponent should now be interpreted as xsd:decimals instead of xsd:doubles.

[RIO-38] Allow an optional sign before double

Tue, 7 Feb 2006 11:57:45 +0100 (CET)

Negative doubles (aka "floating") and optional +-signs are now allowed for Turtle doubles

[RIO-37] Allow an optional sign before integer

Tue, 7 Feb 2006 11:57:54 +0100 (CET)

negative integers and optional +-signs are now allowed for Turtle integers (2006-01-02 revision)

[RIO-36] RDF/XML parser doesn't handle required unqualified attributes

Tue, 7 Feb 2006 11:58:06 +0100 (CET)

Issue came up on the forum: http://www.openrdf.org/forum/mvnforum/viewthread?thread=776

For backwards compatibility with existing RDF documents, RDF/XML parsers are required to handle a limited set of unqualified attributes as coming from the RDF namespace. The unqualified attributes to support are ID, about, resource, parseType and type, as is specified under "URI" in section 6.1.4 of the revised RDF/XML spec:
http://www.w3.org/TR/rdf-syntax-grammar/#section-attribute-node

[RIO-35] Parsing attributes on properties

Tue, 7 Feb 2006 12:00:19 +0100 (CET)

Rio does not allow to parse statements that use attributes on properties for nodes that are not bnode.

eg:

<rdf:RDF>
  <sioc:Site rdf:about="http://rdfs.org">
    <sioc:name>rdfs.org - Home of SIOC</sioc:name>
    <sioc:host_of rdfs:label="SIOC Forum">
      <sioc:Forum rdf:about="http://rdfs.org/sioc/forums">
        <rdfs:seeAlso rdf:resource="http://rdfs.org/sioc2/forum/9"/>
      </sioc:Forum>
    </sioc:host_of>
    <sioc:link rdfs:label="rdfs.org - Home of SIOC" rdf:resource="http://rdfs.org"/>
  </sioc:Site>
</rdf:RDF>

rdfs:label on sioc:link doesn't give any error, but the one on sioc:host_of give the following error:

[Fatal Error] local:18:12: Element type "rdfs:label" must be followed by either attribute specifications, ">" or "/>".
Exception in thread "main" org.openrdf.rio.ParseException: org.xml.sax.SAXParseException: Element type "rdfs:label" must be followed by either attribute specifications, ">" or "/>".

Yet, it seems (see 2005/12/13 discussion log for #swig) that specs don't clearly mention if the syntax is right or not, and raptor parses it fine but not the W3 validator.

Maybe Rio should (or not) parse it also correctly / w/warnings

[RIO-34] N3Writer escapes single quotes in strings, which is not required

Tue, 7 Feb 2006 11:55:45 +0100 (CET)

Although the escape sequences table at http://www.w3.org/DesignIssues/Notation3.html specifies the \' escape sequence, escaping single quotes in strings is not required. As such, single quote escapes are merely overhead and should be removed.

[RIO-33] RDF/XML Parser fails to parse some occurences of empty XML literals

Tue, 7 Feb 2006 11:56:03 +0100 (CET)

Rio's RDF/XML parser fails to parse the data below, throwing the following error:

org.openrdf.rio.ParseException: org.xml.sax.SAXException: unexpected literal

----------------------------------------------------------------
<?xml version="1.0" encoding="US-ASCII"?>
<rdf:RDF
xmlns:ex="http://exampl.org/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">

<rdf:Description rdf:about="http://example.org/">
<ex:abstract rdf:parseType="Literal"></ex:abstract>
<rdfs:label>Example.org</rdfs:label>
</rdf:Description>

</rdf:RDF>
----------------------------------------------------------------

The error does not occur when XML literal is not empty. The error also doesn't occur when there's whitespace between the start- and end tags, but in that case the triple is completely ignored which also is not good.

[RIO-32] Turtle writer doesn't escape '>' character in URIs

Cause — Tue, 7 Feb 2006 11:56:13 +0100 (CET)

In our repository we have URIs where the '<' and '>' characters have been encoded (<, >). The Turtle writer, unlike the RDF/XML writer, decodes these, resulting in invalid Turtle: See example below:

In RDF/XML:

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
xmlns:my="http://www.cs.vu.nl/~mcaklein/onto/swrc-ext/2005/05#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:vs="http://www.w3.org/2003/06/sw-vocab-status/ns#"
xmlns:wot="http://xmlns.com/wot/0.1/"
xmlns:ow="http://swrc.ontoware.org/ontology#"
xmlns:dc="http://purl.org/dc/elements/1.1/">

<rdf:Description rdf:about="http://cvs.berlios.de/cgi-bin/viewcvs.cgi/cybop/doc/papers/2003_system_communication/references.bib?rev=1.3#sanderson">
<rdf:type rdf:resource="http://xmlns.com/foaf/0.1/Document"/>
<rdf:type rdf:resource="http://xmlns.com/wordnet/1.6/Document"/>
<rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Publication"/>
<rdf:type rdf:nodeID="node10qtt8t2cx82"/>
<rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Book"/>
<rdf:type rdf:nodeID="node10qtt8t2cx93"/>
<rdf:type rdf:nodeID="node10qtt8t2cx94"/>
<rdf:type rdf:nodeID="node10qtt8t2cx95"/>
<owl:sameAs rdf:resource="http://cvs.berlios.de/cgi-bin/viewcvs.cgi/cybop/doc/papers/2003_system_communication/references.bib?rev=1.3#sanderson"/>
<ow:author rdf:resource="http://cvs.berlios.de/cgi-bin/viewcvs.cgi/cybop/doc/papers/2003_system_communication/references.bib?rev=1.3#rick_sanderson_<ricks@fourbitcom>_the_fourbit_group"/>
<my:authorList rdf:nodeID="node10qtt8t2cx1807"/>
<rdfs:label>Rick Sanderson. <ricks@fourbit.com> The Fourbit Group..</rdfs:label>
<ow:note>http://www.fourbit.com</ow:note>
<ow:key>sanderson</ow:key>
</rdf:Description>

</rdf:RDF>

In Turtle:

@prefix my: <http://www.cs.vu.nl/~mcaklein/onto/swrc-ext/2005/05#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix vs: <http://www.w3.org/2003/06/sw-vocab-status/ns#> .
@prefix wot: <http://xmlns.com/wot/0.1/> .
@prefix ow: <http://swrc.ontoware.org/ontology#> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .

<http://cvs.berlios.de/cgi-bin/viewcvs.cgi/cybop/doc/papers/2003_system_communication/references.bib?rev=1.3#sanderson> a foaf:Document , <http://xmlns.com/wordnet/1.6/Document> , ow:Publication , _:node10qtt8t2cx82 , ow:Book , _:node10qtt8t2cx93 , _:node10qtt8t2cx94 , _:node10qtt8t2cx95 ;
owl:sameAs <http://cvs.berlios.de/cgi-bin/viewcvs.cgi/cybop/doc/papers/2003_system_communication/references.bib?rev=1.3#sanderson> ;
ow:author <http://cvs.berlios.de/cgi-bin/viewcvs.cgi/cybop/doc/papers/2003_system_communication/references.bib?rev=1.3#rick_sanderson_<ricks@fourbitcom>_the_fourbit_group> ;
my:authorList _:node10qtt8t2cx1807 ;
rdfs:label "Rick Sanderson. <ricks@fourbit.com> The Fourbit Group.." ;
ow:note "http://www.fourbit.com" ;
ow:key "sanderson" .

[RIO-31] Default namespaces improperly handled by RDF/XML writer

Tue, 7 Feb 2006 11:56:27 +0100 (CET)

Default namespaces, which can be set by specifying an empty namespace prefix string, are improperly handled by the RDF/XML writer. Specifying such a namespace results in the following two errors:

1) The namespace declaration contains a "xmlns:=...." attribute,
2) Element names that use the default namespace are rendered as "<:localName ..." and "</:localName>".

In both cases, the colon should not have been included in the output.

[RIO-27] openrdf-model.jar and openrdf-util.jar not included in tar.gz release packages

Fri, 23 Sep 2005 17:34:29 +0200 (CEST)

The rio-1.0.4.tar.gz release does not contain the required openrdf-model.jar and openrdf-util.jar files. The zip-version does include these files.

[RIO-26] AbbreviatedRdfXmlWriter mixes up closing tags

Fri, 26 Aug 2005 11:23:10 +0200 (CEST)

It appears that on some (not all) data sets the AbbreviatedRdfXmlWriter mixes up closing tags, effectively producing malformed RDF/XML.

For example, an export from a store that includes entailed statements can produce fragments like:

<rdf:Description rdf:about="http://www.w3.org/2000/01/rdf-schema#Datatype">
<rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
<rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Resource"/>
<rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Datatype"/>
</rdfs:Resource>

or altogether forgetting to close an element:

<adm:ExtResource rdf:about="http://www.photojournal.com/classicart/italmasters/michelangelo/sculptur/descent.jpg">
<adm:title xml:lang="en">Descent</adm:title>
<cult:Artifact rdf:about="http://www.photojournal.com/classicart/italmasters/michelangelo/sculptur/descent.jpg"/>

[RIO-25] Update Turtle parser & writer to latest revision of the spec

Cause — Tue, 7 Feb 2006 11:56:37 +0100 (CET)

Update Turtle parser & writer to latest revision of the spec

[RIO-24] Stacked xml:base directives with relative URIs not processed correctly

Fri, 23 Sep 2005 17:33:01 +0200 (CEST)

See also http://lists.w3.org/Archives/Public/www-archive/2005Jul/0017.html

Rio does not correctly parse 'stacked' xml:base directives that contain relative URIs. For example:

<?xml version="1.0"?>
<rdf:RDF xml:base="http://example.org/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:dc="http://purl.org/dc/elements/1.1/">
  <rdf:Description rdf:about="http://www.w3.org/" xml:base="test1/">
    <dc:title>World Wide Web Consortium</dc:title>
    <dc:source rdf:resource="test2/"/>
    <dc:relation rdf:resource=""/>
  </rdf:Description>
</rdf:RDF>

produces:

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .

<http://www.w3.org/> dc:source <test1/test2/> ;
dc:relation <test1/> ;
dc:title "World Wide Web Consortium" .

But it should be:

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .

<http://www.w3.org/> dc:source <http://example.org/test1/test2/> ;
dc:relation <http://example.org/test1/> ;
dc:title "World Wide Web Consortium" .

[RIO-23] Adding stylesheet information to generated RDF/XML

Tue, 7 Feb 2006 11:56:48 +0100 (CET)

It would be useful to have the possibility to add stylesheet information to the RIO generated RDF/XML, for example in the case of RSS, which is often translated to HTML that way.

[RIO-21] AbbreviatedRdfXmlWriter produces EmptyStackException if a single type statement is written about a resource

Fri, 23 Sep 2005 17:33:27 +0200 (CEST)

AbbreviatedRdfXmlWriter produces EmptyStackException if a single type statement is written about a resource.

[RIO-20] Abbreviated RDF/XML writer

Fri, 23 Sep 2005 17:33:55 +0200 (CEST)

An RDF/XML writer that uses Abbreviated RDF/XML syntax would be a useful addition to the set of Rio serializers.

[RIO-18] Turtle parser fails to parse predicate-object lists nested in blanks properly

Fri, 23 Sep 2005 17:32:25 +0200 (CEST)

The Turtle parser stumbles on predicate-object lists ending with a ';' when these are contained in a blank node.

Parsing the following data:

<foo:subject> <foo:pred>
[ <nested:pred> <nested:obj> ; ] .

gives this error:

Error[line=2]:
Expected '<', ':' or a letter, found ']'

[RIO-16] Error handling/reporting is not consistent across parsers

Fri, 23 Sep 2005 17:31:14 +0200 (CEST)

There are some differences in the handling and reporting of parse errors between the RDF/XML, N-Triples and Turtle parsers. These differences should be scrutinized and probably be equalized.

[RIO-15] Turtle parser goes into infinite loop in when bNode ID preservation is enabled

Fri, 23 Sep 2005 17:31:49 +0200 (CEST)

Bug reported via e-mail by Benja Fallenstein:

The RIO Turtle parser goes into an infinite loop in _createBNode(String) when _preserveBNodeIds is true. Looking at the code in CVS, this seems to happen always when a new node ID is encountered for the first time:

private BNode _createBNode(String nodeID)
    throws ParseException
  {
    // Maybe the node ID has been used before:
    BNode result = (BNode)_bNodeIdMap.get(nodeID);

if (result == null) {
      // This is a new node ID, create a new BNode object for it
      if (_preserveBNodeIds) {
        result = _createBNode(nodeID);
      }
      else {
        result = _createBNode();
      }

// Remember it, the nodeID might occur again.
      _bNodeIdMap.put(nodeID, result);
    }

return result;
  }

I suppose the recursive _createBNode(nodeID) should look something like _valFactory.createBNode(nodeID)?

Cheers,
- Benja

[RIO-14] RDF/XML parser fails to parse datatyped empty strings

Mon, 11 Apr 2005 13:52:37 +0200 (CEST)

Bug originally reported on the forum: http://www.openrdf.org/forum/mvnforum/viewthread?thread=525

Related error in RDF/XML specification reported on www-rdf-comments mailing list: http://lists.w3.org/Archives/Public/www-rdf-comments/2005AprJun/0000.html

The RDF/XML parser in Rio/Sesame fails to parse the following data fragment:

...
   <rdf:Description rdf:ID="ID1">
       <foo:prop rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
       ></foo:prop>
   </rdf:Description>
   ...

Although the RDF/XML specification indicates that this is indeed an illegal piece of RDF/XML, the general consensus seems to be that this should represent an empty datatyped literal. The Turtle equivalent of the literal being ""^^xsd:string.