Re: Unfortunate choice of attribute name in XForms 1.1: xforms:submission/@target

Rogelio -- you are right, but it has been 're-introduced' in XHTML 1.1

And Erik, you are exactly right that we need this, but I think John's
answer might cover this.

John says that @target could be used in a number of ways depending on
the context, and the reason this is legitimate is that in XHTML
@target is actually only a hint.

It's probably obvious why it's a hint--if a browser doesn't have
support for multiple windows, or is only a small screen device or a
photocopier, then @target="x" might have to do nothing. It's not
dissimilar to the way we do some things in XForms, in that it captures
the 'authors intent', but that doesn't necessarily mean that the
author will get what they want in all environments.

So the question is about whether it being a hint is appropriate to all
uses of @target in XForms (i.e., there may be situations where the
processor _must_ act in a certain way, in which case you might argue
it's no longer a hint). I haven't been through and looked at them,



2008/4/8 Rogelio Pérez Cano <>:
>  Hi Erik, all,
>   please correct me if I´m wrong but at least in XHTML 1.0 Strict the
>  "target" attribute doesn´t exist, so I´m not sure if it´s going to be a
>  problem, for sure xhtml/html experts in the group may have better opinion on
>  it.
>  Regards.
>  Roger.
>  -----Mensaje original-----
>  De: [] En
>  nombre de Erik Bruchez
>  Enviado el: martes, 08 de abril de 2008 2:24
>  Para: Forms WG (new)
>  Asunto: Unfortunate choice of attribute name in XForms 1.1:
> xforms:submission/@target
>  All,
>  It just occurred to me that the XForms 1.1 xforms:submission/@target
>  attribute [1] is badly chosen.
>  The reason is that a "target", in HTML speak, specifies an optional target
>  window or frame. This, in particular, applies to <a> and <form> in HTML. [2]
>  In the future, we may want to officially support such a concept of target
>  window or frame in XForms. Purely out of familiarity with HTML, the name
>  "target" would be an obvious choice. But if we use "target"
>  now to specify the destination for data replacement, we won't be able to use
>  that name.
>  (Note that in our implementation, we already support an extension attribute
>  called xxforms:target on xforms:submission and xforms:load, which behaves
>  like its HTML counterpart.)
>  For this reason I suggest that we change the name of this attribute in
>  XForms 1.1. Suggestions are welcome, but "destination" could work.
>  -Erik
>  [1]
>  [2]
>  --
>  Orbeon Forms - Web Forms for the Enterprise Done the Right Way

 Mark Birbeck | +44 (0) 20 7689 9232 | Ltd. is registered in England and Wales, number 03730711
 The registered office is at:

 2nd Floor
 Titchfield House
 69-85 Tabernacle Street

Received on Wednesday, 9 April 2008 10:16:55 UTC