W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > January 2008

Further updates and outstanding issues

From: Mark Birbeck <mark.birbeck@formsPlayer.com>
Date: Wed, 23 Jan 2008 23:18:43 +0000
Message-ID: <a707f8300801231518x535e6bd8i843bd1d8ef59772f@mail.gmail.com>
To: "W3C RDFa task force" <public-rdf-in-xhtml-tf@w3.org>

Hello all,

I have just committed my final changes for now. I think it's ready for
the next stage of reviewing.

I've highlighted in the document nearly all of the outstanding issues,
details of which I've placed below for easy reference. The one that
isn't in there -- because I couldn't decide where to put it...and it's
late here -- is the one about whether @src is a subject or an object.

Anyway, the issues that are currently under discussion (and the
associated description of each issue that I have placed in the
document), are as follows:

== rel and rev values ==

  This approach to @rel and @rev has not yet been voted on. However, there is a
  general desire that legacy values like @rel="next", should result in
a meaningful
  triple being added to the [default graph], whilst @rel="foo" should
not. So if this
  is not the solution, something similar will be found.


== Use of @src, @href and @resource to complete hanging triples ==

  There is an outstanding issue as to whether the @src, @href and @resource
  attributes with no @rel or @rev values, should complete hanging triples. The
  question is whether the following mark-up should generate three
triples or none:

  Ivan knows
  <div about="http://www.w3.org/peopel/ivan#me" rel="foaf:knows">
    <a href="#mark">Mark</a> and <a href="#ben">Ben</a>.
    Note how I'm using <a href="http://foaf.org">FOAF</a> here.
  </div>

  The problem is that the third link is to the FOAF web-site, and not to someone
  that Ivan knows. The question is whether someone could do this accidentally,
  since to actually inhibit the triple is easily achieved by using an empty @rel
  value:

  Ivan knows
  <div about="http://www.w3.org/peopel/ivan#me" rel="foaf:knows">
    <a href="#mark">Mark</a> and <a href="#ben">Ben</a>.
    Note how I'm using <a rel="" href="http://foaf.org">FOAF</a> here.
  </div>


== Use of @href and @resource as subjects ==

  There is an outstanding issue as to how far @href and @resource
  attributes should go in setting the subject. The various questions are:

  1. Should a lone @href or @resource set the subject for any nested
      statements:

      I met with
      <a href="http://www.w3.org/peopel/ivan#me">
        <span property="foaf:name">Ivan</span>
      </a>
      Ivan the other day.

  2. Should @property set predicates for a lone @href or @resource on
      the same element:

      I met with
      <a href="http://www.w3.org/peopel/ivan#me" property="foaf:name">
        Ivan
      </a>
      Ivan the other day.


== Use of @instanceof with @href and @resource ==

  There is an outstanding issue as to whether @instanceof should apply
  to @href and @resource. For example, should the following set the type
  of the URI identified in the link:

  I met with
  <a href="http://www.w3.org/peopel/ivan#me" instanceof="foaf:Person">
    <span property="foaf:name">Ivan</span>
  </a>
  Ivan the other day.

Regards,

Mark

-- 
  Mark Birbeck, formsPlayer

  mark.birbeck@formsPlayer.com | +44 (0) 20 7689 9232
  http://www.formsPlayer.com | http://internet-apps.blogspot.com

  standards. innovation.
Received on Wednesday, 23 January 2008 23:19:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 23 January 2008 23:19:57 GMT