- From: Al Gilman <Alfred.S.Gilman@IEEE.org>
- Date: Fri, 7 Mar 2008 11:01:57 -0500
- To: public-xhtml2@w3.org
- Cc: wai-liaison@w3.org
[previous attempt: http://lists.w3.org/Archives/Member/wai-liaison/2008Mar/0010.html] Refer to joint meeting minutes: http://www.w3.org/2008/02/20-xhtml-minutes#item07 Steven, Roland, Shane, et_al: Here is proposed language for the predefined roles in the Role Module specification. There are a few discussion threads that we hadn't necessarily run into the ground in these confined areas: 1) the choice of the 'complementary' mnemonic for this role -- possibly s/complementary/supplemental ..or.. s/complementary/related 2) last sentence for 'complementary' -- possibly s/completely separable/completely independent 3) the choice of 'contentinfo' mnemonic for that role; possibly s/contentinfo/footer I want to pass the monkey to XHTML2 in terms of deciding how much longer to consider these points, as a) we've kept this much longer that initially projected already http://www.w3.org/2008/02/20-xhtml-irc#T13-56-33 b) the original action was to adjust the definitions... c) PFWG goes to sleep for a week on account of CSUN this coming week d) issues of mnemonic choice hinge on author comprehension, where XHTML2 WG has as much of a handle on the problem as does PFWG. All of the content cavils represent single voices at the moment, but we ran this by them fast. They could be ignored as the 'better fighting against the good' or deferred on the basis that 'a last call will bring these questions anyway' or debated, as you chose. If you want to consider further discussion on the soft spots identified above, you may wish to cross-post the threads or post XHTML2 agenda to PF list <w3c-wai-pf@w3.org>. As chair of PFWG, I am saying "you have our action item response." Rough-Consensus-of-PFWG language with a few yellow warning tags. Al /chair, PFWG -- banner A region that contains the prime heading or internal title of a page. Most of the content of a banner is site-oriented, rather than being page-specific. Site-oriented content typically includes things such as the logo of the site sponsor, the main heading for the page, and site-specific search tool. Typically this appears at the top of the page spanning the full width. complementary Any section of the document that supports but is separable from the main content, but is semantically meaningful on its own even when separated from it. There are various types of content that would appropriately have this role. For example, in the case of a portal, this may include but not be limited to show times, current weather, related articles, or stocks to watch. The content should be relevant to the main content; if it is completely separable, a more general role should be used instead. contentinfo Meta information about the content on the page or the page as a whole. For example, footnotes, copyrights, links to privacy statements, etc. would belong here. main Main content in a document. This marks the content that is directly related to or expands upon the central topic of the page. navigation A collection of links suitable for use when navigating the document or related documents. search The search tool of a web document. This is typically a form used to submit search requests about the site or to a more general Internet search service. definition A definition of a term or concept. A role is not provided to specify the term being defined, although host languages may provide such an element; in HTML this is the dfn element. The defined term should be included in such an element even when occurring within an element having the definition role. note The content is parenthetic or ancillary to the main content of the resource.
Received on Friday, 7 March 2008 16:02:21 UTC