- From: Shane McCarron <shane@aptest.com>
- Date: Wed, 23 Jan 2008 18:29:49 -0600
- To: Mark Birbeck <mark.birbeck@formsPlayer.com>
- CC: W3C RDFa task force <public-rdf-in-xhtml-tf@w3.org>
Apologies - I assumed Mark was done for the day. I have updated the editor's draft in place against these checkins. Mark Birbeck wrote: > 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 > > -- 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 January 2008 00:30:10 UTC