<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Arkytekture &#187; Text</title>
	<atom:link href="http://psoug.org/blogs/arkytekture/tag/text/feed/" rel="self" type="application/rss+xml" />
	<link>http://psoug.org/blogs/arkytekture</link>
	<description>Oracle and Data architecture blog</description>
	<lastBuildDate>Sat, 18 Dec 2010 17:22:43 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>What&#8217;s your XML strategy?</title>
		<link>http://psoug.org/blogs/arkytekture/2010/04/15/whats-your-xml-strategy/</link>
		<comments>http://psoug.org/blogs/arkytekture/2010/04/15/whats-your-xml-strategy/#comments</comments>
		<pubDate>Fri, 16 Apr 2010 01:49:38 +0000</pubDate>
		<dc:creator>arkytekture</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[CLOB]]></category>
		<category><![CDATA[language]]></category>
		<category><![CDATA[LOB Index]]></category>
		<category><![CDATA[LOB Segment]]></category>
		<category><![CDATA[Text]]></category>
		<category><![CDATA[XML]]></category>
		<category><![CDATA[XMLType]]></category>
		<category><![CDATA[XSD]]></category>

		<guid isPermaLink="false">http://psoug.org/blogs/arkytekture/?p=10</guid>
		<description><![CDATA[The choices you have on implementing XML depends upon the architecture of your solution. 1) Do you plan to a) parse the XML docs and store them into multiple relational tables&#160;&#160; ? If so, what languages or techniques do you intend to use to accomplish this? b) store an XML doc in a single XMLType [...]]]></description>
				<content:encoded><![CDATA[<p>The choices you have on implementing XML depends upon the architecture of your solution.</p>
<h2>1) Do you plan to</h2>
<p>a) parse the XML docs and store them into multiple relational tables&nbsp;&nbsp; ?</p>
<p style="padding-left: 30px"><em>If so, what languages or techniques do you intend to use to accomplish this?</em></p>
<p>b) store an XML doc in a single XMLType column in the Oracle database?</p>
<p style="padding-left: 30px"><em>Do you need to index the data to perform XML or &quot;free text&quot; searches?</em></p>
<p style="padding-left: 30px"><em>If so, what XPATH indexing do you intend to perform?</em></p>
<p>c) Register XSD as an XML Schema and have Oracle validate incoming XML documents such that<br />
	data is automatically shredded into object-relational tables based upon the different<br />
	types and attributes?</p>
<p style="padding-left: 30px"><em>If you choose (c), how will you reload and revalidate data against the new XSD should<br />
	new data elements become available in the XSD?</em></p>
<h2>2) How important is it to preserve the exact XML document ingested in Oracle?</h2>
<p>&nbsp;</p>
<p><li>Will you&nbsp; need to reconstruct or otherwise output data in the exact format to interchange with<br />
		people working in a regulated industry such as banking, health care, education ?</li>
</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<li>Or will a logical copy that is faithful to the structure be acceptable?</li>
<p>&nbsp;</p>
<h2>About Character Large Objects (CLOBs)</h2>
<p>Yes, you can store CLOBs in line with a database row up to 4,000 characters, else it&#39;s written to a separate LOB segment.</p>
<p>	Oracle automatically creates LOB indexes whether you want them or not, so you might want to review the non-XML CLOBS in your design and determine whether they would be well under the 4,000 characters and thus fit into a VARCHAR2 data column.</p>
]]></content:encoded>
			<wfw:commentRss>http://psoug.org/blogs/arkytekture/2010/04/15/whats-your-xml-strategy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
