W3C home > Mailing lists > Public > public-appformats@w3.org > April 2007

Re: [XBL Primer] new scenarios

From: José Manuel Cantera Fonseca <jmcf@tid.es>
Date: Mon, 16 Apr 2007 13:43:13 +0200
To: Marcos Caceres <m.caceres@qut.edu.au>
Cc: "WAF WG (public)" <public-appformats@w3.org>
Message-id: <46236151.2050509@tid.es>

Hi Marcos,

I think that the set of examples you are envisaging could be quite 
useful. however, I have some concerns:

+ You talk about Web Forms 2. As far as I know it is not clear that Web 
Forms 2 is something to be adopted by W3C. The Forms Task Force is 
working on XFORMS Transitional [1]. I think the example should avoid 
using any Web Forms 2 syntax.

+ You talk about HTML 5. The former comment also applies here. At the 
moment it is not clear if the W3C is going to adopt the WHATWG proposal 
or not. So, IMHO, the examples should be neutral and be built upon HTML 
4.01 or XHTML 1.1.

+ Example 4 is something within the domain of a content adaptation tool 
and not in the domain of XBL. This comment may be applied to other 
examples, I think the Primer should not create confusion in authors and 
lead them to think that XBL is something intended to avoid the usage of 
a content adaptation platform.

+ I miss an example devoted to the extension of an existing UI 
component. IMHO, this is an important application of XBL, IMHO even more 
important that the content adaptation applications you are suggesting.

Thanks and best wishes

[1] http://www.w3.org/2007/03/XForms-Transitional/

Marcos Caceres escribió:
>
> Hi all,
> A few of us have been discussing the XBL Primer and we have come up
> with some additional scenarios which we feel may introduce features of
> XBL that will be of most value to web developers. WAF meeting this
> week in Brisbane (Australia) to discuss the following scenarios in
> details, so any feedback we received in the next few days will be part
> of our decision-making process.
>
> Please note that the order in which the following scenarios will
> actually appear in the spec is still under discussion.
>
> 1.  Creating a multi-column layout with XBL: The purpose of this
> scenario is to demonstrate XBL's ability to reorder content, as we
> believe content reordering will be a fairly common use-case. Apart
> from introducing developers to bindings, this scenario introduces
> loading and applying custom style sheets. This particular scenario may
> also focus on dynamically adapting content for mobile devices through
> XBL (however, the likelihood that XBL will be implemented on a mobile
> device in the near future is rather optimistic:)).
>
> Elements/concepts:
>     * binding attachment
>     * xbl element
>     * template element
>     * content element
>     * div element
>     * resource(s) element
>     * style element
>
> 2. Form controls: performing form validation and enhancing
> presentation/user experience. We assume that form validation will
> likely be one of the most common use cases of XBL. We are thinking of
> extending the login widget example that is currently in the Primer
> with richer presentation and user feedback.
>
> We will probably create another form validation scenario that shows
> validation on a more complex form (I personally want to demonstrate
> how to use XBL with XHR). We are contemplating examples using both
> HTML and Web Forms 2. However, we are still trying to identify
> non-trivial gaps in Web Forms 2 that XBL can fill, so input is here is
> very welcomed.
>
> Elements/concepts:
> * implementation
> * scripts
> * inheritance
> * event forwarding
> * fallback content
> * handler(s) elements
> * key, mouse, and DOM events
> * xbl:psudo
> * prefetch
>
> 3. Enhancing user experience: We have been considering creating an
> example that shows how to take existing content and enhancing its
> presentation/experience with XBL. The scenario we have been discussing
> focuses around a sample document that contains various <cite> elements
> and a bibliography marked-up using a <dl>. We essentially want to do
> something like display the bibliographical information for a reference
> when the user mouses over a citation.
>
> Main elements/concepts:
>     * enhancing presentation without changing the content
>        * content reordering
>     * events
>     * Author sheets
>
> 4. Re-purposing content to increase accessibility: the scenario would
> be one where stock quotes, or some other symbolic data, are
> represented in a more accessible way (eg. spoken or graphically). The
> idea would be to pull in data, say using XHR or HTML5's event-source,
> and to (re)present the data using text-to-speech (either using Aural
> CSS or voiceXML), SVG, or Canvas.
>
> Main elements/concepts:
>     Accessibility
>     XBL media independence
>
> The technical details of this particular scenario are obviously yet to
> be fully sketched out.
>
> 5. Language reference (as an Appendix): The language reference will
> cover the elements/attributes in the spec, but in terms that
> developers (like me) can more easily understand. Essentially, we want
> to create a reference that developers can use in everyday work
> situations. It will also have examples in HTML (possibly HTML5)
> instead of XML. There is debate within the working group about wether
> the Primer should include a language reference. I personally feel it
> does no harm having it as long as it is informative, accurate, and
> contains applicable usage examples. Please let us know if this is a
> section that is desired/helpful.
>
> Again, we would really appreciate more public feedback regarding the 
> Primer.
>
> Kind regards,
Received on Monday, 16 April 2007 11:47:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:10:22 GMT