[XBL Primer] new scenarios

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,
-- 
Marcos Caceres
http://datadriven.com.au

Received on Sunday, 15 April 2007 11:35:33 UTC