W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > November 2011

Behavior of @property with @typeof and incomplete triples

From: Gregg Kellogg <gregg@kellogg-assoc.com>
Date: Fri, 11 Nov 2011 14:58:51 -0500
To: RDFa WG <public-rdfa-wg@w3.org>
Message-ID: <BA550F10-652E-49ED-B241-01DF7E1162E7@greggkellogg.net>
As I mentioned before, the new @property/@typeof rules break some tests, including 0058. This one is interesting, because it involves the use of both hanging @rels, @typeof and @property.

<html xmlns="http://www.w3.org/1999/xhtml" xmlns:foaf="http://xmlns.com/foaf/0.1/" version="XHTML+RDFa 1.1">
  <head>
    <title>Test 0058</title>
  </head>
  <body>
    <div about="http://www.example.org/#ben" rel="foaf:knows">
      <p typeof="foaf:Person" property="foaf:name">Mark Birbeck</p>
      <p typeof="foaf:Person" property="foaf:name">Ivan Herman</p>
    </div>
  </body>
</html>

The new rules say that because both <p> elements have a @typeof and @property, it results in chaining to a new BNode. This is in Step 5 (part 1). In Step 11, the "otherwise, if @typeof is present ..." causes "typed resource" to be used as the @property value. But, the existence of incomplete triples is intended to pick up these new objects. I think we need to revise this step:

[[[
11.
...
otherwise, if @typeof is present and @about is not and the  incomplete triples within the current context is empty, the value of typed resource.
]]]

This also applies to test 0078, 0081, and 0082.

Gregg
Received on Friday, 11 November 2011 19:59:49 GMT

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