- From: T.V Raman <raman@google.com>
- Date: Mon, 8 Jun 2009 11:40:04 -0700
- To: ebruchez@orbeon.com
- Cc: public-forms@w3.org
we should consider xInclude -- but we should remember not to do this unlike the past where dependencies were inherited simply because "it was related W3C technology", Erik Bruchez writes: > Quick note on this: we need to at least consider the benefits/ > drawbacks of using XInclude, which provides a simple inclusion semantic. > > -Erik > > On May 27, 2009, at 8:09 AM, Steven Pemberton wrote: > > > Kicking off the future version discussion. Here is the first of the > > features I would like to see. > > > > External models > > > > <model id="tax" src="taxes.xml" /> > > > > This is above all useful for making several forms for editing a > > model, so that you don't have to keep updating the models all over > > the place as the details change. Binds can be used to shield the > > forms from internal model changes. > > > > I'm not sure that much has to change to support this, though we need > > to explicitely address the question of whether it is still ok that > > @bind is an idref > > > > <input model="tax" bind="income">... > > > > Maybe in XForms 2, we could change the use of IDREF into something > > else, so that we are not restricted in the same way as we have been > > (thereby making the switch in repeat problem go away). > > > > Steven > > > > -- > Orbeon Forms - Web Forms for the Enterprise Done the Right Way > http://www.orbeon.com/ > -- Best Regards, --raman Title: Research Scientist Email: raman@google.com WWW: http://emacspeak.sf.net/raman/ Google: tv+raman GTalk: raman@google.com, tv.raman.tv@gmail.com PGP: http://emacspeak.sf.net/raman/raman-almaden.asc
Received on Monday, 8 June 2009 18:40:52 UTC