<?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>Nick Gall &#187; extensibility</title>
	<atom:link href="http://blogs.gartner.com/nick_gall/category/extensibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/nick_gall</link>
	<description>A member of the Gartner Blog Network</description>
	<lastBuildDate>Mon, 12 Sep 2011 20:14:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Linked Data: Turning Stovepiped Data Into a Web of Data</title>
		<link>http://blogs.gartner.com/nick_gall/2008/09/19/linked-data-turning-stovepiped-data-into-a-web-of-data/</link>
		<comments>http://blogs.gartner.com/nick_gall/2008/09/19/linked-data-turning-stovepiped-data-into-a-web-of-data/#comments</comments>
		<pubDate>Fri, 19 Sep 2008 21:07:40 +0000</pubDate>
		<dc:creator>Nick Gall</dc:creator>
				<category><![CDATA[WOA]]></category>
		<category><![CDATA[extensibility]]></category>
		<category><![CDATA[information architecture]]></category>
		<category><![CDATA[IFaPs]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/nick_gall/?p=12</guid>
		<description><![CDATA[In talking with clients about SOA, WOA, and application integration generally, the conversation often turns to best practices for their IFaPs (Identifiers, Formats, and Protocols). First I always stress, as Tim Berners-Lee does, that of the three (I,F, and P) &#8212; Identifiers are by far the most important to information sharing. After all, the Web [...]]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal">In talking with clients about SOA, WOA, and application integration generally, the conversation often turns to best practices for their IFaPs (Identifiers, Formats, and Protocols). First I always stress, as Tim Berners-Lee does, that of the three (I,F, and P) &#8212; Identifiers are by far the most important to information sharing. After all, the Web is fundamentally a web of LINKS!</p>
<p class="MsoNormal">After such conversations, I typical send a follow up email with some good examples of &#8220;linked data&#8221; and some pointers on versioning IFaPs &#8212; two of the most critical aspects of a successful information architecture IMO. Here is one such example&#8230;</p>
<p class="MsoNormal"><span style="font-family: Arial;font-size: x-small"><span>Here are some links to the Linked  Data initiatives I mentioned:</span></span></p>
<ol type="1">
<li class="MsoNormal"><span style="font-family: Arial;font-size: x-small"><span><a title="http://en.wikipedia.org/wiki/Linked_Data" href="http://en.wikipedia.org/wiki/Linked_Data">http://en.wikipedia.org/wiki/Linked_Data</a></span></span></li>
<li class="MsoNormal"><span style="font-family: Arial;font-size: x-small"><span><a title="http://en.wikipedia.org/wiki/Open_Data" href="http://en.wikipedia.org/wiki/Open_Data">http://en.wikipedia.org/wiki/Open_Data</a></span></span></li>
<li class="MsoNormal"><span style="font-family: Arial;font-size: x-small"><span><a title="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData" href="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData">http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData</a></span></span></li>
</ol>
<p class="MsoNormal"><span style="font-family: Arial;font-size: x-small"><span> I forgot to mention one other  pioneering effort in &#8220;linked data&#8221;: the use of XBRL by the FDIC et al and the  SEC. XBRL.org just published the US GAAP Taxonomies in XBRL &#8212; a major  achievement: <a title="http://xbrl.us/pages/us-gaap.aspx" href="http://xbrl.us/pages/us-gaap.aspx">http://xbrl.us/pages/us-gaap.aspx</a>   . The links on this page lead to a nice &#8220;taxonomy browser&#8221; that makes it  (relatively) easy to navigate these complex  taxonomies. </span></span></p>
<p class="MsoNormal"><span style="font-family: Arial;font-size: x-small"><span>Finally, we only mentioned it in  passing, but extensibility/versioning strategies for XML and other Web languages  (e.g., HTML) is another poorly understood topic. I think people read the X in  XML (meaning eXtensible) and believe (mistakenly) that XML is extensible by  default. It is NOT. Here are some useful references into the leading thinking on  this issue:</span></span></p>
<ol type="1">
<li class="MsoNormal"><span style="font-family: Arial;font-size: x-small"><span><a title="http://www.w3.org/2001/tag/doc/versioning-compatibility-strategies" href="http://www.w3.org/2001/tag/doc/versioning-compatibility-strategies">http://www.w3.org/2001/tag/doc/versioning-compatibility-strategies</a> </span></span></li>
<li class="MsoNormal"><span style="font-family: Arial;font-size: x-small"><span><a title="http://www.w3.org/2001/tag/doc/versioning" href="http://www.w3.org/2001/tag/doc/versioning">http://www.w3.org/2001/tag/doc/versioning</a> </span></span></li>
<li class="MsoNormal"><span style="font-family: Arial;font-size: x-small"><span><a title="http://www.w3.org/2001/tag/doc/versioning-xml" href="http://www.w3.org/2001/tag/doc/versioning-xml">http://www.w3.org/2001/tag/doc/versioning-xml</a> </span></span></li>
<li class="MsoNormal"><span style="font-family: Arial;font-size: x-small"><span><a title="http://www.pacificspirit.com/Authoring/Compatibility" href="http://www.pacificspirit.com/Authoring/Compatibility">http://www.pacificspirit.com/Authoring/Compatibility</a></span></span></li>
</ol>
<p class="MsoNormal"> </p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/nick_gall/2008/09/19/linked-data-turning-stovepiped-data-into-a-web-of-data/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

