xsltforms-support

[Xsltforms-support] XForms 2.0 new features and limitations due to id attribute

[Alain C. <ala...@ag...>]

Hello,

I just added a new post at XForms Users Community Group about XForms 2.0 
new features and limitations due to id attr: 
http://www.w3.org/community/xformsusers/2012/10/20/xforms-2-0-new-features-and-limitations-due-to-id-attribute-use/

Please join the community group and vote for the embedded poll!

Thanks!

-Alain

Re: [Xsltforms-support] XForms 2.0 new features and limitations due to id attribute

[Alexander H. <ale...@ho...>]

Hi Alain,

On Oct 20, 2012, at 11:35 AM, Alain Couthures wrote:

> Hello,
> 
> I just added a new post at XForms Users Community Group about XForms 2.0 
> new features and limitations due to id attr: 
> http://www.w3.org/community/xformsusers/2012/10/20/xforms-2-0-new-features-and-limitations-due-to-id-attribute-use/
> 
> Please join the community group and vote for the embedded poll!
> 
> Thanks!

getting rid of @id would be a great thing, IMHO.

Regarding the voting options - from your view point as an XForms implementor - can you please discuss a bit about the implications of

· Allow author to choose between @id and @name
  vs.
· Deprecate @id and use @name everywhere

Thanks a lot,
	Alex

Re: [Xsltforms-support] XForms 2.0 new features and limitations due to id attribute

[Alain C. <ala...@ag...>]

Hi Alex,

> getting rid of @id would be a great thing, IMHO.
>
> Regarding the voting options - from your view point as an XForms implementor - can you please discuss a bit about the implications of
>
> · Allow author to choose between @id and @name
>    vs.
> · Deprecate @id and use @name everywhere
>
If @id is deprecated, current implementations could ignore issues 
regarding it and new implementations would be allowed to not support it 
at all.

Choosing between @id and @name is much better for ascending compatibility.

BTW, actions, such as setfocus, toggle and dispatch, should be extended 
to work with @name.

-Alain