<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Xforms to the fore?</title>
	<atom:link href="http://dharmeshmistry.wordpress.com/2008/08/26/xforms-to-the-fore/feed/" rel="self" type="application/rss+xml" />
	<link>http://dharmeshmistry.wordpress.com/2008/08/26/xforms-to-the-fore/</link>
	<description></description>
	<lastBuildDate>Tue, 11 Aug 2009 09:53:46 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Д</title>
		<link>http://dharmeshmistry.wordpress.com/2008/08/26/xforms-to-the-fore/#comment-86</link>
		<dc:creator>Д</dc:creator>
		<pubDate>Fri, 22 May 2009 08:39:55 +0000</pubDate>
		<guid isPermaLink="false">http://dharmeshmistry.wordpress.com/?p=50#comment-86</guid>
		<description>Да тут и добавить то нечего, спасибо всё толково.</description>
		<content:encoded><![CDATA[<p>Да тут и добавить то нечего, спасибо всё толково.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Bruchez</title>
		<link>http://dharmeshmistry.wordpress.com/2008/08/26/xforms-to-the-fore/#comment-18</link>
		<dc:creator>Erik Bruchez</dc:creator>
		<pubDate>Wed, 17 Sep 2008 18:15:58 +0000</pubDate>
		<guid isPermaLink="false">http://dharmeshmistry.wordpress.com/?p=50#comment-18</guid>
		<description>Hi Dharmesh,

I think it is fair to say that XForms requires a learning curve. That is also the price to pay for having an XML-based data model and a pretty smart processing model. This said, the XForms Working Group does have a &quot;simplified syntax&quot; in the works, to lower the barrier to entry.

The Working Group&#039;s wiki has a section about future features being discussed, if you have any interest:

http://www.w3.org/MarkUp/Forms/wiki/XForms_Future_Features

But clearly, defining standards takes time ;-)

-Erik</description>
		<content:encoded><![CDATA[<p>Hi Dharmesh,</p>
<p>I think it is fair to say that XForms requires a learning curve. That is also the price to pay for having an XML-based data model and a pretty smart processing model. This said, the XForms Working Group does have a &#8220;simplified syntax&#8221; in the works, to lower the barrier to entry.</p>
<p>The Working Group&#8217;s wiki has a section about future features being discussed, if you have any interest:</p>
<p><a href="http://www.w3.org/MarkUp/Forms/wiki/XForms_Future_Features" rel="nofollow">http://www.w3.org/MarkUp/Forms/wiki/XForms_Future_Features</a></p>
<p>But clearly, defining standards takes time <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>-Erik</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dharmesh Mistry</title>
		<link>http://dharmeshmistry.wordpress.com/2008/08/26/xforms-to-the-fore/#comment-16</link>
		<dc:creator>Dharmesh Mistry</dc:creator>
		<pubDate>Mon, 01 Sep 2008 08:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://dharmeshmistry.wordpress.com/?p=50#comment-16</guid>
		<description>Thanks for your post Erik.

I am aware that there is a server side rendering option within xForms, and certainly that Orbeon is a great example of that option. 

I think the challenges that XForms faces (and even the other &quot;standards&quot;)is making the standard mass market, which would require the syntactical nature to become accessible to less skilled developers. This is something Steve Pemberton alluded to as the next phase of Xforms at a UK conference at IBM a few years ago. Unfortunately we&#039;ve seen little progress of that.

The base approach of Orbeon is a great idea and edge IPK shares much of the philosphies you do, except we have not tied ourselves in exclusively to xForms. 

Another challenge is moving xForms into the presentation layer, currently we would charactise it only as a Forms subsegment, and our experience with clients would suggest that this is a key issue. Many forms tend to be parts of complete applications rather than standalone forms and as such have additional issues to cater for example security, menu driven, session data control etc...

kind regards - Dharmesh</description>
		<content:encoded><![CDATA[<p>Thanks for your post Erik.</p>
<p>I am aware that there is a server side rendering option within xForms, and certainly that Orbeon is a great example of that option. </p>
<p>I think the challenges that XForms faces (and even the other &#8220;standards&#8221;)is making the standard mass market, which would require the syntactical nature to become accessible to less skilled developers. This is something Steve Pemberton alluded to as the next phase of Xforms at a UK conference at IBM a few years ago. Unfortunately we&#8217;ve seen little progress of that.</p>
<p>The base approach of Orbeon is a great idea and edge IPK shares much of the philosphies you do, except we have not tied ourselves in exclusively to xForms. </p>
<p>Another challenge is moving xForms into the presentation layer, currently we would charactise it only as a Forms subsegment, and our experience with clients would suggest that this is a key issue. Many forms tend to be parts of complete applications rather than standalone forms and as such have additional issues to cater for example security, menu driven, session data control etc&#8230;</p>
<p>kind regards &#8211; Dharmesh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Bruchez</title>
		<link>http://dharmeshmistry.wordpress.com/2008/08/26/xforms-to-the-fore/#comment-15</link>
		<dc:creator>Erik Bruchez</dc:creator>
		<pubDate>Wed, 27 Aug 2008 15:35:58 +0000</pubDate>
		<guid isPermaLink="false">http://dharmeshmistry.wordpress.com/?p=50#comment-15</guid>
		<description>Hi,

Good to see interest in XForms.

Luckily, you do not need XForms implemented on the client to use XForms. There are alternatives, including Ajax-based implementations (Orbeon Forms, of which I am a developer), and JavaScript implementations (Ubiquity XForms). Both these examples are entirely open source.

BTW I don&#039;t think that so far any forms technology has come close to XForms. Web Forms 2.0 / HTML 5 improves on HTML forms, which is great, but 1) this pales in comparison with XForms and 2) this is not available in browsers today either.

-Erik</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Good to see interest in XForms.</p>
<p>Luckily, you do not need XForms implemented on the client to use XForms. There are alternatives, including Ajax-based implementations (Orbeon Forms, of which I am a developer), and JavaScript implementations (Ubiquity XForms). Both these examples are entirely open source.</p>
<p>BTW I don&#8217;t think that so far any forms technology has come close to XForms. Web Forms 2.0 / HTML 5 improves on HTML forms, which is great, but 1) this pales in comparison with XForms and 2) this is not available in browsers today either.</p>
<p>-Erik</p>
]]></content:encoded>
	</item>
</channel>
</rss>
