- From: Marcos Caceres <m.caceres@qut.edu.au>
- Date: Tue, 7 Nov 2006 23:15:58 +1000 (EST)
- To: m.caceres@qut.edu.au, public-appformats@w3.org
In section 3.7.3, I suggest simplifying the example. It currelny says: "Consider the following completely useless but conveniently simple binding:" I'm sorry, but this example is hardly simple (particulary as you have added content inheritance into the mix). It could be made a bit simpler if you added id's to the last 2 bindings (call them b and c). And maybe add a litte diagram showing that b->a and then when c is added to the mix it forms: (ROOT) -> c (implicit) -> b -> a Here is the new code, <xbl xmlns="http://www.w3.org/ns/xbl"> <binding id="a"> <template> l <inherited> l <content> o </content> - </inherited> W </template> </binding> <binding element="[X]" extends="#a" id="b"> <template> e <inherited> error </inherited> o <content> r </content> </template> </binding> <binding element="[Y]" id="c"> <template> H <inherited> error </inherited> l <content/> ! </template> </binding> </xbl> (note I also changed the last binding, is this correct?) so, then the reader can see where each bit of content is coming from: c b a a a a a b b c c c ------------------------------ H e l l o - W o r l d ! (I think the above is right, but might be best to check it over;)) --- Creative Industries Faculty Queensland University of Technology +61423 142 435 www.datadriven.com.au
Received on Tuesday, 7 November 2006 13:17:13 UTC