W3C home > Mailing lists > Public > www-tag@w3.org > February 2008

Re: State and Status of WAI-ARIA approach to host-language embedding

From: Tim Berners-Lee <timbl@w3.org>
Date: Thu, 28 Feb 2008 14:26:52 -0800
Cc: TAG List <www-tag@w3.org>, Michael N Cooper <cooper@w3.org>, Judy Brewer <jbrewer@w3.org>
Message-Id: <53B19371-16E0-4881-95FC-4530F99883AA@w3.org>
To: Al Gilman <Alfred.S.Gilman@IEEE.org>

Very much in summary, some of the feedback from th TAG has been along  
the following lines

- The idea of effectively using aria- s a sort namespace prefix in has  
issues
     -- it is reinvention of the namespace system
     -- the NS WG decided to use ':' among all eht various name chars  
to select
     -- Users will find it very confusing to use sometimes aria- and  
sometimes aria:

We wondered why the following was rejected:

-   Use aria:foo elements in the HTML version too.  get HTML to allow  
these in a non-ns-aware HTML scearipo, with a an *implicit* prefix  
declaration
- Maybe have a list of implicit NS prefixes fro the text/html MIME  
type stored in a file linked from the MIME type declaration  -- could  
this b a general way of mapping non-XML to namespaced XML?

     -- What is et problem with browsers handling a colon in an HTML  
tag name?  Pointers?

Tim

On 2008-02 -25, at 15:06, Al Gilman wrote:

>
>
> ** introduction
>
> WAI-ARIA is an aspect or facet of web markup that
> is not a standalone format but a module of
> markup-practice-maintenance that is targeted to
> be integrated into multiple host languages that
> span the 'divide' between formats that assume
> well-formed XML as a prerequisite or platform,
> and HTML "as she is used in the wild" which means,
> more or less, as processed with a lot of ad-hoc
> recovery processing by browsers today.
>
> The TAG has identified an issue termed
> TagSoupIntegration-54 which deals with creating
> composite documents and applications that blend
> content from both sides of this 'divide.'
>
> We of PFWG have requested that the TAG review
> what we are doing in the area of host-language
> insertion.  There are two reasons for this:
> One, the TAG has done some thinking about the
> above issue that will make them a good source
> of review for our approach.
>
> Two, we have wrestled with this issue in devising
> our approach to host language insertion, and our
> experience and conclusions may help the TAG in
> coming to a more cogent statement of the issue
> and an effective strategy for moving ahead in this
> area.   Perhaps also in the larger issue of format
> evolution and discipline in the presence of a
> lot of markup unorthodoxy and informally-arrived-at
> fixup practice. This message is an annotated bibliography
> for TAG participants and Public contributors to www-tag
> on the WAI-ARIA host-language insertion approach;
> what it is today and how we got there.
>
> ** WAI-ARIA host-language insertion
>
> The immediate statement of this approach is in
> the section "5 Implementation in Host Languages"
> of the WAI-ARIA specification,
> which is available as a Working Draft at:
>
> http://www.w3.org/TR/wai-aria/#implementation
>
> .. although some reading of the Conformance section
> may be required to complete the picture for the
> purpose of relating to the above-mentioned TAG issue.
>
> http://www.w3.org/TR/wai-aria/#s_event_module_conformance
>
> A quick summary of our "when in Rome" or
> "different syntax for the same effect"
> approach is on the public record at
>
> http://lists.w3.org/Archives/Public/public-html/2008Jan/0200.html
>
> Some level of context is probably needed to appreciate
> the reasons for taking this approach.  The overall
> project context is given in several forms.
>
> There is the W3C news announcement of the latest,
> re-structured suite of documents:
>
> http://www.w3.org/News/2008#item17
>
> The Best Practices, while rough at present, give
> a Web Practitioner perspective which is important
> for the "insertion in the Web as practiced today"
> side of the comparison.
>
> http://www.w3.org/TR/wai-aria-practices
>
> The Roadmap takes a technology assessment and
> planning perspective.
>
> http://www.w3.org/TR/wai-aria-roadmap
>
> The Primer gives the need for and approach of the
> WAI-ARIA technology in a brief compass.
>
> http://www.w3.org/TR/wai-aria-primer
>
> for TAG consumption I would also suggest that the
> briefing to the 2006 Technical Plenary could be
> a quick way to frame "what is WAI-ARIA, anyway?"
> in a way that motivates architectural choices.
>
> http://www.w3.org/2006/03/01-Gilman/tree2.xhtml
>
> The W3C Process context for the above snapshot
> of a work in progress is that PFWG considers these
> TR drafts to be the last TR release before a Last
> Call release, and the proposition that this is
> a cross-host-language technology has been coordinated
> through the Hypertext CG on a continuing basis, with
> a public-record joint meeting at TPAC 2007.
>
> http://www.w3.org/2007/11/06-aria-minutes.html
>
> Al
> /chair PFWG
> http://www.w3.org/WAI/PF
Received on Thursday, 28 February 2008 22:27:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:52 GMT