From the Orbeon Forms Soapbox..

>
> I wanted to mention some colleagues reactions to OF for the
> first time.  I hope you don't mind any interruption.  Feel
> free to delete...
>
> I had a meeting with some colleagues a the San Diego
> Super computer Center at the University of California:
> http://www.sdsc.edu/
>
> It is interesting to be asked "where is your code" when
> I try to describe to them how an Orbeon Forms application
> is constructed. "But where are the Java Objects" is a
> typical response.  In the end, they are very
> impressed with the technology. Those working a lot with
> XML are astonished. PHP programmers are hard to persuade.
>
> I would say a key factor is the extent to which they need
> or want to work with XML, and whether they see XML as a
> message format or a data format.
>
> Some groups I work with have made multi-year efforts to
> create XML Schemas, http://diggsml.com/ that are
> derived from GML and include other standards formats
> (for units of measure, e.g.)  I think they clearly see
> the advantages of pipelining XML and having access to
> all the XPath functions and XSLT.
>
> There continue to be debates about REST and SOAP, but
> again, if you are trying to deliver the results of a
> SQL query, or you are the developer rather than the
> consumer of these services ;-) you will let a tool
> automate the process (and use SOAP).
>
> Very Best of Luck to you all,
> Hank
>
> NEES@UCSB
> http://nees.ucsb.edu/
> (website is in some big transition/disrepair, sorry)

> Hank,
>
> Thanks for sharing this. I can understand how building apps with  
> all these XML technologies will be a little surprising for Java or  
> PHP programmers ;-)
>
> There are some pretty cool benefits that can be pointed out (in  
> addition to the high compatibility with XML data).
>
> For example, we are now working on what we call the "noscript mode"  
> of the XForms engine. Because XForms is quite declarative, we are  
> now able to send to the browser pure HTML pages, while still  
> retaining the same XHTML+XForms source documents. As a developer,  
> you write XHTML+XForms. The engine then produces either a  
> JavaScript-based output, or a JavaScript-free output. Try doing  
> this with PHP or Java frameworks ;-)
>
> -Erik
>

>
> Erik,
>
> It would be especially helpful for accessibility compliance, which the
> University of California and others (Target) have faced legal action  
> over.
>
> There are a few other accessibility issues associated with dynamically
> changing content, but the ability to run JavaScript free is a big  
> step.
>
> The committees here that monitor our progress in this area will be
> very interested.
>
> Very best,
> Hank
>
> On Jul 14, 2008, at 4:43 PM, Erik Bruchez wrote:
>
>> Hank,
>>
>> Thanks for sharing this. I can understand how building apps with  
>> all these XML technologies will be a little surprising for Java or  
>> PHP programmers ;-)
>>
>> There are some pretty cool benefits that can be pointed out (in  
>> addition to the high compatibility with XML data).
>>
>> For example, we are now working on what we call the "noscript mode"  
>> of the XForms engine. Because XForms is quite declarative, we are  
>> now able to send to the browser pure HTML pages, while still  
>> retaining the same XHTML+XForms source documents. As a developer,  
>> you write XHTML+XForms. The engine then produces either a  
>> JavaScript-based output, or a JavaScript-free output. Try doing  
>> this with PHP or Java frameworks ;-)
>>
>> -Erik
>>
>
> Hank Ratzesberger
> NEES@UCSB
> Institute for Crustal Studies,
> University of California, Santa Barbara
> 805-893-8042
>
>
>
>
>
>
> --
> You receive this message as a subscriber of the [hidden email]  
> mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws