Re: bug in syntax of rif:List

On Fri, Apr 23, 2010 at 9:58 AM, Sandro Hawke <sandro@w3.org> wrote:

>
> Hm, I remember us as having decided in a telecon to proceed with option
> 2.  Perhaps my memory is faulty, but if no one objects, I think we can
> proceed as if my memory were correct.
>
> Stella, will it be hard to update the PS->XML code to do this?
>

I made this change, but guess I should wait until the schemas are
updated before checking the new xml versions of the test cases into the
repository. It won't be hard to make another update if the details of the
decision change.

Stella



>
>  -- Sandro
>
> > We had an email discussion about that bug in the syntax of rif:List
> (no=20
> > IRIMETA) [1], but we never discussed it at a telecon, nor did we make
> a=20
> > decision on how to correct it or acted to actually correct it.
> >
> > There were two proposed corrections:
> >
> > 1. Just add the missing IRIMETA in the XML schema, changing it to
> (change=20
> > GROUNDTERM to LISTELEMENT for BLD):
> >  <xs:element name=3D"List">
> >    <xs:complexType>
> >      <xs:sequence>
> >        <xs:group ref=3D"IRIMETA" minOccurs=3D"0" maxOccurs=3D"1"/>
> >        <xs:group ref=3D"GROUNDTERM" minOccurs=3D"0"
> maxOccurs=3D"unbounded"=
> > />
> >      </xs:sequence>
> >    </xs:complexType>
> >  </xs:element>=20
> >
> > 2. Take the opportunity and align the syntax of <List> with that of
> Atom=20
> > and Expr, adding an <items ordered=3D"yes"> role element, and changing
> the =
> >
> > schema to the same effect as (change GROUNDTERM to LISTELEMENT for BLD):
> >  <xs:element name=3D"List">
> >    <xs:complexType>
> >      <xs:sequence>
> >        <xs:group ref=3D"IRIMETA" minOccurs=3D"0" maxOccurs=3D"1"/>
> >        <xs:element name=3D"items">
> >          <xs:complexType>
> >            <xs:sequence>
> >              <xs:group ref=3D"GROUNDTERM" minOccurs=3D"0"=20
> > maxOccurs=3D"unbounded"/>
> >            </xs:sequence>
> >            <xs:attribute name=3D"ordered" type=3D"xs:string"
> fixed=3D"yes"/>
> >          </xs:complexType>
> >        </xs:element>=20
> >      </xs:sequence>
> >    </xs:complexType>
> >  </xs:element>=20
> >
> > Harold and Sandro stated their preference for solution 2.=20
> >
> > Shall we decide to go by it, and change Core, BLD and PRD accordingly?
> >
> > Cheers,
> >
> > Christian
> >
> > [1]
> http://lists.w3.org/Archives/Public/public-rif-wg/2010Jan/0028.html=20
> > and following thread
> >
> > PS: Just in case you check the schema in PRD, and wonder why it has=20
> > solution 1: I noticed the absence of IRIMETA sometimes ago when doing=20
> > tests with our implementation, and I made myself a note to correct
> that.=20
> > It is only after I made the correction in PRD, today, and I checked
> that=20
> > it was aligned with Core and BLD, that I remembered that no decision
> had=20
> > been made wrt the above discussion.
> >
> > IBM
> > 9 rue de Verdun
> > 94253 - Gentilly cedex - FRANCE
> > Tel. +33 1 49 08 35 00
> > Fax +33 1 49 08 35 10
> >
> >
> > Sauf indication contraire ci-dessus:/ Unless stated otherwise above:
> > Compagnie IBM France
> > Siege Social : 17 avenue de l'Europe, 92275 Bois-Colombes Cedex
> > RCS Nanterre 552 118 465
> > Forme Sociale : S.A.S.
> > Capital Social : 611.451.766,20 ?
> > SIREN/SIRET : 552 118 465 03644
> >
> >
> > --=_alternative 005A7720C125770C_=
> > Content-Type: text/html; charset="ISO-8859-1"
> > Content-Transfer-Encoding: quoted-printable
> >
> >
> > <br><font size=3D2 face=3D"sans-serif">Sandro, Harold, all,</font>
> > <br>
> > <br><font size=3D2 face=3D"sans-serif">We had an email discussion about
> that
> > bug in the syntax of rif:List (no IRIMETA) [1], but we never discussed
> > it at a telecon, nor did we make a decision on how to correct it or acted
> > to actually correct it.</font>
> > <br>
> > <br><font size=3D2 face=3D"sans-serif">There were two proposed
> corrections:=
> > </font>
> > <br>
> > <br><font size=3D2 face=3D"sans-serif">1. Just add the missing IRIMETA in
> t=
> > he
> > XML schema, changing it to (change GROUNDTERM to LISTELEMENT for
> BLD):</fon=
> > t>
> > <br><tt><font size=3D3>&nbsp;&lt;xs:element
> name=3D&quot;List&quot;&gt;<br>
> >  &nbsp; &lt;xs:complexType&gt;<br>
> >  &nbsp; &nbsp; &lt;xs:sequence&gt;<br>
> >  &nbsp; &nbsp; &nbsp; &lt;xs:group ref=3D&quot;IRIMETA&quot;
> minOccurs=3D&q=
> > uot;0&quot;
> > maxOccurs=3D&quot;1&quot;/&gt;<br>
> >  &nbsp; &nbsp; &nbsp; &lt;xs:group ref=3D&quot;GROUNDTERM&quot;
> minOccurs=
> > =3D&quot;0&quot;
> > maxOccurs=3D&quot;unbounded&quot;/&gt;<br>
> >  &nbsp; &nbsp; &lt;/xs:sequence&gt;<br>
> >  &nbsp; &lt;/xs:complexType&gt;<br>
> >  &lt;/xs:element&gt; </font></tt>
> > <br>
> > <br><font size=3D2 face=3D"sans-serif">2. Take the opportunity and align
> the
> > syntax of &lt;List&gt; with that of Atom and Expr, adding an &lt;items
> > ordered=3D&quot;yes&quot;&gt; role element, and changing the schema to
> the
> > same effect as (change GROUNDTERM to LISTELEMENT for BLD):</font>
> > <br><tt><font size=3D3>&nbsp;&lt;xs:element
> name=3D&quot;List&quot;&gt;<br>
> >  &nbsp; &lt;xs:complexType&gt;<br>
> >  &nbsp; &nbsp; &lt;xs:sequence&gt;<br>
> >  &nbsp; &nbsp; &nbsp; &lt;xs:group ref=3D&quot;IRIMETA&quot;
> minOccurs=3D&q=
> > uot;0&quot;
> > maxOccurs=3D&quot;1&quot;/&gt;</font></tt>
> > <br><tt><font size=3D3>&nbsp; &nbsp; &nbsp; &nbsp;&lt;xs:element
> name=3D&qu=
> > ot;items&quot;&gt;</font></tt>
> > <br><tt><font size=3D3>&nbsp; &nbsp; &nbsp; &nbsp;
> &nbsp;&lt;xs:complexType=
> > &gt;</font></tt>
> > <br><tt><font size=3D3>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
> &nbsp;&lt;xs:sequ=
> > ence&gt;<br>
> >  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;xs:group
> ref=3D&quot;GROUNDT=
> > ERM&quot;
> > minOccurs=3D&quot;0&quot; maxOccurs=3D&quot;unbounded&quot;/&gt;<br>
> >  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;/xs:sequence&gt;<br>
> >  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;xs:attribute
> name=3D&quot;ordered&q=
> > uot;
> > type=3D&quot;xs:string&quot; fixed=3D&quot;yes&quot;/&gt;<br>
> >  &nbsp; &nbsp; &nbsp; &nbsp; &lt;/xs:complexType&gt;<br>
> >  &nbsp; &nbsp; &nbsp; &lt;/xs:element&gt; </font></tt>
> > <br><tt><font size=3D3>&nbsp; &nbsp; &nbsp;&lt;/xs:sequence&gt;<br>
> >  &nbsp; &lt;/xs:complexType&gt;<br>
> >  &lt;/xs:element&gt; </font></tt>
> > <br>
> > <br><font size=3D2 face=3D"sans-serif">Harold and Sandro stated their
> prefe=
> > rence
> > for solution 2. </font>
> > <br>
> > <br><font size=3D2 face=3D"sans-serif">Shall we decide to go by it, and
> cha=
> > nge
> > Core, BLD and PRD accordingly?</font>
> > <br>
> > <br><font size=3D2 face=3D"sans-serif">Cheers,</font>
> > <br>
> > <br><font size=3D2 face=3D"sans-serif">Christian</font>
> > <br>
> > <br><font size=3D2 face=3D"sans-serif">[1] </font><a href=3D"
> http://lists.w=
> > 3.org/Archives/Public/public-rif-wg/2010Jan/0028.html"><font size=3D2
> face=
> > =3D"sans-serif">
> http://lists.w3.org/Archives/Public/public-rif-wg/2010Jan/0=
> > 028.html</font></a><font size=3D2 face=3D"sans-serif">
> > and following thread</font>
> > <br>
> > <br><font size=3D2 face=3D"sans-serif">PS: Just in case you check the
> schema
> > in PRD, and wonder why it has solution 1: I noticed the absence of
> IRIMETA
> > sometimes ago when doing tests with our implementation, and I made myself
> > a note to correct that. It is only after I made the correction in PRD,
> > today, and I checked that it was aligned with Core and BLD, that I
> remember=
> > ed
> > that no decision had been made wrt the above discussion.</font>
> > <br>
> > <br><font size=3D2 face=3D"sans-serif">IBM<br>
> > 9 rue de Verdun<br>
> > 94253 - Gentilly cedex - FRANCE<br>
> > Tel. +33 1 49 08 35 00<br>
> > Fax +33 1 49 08 35 10<br>
> > <br>
> > <br>
> > Sauf indication contraire ci-dessus:/ Unless stated otherwise above:<br>
> > Compagnie IBM France<br>
> > Siege Social : 17 avenue de l'Europe, 92275 Bois-Colombes Cedex<br>
> > RCS Nanterre 552 118 465<br>
> > Forme Sociale : S.A.S.<br>
> > Capital Social : 611.451.766,20 &#8364;<br>
> > SIREN/SIRET : 552 118 465 03644<br>
> > <br>
> > </font>
> > --=_alternative 005A7720C125770C_=--
> >
>
>

Received on Saturday, 24 April 2010 23:49:54 UTC