W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > August 2010

ISSUE-41 (processor graph vocabulary): Processor Graph Vocabulary is under-defined [RDFa 1.1 Core]

From: RDFa Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 05 Aug 2010 13:44:40 +0000
To: public-rdfa-wg@w3.org
Message-Id: <E1Oh0kS-0003c7-7b@barney.w3.org>

ISSUE-41 (processor graph vocabulary): Processor Graph Vocabulary is under-defined [RDFa 1.1 Core]


Raised by: Manu Sporny
On product: RDFa 1.1 Core

>From Gregg Kellogg:

Providing language that requires that errors and warnings be generated, without providing guidance as to exactly what should be generated makes it difficult for me to know the level of detail to include as a parser implementor, and makes it pretty useless for a consumer to know what to expect. I would request that the WG revisit this issue and come up with a vocabulary, required production and examples that provide more guidance to implementors.

Looking at previous discussions, both EARL and an RDFa-defined vocabulary were considered. Looking at EARL, it's not clear to me exactly what would be used to generate warnings. The best example I saw used an RDF-defined vocabulary to define a simple production as follows:

>>>>>      _:1 a rdfa:ProfileReferenceError ;
>>>>>      _:1 dc:description "The @profile value could not be deferenced" ;
>>>>>      _:1 dc:date "2010-06-30T13:40"^^xsd:dateTime ;

I'd also expect to see some form of source, representing an XPATH or CSS selector to the location of the error, along with more defined error classes, at least those that are required for production, but other warning and informational classes as well. You may also want to include an ordering, either a sequence number or some other mechanism. A dateTime certainly isn't precise enough to gather all information. Alternatively, and rdf:List (even though it can't be expressed well in RDFa itself, but that's another matter).

The following terms could be considered:

Received on Thursday, 5 August 2010 13:44:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:48 UTC