- From: Myles, Stuart <SMyles@ap.org>
- Date: Wed, 24 Oct 2012 07:15:33 +0000
- To: Michael Cooper <cooper@w3.org>, Andreas Gebhard <Andreas.Gebhard@gettyimages.com>, Evan Sandhaus <sandhes@nytimes.com>, "Brian Ellin" <bellin@twitter.com>
- CC: PFWG Public Comments <public-pfwg-comments@w3.org>
- Message-ID: <2B3AA5056E3CB8428BDE670B2CEEC54F2567CFE1@CTCXMBX02.ap.org>
Hi Michael, Thank you for drawing my attention to this proposal. I took a quick look and the idea of a @role attribute to supply additional machine-readable information about the intent of an element seems useful to me. It appears somewhat similar to the use of @role in IPTC’s NewsML-G2 b2b markup standards http://www.iptc.org/site/News_Exchange_Formats/. Perhaps this is a bit of a detail point, but I was slightly confused by the wording in the document-conformance section: http://www.w3.org/TR/role-attribute/#document-conformance If the host language is an XML markup language and is not in the XHTML namespace, and the host language does not incorporate this attribute in 'no namespace', then the document must contain an XML namespace declaration for the Role Attribute Module namespace [XML-NAMES11<http://www.w3.org/TR/role-attribute/#bib-XML-NAMES11>]. The namespace for Role Attribute Module is defined to be http://www.w3.org/1999/xhtml. This appears to be saying that either a host XML markup language must include the @role attribute in no namespace or it must include the @role attribute in the XHTML namespace. Why the choice of no namespace @role and the XHTML namespace @role? Regards, Stuart From: Michael Cooper [mailto:cooper@w3.org] Sent: Tuesday, October 23, 2012 2:51 PM To: Andreas Gebhard; Evan Sandhaus; Myles, Stuart; Brian Ellin Cc: PFWG Public Comments Subject: [Fwd: Second Draft Role review] Hello - I believe you are aware of the W3C Role Attribute specification [1] which allows the author to annotate markup languages with machine-extractable semantic information about the purpose of an element. This attribute as an important support for Accessible Rich Internet Applications (WAI-ARIA) 1.0 [2] and also can be used with RDFa [3]. This specification is currently a Candidate Recommendation, which means that technical development is complete and testing is underway. We hope soon to advance to Proposed Recommendation, which is a sign-off from the W3C Membership. We haven't received much input from the public and have decided to check with known interested parties to see if you have any concerns about the specification in its current form. Can you let us know either way, if you have any serious issues, or if you believe it would be ok to advance the specification. We request to hear from you by Monday, 29 October 2012. Thank you for your attention. For the W3C Protocols and Formats Working Group, Michael Cooper [1] http://www.w3.org/TR/role-attribute/ [2] http://www.w3.org/TR/wai-aria/ [3] http://www.w3.org/TR/rdfa-core/ -- Michael Cooper Web Accessibility Specialist World Wide Web Consortium, Web Accessibility Initiative E-mail cooper@w3.org<mailto:cooper@w3.org> Information Page<http://www.w3.org/People/cooper/> The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1898 and delete this email. Thank you. [IP_US_DISC] msk dccc60c6d2c3a6438f0cf467d9a4938
Received on Wednesday, 24 October 2012 07:16:16 UTC