--- Ime Asangansi <asangansi at yahoo.com> wrote:

> Date: Wed, 9 Apr 2008 10:51:50 -0700 (PDT)
> From: Ime Asangansi <asangansi at yahoo.com>
> Subject: Re: xml archetypes to xforms
> To: adam.flinton at nhs.net
> 
> Hi Adams,
> 
> Please find my comments below:
> 
> > I have the XForms Engine up on the OHT site but they're waiting to "go 
> > public" (I have no real idea what the delay is but....)...hopefully 
> > anonymous access is an "any day now" event.
> > https://xmlprocess.projects.openhealthtools.org/
> 
> I have since downloaded but I had errors when I tried to run.
> I have sent you the tomcat log for your very kind scrutiny
> 
> 
> > This drill down is what is a bit of a pain at the moment were one to 
> > wish to open a template & then see a generated XForm GUI...
> 
> This would be the ultimate IMHO
> 
> > C) Wrt moving existing forms etc into Archetypes/templates etc what I've 
> > been playing with is OpenOffice as it's forms designer is XForms based & 
> > allows one to create a model/instance based form in a WYSIWYG way with 
> > all the niceties XForms offers wrt data analysis/mapping  e.g. types 
> > from both std XSD & your own schemas/simple types (e.g. restricting a 
> > length or applying a pattern). You can then map that model to the 
> > relevant templates/archetypes while allowing the users to be sure that 
> > you've captured all the fields that their current form captures. In a 
> > very neat move you can even exports that form as an Adobe pdf form.
> 
> cool... uh..
> 
> > D) What has raised itself as I've been playing with concepts to do with 
> > this is that you should be able to create a form at the lowest possible 
> > level & then accrete them into a whole i.e. a template/archetype should 
> > have it's own xform
> 
> This is really interesting to hear (in the absence of a template 
> specification, Adam.
> Here you are kind of talking about archetype xforms.
> I am really wondering how you convert those constraints stuff in the 
> definition part of the
> archetype into some cool xforms stuff.
> Adam, I didnt contribute to the archetype specs neither do I fully understand 
> it... but I kinda
> think this is the core issue
> 
> > which is locatable e.g. archFileName_xform.xhtml 
> > which then includes...etc. i.e. if I open a template xform & the xform 
> > contains other templates/archetypes etc it would be nice to simply load 
> > them via linking (e.g. xlink or similar) rather than some sort of 
> > involved drill down & render approach.
> > 
> > i.e. for a given archetype/template, the XForm is just for that 
> > archetype/tamplate & then includes the relevant form for the relevant 
> > child archetype/template etc.
> > 
> > an example is that you might have an "A&E admissions form" with a 
> > select1 tick box & a set of choices e.g. "has: head wound chest wound 
> > leg wound" & if you click head wound you would want to see the head 
> > wound form.
> > 
> > e.g.
> > 
> > http://internet-apps.blogspot.com/2006/08/using-subforms-in-xforms.html
> > 
> > 
> > It is possible that the operational template as per:
> > 
> > "- the XML templates should probably become .xts (ts = template
> > 
> > specification), because there will also be an operational template file, 
> > which is a template with all substitutions done, with an extension like 
> > .xot (ot = operational template) or .xtom (tom = template object model). 
> > The current 'templates' are template 'specifications', i.e. a set of 
> > differences with respect to archetypes. The 'operational' form is what 
> > can be used to create message definitions from, and can be used at runtime."
> 
> cool
> 
> 
> Thanks, Adam, for this
> 
> Cheers,
> Ime
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Reply via email to