W3C home > Mailing lists > Public > public-i18n-its@w3.org > January to March 2006

[Bug 2926] RELAX NG schemas can de ambiguous

From: <bugzilla@wiggum.w3.org>
Date: Thu, 23 Feb 2006 13:43:42 +0000
To: public-i18n-its@w3.org
Message-Id: <E1FCGkw-00043I-ND@wiggum.w3.org>


------- Additional Comments From fsasaki@w3.org  2006-02-23 13:43 -------
(In reply to comment #0)
> I think that you need to say something about ambiguous RELAX NG schema that
> could lead to conflicting rules, such as for instance:
> <choice>
> <element name="p">
>  <its:schemaRule its:translate="yes"/> ...
> </element>
> <element name="p">
>  <its:schemaRule its:translate="no"/> ...
> </element>
> </choice>
> Of course, this is a simplistic example and in practice, ambiguous schemas can
> be much more complex to detect and rewrite.
> Eric
yes, we need to do say s.t. about that. Actually we have not addressed
processing of schemaRule elements at all so far (e.g. how about <p> declared as
part of <text> versus <p> declared as part of <footnote>? Who is responsible for
finding out which <p> is meant? Do we mandate a schema processor for this? This
question arises even without ambiguity.
I don't know an answer yet, though.
Received on Thursday, 23 February 2006 13:43:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:06 UTC