<?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: A Memo to XBRL-US</title>
	<atom:link href="http://hitachidatainteractive.com/2007/02/06/a-memo-to-xbrl-us/feed/" rel="self" type="application/rss+xml" />
	<link>http://hitachidatainteractive.com/2007/02/06/a-memo-to-xbrl-us/</link>
	<description>XBRL News and Commentary from the Hitachi XBRL Business Unit</description>
	<lastBuildDate>Wed, 11 Apr 2012 17:47:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Max Rottersman</title>
		<link>http://hitachidatainteractive.com/2007/02/06/a-memo-to-xbrl-us/comment-page-1/#comment-44</link>
		<dc:creator>Max Rottersman</dc:creator>
		<pubDate>Fri, 09 Feb 2007 13:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hitachixbrl.com/2007/02/06/a-memo-to-xbrl-us/#comment-44</guid>
		<description>I couldn&#039;t agree with you more.  I still use Office 2000 Excel.  Until everyone is using a spreadsheet that can both read and write XBRL, out of the box, how much can we expect of XBRL in an end-user environment?  As you say, &quot;we find little enthusiasm for pushing the XBRL model down through the entire data delivery pipeline to end users.&quot;  The market has spoken. 

But you&#039;ve boiled down the features that everyone can benefit from today,

Organization, collection, and validation.  OCV all the way!

When I read about XBRL I get the sense they&#039;re trying to build the highways, roads, gas stations and cars.  I&#039;m with you (I think).  Focus on the Interstate and commercial trucking and let time and market catch up with the rest.</description>
		<content:encoded><![CDATA[<p>I couldn't agree with you more.  I still use Office 2000 Excel.  Until everyone is using a spreadsheet that can both read and write XBRL, out of the box, how much can we expect of XBRL in an end-user environment?  As you say, "we find little enthusiasm for pushing the XBRL model down through the entire data delivery pipeline to end users."  The market has spoken. </p>
<p>But you've boiled down the features that everyone can benefit from today,</p>
<p>Organization, collection, and validation.  OCV all the way!</p>
<p>When I read about XBRL I get the sense they're trying to build the highways, roads, gas stations and cars.  I'm with you (I think).  Focus on the Interstate and commercial trucking and let time and market catch up with the rest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David vun Kannon</title>
		<link>http://hitachidatainteractive.com/2007/02/06/a-memo-to-xbrl-us/comment-page-1/#comment-40</link>
		<dc:creator>David vun Kannon</dc:creator>
		<pubDate>Wed, 07 Feb 2007 14:57:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hitachixbrl.com/2007/02/06/a-memo-to-xbrl-us/#comment-40</guid>
		<description>It is certainly true that XBRL has had its greatest penetration in markets where the consumer is able to mandate its use to the producer, aka regulators. Where producers and consumers must negotiate to an agrrement on the value of using XBRL, we have so far seen a chicken-and-egg problem preventing adoption, even in cases such as the FFIEC, who are now sitting an ever growing pool of XBRL data.
My own expectation is that this situation will be resolved in one of two ways. Either the dam bursts, which in the case of the FFIEC means that consumers become convinced that the XBRL data, in aggregate, has become of compelling value, or a single savvy consumer attempts to obtain a first-mover advantage (however temporary) and sets off an arms race among consumers which precipitates a demand for XBRL from the producer.

I&#039;m not at all clear that XBRL US should entirely cease its evangelism for XBRL outside the regulatory use case. It would be better off to just tailor investmwents to expected near term payoffs rather than distant future goals.</description>
		<content:encoded><![CDATA[<p>It is certainly true that XBRL has had its greatest penetration in markets where the consumer is able to mandate its use to the producer, aka regulators. Where producers and consumers must negotiate to an agrrement on the value of using XBRL, we have so far seen a chicken-and-egg problem preventing adoption, even in cases such as the FFIEC, who are now sitting an ever growing pool of XBRL data.<br />
My own expectation is that this situation will be resolved in one of two ways. Either the dam bursts, which in the case of the FFIEC means that consumers become convinced that the XBRL data, in aggregate, has become of compelling value, or a single savvy consumer attempts to obtain a first-mover advantage (however temporary) and sets off an arms race among consumers which precipitates a demand for XBRL from the producer.</p>
<p>I'm not at all clear that XBRL US should entirely cease its evangelism for XBRL outside the regulatory use case. It would be better off to just tailor investmwents to expected near term payoffs rather than distant future goals.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

