<?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/"
		>
<channel>
	<title>Comments on: XForms: binding to an optional element</title>
	<atom:link href="http://dubinko.info/blog/2010/01/20/xforms-binding/feed/" rel="self" type="application/rss+xml" />
	<link>http://dubinko.info/blog/2010/01/20/xforms-binding/</link>
	<description>From an XML geek, a reader, a writer, a connector, a man of the people (says keep hope alive)</description>
	<lastBuildDate>Sat, 01 Oct 2011 16:18:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Alessandro Vernet</title>
		<link>http://dubinko.info/blog/2010/01/20/xforms-binding/comment-page-1/#comment-4779</link>
		<dc:creator>Alessandro Vernet</dc:creator>
		<pubDate>Sat, 23 Jan 2010 08:08:55 +0000</pubDate>
		<guid isPermaLink="false">http://dubinko.info/blog/?p=782#comment-4779</guid>
		<description>Hi Micah,

One way (workaround?) to deal with this is to set the value of the element to empty when user select &quot;default&quot; in the select1. When doing the submission, before doing the xforms:send, set a flag in some other instance, and after the xforms:send, reset that flag. Define an xforms:bind that makes the element you want to remove non-relevant if the flag is set and its value is empty. This will make the element temporarily non-relevant just when the submission is done. This way the element won&#039;t be sent to the service you call, without impacting the controls.

Alex</description>
		<content:encoded><![CDATA[<p>Hi Micah,</p>
<p>One way (workaround?) to deal with this is to set the value of the element to empty when user select &#8220;default&#8221; in the select1. When doing the submission, before doing the xforms:send, set a flag in some other instance, and after the xforms:send, reset that flag. Define an xforms:bind that makes the element you want to remove non-relevant if the flag is set and its value is empty. This will make the element temporarily non-relevant just when the submission is done. This way the element won&#8217;t be sent to the service you call, without impacting the controls.</p>
<p>Alex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Fennell</title>
		<link>http://dubinko.info/blog/2010/01/20/xforms-binding/comment-page-1/#comment-4771</link>
		<dc:creator>Philip Fennell</dc:creator>
		<pubDate>Wed, 20 Jan 2010 15:01:25 +0000</pubDate>
		<guid isPermaLink="false">http://dubinko.info/blog/?p=782#comment-4771</guid>
		<description>Micah,

No I don&#039;t think there are any solutions in 1.1. I raised this issue three years ago on the www-forms mailing list . I was editing styles for SVG with XForms where the exact same issue occurs for style properties. For example, the absence of font-weight is the same as font-weight=&#039;normal&#039;, but when it&#039;s absent it is not relevant!

Have a look at the e-mail thread, it may be of use.</description>
		<content:encoded><![CDATA[<p>Micah,</p>
<p>No I don&#8217;t think there are any solutions in 1.1. I raised this issue three years ago on the www-forms mailing list . I was editing styles for SVG with XForms where the exact same issue occurs for style properties. For example, the absence of font-weight is the same as font-weight=&#8217;normal&#8217;, but when it&#8217;s absent it is not relevant!</p>
<p>Have a look at the e-mail thread, it may be of use.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

