You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Piroumian Konstantin <KP...@protek.com> on 2002/08/22 15:47:19 UTC
RE: new W3C xforms 1.0 draft - changes affect cocoon xforms imple
mentation
> From: Simon Price [mailto:simon.price@bristol.ac.uk]
>
> There's a new "XForms 1.0, W3C Working Draft 21 August 2002" that
> changes the names of some of the elements plus other minor changes.
> Cocoon 2.1 might want to use the new names (eg. selectOne -> select1,
> selectMany -> select)?
Hm... selectOne -> select1 ?! Isn't it a typo?
If not then, IMHO, it's much better to have something like 'singleSelect',
'multiSelect'.
Konstantin
>
> See http://www.w3.org/TR/2002/WD-xforms-20020821/
>
> Cheers
>
> Simon
>
> -------------------------------------------------------------------
> Simon Price
> Institute for Learning and Research Technology
> University of Bristol
> 8-10 Berkeley Square
> Bristol BS8 1HH
> United Kingdom
>
> Direct: +44 (0)7071 226 720
> Office: +44 (0)117 928 7193
> Fax: +44 (0)117 928 7112
> Simon.Price@bristol.ac.uk
> http://www.ilrt.bristol.ac.uk
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: new W3C xforms 1.0 draft - changes affect cocoon xforms implementation
Posted by Torsten Curdt <tc...@dff.st>.
On Thursday 22 August 2002 15:52, Simon Price wrote:
> Piroumian Konstantin wrote:
> >>From: Simon Price [mailto:simon.price@bristol.ac.uk]
> >>
> >>There's a new "XForms 1.0, W3C Working Draft 21 August 2002" that
> >>changes the names of some of the elements plus other minor changes.
> >>Cocoon 2.1 might want to use the new names (eg. selectOne -> select1,
> >>selectMany -> select)?
> >
> > Hm... selectOne -> select1 ?! Isn't it a typo?
> >
> > If not then, IMHO, it's much better to have something like
> > 'singleSelect', 'multiSelect'.
> >
> > Konstantin
>
> I think you're right but its probably a good idea to keep as close to
> the xforms standards as possible - even if "select1" sucks as a name ;-)
(Thousands of dicussions later) I still see no reason for that...
...we are *NOT* implementing xforms because it's not ment to be implemented
for server side techniques (although chiba does quite a good job on it...)
I wouldn't care about the new spec...
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: new W3C xforms 1.0 draft - changes affect cocoon xforms implementation
Posted by Ivelin Ivanov <iv...@apache.org>.
Konstantin,
since you're on the XForms list,
you can add my vote to the names that you propose.
----- Original Message -----
From: "Simon Price" <si...@bristol.ac.uk>
To: <co...@xml.apache.org>
Sent: Thursday, August 22, 2002 8:52 AM
Subject: Re: new W3C xforms 1.0 draft - changes affect cocoon xforms
implementation
> Piroumian Konstantin wrote:
>
> >>From: Simon Price [mailto:simon.price@bristol.ac.uk]
> >>
> >>There's a new "XForms 1.0, W3C Working Draft 21 August 2002" that
> >>changes the names of some of the elements plus other minor changes.
> >>Cocoon 2.1 might want to use the new names (eg. selectOne -> select1,
> >>selectMany -> select)?
> >>
> >
> > Hm... selectOne -> select1 ?! Isn't it a typo?
> >
> > If not then, IMHO, it's much better to have something like
'singleSelect',
> > 'multiSelect'.
> >
> > Konstantin
>
> I think you're right but its probably a good idea to keep as close to
> the xforms standards as possible - even if "select1" sucks as a name ;-)
>
> Simon
>
> -------------------------------------------------------------------
> Simon Price
> Institute for Learning and Research Technology
> University of Bristol
> 8-10 Berkeley Square
> Bristol BS8 1HH
> United Kingdom
>
> Direct: +44 (0)7071 226 720
> Office: +44 (0)117 928 7193
> Fax: +44 (0)117 928 7112
> Simon.Price@bristol.ac.uk
> http://www.ilrt.bristol.ac.uk
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: new W3C xforms 1.0 draft - changes affect cocoon xforms implementation
Posted by Simon Price <si...@bristol.ac.uk>.
Piroumian Konstantin wrote:
>>From: Simon Price [mailto:simon.price@bristol.ac.uk]
>>
>>There's a new "XForms 1.0, W3C Working Draft 21 August 2002" that
>>changes the names of some of the elements plus other minor changes.
>>Cocoon 2.1 might want to use the new names (eg. selectOne -> select1,
>>selectMany -> select)?
>>
>
> Hm... selectOne -> select1 ?! Isn't it a typo?
>
> If not then, IMHO, it's much better to have something like 'singleSelect',
> 'multiSelect'.
>
> Konstantin
I think you're right but its probably a good idea to keep as close to
the xforms standards as possible - even if "select1" sucks as a name ;-)
Simon
-------------------------------------------------------------------
Simon Price
Institute for Learning and Research Technology
University of Bristol
8-10 Berkeley Square
Bristol BS8 1HH
United Kingdom
Direct: +44 (0)7071 226 720
Office: +44 (0)117 928 7193
Fax: +44 (0)117 928 7112
Simon.Price@bristol.ac.uk
http://www.ilrt.bristol.ac.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org