<?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>J. Jeffrey Hanson &#187; linked data</title>
	<atom:link href="http://jeffhanson.com/category/linked-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://jeffhanson.com</link>
	<description>The Mythical Spam Lunch</description>
	<lastBuildDate>Wed, 23 Nov 2011 02:59:40 +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>Mashstream defines the basics for mashups, linked data, and semantic web</title>
		<link>http://jeffhanson.com/mashups/mashstream-defines-the-basics-for-mashups-linked-data-and-semantic-web/</link>
		<comments>http://jeffhanson.com/mashups/mashstream-defines-the-basics-for-mashups-linked-data-and-semantic-web/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 01:12:52 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[linked data]]></category>
		<category><![CDATA[mashups]]></category>
		<category><![CDATA[semantic Web]]></category>

		<guid isPermaLink="false">http://jeffhanson.com/?p=65</guid>
		<description><![CDATA[<p>In his <a href="http://mashstream.com/uncategorized/about-mashups-and-linked-data/">post</a>, Michael Hiatt defines the basics of mashups, linked data, and the semantic web in very understandable terms. He also explains some of the challenges and projections for these concepts. I particularly like his example of a simple enterprise mashup:</p> <p>&#8220;One simple example of a mashup is an aggregated Sales application that [...]]]></description>
			<content:encoded><![CDATA[<p>In his <a href="http://mashstream.com/uncategorized/about-mashups-and-linked-data/">post</a>, Michael Hiatt defines the basics of mashups, linked data, and the semantic web in very understandable terms. He also explains some of the challenges and projections for these concepts. I particularly like his example of a simple enterprise mashup:</p>
<p><em>&#8220;One simple example of a mashup is an aggregated Sales application that integrates CRM and financial data with functionality from the Web and corporate backend data. This example mashup would employ real-time information, streaming content, and Web services to form a coordinated application using all of these data sources. Integrated sales information for the traveling sales person could be available from their smart phone or laptop. I imagine this sample application to include these integrated features:</em></p>
<ul>
<li><em>Streams real-time Web information of financial and customer relationship management (CRM) data from </em><a onclick="javascript:pageTracker._trackPageview('/outbound/article/www.netsuite.com');" href="http://www.netsuite.com/portal/home.shtml"><em>NetSuite</em></a><em> or </em><a onclick="javascript:pageTracker._trackPageview('/outbound/article/www.salesforce.com');" href="https://www.salesforce.com/form/sem/crm_demo_1wpi.jsp?d=70130000000Dvxq&amp;opID=crm-hosted&amp;DCMP=KNC-Google&amp;gcid=3531476219&amp;gclid=CLmav5WmkJ4CFSZdagodhktmsw"><em>Salesforce.com</em></a><em>, combining it with online maps to visually identify, locate and categorize customers for each geographical location. Using </em><a onclick="javascript:pageTracker._trackPageview('/outbound/article/maps.google.com');" href="http://maps.google.com/maps?hl=en&amp;tab=wl"><em>Google Maps</em></a><em> or </em><a onclick="javascript:pageTracker._trackPageview('/outbound/article/www.mapquest.com');" href="http://www.mapquest.com/"><em>Mapquest</em></a><em> APIs, each customer site appears on the map and allows the sales person to drill down using the map paradigm to identify customer sites to expose new sales or possible upsell opportunities.</em></li>
<li><em>Background information and Request for Information (RFI) documents could be generated partly using semantically rich content from </em><a onclick="javascript:pageTracker._trackPageview('/outbound/article/dbpedia.org');" href="http://dbpedia.org/"><em>DBpedia</em></a><em>, the semantically structured content from Wikipedia. Integrated and updated glossary definitions of domain vernacular, references to partners and competitors could come together as competitive analysis documents. Prospective customers could read marketing evaluations combined with general reference content, and links to trusted independent blogger opinions, all from a single document.</em></li>
<li><em>Internal, proprietary customer data about installed products, contracts, and upsell possibilities can be integrated with the maps, reference information, and sales database to provide personalized content for customers.&#8221;</em></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://jeffhanson.com/mashups/mashstream-defines-the-basics-for-mashups-linked-data-and-semantic-web/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

