Hi Alex,
Le mercredi 02 f�vrier 2005 � 15:11 -0800, Alessandro Vernet a �crit :
> --- Eric van der Vlist <[EMAIL PROTECTED]> wrote:
>
> > Good news: http://www.mozilla.org/press/mozilla-2005-02-02.html...
> >
> > I think that Presentation Server is in a unique position to enable web
> > applications that can speak XForms with browsers that support it and do
> > server side XForms with the others and I am wondering how difficult that
> > would be to implement.
>
> Indeed, this is great news. We love to see XForms is getting more coverage
> and in the future we want leverage client-side implementations when
> available, and this in a way that is transparent to the developer of a
> Presentation Server application. We have ideas on how to do this, but no
> definite architecture or implementation plan yet at this point.
Of course, that's still quite early and difficult for you to say, but
won't that have an impact on the forms we're designing today?
One thing I have noticed is that the support of XForms isn't always very
clearly separated from the application design.
One example of that is the way the instance mixes service information
needed for the server side implementation of XForms and the actual
document, the following structure being suggested:
<form>
<action/>
...
<document-id/>
<document>
...
</document>
</form>
This structure has an impact on all the XPath expressions written in
pipelines or XSLT transformations.
Now, if we migrate to client side XSLT, will this structure still be the
same?
Probably not. Actions used for things such as adding repeated items will
not be needed any longer, instances will only be uploaded if they don't
have errors, ...
I am wondering if that wouldn't be a good thing (for a future release)
to try to decouple the server side implementation from the XForms
itself.
This could include normalising a server side envelope that encapsulate
actual instance documents and also providing the envelope and the actual
instance document as two different inputs.
We could then write XPath expressions against the root of the actual
instance that would be independent of the envelope.
That can be done right now by replacing "/form/document/root" by
"//root". Maybe we should consider that a good practise even if it can
have impacts on the performances?
What do you think?
Are there other evolutions and/or good practises that could maximise the
portability of XForms forms designed to run on Presentation Server?
Eric
>
--
Tired of typing XML tags?
http://wikiml.org
------------------------------------------------------------------------
Eric van der Vlist http://xmlfr.org http://dyomedea.com
(ISO) RELAX NG ISBN:0-596-00421-4 http://oreilly.com/catalog/relax
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
orbeon-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/orbeon-user
