I think there's nothing in the spec that prevents such optimization. As
long as you can't tell the difference
from an interoperability perspective, it should be OK.
The tricky bit would be detecting whether the instance is being
referenced. During model construction,
the attempt to do xforms-rebuild and resolving UI bindings could all lead
to references of the data.
As far as I can tell, the only way the optimization you describe would be
of benefit is if the data is *never*
referenced except by actions. This seems like a fairly special case. I.e.
forms could be made to
work this way, but it would be at the expense of the benefits derived from
the declarative nature of the
xforms model.
John M. Boyer, Ph.D.
Senior Product Architect/Research Scientist
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com http://www.ibm.com/software/
"Rafael Benito" <rbenito@satec.es>
Sent by: www-forms-request@w3.org
08/29/2005 04:02 AM
To
<www-forms@w3.org>
cc
Subject
src instance attribute processing
Hi,
the data pointed by the "src" attribute must be processed at the initial
processing XForms. I think this is not necessary. It should be sufficient
if it were processed the firsr time a reference to such a data is used in
the application. There could be cases in which the execution never
makesreference to that data and, therefore, there is no need to process
it. This is of interest for small device XForms processing.
Regards,
Rafael Benito RuÃ­z de Villa
Responsable Sistemas de Negocio en Red
MÃ³vil (+34) 617 314 293
rbenito@satec.es
MADRID
Avda. Europa, 34 A
28023 Aravaca
Telf.: (+34) 91 708 90 00 / 91 211 03 00
Fax: (+34) 91 708 90 90 / 91 211 03 90