See also: IRC log, previous 2006-05-08 meeting
ACTION: [DONE] Ben update hGRDDL issue to note a possible requirement for explicit pipelining in GRDDL [recorded in http://www.w3.org/2006/05/08-htmltf-minutes.html#action07]
ACTION: Ben write a prototype hGRDDL profile for XHTML 1 [recorded in http://www.w3.org/2006/05/08-htmltf-minutes.html#action06] [CONTINUES]
Ben: have some related email from Laurian Gridinoc; Re: Proposal: hGRDDL, an extraction from Microformats to RDFa [Laurian Gridinoc]
Ben: transformation rules will be ok but quoting will present a challenge
ACTION: Ben start separate mail threads on remaining discussion topics [recorded in http://www.w3.org/2005/12/06-swbp-minutes#action04] [CONTINUES]
Ben: making progress
ACTION: Ben to draft full response to Bjoern's 2004 email [recorded in http://www.w3.org/2006/01/24-swbp-minutes.html#action03] [CONTINUES]
Ben: I do have all the feedback I need
ACTION: Ben, Mark be ready on 15 May to discuss WWW2006 presentations [recorded in http://www.w3.org/2006/05/01-htmltf-minutes.html#action04] [DONE]
<MarkB_> Had network problems over the w/e so didn't get round to posting link to my presentation for XTech 2006. However, here it is: http://skimstone.x-port.net/node/289
<MarkB_> Will also send to list.
ACTION: [DONE] Ben, Mark send outlines of their XTech and WWW2006 presentations this week [recorded in http://www.w3.org/2006/05/01-htmltf-minutes.html#action05]
ACTION: once Steven sends editors' draft of XHTML2, all TF members take a look and comment on showstopper issues only [recorded in http://www.w3.org/2006/02/06-htmltf-minutes.html#action01] [CONTINUES]
Steven: I give a presentation tomorrow. I saw no comments on my draft, so I assume everyone is OK
(pointer to Steven's slides near http://www.w3.org/2006/05/01-htmltf-minutes.html#action05 )
<Steven> 11 slides starting http://www.w3.org/2006/Talks/05-16-Steven-XHTML2-XForms/#metadata
Mark: the point I would like to stress is that RDFa makes a lot of information available to browsers; this improves the user experience by enhancing the UI using the metadata
-> ACTION: MB to post link to his XTech 2006 presentation on RDFa [Mark]
-> RDFa: The easy way to publish your metadata
Mark: how many presenters?
Ben: you can use my slides but as you are listed as the presenter, there's no need for me to be on the podium
Ralph: I think the presentation would come across better if there is only one person on the podium
Ben: for W3C track I plan to show demos but not delve into the code. For Developer's Track I may get into looking at the code
Ralph: sounds right
Mark: the presentation in node/289 is meant to be given this Thursday
<Ralph> [there's especially good stuff in node/266]
<Ralph> [Steven, re: your slide "RDF Terminology" - while it's true that the term "triple" is in common usage today, the formal RDF term is "Statement". Indeed, rdf:Statement is a specified rdfs:Class. I argued for "assertion" but lost. "statement" is at least better than "triple".]
<Steven> [thanks]
<Ralph> [If you do add the term "statement", it's probably good to leave a parenthetic remark about "triple"]
Ben: Mark is taking the lead on developing the story for the "Next Wave" session. I am developing the story for the W3C Track
<Ralph> [/me wishes he were going to be present to hear all these great presentations]
Ben: recommend putting copies of all materials on W3C site as well as local laptops
ACTION: Ben make sure RDFA bookmarklet runs locally [recorded in http://www.w3.org/2006/05/15-htmltf-minutes.html#action08]
RESOLVED that hGRDDL plus explicit default profiles for XHTML1 and XHTML2 are going to be a direction pursued by this TF
<benadida> rel="next"
<benadida> class="foo"
Ben: we need a DOM interpretation of how to declare a base CURIE
Mark: I was just thinking we'd need to specify rel and everything else would fall out of the profile. We might even be able to do this just in prose
Ben: if the preprocessing step is just done with DOM calls then whatever happens to set the CURIE base needs to be reflected in the DOM somehow
Mark: not sure; could just say "when used in a DOM, RDFa has this meaning ...". Ah, but if the spec says "if you see x.y construct, go consult a.b document" then maybe we do need something more
<benadida> href="foo" --> URI
<benadida> rel="foo"
Ben: what do we mean by rel="foo" ?
<benadida> current URI = http://example.org/bar
<benadida> rel="foo" --> what is the CURIE?
Steven: I see use cases for both, and I'm having trouble deciding. rel="next" is a use case for "current document"
<benadida> rel="next" --> rel="xh:next"
Ben: we want to special-case rel="next" to have a specific transform
Mark: like a pre-processing step. The pre-processing idea got us back to nicer syntax without losing compatibility for things like rel='next'
Steven: as I understand it, this "local namespace" idea is for grandfathering unqualified rel values that aren't in the HTML namespace
Ben: intertwined with notion of adding default CURIE base; wouldn't want next to transform to xh:next