<?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/"
		>
<channel>
	<title>Comments on: data format for musicians</title>
	<atom:link href="http://gonze.com/blog/2009/05/19/data-format-for-musicians/feed/" rel="self" type="application/rss+xml" />
	<link>http://gonze.com/blog/2009/05/19/data-format-for-musicians/</link>
	<description>internet music technology since ~2002</description>
	<lastBuildDate>Sat, 31 Jul 2010 19:34:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Yves</title>
		<link>http://gonze.com/blog/2009/05/19/data-format-for-musicians/comment-page-1/#comment-3411</link>
		<dc:creator>Yves</dc:creator>
		<pubDate>Tue, 26 May 2009 20:17:41 +0000</pubDate>
		<guid isPermaLink="false">http://gonze.com/blog/?p=1646#comment-3411</guid>
		<description>Well, in that case I am pretty sure all the formats you mention start from the same feature: being able to expose a particular kind of data (worklow data, stats data, playlist data) in a particular way. That&#039;s certainly the case for MO, hAudio and MDEF, and I guess it is the same for XSPF?</description>
		<content:encoded><![CDATA[<p>Well, in that case I am pretty sure all the formats you mention start from the same feature: being able to expose a particular kind of data (worklow data, stats data, playlist data) in a particular way. That&#8217;s certainly the case for MO, hAudio and MDEF, and I guess it is the same for XSPF?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lucas Gonze</title>
		<link>http://gonze.com/blog/2009/05/19/data-format-for-musicians/comment-page-1/#comment-3409</link>
		<dc:creator>Lucas Gonze</dc:creator>
		<pubDate>Tue, 26 May 2009 16:55:50 +0000</pubDate>
		<guid isPermaLink="false">http://gonze.com/blog/?p=1646#comment-3409</guid>
		<description>Hi Yves,

I try hard to stay away from religion regarding RDF, microformats, and POX, though I do have a clear bias towards anybody who starts with features and works back from there.  That&#039;s the faction I&#039;m referring to.</description>
		<content:encoded><![CDATA[<p>Hi Yves,</p>
<p>I try hard to stay away from religion regarding RDF, microformats, and POX, though I do have a clear bias towards anybody who starts with features and works back from there.  That&#8217;s the faction I&#8217;m referring to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yves</title>
		<link>http://gonze.com/blog/2009/05/19/data-format-for-musicians/comment-page-1/#comment-3402</link>
		<dc:creator>Yves</dc:creator>
		<pubDate>Wed, 20 May 2009 10:34:44 +0000</pubDate>
		<guid isPermaLink="false">http://gonze.com/blog/?p=1646#comment-3402</guid>
		<description>Does that mean music ontology RDF or haudio is not meant to be used by &quot;running code&quot;? There are lots of tools or website out there aggregating/making use of such RDF data, i.e. the top-left of the LOD cloud [1].

Anyway, it&#039;s true that none of the data format I know of deals with such artist-related statistics, so this indeed does need to exist :-)

Cheers,
y

[1] http://www4.wiwiss.fu-berlin.de/bizer/pub/lod-datasets_2009-03-27.html</description>
		<content:encoded><![CDATA[<p>Does that mean music ontology RDF or haudio is not meant to be used by &#8220;running code&#8221;? There are lots of tools or website out there aggregating/making use of such RDF data, i.e. the top-left of the LOD cloud [1].</p>
<p>Anyway, it&#8217;s true that none of the data format I know of deals with such artist-related statistics, so this indeed does need to exist :-)</p>
<p>Cheers,<br />
y</p>
<p>[1] <a href="http://www4.wiwiss.fu-berlin.de/bizer/pub/lod-datasets_2009-03-27.html" rel="nofollow">http://www4.wiwiss.fu-berlin.de/bizer/pub/lod-datasets_2009-03-27.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
