W3C home > Mailing lists > Public > public-svg-wg@w3.org > October to December 2008

ISSUE-2090 (@aria-* atributes): @aria-foo atributes: un-prefixed, forbidden? [Last Call: SVG 1.2 Tiny ]

From: SVG Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 7 Oct 2008 11:53:40 +0000 (GMT)
To: public-svg-wg@w3.org
Message-Id: <20081007115340.D64B36B62C@tibor.w3.org>


ISSUE-2090 (@aria-* atributes): @aria-foo atributes: un-prefixed, forbidden? [Last Call: SVG 1.2 Tiny ]

http://www.w3.org/Graphics/SVG/WG/track/issues/2090

Raised by: Doug Schepers
On product: Last Call: SVG 1.2 Tiny 

Al Gilman
<http://lists.w3.org/Archives/Public/www-svg/2008Oct/0011.html>:
[[
** problems statement

<quote
cite="http://www.w3.org/TR/2008/WD-SVGMobile12-20080915/ 
extend.html#ForeignNamespacesPrivateData">

Unprefixed attributes on elements in the SVG namespace must not be  
used for extensions.

</quote>

But that's exactly what WAI-ARIA asks host languages to allow; that  
the aria-foo attributes appear un-prefixed:

<quote
cite="http://www.w3.org/WAI/PF/aria/#host_general_property">

The names of these attributes do not have a prefix set off by a  
colon; in the terms of Namespaces they are "unprefixed attribute names."

</quote>

(Read at least the whole linked paragraph.)

When I ran our approach through the Hypertext CG, I believe the  
feedback I got was that your group had reviewed this and were willing  
to live with the un-prefixed, aria-foo attribute names for the WAI- 
ARIA states and properties.

So I hope that this is just a matter of incomplete editing, not a  
latent disagreement about the host language embedding approach for ARIA.

** proposed change TBD

This is rough, but one possible way to fix this would be to add a  
section 18.5 to the Metadata chapter that reserves attribute names  
that match the pattern aria-* for use as specified in the [work in  
progress] WAI-ARIA specification.  And allows their presence on  
elements from the SVG namespace.  Then chapter 19 can say "except as  
provided in 18.5, unprefixed attributes on elements in the SVG  
namespace must not be used for extensions."

This prose would be backed in the schema by a loophole in the syntax  
that would accept zero or more attributes with names matching this  
pattern on any SVG element.  We would do actual checking to an  
experimental schema that would be generated from the spec draft,  
until the WAI-ARIA spec completes the Rec track.  This RNG  
(optionally plus Schematron) schema could resemble the example  
discussed at
http://lists.w3.org/Archives/Public/public-schemata-users/2008May/ 
0001.html
]]
Received on Tuesday, 7 October 2008 11:54:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 7 October 2008 11:54:24 GMT