[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [relax-ng] list//interleave//value
- I don't see the justification for doing things differently for <value>
than for <element> and <text>.
- With your proposal,
<list>
<interleave>
<choice>
<value>x</value>
<value>x</value>
</choice>
<value>y</value>
</interleave>
</list>
would be illegal. In my implementation at least, it would be awkward to
detect this because
<choice>
<value>x</value>
<value>x</value>
</choice>
internally gets turned into
<value>x</value>
--On 18 October 2001 13:55 -0700 Kohsuke KAWAGUCHI
<kohsuke.kawaguchi@sun.com> wrote:
>
> James Clark suggested:
>
>> 1. Disallow list//interleave//data
>> 2. Require all <value> in a given interleave to have the same type and
>> datatypeLibrary.
>> 3. Make it an error if there is a value that occurs in both operands of
>> an interleave
>
>
> Is it strange if I change it as:
>
> 1. Disallow list//interleave//data
> 2. Require all <value> in a given interleave to have the same type, the
> same datatypeLibrary and different values.
>
> Under this restriction,
>
> <list>
> <interleave>
> <group>
> <value>AB</value>
> <value>AB</value>
> </group>
> <value>DEF</value>
> </interleave>
> </list>
>
> will be prohibited, which was not prohibited by the restriction of James.
>
> I think this restriction is easier to check, and easier to describe.
>
>
> regards,
> --
> Kohsuke KAWAGUCHI +1 650 786 0721
> Sun Microsystems kohsuke.kawaguchi@sun.com
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC