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

Re: RDFa Core 1.1 XML+RDFa spec bug?

From: Shane McCarron <shane@aptest.com>
Date: Thu, 24 Mar 2011 09:39:59 -0500
Message-ID: <4D8B57BF.9020600@aptest.com>
To: Manu Sporny <msporny@digitalbazaar.com>
CC: RDFa WG <public-rdfa-wg@w3.org>
I disagree - we say this EXPLICITLY already.  For all contexts.  Section 
7.5 starts with the following:

At the beginning of processing, an initial evaluation context is 
created, as follows:

    * the base <http://www.w3.org/2010/02/rdfa/sources/rdfa-core/T-base>
      is set to the URI of the document (or another value specified in a
      language specific manner such as the HTML |base| element);
    * the parent subject
      <http://www.w3.org/2010/02/rdfa/sources/rdfa-core/T-parent-subject> is
      set to the base
      <http://www.w3.org/2010/02/rdfa/sources/rdfa-core/T-base> value;
    * the parent object
      <http://www.w3.org/2010/02/rdfa/sources/rdfa-core/T-parent-object>
      is set to null;
    * the list of incomplete triples
      <http://www.w3.org/2010/02/rdfa/sources/rdfa-core/T-list-of-incomplete-triples>
      is empty;
    * the language
      <http://www.w3.org/2010/02/rdfa/sources/rdfa-core/T-language> is
      set to null.
    * the list of URI mappings
      <http://www.w3.org/2010/02/rdfa/sources/rdfa-core/T-list-of-URI-mappings>
      is empty (or a list defined in the Host Language-defined default
      RDFa Profile).
    * the term mappings
      <http://www.w3.org/2010/02/rdfa/sources/rdfa-core/T-term-mappings>
      is set to null (or a list defined in the Host Language-defined
      default RDFa Profile).
    * the default vocabulary
      <http://www.w3.org/2010/02/rdfa/sources/rdfa-core/T-default-vocabulary>
      is set to null (or a URI defined in the Host Language-defined
      default RDFa Profile).

Note that the parent subject is set to the base value.  What am I 
missing here?


On 3/24/2011 8:00 AM, Manu Sporny wrote:
> We have a last-minute RDFa Core 1.1 spec bug. Thanks to Gregg Kellogg
> for drawing our attention to it.
>
> For the XML+RDFa tests - there is nothing that establishes a new subject
> when the document starts to be processed.
>
> That is 'base' is set to the document URL, but the processing rules are
> written such that this markup wouldn't generate a triple:
>
> <root>
>    <foo property="dc:title">Test</foo>
> </root>
>
> but this /would/ generate a triple:
>
> <root>
>    <blah>
>      <foo property="dc:title">Test</foo>
>    </blah>
> </root>
>
> I think we would all like to see the markup above generate a triple, but
> the processing rules do not allow that to happen. This works for
> XHTML+RDFa because a 'new subject' is specifically set for<head>  and
> <body>.
>
> I have a vague recollection that we did this because we wanted to make
> sure authors in non-XHTML languages would want to generate triples and
> would thus have to be explicit about specifying a subject. That seems
> like an archaic rule now - perhaps we should just say that, in XML+RDFa,
> the initial evaluation context initializes 'new subject' to 'base'. Or
> we can use the same language that we use in the XHTML+RDFa document.
>
> -- manu
>

-- 
Shane P. McCarron                          Phone: +1 763 786-8160 x120
Managing Director                            Fax: +1 763 786-8180
ApTest Minnesota                            Inet: shane@aptest.com
Received on Thursday, 24 March 2011 14:40:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:05:24 UTC