Re: Ditch value=?

Just to be fair, XSLT has already this kind of thing

xsl:number contains @value and @select : one for immediate value, the other
for computed value

I don't feel much confusion there

Furthermore value makes clear the fact that we are waiting for a string

My 2 cents

Moz

On Wed, Mar 19, 2008 at 8:00 PM, Norman Walsh <ndw@nwalsh.com> wrote:

> Is it time to consider ditching value=?
>
> I gather (since there have been no screams of protest) that folks are
> mostly
> happy with the changes I made in the latest drafts. Those changes move us
> closer to XSLT in a lot of ways and I'm starting to feel like the
> select=/value= distinction is causing more confusion rather than less.
>
>                                        Be seeing you,
>                                          norm
>
> --
> Norman Walsh <ndw@nwalsh.com> | The way to get things done is not to
> http://nwalsh.com/            | mind who gets the credit of doing
>                              | them.--Benjamin Jowett
>



-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €