W3C home > Mailing lists > Public > public-appformats@w3.org > October 2006

[XBL] XBL 2.0 Language usability

From: <karl@w3.org>
Date: Thu, 05 Oct 2006 05:45:03 -0000
To: public-appformats@w3.org
Message-Id: <20061005054522.C2A4E4F471@homer.w3.org>

Hi,
This is a QA Review comment for "XML Binding Language (XBL) 2.0"
http://www.w3.org/TR/2006/WD-xbl-20060907/
2006-06-19
Last Call WD

About http://www.w3.org/TR/2006/WD-xbl-20060907/#relationship

The specification might be misused because of these changes.

[[[
There are numerous changes. However, of particular importance to readers familiar with XBL1, there have been some changes to the element names. In particular, the XBL1 element content is now called template, and the XBL1 element children is now called content.
]]] -- XML Binding Language (XBL) 2.0
       http://www.w3.org/TR/2006/WD-xbl-20060619/#attributes
       Tue, 20 Jun 2006 15:27:58 GMT

Changing names might be ok. But renaming an element by giving it a name of another elements is leading to troubles.
There is also the element attribute, which will be more than confusing for many people. ex: "The binding element attribute is element"

    XBL 1       XBL2
    content     template
    children    content

Then it is possible to write in the _same_ specification, things like "content" element has been deprecated. content element is …

It is often said by some groups inside and outside W3C. That usability of the language is very important. For example, some people complained about the "l" element in XHTML 2.0. XBL 2 is taking the same road? Is it the only possible solution?

Please minimize ambiguities by changing names.




-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***
Received on Thursday, 5 October 2006 05:45:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:50:05 UTC