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

Re: [XBL] XBL 2.0 Expected context, Expected children

From: Karl Dubost <karl@w3.org>
Date: Tue, 10 Oct 2006 16:01:14 +0900
Message-Id: <361912F7-4787-4DFB-96FF-F6C101316A7F@w3.org>
Cc: public-appformats@w3.org
To: Ian Hickson <ian@hixie.ch>


Le 06-10-06 à 08:41, Ian Hickson a écrit :

> On Thu, 5 Oct 2006 karl@w3.org wrote:
>>
>> # When an XBL element is found inside an element other than that  
>> listed
>> # as its "Expected context", it is in error.
>>
>> 1. Please define an "expected context" and "expected children" in
>> Terminology.
>
> I don't understand what the definition would be. The reader will
> immediately see what is being referred to as soon as they look at  
> the next
> section, since the headings are highlighted and everything.  
> However, in an
> attempt to resolve this, I've slightly changed the sentence you quoted
> above to work around this.

The sentence is better.
Are there unexpected contexts? Is "expected" word necessary?

>> 2. It seems to be important enough to the specification. Please,  
>> define
>> a schema (any kind) that gives a programmatic way of checking the
>> expected context or expected children.
>
> I am not aware of any language that is expressive enough to  
> unambiguously
> and fully describe the syntactical requirements of XBL2.

Do you mean because of multi namespaces? What are the precise  
syntactical requirements which can't be expressed?



-- 
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 Tuesday, 10 October 2006 07:29:13 UTC

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