Is this an MCE syntax error?
Francis Cave
francis at franciscave.com
Thu Sep 20 18:07:50 CEST 2012
Presumably, if the MCE processor understands namespace 'foo', it will know
what to do with your example, which will presumably be to replace the entire
ACB with something else that is syntactically correct. 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
More information about the sc34wg4
mailing list