<?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: Creating case sensitive XML Attributes</title>
	<atom:link href="http://chafic.com/2003/06/26/creating-case-sensitive-xml-attributes/feed/" rel="self" type="application/rss+xml" />
	<link>http://chafic.com/2003/06/26/creating-case-sensitive-xml-attributes/</link>
	<description>Technical discussion of Flex, Flash, and RIA development</description>
	<lastBuildDate>Thu, 10 Apr 2008 01:10:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Steven Erat</title>
		<link>http://chafic.com/2003/06/26/creating-case-sensitive-xml-attributes/comment-page-1/#comment-57</link>
		<dc:creator>Steven Erat</dc:creator>
		<pubDate>Wed, 30 Jul 2003 19:55:51 +0000</pubDate>
		<guid isPermaLink="false">http://rewindlife.com/?p=21#comment-57</guid>
		<description>Sam,
Great post, thanks! I think that this may have solved the problem for which I created an xmlsearchnocase() udf.  There is a change in behavior when running CFXML_Blog on CFMX U3 vs running on the upcoming maintenance release where xmlattribute names were lowercased but are now uppercased while using the same code.  When I isolated the block of code used to save blog entries the difference in behavior could not be reproduced, so the problem must lie somewhere deeper in the blogging app.  My udf doubles the work by searching for both cases (ignoring mixed case possibilities) and then joining them into a single array for return.  With the information from this blog entry, I realize that I can just ensure that all xml attrs are created with structure syntax, and that should eliminate the need for a double-duty udf.
-Steve</description>
		<content:encoded><![CDATA[<p>Sam, </p>
<p>Great post, thanks! I think that this may have solved the problem for which I created an xmlsearchnocase() udf.  There is a change in behavior when running CFXML_Blog on CFMX U3 vs running on the upcoming maintenance release where xmlattribute names were lowercased but are now uppercased while using the same code.  When I isolated the block of code used to save blog entries the difference in behavior could not be reproduced, so the problem must lie somewhere deeper in the blogging app.  My udf doubles the work by searching for both cases (ignoring mixed case possibilities) and then joining them into a single array for return.  With the information from this blog entry, I realize that I can just ensure that all xml attrs are created with structure syntax, and that should eliminate the need for a double-duty udf.</p>
<p>-Steve</p>
]]></content:encoded>
	</item>
</channel>
</rss>

