W3C home > Mailing lists > Public > www-rdf-interest@w3.org > August 2003

Re: RDF validator error

From: Frank Manola <fmanola@mitre.org>
Date: Wed, 27 Aug 2003 12:02:59 -0400
Message-ID: <3F4CD633.5010300@mitre.org>
To: Jeremy Carroll <jjc@hplb.hpl.hp.com>
Cc: Charlie Abela <abcharl@keyworld.net>, www-rdf-interest@w3.org

Formerly the validator generated a "synthetic" URI to use as the base 
for pasted-in examples lacking an xml:base.  I don't find the current 
behavior very helpful in, for example, validating examples from the 
Primer (and I would not like to have to individually create such 
examples as separate files and upload to a URI from which they could be 
validated by URI).  I think the generation of a synthetic URI, together 
with a warning, would be reasonable behavior.  Alternatively, there 
could be a separate option (e.g., under the "Advanced Features" in the 
W3C validation service) to indicate whether to check relative URIs or not.


Jeremy Carroll wrote:

> (Would value comment from other WG members)
> Charlie Abela wrote:
>> I am trying to parse some DAML with the validator. The parsing of this 
>> file used to give no complaint except that lately I am being faced 
>> with this error: Error: {W130} Base URI is "", relative URIs left as 
>> relative and I can?t figure out why?
> Also this example from Art Barstow:
> <rdf:Description rdf:ID="Profile">
> <dc:title>World Wide Web Consortium</dc:title>
> </rdf:Description>
> generating the same error.
> At some point I upgraded ARP to correctly identify the use of relative 
> URIs in documents given with relative URIs as a problem.
> The RDF graph uses absolute URI refs, and if no absolute URI can be 
> established then there is an issue. Whether this is a warning or an 
> error depends on the use case, and ARP supports either. The validator I 
> believe runs in strict mode, and so most problems are treated as errors.
> Recently the validator has had the ARP engine upgraded. At which point 
> this behaviour was introduced.
> I agree that it is a bug in the validator, since while no base URI can 
> be determined for text pasted into a web form, it is unhelpful to 
> complain about this. It is however not a bug in a compliant parser.
> I suggest one of the following fixes in the validator code:
> a) specify an arbitrary base URI instead of ""
> or
> b) tell ARP to ignore this condition
>   setErrorMode(
>      ARPErrorNumbers.EM_IGNORE );
> Personally I think option (b) is better.
> A workaround until the validator is updated is to have the file to be 
> tested as web accessible and use the validate URL option.
> Jeremy

Frank Manola                   The MITRE Corporation
202 Burlington Road, MS A345   Bedford, MA 01730-1420
mailto:fmanola@mitre.org       voice: 781-271-8147   FAX: 781-271-875
Received on Wednesday, 27 August 2003 11:41:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:44 UTC