<?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: Presentations from the Philadelphia Conference</title>
	<atom:link href="http://hitachidatainteractive.com/2007/01/19/presentations-from-the-philadelphia-conference/feed/" rel="self" type="application/rss+xml" />
	<link>http://hitachidatainteractive.com/2007/01/19/presentations-from-the-philadelphia-conference/</link>
	<description>XBRL News and Commentary from the Hitachi XBRL Business Unit</description>
	<lastBuildDate>Wed, 18 Jan 2012 04:45:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: David vun Kannon</title>
		<link>http://hitachidatainteractive.com/2007/01/19/presentations-from-the-philadelphia-conference/comment-page-1/#comment-94</link>
		<dc:creator>David vun Kannon</dc:creator>
		<pubDate>Tue, 27 Feb 2007 16:54:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hitachixbrl.com/2007/01/19/presentations-from-the-philadelphia-conference/#comment-94</guid>
		<description>Jay,


Yes, it is certainly possible for a company to create an extension that does this kind of rewiring of the calculation hierarchy. The issue is whether companies will do it or not. Current tools don&#039;t make it easy to correct the situation by suggesting how to solve this, or building the whole solution for the user. Instead, people just live with the situation.</description>
		<content:encoded><![CDATA[<p>Jay,</p>
<p>Yes, it is certainly possible for a company to create an extension that does this kind of rewiring of the calculation hierarchy. The issue is whether companies will do it or not. Current tools don't make it easy to correct the situation by suggesting how to solve this, or building the whole solution for the user. Instead, people just live with the situation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Chandran</title>
		<link>http://hitachidatainteractive.com/2007/01/19/presentations-from-the-philadelphia-conference/comment-page-1/#comment-61</link>
		<dc:creator>Jay Chandran</dc:creator>
		<pubDate>Fri, 16 Feb 2007 09:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hitachixbrl.com/2007/01/19/presentations-from-the-philadelphia-conference/#comment-61</guid>
		<description>Hi David, you indicate that &quot;if a taxonomy includes a sub-total not used by a company, it is very easy to generate a calculation inconsistency&quot;.

In such a case, shouldn&#039;t the taxonomy be extended to &#039;prohibit&#039; such a sub-total, thereby avoiding the calculation inconsistency?

Thanks, Jay</description>
		<content:encoded><![CDATA[<p>Hi David, you indicate that "if a taxonomy includes a sub-total not used by a company, it is very easy to generate a calculation inconsistency".</p>
<p>In such a case, shouldn't the taxonomy be extended to 'prohibit' such a sub-total, thereby avoiding the calculation inconsistency?</p>
<p>Thanks, Jay</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David vun Kannon</title>
		<link>http://hitachidatainteractive.com/2007/01/19/presentations-from-the-philadelphia-conference/comment-page-1/#comment-39</link>
		<dc:creator>David vun Kannon</dc:creator>
		<pubDate>Wed, 07 Feb 2007 14:41:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hitachixbrl.com/2007/01/19/presentations-from-the-philadelphia-conference/#comment-39</guid>
		<description>With respect to the presentation entitled &quot;HowValid Are They&quot;, there are two problems. One is the misleading title. Validity has a specific technical meaning in XML and in XBRL. None of the instance documents filed with the SEC are invalid. The second is the conflation of &quot;inconsistency&quot; with &quot;error&quot; in uses of the calculation linkbase networks of relationships. As an example, if a taxonomy includes a sub-total not used by a company, it is very easy to generate a calculation inconsistency. The study does not distinguish between these cases and cases where a material value is not reported in the instance, but can be found in the corresponding text filing.
Many of the other statistics gathered and discussed in the study are useful and interesting, and provide a good start on the field of taxonomy analysis. But the treatment of calculation inconsistencies and representation as errors is a serious flaw, in my view.</description>
		<content:encoded><![CDATA[<p>With respect to the presentation entitled "HowValid Are They", there are two problems. One is the misleading title. Validity has a specific technical meaning in XML and in XBRL. None of the instance documents filed with the SEC are invalid. The second is the conflation of "inconsistency" with "error" in uses of the calculation linkbase networks of relationships. As an example, if a taxonomy includes a sub-total not used by a company, it is very easy to generate a calculation inconsistency. The study does not distinguish between these cases and cases where a material value is not reported in the instance, but can be found in the corresponding text filing.<br />
Many of the other statistics gathered and discussed in the study are useful and interesting, and provide a good start on the field of taxonomy analysis. But the treatment of calculation inconsistencies and representation as errors is a serious flaw, in my view.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

