Is this an MCE syntax error?

[MURATA Makoto]

2012/9/21 Francis Cave <francis at franciscave.com>:
> Presumably, if the MCE processor understands namespace 'foo', it will know

Actually, the MCE processor understands the MCE namespace only.
But it will behave as instructed by a given configuration, which is a
set of namespaces understood by the application program.

Do you mean that the foo namespace is included in the given
configuration?  (In other words, the application program understand
it.)

> what to do with your example, which will presumably be to replace the entire
> ACB with something else that is syntactically correct.

But such a behavior is never specified.

If the ns for foo is included in the given configuration, what should happen?
Is this an error?  My understanding of the spec is as follows:

Case 1: understood and ignorable
            I have no ideas.
Case 2: understood and  non-ignorable
            I have no ideas.
Case 3: not understood and ignorable
             not an error
Case 4: not understood and non-ignorable
             error

I think that this should be an error for all these cases.

Regards,
Makoto


> But what that might
> be is completely unknowable, because <foo:bar/> might say something like: if
> you understand 'foo', change the choices and the fallback in some specified
> way.
>
> In effect, the namespace 'foo' would contain extensions to the MCE namespace
> itself.
>
> Francis
>
>
>
>> -----Original Message-----
>> From: eb2mmrt at gmail.com [mailto:eb2mmrt at gmail.com] On Behalf Of MURATA
>> Makoto
>> Sent: 20 September 2012 16:29
>> To: SC34
>> Subject: Is this an MCE syntax error?
>>
>> Dear colleagues,
>>
>> Consider
>>
>> <mce:AlternateContent>
>>   <foo:bar/>
>>   <mce:Choice ...>..</mce:Choice   ... >
>> </mce:AtternateContent>
>>
>> where mce and foo are prefixes for the MCE namespace and an ignorable
>> namespace.Does this fragment have an error?
>>
>> Suppose that an application program understands the namespace foo.
>> Then, this document has an MCE syntax error. Suppose that it does not.
>> Then, there are no MCE errors.
>>
>> This is because of the following text in 10.2.1 of Part 3.
>>
>> AlternateContent elements might have ignored attributes or contain
>> ignored child elements. Markup consumers shall not generate an error
>> when encountering such attributes or child elements. However, markup
>> consumers shall generate an error when encountering an attribute or
>> child element of the AlternateContent element that belongs to a
>> namespace that is neither understood nor ignorable. [Note:  In addition
>> to Choice and Fallback elements, an ignored element can occur as a
>> child of AlternateContent. end note]
>>
>> I hate this design.  Syntactical correctness of data shouldn't depend
>> on application programs.
>>
>>
>> Regards,
>> Makoto
>



-- 

Praying for the victims of the Japan Tohoku earthquake

Makoto