See also: IRC log
so far only 2 people intend to be there
<oedipus> GJR will be at plenary
<oedipus> GJR notes conflict between XHTML2 and HTML5 working group meetings
<ShaneM> that's ironic
<oedipus> GJR may be joint HTML-Forms Task Force meeting at plenary
RESOLUTION: September face 2 face is cancelled
http://www.w3.org/MarkUp/Drafts/#xhtml-modularization
A few changes need to be made to reflect response to Schema WG
Shane has made the changes, but not added the examples
Mark recalls his action to create the example that Shane needs to add
<Steven> http://www.w3.org/MarkUp/Drafts/#xhtml-modularization
<oedipus> XHTML Modularization 1.1: http://www.w3.org/MarkUp/2007/ED-xhtml-modularization-20070404
<oedipus> XHTML Role Attribute Module: http://www.w3.org/MarkUp/2007/ED-xhtml-rdfa-20070811
Comments this week on mailing list wrt XHTML Modularization
Steven has sent a note to mailing seeking clarification of "digits" problem
http://lists.w3.org/Archives/Public/public-xhtml2/2007Aug/0015
http://lists.w3.org/Archives/Public/public-xhtml2/2007Aug/0023
http://lists.w3.org/Archives/Public/www-html-editor/2007JulSep/0024
note from Tina : http://lists.w3.org/Archives/Public/public-xhtml2/2007Aug/0020
<Tina> And I'm without a phone as of five minutes ago.
Shane has spoken to Tina on this subject at some length
<oedipus> GJR: role on DIV can be used with ownedby labelledby etc.
Shane would be prepared to continue working the issue with Tina (who is not on the call today)
<oedipus> DIV can be given meaning by owing or being owned by an object containing it
Rich says that there are large numbers of examples of use of @role for ARIA.
Mark believes that there is a misunderstanding that needs to be resolved
Rich will reply to Tina
http://lists.w3.org/Archives/Public/public-xhtml2/2007Aug/0017
A never ending problem with Modularization
For the specific case of @role we have usage by ARIA
The spec for role only defines syntax and no semantics
Mark: if there is a DOM we should describe how @role works
Mark the semantics for @role are very rudimentary
<ShaneM> Remember that while we are discussing @role, we also have the access module, and other potential small modules.
Base proposal from Shane is that we should ceate a host driver language to test a module in isolation.
<ShaneM> I think CR exit criteria is independent of the QA test suite requirements
RESOLUTION: adopt Shane's proposal http://lists.w3.org/Archives/Public/public-xhtml2/2007Aug/0017]
<ShaneM> Dan said, as an aside in a comment to html-editor: p.s. I'm new to reviewing this document. The status section says it's "relatively mature"; are there any test cases I could study? Even if they're not 100% finished, I'd like to have a look.
Request from Dan.C [ http://lists.w3.org/Archives/Public/www-html-editor/2007JulSep/0003 ]
Review history of decision, perceived to be purely presentational
A need for a separator is accepted, hence separator
<oedipus> deprecate HR, replace with LS (post to public-html): http://lists.w3.org/Archives/Public/public-html/2007Apr/0099.html
Steven proposes to keep hr for legacy reasons and deprecate it
Shane has no problems with it
<oedipus> GJR notes that use of BLOCKQUOTE for formatting deprecated in HTML 4.01 -- hasn't made a difference
Mark states that we could keep such items in a module and that a decision to include a module is up to the language designer
<markbirbeck> Mark: Another approach is to have a 'presentational' module in a way similar to MathML. Then it's clear to people what is best practice, but those elements are there for people if they really want them.
[Out of time, no resolution, adjourned]