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

ISSUE-40 (no triples for empty elements): Empty elements should not create literals [RDFa 1.1 Core]

From: RDFa Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 05 Aug 2010 13:31:11 +0000
To: public-rdfa-wg@w3.org
Message-Id: <E1Oh0XP-00007B-Kz@stu.w3.org>

ISSUE-40 (no triples for empty elements): Empty elements should not create literals [RDFa 1.1 Core]

http://www.w3.org/2010/02/rdfa/track/issues/40

Raised by: Manu Sporny
On product: RDFa 1.1 Core

>From Richard Cyganiak:

   <div about="#person">
     <dt>Job title</dt>
     <dd class="job" property="jobtitle"></dd>
   </div>

After RDFa parsing, the following RDF triple is generated from this snippet (assuming a term mapping for jobtitle):

   <#person> ex:jobtitle "" .

I ask that the parsing algorithm be changed so that no triple is generated in the case where an element has a @property attribute, no @content attribute, and no text content.

The motivation for this change: Template-generated HTML often contains empty elements like in the example above. This happens when a field is not present in a given record. Generating an empty <td/> or <span/> is often less effort than suppressing the generation of the element altogether, so thats' what template authors often do. When a zero-length element carrying @property is encountered, then it's almost certain that the author's intention was *not* to generate a zero-length literal, so the parsing algorithm should reflect that. 
Received on Thursday, 5 August 2010 13:31:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:55:07 GMT