<?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: XML and Data</title>
	<atom:link href="http://dandube.com/blog/?feed=rss2&#038;p=332" rel="self" type="application/rss+xml" />
	<link>http://dandube.com/blog/?p=332</link>
	<description></description>
	<lastBuildDate>Fri, 19 Mar 2010 08:28:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Eric Likness</title>
		<link>http://dandube.com/blog/?p=332&#038;cpage=1#comment-92</link>
		<dc:creator>Eric Likness</dc:creator>
		<pubDate>Mon, 24 Aug 2009 16:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://dandube.com/blog/?p=332#comment-92</guid>
		<description>XML definitely held sway for a while until people started bumping into the extra characters problem. Some people advocated using Binary XML where all the UTF-8 and ASCII was just converted over into a binary format in order to traverse the Interwebs easily. In that case the issue was packet size and speed of transmission. But for databases, Hmmm. Good Question. The DTD for a given document is supposed to hold all the schema stuff that the Oracle &#039;external&#039; file is supposed to keep records for. In that way it gets schmematized once, then all your XML is just data with each field relating back to th DTD hosted centrally at the WC3 or your own webserver. That way everything is uniform and consistent.

Maybe what you need is an XSL Transform of what you get to map more easily into tables and rows. The real issue is Objects versus Table and Rows again. XML is more about objects, or flat files even whereas SQL is always tables and rows.</description>
		<content:encoded><![CDATA[<p>XML definitely held sway for a while until people started bumping into the extra characters problem. Some people advocated using Binary XML where all the UTF-8 and ASCII was just converted over into a binary format in order to traverse the Interwebs easily. In that case the issue was packet size and speed of transmission. But for databases, Hmmm. Good Question. The DTD for a given document is supposed to hold all the schema stuff that the Oracle &#8216;external&#8217; file is supposed to keep records for. In that way it gets schmematized once, then all your XML is just data with each field relating back to th DTD hosted centrally at the WC3 or your own webserver. That way everything is uniform and consistent.</p>
<p>Maybe what you need is an XSL Transform of what you get to map more easily into tables and rows. The real issue is Objects versus Table and Rows again. XML is more about objects, or flat files even whereas SQL is always tables and rows.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
