<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: My Notes from the 2010 MIT Sloan CIO Symposium Notes: Enterprise 3.0?</title>
	<atom:link href="http://www.fastforwardblog.com/2010/05/26/my-notes-from-the-2010-mit-sloan-cio-symposium-notes-enterprise-3-0/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fastforwardblog.com/2010/05/26/my-notes-from-the-2010-mit-sloan-cio-symposium-notes-enterprise-3-0/</link>
	<description></description>
	<lastBuildDate>Fri, 28 Oct 2011 01:28:22 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kingsley Idehen</title>
		<link>http://www.fastforwardblog.com/2010/05/26/my-notes-from-the-2010-mit-sloan-cio-symposium-notes-enterprise-3-0/comment-page-1/#comment-296218</link>
		<dc:creator>Kingsley Idehen</dc:creator>
		<pubDate>Fri, 04 Jun 2010 13:53:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/?p=4937#comment-296218</guid>
		<description>Bill,

Enterprise 3.0 is about adding Stuctured Linked Data to Enteprise 2.0. In a nutshell, every Blog, Wiki, Shared Bookmark System, Discussion Forum, Feed Aggregator, Photo Gallery etc.. becomes a Container of Data Objects (Data Items or Entities).

As per my Data 3.0 manifesto, each Data Object must be identified using a Name that Resolves to a Representation of its Description via a Descriptor Document (or Resource).

When the above is in place, you have enterprise collaboration solutions that work as follows:

1. Every user has an Identifier
2. Every Data Object (or Item) is associated with its Creator via said Creators Identifier (Name)
3. Every Data Object is Described via a Constellation of Attributes that coalesce around its Identifier (Name)
4. Collections of Data Objects resided in Data Spaces (nee. Web Sites) which are clearly Identified (Named) and associaed with their Creator(s) and hosted Data Items.

I hope this helps.

We should be able to refer-to and access representations-of data objects descriptors across public and private HTTP based networks without compromising security or privacy etc..

Links:

1. http://bit.ly/bmdv5N -- Data 3.0 Manifesto
2. http://www.slideshare.net/kidehen/meet-charlie-what-is-enterprise-30 -- Meet Charlie Mr. Enterprise 3.0

Kingsley</description>
		<content:encoded><![CDATA[<p>Bill,</p>
<p>Enterprise 3.0 is about adding Stuctured Linked Data to Enteprise 2.0. In a nutshell, every Blog, Wiki, Shared Bookmark System, Discussion Forum, Feed Aggregator, Photo Gallery etc.. becomes a Container of Data Objects (Data Items or Entities).</p>
<p>As per my Data 3.0 manifesto, each Data Object must be identified using a Name that Resolves to a Representation of its Description via a Descriptor Document (or Resource).</p>
<p>When the above is in place, you have enterprise collaboration solutions that work as follows:</p>
<p>1. Every user has an Identifier<br />
2. Every Data Object (or Item) is associated with its Creator via said Creators Identifier (Name)<br />
3. Every Data Object is Described via a Constellation of Attributes that coalesce around its Identifier (Name)<br />
4. Collections of Data Objects resided in Data Spaces (nee. Web Sites) which are clearly Identified (Named) and associaed with their Creator(s) and hosted Data Items.</p>
<p>I hope this helps.</p>
<p>We should be able to refer-to and access representations-of data objects descriptors across public and private HTTP based networks without compromising security or privacy etc..</p>
<p>Links:</p>
<p>1. <a href="http://bit.ly/bmdv5N" rel="nofollow">http://bit.ly/bmdv5N</a> &#8212; Data 3.0 Manifesto<br />
2. <a href="http://www.slideshare.net/kidehen/meet-charlie-what-is-enterprise-30" rel="nofollow">http://www.slideshare.net/kidehen/meet-charlie-what-is-enterprise-30</a> &#8212; Meet Charlie Mr. Enterprise 3.0</p>
<p>Kingsley</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rotkapchen</title>
		<link>http://www.fastforwardblog.com/2010/05/26/my-notes-from-the-2010-mit-sloan-cio-symposium-notes-enterprise-3-0/comment-page-1/#comment-295232</link>
		<dc:creator>Rotkapchen</dc:creator>
		<pubDate>Fri, 28 May 2010 05:48:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/?p=4937#comment-295232</guid>
		<description>Indeed, why not call it semantic web. You won&#039;t find me using the term E3.0 -- and I told a fellowe at EDS the same thing when he was attempting to write a research piece with the same title 4 years ago. 

It hardly seemed relevant for EDS to worry about E3.0 when they hadn&#039;t even begun to take a look at E2.0</description>
		<content:encoded><![CDATA[<p>Indeed, why not call it semantic web. You won&#8217;t find me using the term E3.0 &#8212; and I told a fellowe at EDS the same thing when he was attempting to write a research piece with the same title 4 years ago. </p>
<p>It hardly seemed relevant for EDS to worry about E3.0 when they hadn&#8217;t even begun to take a look at E2.0</p>
]]></content:encoded>
	</item>
</channel>
</rss>

