[XBL Primer] Comments

[José Manuel Cantera Fonseca]

Commenting: http://dev.w3.org/cvsweb/2006/waf/XBLPrimer/Overview.src.html?rev=1.16 + There are some typos in the document + Abstract "This document provides you with the practical knowledge ..." Shouldn't it say "This document provides the practical knowledge ..." Perhaps for you native speakers it sounds ok but for me no, I don't know ... + Status of document "Implementors should be aware that this specification is not stable ... "This document was produced ... Is this really needed for a W3C Note? This is not the XBL 2 spec .... + Table of contents It would be good to have it completed, although some of the contents were empty. This would give the reader an overview of the whole document and what the editors are planning to do for the next versions + Use of the word XBL. It should be used consistently over the whole document i.e. it should be used XBL 2 everytime or there should be a statement saying that "hereinafter when the 'XBL' word is appearing we are talking about 'XBL 2'" + Introduction Perhaps the statement "The move in web development towards avoiding the table element for layout has led developers to consider how to exploit other HTML elements, CSS, and ECMAScript to achieve complex layouts." should not be the first in this paragraph and should be used as an example of highly accessible content i.e avoiding usage of tables for layout + XBL concepts The content under this section hasn't any concepts ... + Working example. In the text it is mentioned "Log on· as legend, but in the markup example appears "Log in" in the legend tag. In the next step (adding divs and CSS) in the figure appears login instead of log on :) You don't have put a label for the submit input, this occasionates that a default label is put in the submit button and that label depends on the browser language, so in my browser, which is configured in Spanish, I see a Spanish label intermixed with the English labels of the other fields. In the div example the CSS is not shown. This can be misleading I don't see the need of duplicating the effort creating one XML version and another HTML version of the example. One practical way to face this difference would be to work in XHTML (the more general option) and provide an specific example wrt attaching the XBL via CSS (which is also permitted in XHTML) and say "this is the way how an HTML document would be bound to an XBL binding" + Creating an XBL document and attaching it to another document It seems that this section looses the continuity with the example, shouldn't be the continuation of the example? + Attaching XBL using ... I'm missing the example of attaching XBL by means of CSS The example stops "violently", why the first example is not completed with the actual binding used to resolve the problem? + Recap of terminology Shouldn't it be in chapter 1? under the concepts section? + The <xbl> element "XBL elements that are not inside an XBL declaration are treated as arbitrary XML, even is the elements are scoped through a namespace" What are you trying to mean? Does it make sense to have XBL elements outside an XBL declaration?. if it is an obscure feature it shouldn't be mentioned in a primer + The content element The examples are not read properly. They are confusing. The purpose of the example, the problem to solve and the binding used is not explained clearly + Rest of the document. Examples are missing Could it make sense to have a complete example, use case that illustrates the usage of the prefetch, resources, style, etc, at the same time? Thanks and best regards