<?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>MarkupAsAnApi &#187; semweb</title>
	<atom:link href="http://www.markupasanapi.com/tag/semweb/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markupasanapi.com</link>
	<description>Publish once, publish everywhere</description>
	<lastBuildDate>Mon, 07 Sep 2009 03:56:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Custom non-visible data in HTML 5</title>
		<link>http://www.markupasanapi.com/2008/07/14/custom-non-visible-data-in-html-5/</link>
		<comments>http://www.markupasanapi.com/2008/07/14/custom-non-visible-data-in-html-5/#comments</comments>
		<pubDate>Mon, 14 Jul 2008 12:43:36 +0000</pubDate>
		<dc:creator>halans</dc:creator>
				<category><![CDATA[Javascript]]></category>
		<category><![CDATA[Semantic Web]]></category>
		<category><![CDATA[attributes]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[semantic web]]></category>
		<category><![CDATA[semweb]]></category>
		<category><![CDATA[w3c]]></category>

		<guid isPermaLink="false">http://www.markupasanapi.com/?p=12</guid>
		<description><![CDATA[Short and sweet: HTML 5 offers custom data attributes on HTML elements, intended to store custom data, which can then be handled on-page by JavaScript, or off-page by other (web-)applications. John Resig discusses a number of useful benefits. Post from Jean-Jacques Halans MarkupAsAnApi blog.Custom non-visible data in HTML 5<p>Post from <a href="http://www.halans.com">Jean-Jacques Halans</a> <a href="http://www.markupasanapi.com">MarkupAsAnApi</a> blog.<br/><br/><a href="http://www.markupasanapi.com/2008/07/14/custom-non-visible-data-in-html-5/">Custom non-visible data in HTML 5</a></p>
]]></description>
			<content:encoded><![CDATA[<p>Short and sweet: HTML 5 offers <a title="HTML 5" href="http://www.w3.org/html/wg/html5/#custom">custom data attributes</a> on HTML elements, intended to store custom data, which can then be handled on-page by JavaScript, or off-page by other (web-)applications.</p>
<p>John Resig discusses  <a title="Data attributes" href="http://ejohn.org/blog/html-5-data-attributes/">a number of useful benefits</a>.</p>
<p>Post from <a href="http://www.halans.com">Jean-Jacques Halans</a> <a href="http://www.markupasanapi.com">MarkupAsAnApi</a> blog.<br/><br/><a href="http://www.markupasanapi.com/2008/07/14/custom-non-visible-data-in-html-5/">Custom non-visible data in HTML 5</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.markupasanapi.com/2008/07/14/custom-non-visible-data-in-html-5/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Yahoo! Search understands semantics</title>
		<link>http://www.markupasanapi.com/2008/03/17/yahoo-search-understands-semantics/</link>
		<comments>http://www.markupasanapi.com/2008/03/17/yahoo-search-understands-semantics/#comments</comments>
		<pubDate>Mon, 17 Mar 2008 05:36:14 +0000</pubDate>
		<dc:creator>halans</dc:creator>
				<category><![CDATA[Microformats]]></category>
		<category><![CDATA[Semantic Web]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[search engines]]></category>
		<category><![CDATA[semantic web]]></category>
		<category><![CDATA[semantic web standards]]></category>
		<category><![CDATA[semweb]]></category>
		<category><![CDATA[Yahoo!]]></category>

		<guid isPermaLink="false">http://www.markupasanapi.com/?p=9</guid>
		<description><![CDATA[Yahoo! Search announced that it will support semantic web standards, like Microformats, RDFa and Dublin Core: By supporting semantic web standards, Yahoo! Search and site owners can bring a far richer and more useful search experience to consumers. For example, by marking up its profile pages with microformats, LinkedIn can allow Yahoo! Search and others [...]<p>Post from <a href="http://www.halans.com">Jean-Jacques Halans</a> <a href="http://www.markupasanapi.com">MarkupAsAnApi</a> blog.<br/><br/><a href="http://www.markupasanapi.com/2008/03/17/yahoo-search-understands-semantics/">Yahoo! Search understands semantics</a></p>
]]></description>
			<content:encoded><![CDATA[<p>Yahoo! Search <a title="Yahoo Search blog" href="http://www.ysearchblog.com/archives/000527.html">announced</a> that it will support semantic web standards, like Microformats, RDFa and Dublin Core:</p>
<blockquote><p>By supporting semantic web standards, Yahoo! Search and site owners can bring a far richer and more useful search experience to consumers. For example, by marking up its profile pages with microformats, <a href="http://www.linkedin.com/">LinkedIn</a> can allow Yahoo! Search and others to understand the semantic content and the relationships of the many components of its site.</p></blockquote>
<p>By getting this out in the open, maybe other search engines (think &#8220;G&#8221;) might come out and proclaim their love for the semantic web?</p>
<p>You can try it out for yourself at <a title="Yahoo! Microsearch" href="http://www.yr-bcn.es/demos/microsearch/">Yahoo! Microsearch</a>.</p>
<p>Post from <a href="http://www.halans.com">Jean-Jacques Halans</a> <a href="http://www.markupasanapi.com">MarkupAsAnApi</a> blog.<br/><br/><a href="http://www.markupasanapi.com/2008/03/17/yahoo-search-understands-semantics/">Yahoo! Search understands semantics</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.markupasanapi.com/2008/03/17/yahoo-search-understands-semantics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Markup as an API</title>
		<link>http://www.markupasanapi.com/2007/10/08/markup-as-an-api/</link>
		<comments>http://www.markupasanapi.com/2007/10/08/markup-as-an-api/#comments</comments>
		<pubDate>Mon, 08 Oct 2007 10:26:16 +0000</pubDate>
		<dc:creator>halans</dc:creator>
				<category><![CDATA[Javascript]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[Semantic Web]]></category>
		<category><![CDATA[rdf]]></category>
		<category><![CDATA[screenscraping]]></category>
		<category><![CDATA[semweb]]></category>
		<category><![CDATA[xml]]></category>

		<guid isPermaLink="false">http://www.markupasanapi.com/?p=4</guid>
		<description><![CDATA[HTML describes documents, and the link between documents. We read these documents, we print them, bookmark them for later retrieval. We might copy/paste content into another document, constructing a new one. If we wanted to automate this, we&#8217;d resort tot screen scraping. But this easily breaks, as there&#8217;s no standard or &#8220;contract&#8221; between the original [...]<p>Post from <a href="http://www.halans.com">Jean-Jacques Halans</a> <a href="http://www.markupasanapi.com">MarkupAsAnApi</a> blog.<br/><br/><a href="http://www.markupasanapi.com/2007/10/08/markup-as-an-api/">Markup as an API</a></p>
]]></description>
			<content:encoded><![CDATA[<p>HTML describes documents, and the link between documents.</p>
<p>
We read these documents, we print them, bookmark them for later retrieval. We might copy/paste content into another document, constructing a new one.
</p>
<p>
If we wanted to automate this, we&#8217;d resort tot screen scraping. But this easily breaks, as there&#8217;s no standard or &#8220;contract&#8221; between the original site and the screen scraper.
</p>
<p>
Or we&#8217;d go for duplicating content into a new format like XML, with an agreed upon format. That way we could build product price aggregators using SOA Web Services with SOAP, WSDL,&#8230; Or use a REST architecture which takes us a bit closer back to our original HTTP request.
</p>
<p>
Most popular formats for sharing (XML) data is RSS and Atom, were again we duplicate the content we publish online.
</p>
<p>
But we&#8217;ve come a long way last couple of years, towards Web Standards, pushed by organisations like the Web Standards Project (WaSP) and Web Standards Group (WSG). They promote standards for separation of content, styling and behaviour, and the use of semantic HTML.
</p>
<p>
And then there&#8217;s the W3C, who promotes the Semantic Web as knowledge representation, using Resource Description Framework. RDF is a general method of modelling information making statements about resources in triples. Triples represent a subject-predicate-object expression, for example JJ &#8211; isBornIn &#8211; Belgium.
</p>
<p>The W3C&#8217;s Web Ontology Language, or OWL, provides additional vocabulary and formal semantics, providing greater machine interpretability of Web content, but with added complexity.</p>
<p>But as of yet there isn&#8217;t much RDF data online, or ontologies are missing for many application domains. The W3C&#8217;s projects are rather academic, and aren&#8217;t close to any web developer&#8217;s mindset.</p>
<p>What is closer to the web developer though is semantic HTML, the correct use of heading levels and paragraphs to introduce structure, blockquotes and correct use of tables, for tabular data.</p>
<p>Now we add rich semantics, standardised Microformats. They are small pieces of metadata, within the markup, using CSS. They are discoverable, interpreted by machines.</p></p>
<p>Post from <a href="http://www.halans.com">Jean-Jacques Halans</a> <a href="http://www.markupasanapi.com">MarkupAsAnApi</a> blog.<br/><br/><a href="http://www.markupasanapi.com/2007/10/08/markup-as-an-api/">Markup as an API</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.markupasanapi.com/2007/10/08/markup-as-an-api/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
