<?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>Simon Whatley &#187; FOAF</title>
	<atom:link href="http://www.simonwhatley.co.uk/tag/foaf/feed" rel="self" type="application/rss+xml" />
	<link>http://www.simonwhatley.co.uk</link>
	<description>The opposite of every great idea is another great idea</description>
	<lastBuildDate>Wed, 02 Nov 2011 09:28:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>An Introduction to the Semantic Web</title>
		<link>http://www.simonwhatley.co.uk/an-introduction-to-the-semantic-web</link>
		<comments>http://www.simonwhatley.co.uk/an-introduction-to-the-semantic-web#comments</comments>
		<pubDate>Fri, 18 Jun 2010 12:20:49 +0000</pubDate>
		<dc:creator>Simon</dc:creator>
				<category><![CDATA[Semantic Web]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[DCMI]]></category>
		<category><![CDATA[Dublin Core]]></category>
		<category><![CDATA[Dublin Core Metadata Initiative]]></category>
		<category><![CDATA[FOAF]]></category>
		<category><![CDATA[Friend of a Friend]]></category>
		<category><![CDATA[graphs]]></category>
		<category><![CDATA[HTTP]]></category>
		<category><![CDATA[Linked Data]]></category>
		<category><![CDATA[machine readable]]></category>
		<category><![CDATA[Natural Language Processing]]></category>
		<category><![CDATA[ontology]]></category>
		<category><![CDATA[OpenCalais]]></category>
		<category><![CDATA[OWL]]></category>
		<category><![CDATA[protocol]]></category>
		<category><![CDATA[PURL]]></category>
		<category><![CDATA[RDF]]></category>
		<category><![CDATA[RDF query language]]></category>
		<category><![CDATA[RDFa]]></category>
		<category><![CDATA[RDFs]]></category>
		<category><![CDATA[Resource Description Framework]]></category>
		<category><![CDATA[semantic]]></category>
		<category><![CDATA[SPARQL]]></category>
		<category><![CDATA[subject-predicate-object]]></category>
		<category><![CDATA[Thomson Reuters]]></category>
		<category><![CDATA[Tim Berners-Lee]]></category>
		<category><![CDATA[Triplestore]]></category>
		<category><![CDATA[Uniform Resource Identifier]]></category>
		<category><![CDATA[Uniform Resource Locator]]></category>
		<category><![CDATA[Uniform Resource Name]]></category>
		<category><![CDATA[URI]]></category>
		<category><![CDATA[url]]></category>
		<category><![CDATA[web of data]]></category>
		<category><![CDATA[Web Ontology Language]]></category>
		<category><![CDATA[world wide web]]></category>
		<category><![CDATA[XML]]></category>

		<guid isPermaLink="false">http://www.simonwhatley.co.uk/?p=3559</guid>
		<description><![CDATA[The Semantic Web is a web of data. There is lots of data we all use every day, and most of it is not part of the web. I can see my bank statements on the web, and my photographs, and I can see my appointments in a calendar. But can I see my photos in a calendar to see what I was doing when I took them and on a map so I know where I took them? Can I see bank statement lines in a calendar? The answer, right now, is no.]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://en.wikipedia.org/wiki/Semantic_Web" title="Wikipedia: Semantic Web" target="_blank" rel="nofollow">Semantic Web</a> is a <a href="http://en.wikipedia.org/wiki/Linked_Data" title="Wikipedia: Linked Data" target="_blank" rel="nofollow">web of data</a>. There is lots of data we all use every day, and most of it is not part of the web. I can see my bank statements on the web, and my photographs, and I can see my appointments in a calendar. But can I see my photos in a calendar to see what I was doing when I took them and on a map so I know where I took them? Can I see bank statement lines in a calendar? The answer, right now, is no.</p>
<p>But why not? Because we don&#8217;t have a web of data. Because data is controlled by applications, and each application keeps its data to itself; applications don&#8217;t like to share.</p>
<p>The original Web mainly concentrated on the interchange of documents, however, the Semantic Web is about two things: It is about common formats for integration and combination of data drawn from diverse sources. It is also about language for recording how the data relates to real world objects. That allows a person, or a machine, to start off in one database, and then move through an unending set of databases which are connected not by wires but by being about the same thing.</p>
<p>Tim Berners-Lee describes the Semantic Web vision as:</p>
<blockquote><p>I have a dream for the Web [in which computers] become capable of analysing all the data on the Web, the content, links, and transactions between people and computers. A Semantic Web, which should make this possible, has yet to emerge, but when it does, the day-to-day mechanisms of trade, bureaucracy and our daily lives will be handled by machines talking to machines. The intelligent agents people have touted for ages will finally materialise.</p></blockquote>
<p>What are the ideas and technologies that facilitate this vision? Below I give an overview and links to a number of them:</p>
<p><script type="text/javascript"><!--
google_ad_client = "pub-6475233631580417";
/* 468x60 Basic */
google_ad_slot = "7117418273";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
<h3>Linked Data</h3>
<p>Linked Data is about using the Web to connect related data that wasn&#8217;t previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. More specifically, Wikipedia defines Linked Data as &#8220;a term used to describe a recommended best practice for exposing, sharing, and connecting pieces of data, information, and knowledge on the Semantic Web using <abbr title="Uniform Resource Identifier">URIs</abbr> and <abbr title="Resource Description Framework">RDF</abbr>.&#8221;</p>
<ul>
<li><a href="http://linkeddata.org" title="Linked Data: Connect Distributed Data Across The Web" target="_blank" rel="nofollow">http://linkeddata.org</a></li>
<li><a href="http://en.wikipedia.org/wiki/Linked_Data" title="Wikipedia: Linked Data" target="_blank" rel="nofollow">http://en.wikipedia.org/wiki/Linked_Data</a></li>
</ul>
<h3>Resource Description Framework</h3>
<p>The Resource Description Framework (<abbr title="Resource Description Framework">RDF</abbr>) is a general-purpose language for representing information in the Web.</p>
<p>The <strong>Resource Description Framework Schema (<abbr title="Resource Description Framework Schema">RDF-S</abbr>)</strong> is a semantic extension of <abbr title="Resource Description Framework">RDF</abbr> that provides mechanisms for describing groups of related resources and the relationships between these resources.</p>
<ul>
<li><a href="http://www.w3.org/TR/rdf-schema/" title="World Wide Web Consortium: RDF Schema" target="_blank" rel="nofollow">http://www.w3.org/TR/rdf-schema/</a></li>
<li><a href="http://en.wikipedia.org/wiki/RDF_Schema" title="Wikipedia: RDF Schema" target="_blank" rel="nofollow">http://en.wikipedia.org/wiki/RDF_Schema</a></li>
</ul>
<p>The <strong>Resource Description Framework in Attributes (<abbr title="Resource Description Framework in Attributes">RDFa)</strong> allows authors to add meaning to web page elements. Using a few simple <abbr title="eXtensible HyperText Markup Language">XHTML</abbr> attributes, authors can mark up human-readable data with machine-readable indicators for browsers and other programs to interpret. A web page can include markup for items as simple as the title of an article, or as complex as a user&#8217;s complete social network.</p>
<ul>
<li><a href="http://www.w3.org/TR/xhtml-rdfa-primer/" title="World Wide Web Consortium: XHTML RDFa Primer" target="_blank" rel="nofollow">http://www.w3.org/TR/xhtml-rdfa-primer/</a></li>
<li><a href="http://en.wikipedia.org/wiki/RDFa" title="Wikipedia: RDFa" target="_blank" rel="nofollow">http://en.wikipedia.org/wiki/RDFa</a></li>
</ul>
<h3>Friend of a Friend (<abbr title="Friend of a Friend">FOAF</abbr>)</h3>
<p>The <em>Friend of a Friend</em> project is creating a Web of machine-readable pages describing people, the links between them and the things they create and do. <abbr title="Friend of a Friend">FOAF</abbr> is about your place in the Web, and the Web&#8217;s place in our world. <abbr title="Friend of a Friend">FOAF</abbr> is a simple technology that makes it easier to share and use information about people and their activities (eg. photos, calendars, weblogs), to transfer information between Web sites, and to automatically extend, merge and re-use it online.</p>
<ul>
<li><a href="http://www.foaf-project.org" title="FOAF Project" target="_blank" rel="nofollow">http://www.foaf-project.org</a></li>
<li><a href="http://en.wikipedia.org/wiki/FOAF_(software)" title="Wikipedia: FOAF (Software)" target="_blank" rel="nofollow">http://en.wikipedia.org/wiki/FOAF_(software)</a></li>
<li><a href="http://en.wikipedia.org/wiki/Friend_of_a_friend" title="Wikipedia: Friend of a Friend" target="_blank" rel="nofollow">http://en.wikipedia.org/wiki/Friend_of_a_friend</a></li>
<li><a href="http://xmlns.com/foaf/spec/" title="FOAF Vocabulary Specification" target="_blank" rel="nofollow">http://xmlns.com/foaf/spec/</a></li>
</ul>
<h3>Web Ontology Language (<abbr title="Web Ontology Language">OWL</abbr>)</h3>
<p>The <abbr title="Web Ontology Language">OWL</abbr> Web Ontology Language is designed for use by applications that need to process the content of information instead of just presenting information to humans. <abbr title="Web Ontology Language">OWL</abbr> facilitates greater machine interpretability of Web content than that supported by <abbr title="eXtensible Markup Language">XML</abbr>, <abbr title="Resource Description Framework">RDF</abbr>, and <abbr title="Resource Description Framework">RDF</abbr> Schema (<abbr title="Resource Description Framework Schema">RDF-S</abbr>) by providing additional vocabulary along with a formal semantics.</p>
<ul>
<li><a href="http://www.w3.org/TR/owl-features/" title="World Wide Web Consortium: OWL Web Ontology Language" target="_blank" rel="nofollow">http://www.w3.org/TR/owl-features/</a></li>
<li><a href="http://en.wikipedia.org/wiki/Web_Ontology_Language" title="Wikipedia: Web Ontology Language" target="_blank" rel="nofollow">http://en.wikipedia.org/wiki/Web_Ontology_Language</a></li>
</ul>
<p><script type="text/javascript"><!--
google_ad_client = "pub-6475233631580417";
/* 468x60 Basic */
google_ad_slot = "7117418273";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
<h3>Dublin Core Metadata Initiative (<abbr title="Dublin Core Metadata Initiative">DCMI</abbr>)</h3>
<p>The Dublin Core set of metadata elements provides a small and fundamental group of text elements through which most resources can be described and catalogued. Using only 15 base text fields, a Dublin Core metadata record can describe physical resources such as books, digital materials such as video, sound, image, or text files, and composite media like web pages. Metadata records based on Dublin Core are intended to be used for cross-domain information resource description and have become standard in the fields of library science and computer science. Implementations of Dublin Core typically make use of <abbr title="eXtensible Markup Language">XML</abbr> and are Resource Description Framework (<abbr title="Resource Description Framework">RDF</abbr>) based.</p>
<ul>
<li><a href="http://dublincore.org" title="Dublin Core Metadata Initiative" target="_blank" rel="nofollow">http://dublincore.org</a></li>
<li><a href="http://en.wikipedia.org/wiki/Dublin_core" title="Wikipedia: Dublin Core" target="_blank" rel="nofollow">http://en.wikipedia.org/wiki/Dublin_core</a></li>
</ul>
<h3>Triplestore</h3>
<p>A triplestore is a purpose-built database for the storage and retrieval of Resource Description Framework (<abbr title="Resource Description Framework">RDF</abbr>) metadata.</p>
<p>Much like a relational database, information is stored in a triplestore and retrieved via a query language called <abbr title="SPARQL Protocol and RDF Query Language">SPARQL</abbr>. Unlike a relational database, a triplestore is optimised for the storage and retrieval of many short statements called triples, in the form of subject-predicate-object, like &#8220;Bob is 35&#8243; or &#8220;Bob knows Fred&#8221;.</p>
<ul>
<li><a href="http://en.wikipedia.org/wiki/Triplestore" title="Wikipedia: Triplestore" target="_blank" rel="nofollow">http://en.wikipedia.org/wiki/Triplestore</a></li>
</ul>
<h3>SPARQL Protocol and RDF Query Language (<abbr title="SPARQL Protocol and RDF Query Language">SPARQL</abbr>)</h3>
<p><abbr title="SPARQL Protocol and RDF Query Language">SPARQL</abbr> is an <abbr title="Resource Description Framework">RDF</abbr> query language, which can be used to express queries across diverse data sources, whether the data is stored natively as <abbr title="Resource Description Framework">RDF</abbr> or viewed as <abbr title="Resource Description Framework">RDF</abbr> via middleware. <abbr title="SPARQL Protocol and RDF Query Language">SPARQL</abbr> contains capabilities for querying required and optional graph patterns along with their conjunctions and disjunctions. <abbr title="SPARQL Protocol and RDF Query Language">SPARQL</abbr> also supports extensible value testing and constraining queries by source <abbr title="Resource Description Framework">RDF</abbr> graph. The results of <abbr title="SPARQL Protocol and RDF Query Language">SPARQL</abbr> queries can be results sets or <abbr title="Resource Description Framework">RDF</abbr> graphs.</p>
<ul>
<li><a href="http://www.w3.org/TR/rdf-sparql-query/" title="World Wide Web Consortium: SPARQL Query" target="_blank" rel="nofollow">http://www.w3.org/TR/rdf-sparql-query/</a></li>
<li><a href="http://en.wikipedia.org/wiki/Sparql" title="Wikipedia: SPARQL" target="_blank" rel="nofollow">http://en.wikipedia.org/wiki/Sparql</a></li>
</ul>
<h3>Simple Knowledge Organization System (<abbr title="Simple Knowledge Organization System">SKOS</abbr>) </h3>
<p><abbr title="Simple Knowledge Organization System">SKOS</abbr> is a family of formal languages designed for representation of thesauri, classification schemes, taxonomies, subject-heading systems, or any other type of structured controlled vocabulary. <abbr title="Simple Knowledge Organization System">SKOS</abbr> is built upon <abbr title="Resource Description Framework">RDF</abbr> and <abbr title="Resource Description Framework Schema">RDF-S</abbr>, and its main objective is to enable easy publication of controlled structured vocabularies for the Semantic Web.</p>
<ul>
<li><a href="http://www.w3.org/2004/02/skos/" title="World Wide Web Consortium: SKOS" target="_blank" rel="nofollow">http://www.w3.org/2004/02/skos/</a></li>
<li><a href="http://en.wikipedia.org/wiki/Simple_Knowledge_Organization_System" title="Wikipedia: Simple Knowledge Organisation System" target="_blank" rel="nofollow">http://en.wikipedia.org/wiki/Simple_Knowledge_Organization_System</a></li>
</ul>
<h3>Persistent Uniform Resource Locator (<abbr title="Persistent Uniform Resource Locator">PURL</abbr>)</h3>
<p>A <abbr title="Persistent Uniform Resource Locator">PURL</abbr> is a type of Uniform Resource Locator (<abbr title="Uniform Resource Locator">URL</abbr>) that does not directly describe the location of the resource to be retrieved but instead describes an intermediate, more persistent location which, when retrieved, results in redirection (e.g. via a 302 <abbr title="HyperText Transfer Protocol">HTTP</abbr> status code) to the current location of the final resource.</p>
<p><abbr title="Persistent Uniform Resource Locator">PURLs</abbr> are an interim measure, while Uniform Resource Names (<abbr title="Uniform Resource Names">URNs</abbr>) are being mainstreamed, to solve the problem of transitory <abbr title="Uniform Resource Identifier">URIs</abbr> in location-based <abbr title="Uniform Resource Identifier">URI</abbr> schemes like <abbr title="HyperText Transfer Protocol">HTTP</abbr>.</p>
<ul>
<li><a href="http://purl.org/docs/index.html" title="Persistent Uniform Resource Locators" target="_blank" rel="nofollow">http://purl.org/docs/index.html</a></li>
<li><a href="http://en.wikipedia.org/wiki/Persistent_Uniform_Resource_Locator" title="Wikipedia: Persistent Uniform Resource Locator" target="_blank" rel="nofollow">http://en.wikipedia.org/wiki/Persistent_Uniform_Resource_Locator</a></li>
</ul>
<h3>Thomson Reuters OpenCalais</h3>
<p>OpenCalais is a rapidly growing toolkit of capabilities that allow you to readily incorporate state-of-the-art semantic functionality within your blog, content management system, website or application.</p>
<p>The OpenCalais Web Service automatically creates rich semantic metadata for the content you submit. Using Natural Language Processing (<abbr title="Natural Language Processing">NLP</abbr>), machine learning and other methods, Calais analyses your document and finds the entities within it. Calais goes beyond classic entity identification returning the facts and events hidden within your text as well.</p>
<ul>
<li><a href="http://www.opencalais.com" title="Thomson Reuters OpenCalais" target="_blank" rel="nofollow">http://www.opencalais.com</a></li>
</ul>
<p>If you have any more suggestions that should be included above, I&#8217;ll be happy to hear them.</p>
<p><script type="text/javascript"><!--
google_ad_client = "pub-6475233631580417";
/* 468x60 Basic */
google_ad_slot = "7117418273";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
]]></content:encoded>
			<wfw:commentRss>http://www.simonwhatley.co.uk/an-introduction-to-the-semantic-web/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Data Portability for Social Networks</title>
		<link>http://www.simonwhatley.co.uk/data-portability-for-social-networks</link>
		<comments>http://www.simonwhatley.co.uk/data-portability-for-social-networks#comments</comments>
		<pubDate>Fri, 28 Mar 2008 09:50:11 +0000</pubDate>
		<dc:creator>Simon</dc:creator>
				<category><![CDATA[Social Media]]></category>
		<category><![CDATA[Strategy]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[APML]]></category>
		<category><![CDATA[Authentication]]></category>
		<category><![CDATA[Bloglines]]></category>
		<category><![CDATA[Cluztr]]></category>
		<category><![CDATA[Corkâ€™d]]></category>
		<category><![CDATA[Dandelife]]></category>
		<category><![CDATA[Data Portability]]></category>
		<category><![CDATA[Engagd]]></category>
		<category><![CDATA[Fire Eagle]]></category>
		<category><![CDATA[Flickr]]></category>
		<category><![CDATA[FOAF]]></category>
		<category><![CDATA[Get Satisfaction]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[hCard]]></category>
		<category><![CDATA[Idiomag]]></category>
		<category><![CDATA[Last.fm]]></category>
		<category><![CDATA[Magnolia]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[OAuth]]></category>
		<category><![CDATA[Open Social]]></category>
		<category><![CDATA[OpenID]]></category>
		<category><![CDATA[OpenLink Data Spaces]]></category>
		<category><![CDATA[OPML]]></category>
		<category><![CDATA[Particls]]></category>
		<category><![CDATA[Pownce]]></category>
		<category><![CDATA[RDF]]></category>
		<category><![CDATA[RSS]]></category>
		<category><![CDATA[Semantic Web]]></category>
		<category><![CDATA[Social Networking]]></category>
		<category><![CDATA[social networks]]></category>
		<category><![CDATA[Technorati]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[Upcoming]]></category>
		<category><![CDATA[Web 2.0]]></category>
		<category><![CDATA[XFN]]></category>
		<category><![CDATA[Yahoo]]></category>

		<guid isPermaLink="false">http://www.simonwhatley.co.uk/?p=494</guid>
		<description><![CDATA[Social network portability is one of several user-interface ideas and suggestions in the area of data-portability. As users, our identity, photos, videos and other forms of personal data should be discoverable by, and shared between our chosen (and trusted) tools or vendors. When you join a new site, you should be able to import or preferably subscribe to your profile information and your social network from any existing profile of yours. We need a DHCP for Identity. A distributed File System for data. The technologies already exist, we simply need a complete reference design to put the pieces together. This problem is solved by a number existing technologies and initiatives: Microformats, OpenID, OAuth, RDF, RSS, OPML and APML.]]></description>
			<content:encoded><![CDATA[<p align="center"><img src='http://www.simonwhatley.co.uk/blog/wp-content/uploads/2008/03/data-portability-logo.png' alt='Data Portability' /></p>
<p>Social network portability is one of several user-interface ideas and suggestions in the area of data-portability. As users, our identity, photos, videos and other forms of personal data should be discoverable by, and shared between our chosen (and trusted) tools or vendors. When you join a new site, you should be able to import or preferably subscribe to your profile information and your social network from any existing profile of yours. We need a <acronym title="Dynamic Host Configuration Protocol">DHCP</acronym> for Identity. A distributed File System for data. The technologies already exist, we simply need a complete reference design to put the pieces together. This problem is solved by a number existing technologies and initiatives: Microformats, OpenID, OAuth, <acronym title="Resource Description Framework">RDF</acronym>, <acronym title="Really Simple Syndication">RSS</acronym>, <acronym title="Outline Processor Mark-up Language">OPML</acronym> and <acronym title="Attention Profiling Mark-up Language">APML</acronym>.</p>
<p align="center"><img src='http://www.simonwhatley.co.uk/blog/wp-content/uploads/2008/03/dataportability.png' alt='Data Portability Technologies' /></p>
<blockquote><p>Data Portabilities mission is to put all existing technologies and initiatives in context to create a reference design for end-to-end Data Portability. To promote that design to the developer, vendor and end-user community.</p></blockquote>
<p>This post serves a brief primer to each of these technologies.</p>
<p><script type="text/javascript"><!--
google_ad_client = "pub-6475233631580417";
/* 468x60 Basic */
google_ad_slot = "7117418273";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
<h3>Microformats</h3>
<p>Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards. Instead of throwing away what works today, microformats intend to solve simpler problems first by adapting to current behaviours and usage patterns (e.g. <acronym title="eXtensible HyperText Mark-up Language">XHTML</acronym>, blogging).</p>
<p>Examples include:</p>
<dl>
<dt>People and Organizations </dt>
<dd><a href="http://microformats.org/wiki/hcard" title="Microformat: hCard" target="_blank" rel="nofollow" class="snap_noshots">hCard</a></dd>
<dt>Calendars and Events</dt>
<dd><a href="http://microformats.org/wiki/hcalendar" title="Microformat: hCalendar" target="_blank" rel="nofollow" class="snap_noshots">hCalendar</a></dd>
<dt>Opinions, Ratings and Reviews</dt>
<dd><a href="http://microformats.org/wiki/vote-links" title="Microformat: VoteLinks" target="_blank" rel="nofollow" class="snap_noshots">VoteLinks</a>, <a href="http://microformats.org/wiki/hreview" title="Microformat: hReview" target="_blank" rel="nofollow" class="snap_noshots">hReview</a></dd>
<dt>Social Networks</dt>
<dd><a href="http://gmpg.org/xfn" title="Microformat: XFN" target="_blank" rel="nofollow" class="snap_noshots"><abbr title="XHTML Friends Network">XFN</abbr></a></dd>
<dt>Licenses:</dt>
<dd><a href="http://microformats.org/wiki/rel-license" title="Microformat: rel-license" target="_blank" rel="nofollow" class="snap_noshots">rel-license</a></dd>
<dt>Tags, Keywords, Categories</dt>
<dd><a href="http://microformats.org/wiki/rel-tag" title="Microformat: rel-tag" target="_blank" rel="nofollow" class="snap_noshots">rel-tag</a></dd>
<dt>Lists and Outlines</dt>
<dd><a href="http://microformats.org/wiki/xoxo" title="Microformat: XOXO" target="_blank" rel="nofollow" class="snap_noshots">XOXO</a></dd>
</dl>
<p>If you use <a href="http://flickr.com" title="Flickr" target="_blank" rel="nofollow">Flickr</a>, <a href="http://technorati.com" title="Technorati" target="_blank" rel="nofollow">Technorati</a>, <a href="http://upcoming.yahoo.com" title="Upcoming" target="_blank" rel="nofollow">Upcoming</a>, <a href="http://last.fm" title="Last.fm" target="_blank" rel="nofollow">Last.fm</a>, <a href="http://twitter.com" title="Twitter" target="_blank" rel="nofollow">Twitter</a>, <a href="http://corkd.com" title="Cork'd" target="_blank" rel="nofollow">Cork&#8217;d</a> or any number of other services, you can conceivably share data between the different services providers automatically.</p>
<p>More details can be found on the <a href="http://microformats.org" title="Microformats" target="_blank" rel="nofollow">microformats website</a>.</p>
<h3>OpenID</h3>
<p>OpenID is an open, decentralized framework for user-centric digital identity. OpenID takes advantage of already existing internet technology (<acronym title="Universal Resource Indicator">URI</acronym>, <acronym title="HyperText Transfer Protocol">HTTP</acronym>, <acronym title="Secure Sockets Layer">SSL</acronym>, <a href="http://en.wikipedia.org/wiki/Diffie-Hellman" title="Diffie-Hellman" target="_blank" rel="nofollow">Diffie-Hellman</a>) and realizes that people are already creating identities for themselves whether it be at their blog, photostream, profile page, etc. With OpenID you can easily transform one of these existing URIs into an account which can be used at sites which support OpenID logins.</p>
<p>In other words, OpenID allows users to login using shared credentials across different services. It also allows users to decide what information to share between services. For example, you can allow the use of your address on one service, but not another. You can think of OpenID as an extension to the single sign on used by Google or Yahoo! to access their various services.</p>
<p>More details can be found on the <a href="http://openid.net" title="OpenID" target="_blank" rel="nofollow">OpenID website</a>.</p>
<h3>OAuth</h3>
<p>The OAuth protocol is less about authentication, which is the realm of OpenID, but rather authorisation. OAuth is an open protocol to allow secure API authorisation in a simple and standard method from desktop and web applications. For consumer developers, OAuth is a method to publish and interact with protected data. For Service Provider developers, OAuth gives users access to their data while protecting their account credentials.</p>
<p>A number of services have already been implemented. These include <a href="http://fireeagle.yahoo.net" title="Fire Eagle" target="_blank" rel="nofollow">Fire Eagle</a>, <a href="http://code.google.com/apis/opensocial/" title="Open Social" target="_blank" rel="nofollow">Open Social</a>, <a href="http://pownce.com" title="Pownce" target="_blank" rel="nofollow">Pownce</a>, <a href="http://getsatisfaction.com" title="Get Satisfaction" target="_blank" rel="nofollow">Get Satisfaction</a> and <a href="http://ma.gnolia.com" title="Magnolia" target="_blank" rel="nofollow">Magnolia</a>.</p>
<p>More details can be found on the <a href="http://oauth.net" title="OAuth" target="_blank" rel="nofollow">OAuth website</a>.</p>
<h3>Resource Description Framework (<acronym title="Resource Description Framework">RDF</acronym>)</h3>
<p><acronym title="Resource Description Framework">RDF</acronym> is a family of World Wide Web Consortium (<acronym title="World Wide Web Consortium">W3C</acronym>) specifications originally designed as a metadata model but which has come to be used as a general method of modeling information, through a variety of syntax formats.</p>
<p>The <acronym title="Resource Description Framework">RDF</acronym> metadata model is based upon the idea of making statements about resources in the form of subject-predicate-object expressions, called triples in <acronym title="Resource Description Framework">RDF</acronym> terminology. The subject denotes the resource, and the predicate denotes traits or aspects of the resource and expresses a relationship between the subject and the object. For example, one way to represent the notion &#8220;The sky has the color blue&#8221; in <acronym title="Resource Description Framework">RDF</acronym> is as the triple: a subject denoting &#8220;the sky&#8221;, a predicate denoting &#8220;has the color&#8221;, and an object denoting &#8220;blue&#8221;. <acronym title="Resource Description Framework">RDF</acronym> is an abstract model with several serialization formats (i.e. file formats), and so the particular way in which a resource or triple is encoded varies from format to format.</p>
<p>This mechanism for describing resources is a major component in what is proposed by the <acronym title="World Wide Web Consortium">W3C</acronym>&#8216;s Semantic Web activity: an evolutionary stage of the World Wide Web in which automated software can store, exchange, and use machine-readable information distributed throughout the web, in turn enabling users to deal with the information with greater efficiency and certainty. <acronym title="Resource Description Framework">RDF</acronym>&#8216;s simple data model and ability to model disparate, abstract concepts has also led to its increasing use in knowledge management applications unrelated to Semantic Web activity.</p>
<p>More details can be found on the <a href="http://www.w3.org/RDF/" title="W3C" target="_blank" rel="nofollow"><acronym title="World Wide Web Consortium">W3C</acronym> website</a>.</p>
<p><script type="text/javascript"><!--
google_ad_client = "pub-6475233631580417";
/* 468x60 Basic */
google_ad_slot = "7117418273";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
<h3>Really Simple Syndication (<acronym title="Really Simple Syndication">RSS</acronym>)</h3>
<p><acronym title="Really Simple Syndication">RSS</acronym> is a family of Web feed formats used to publish frequently updated content including, but not limited to, blog entries, news headlines, and podcasts. An <acronym title="Really Simple Syndication">RSS</acronym> document, which is called a &#8220;feed&#8221; or &#8220;web feed&#8221; or &#8220;channel&#8221;, contains either a summary of content from an associated web site or the full text. <acronym title="Really Simple Syndication">RSS</acronym> makes it possible for people to keep up with web sites in an automated manner that can be piped into special programs or filtered displays.</p>
<p><acronym title="Really Simple Syndication">RSS</acronym> content can be read using software called an &#8220;<acronym title="Really Simple Syndication">RSS</acronym> reader&#8221;, &#8220;feed reader&#8221; or an &#8220;aggregator&#8221;. The user subscribes to a feed by entering the feed&#8217;s link into the reader or by clicking an <acronym title="Really Simple Syndication">RSS</acronym> icon in a browser that initiates the subscription process. The reader checks the user&#8217;s subscribed feeds regularly for new content, downloading any updates that it finds.</p>
<p>More details can be found on the <a href="http://www.rssboard.org" title="RSS Board" target="_blank" rel="nofollow">RSS Board website</a>.</p>
<h3>Outline Processor Mark-up Language (<acronym title="Outline Processor Mark-up Language">OPML</acronym>)</h3>
<p><acronym title="Outline Processor Mark-up Language">OPML</acronym> is an <acronym title="eXtensible Markup Language">XML</acronym> format for outlines. Originally developed by <a href="http://radio.userland.com" title="Radio UserLand" target="_blank" rel="nofollow">Radio UserLand</a> as a native file format for an outliner application, it has since been adopted for other uses, the most common being to exchange lists of web feeds between web feed aggregators.</p>
<p>The <acronym title="Outline Processor Mark-up Language">OPML</acronym> specification defines an outline as a hierarchical, ordered list of arbitrary elements. The specification is fairly open which makes it suitable for many types of list data.</p>
<p>More details can be found on the <a href="http://www.opml.org" title="Outline Processor Mark-up Language" target="_blank" rel="nofollow"><acronym title="Outline Processor Mark-up Language">OPML</acronym> website</a>.</p>
<h3>Attention Profiling Mark-up Language (<acronym title="Attention Profiling Mark-up Language">APML</acronym>)</h3>
<p><acronym title="Attention Profiling Mark-up Language">APML</acronym> allows you to share your own personal Attention Profile in much the same way that OPML allows the exchange of reading lists between News Readers. The idea is to compress all forms of Attention Data into a portable file format containing a description of your ranked interests.</p>
<p>Services that have adopted <acronym title="Attention Profiling Mark-up Language">APML</acronym> include <a href="http://www.bloglines.com" title="Bloglines" target="_blank" rel="nofollow">Bloglines</a>, <a href="http://www.cluztr.com" title="Cluztr" target="_blank" rel="nofollow">Cluztr</a>, <a href="http://dandelife.com" title="Dandelife" target="_blank" rel="nofollow">Dandelife</a>, <a href="http://www.engagd.com" title="Engagd" target="_blank" rel="nofollow">Engagd</a>, <a href="http://www.idiomag.com" title="Idiomag" target="_blank" rel="nofollow">Idiomag</a>, <a href="http://en.wikipedia.org/wiki/OpenLink_Data_Spaces" title="OpenLink Data Spaces" target="_blank" rel="nofollow">OpenLink Data Spaces</a> and <a href="www.particls.com" title="Particls" target="_blank" rel="nofollow">Particls</a>.</p>
<p>More details can be found on the <a href="http://www.apml.org" title="Attention Profiling Mark-up Language" target="_blank" rel="nofollow"><acronym title="Attention Profiling Mark-up Language">APML</acronym> website</a>.</p>
<p><script type="text/javascript"><!--
google_ad_client = "pub-6475233631580417";
/* 468x60 Basic */
google_ad_slot = "7117418273";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
<p>Securely transfering personal data around the web has become an increasingly important concept to not only users of the web, but service providers. Both Plaxo and Six Apart have been working on a system to allow the transferral of data. However, since Google announce Open Social and the Open Social <acronym title="Application Programming Interface">API</acronym>, the mantle has been handed over and there is now a strong commitment to realising data portability.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.simonwhatley.co.uk/data-portability-for-social-networks/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

