<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Data file format and response format</title>
	<atom:link href="http://niklasbe.wordpress.com/2008/05/24/data-file-format-and-response-format/feed/" rel="self" type="application/rss+xml" />
	<link>http://niklasbe.wordpress.com/2008/05/24/data-file-format-and-response-format/</link>
	<description>A blog following the progress of my Summer of Code project</description>
	<lastBuildDate>Wed, 15 Apr 2009 17:37:48 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: How to Get Six Pack Fast</title>
		<link>http://niklasbe.wordpress.com/2008/05/24/data-file-format-and-response-format/#comment-58</link>
		<dc:creator>How to Get Six Pack Fast</dc:creator>
		<pubDate>Wed, 15 Apr 2009 17:37:48 +0000</pubDate>
		<guid isPermaLink="false">http://niklasbe.wordpress.com/?p=5#comment-58</guid>
		<description>Not that I&#039;m totally impressed, but this is   more than I expected   when I found a link on Furl telling that the info here is quite decent. Thanks.</description>
		<content:encoded><![CDATA[<p>Not that I&#8217;m totally impressed, but this is   more than I expected   when I found a link on Furl telling that the info here is quite decent. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ijabz</title>
		<link>http://niklasbe.wordpress.com/2008/05/24/data-file-format-and-response-format/#comment-13</link>
		<dc:creator>ijabz</dc:creator>
		<pubDate>Wed, 04 Jun 2008 19:18:10 +0000</pubDate>
		<guid isPermaLink="false">http://niklasbe.wordpress.com/?p=5#comment-13</guid>
		<description>I mentioned using owned on irc,  bad idea, not really robust enough. But you could take the cut and paste the folksonomy webservice code  for your project</description>
		<content:encoded><![CDATA[<p>I mentioned using owned on irc,  bad idea, not really robust enough. But you could take the cut and paste the folksonomy webservice code  for your project</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ijabz</title>
		<link>http://niklasbe.wordpress.com/2008/05/24/data-file-format-and-response-format/#comment-12</link>
		<dc:creator>ijabz</dc:creator>
		<pubDate>Wed, 04 Jun 2008 14:02:03 +0000</pubDate>
		<guid isPermaLink="false">http://niklasbe.wordpress.com/?p=5#comment-12</guid>
		<description>Currently tracks are tagged with &#039;owned&#039;  through the website but there is already a webservice for adding tags to a artist/release/track/label so it could easily be done programatically. In fact in the dev version of Jaikoz I can submit genres to tags at a track level , so by entering &#039;owned&#039; instead of a genre into the genre field i can hack it to do this already.</description>
		<content:encoded><![CDATA[<p>Currently tracks are tagged with &#8216;owned&#8217;  through the website but there is already a webservice for adding tags to a artist/release/track/label so it could easily be done programatically. In fact in the dev version of Jaikoz I can submit genres to tags at a track level , so by entering &#8216;owned&#8217; instead of a genre into the genre field i can hack it to do this already.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: niklas</title>
		<link>http://niklasbe.wordpress.com/2008/05/24/data-file-format-and-response-format/#comment-11</link>
		<dc:creator>niklas</dc:creator>
		<pubDate>Wed, 04 Jun 2008 12:19:06 +0000</pubDate>
		<guid isPermaLink="false">http://niklasbe.wordpress.com/?p=5#comment-11</guid>
		<description>&quot;I dont quite follow the example data , are you advocating sending a physical data file rather then sending the data as post parameters. If so I don’t agree you shouldnt impose this restriction some applications may not have access a filesystem, and creating a file is an unneccssary step anyway..&quot;

Yes, I was thinking of producing a file to send, but thats so stupid. Thank you for the feedback, will do another post!


&quot;I guess the following idea has probably been thrown out already but a simpler alternative approach would could be just be for the server to parse tags entities that are currently being tagged with the ‘owned’ tag using the folksonomy service&quot;

Would this require people to manually tag music as owned? Or can this be done automatically with e.g. Picard or Jaikoz somehow?


Working on an exam today, got another one tomorrow morning. That will be my last one. After that expect to see more updates...</description>
		<content:encoded><![CDATA[<p>&#8220;I dont quite follow the example data , are you advocating sending a physical data file rather then sending the data as post parameters. If so I don’t agree you shouldnt impose this restriction some applications may not have access a filesystem, and creating a file is an unneccssary step anyway..&#8221;</p>
<p>Yes, I was thinking of producing a file to send, but thats so stupid. Thank you for the feedback, will do another post!</p>
<p>&#8220;I guess the following idea has probably been thrown out already but a simpler alternative approach would could be just be for the server to parse tags entities that are currently being tagged with the ‘owned’ tag using the folksonomy service&#8221;</p>
<p>Would this require people to manually tag music as owned? Or can this be done automatically with e.g. Picard or Jaikoz somehow?</p>
<p>Working on an exam today, got another one tomorrow morning. That will be my last one. After that expect to see more updates&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ijabz</title>
		<link>http://niklasbe.wordpress.com/2008/05/24/data-file-format-and-response-format/#comment-10</link>
		<dc:creator>ijabz</dc:creator>
		<pubDate>Wed, 04 Jun 2008 11:56:47 +0000</pubDate>
		<guid isPermaLink="false">http://niklasbe.wordpress.com/?p=5#comment-10</guid>
		<description>I dont quite follow the example data , are you advocating sending a physical data file rather then sending the data as post parameters. If so I don&#039;t agree you shouldnt impose this restriction some applications may not have access a filesystem, and creating a file is an unneccssary step anyway..

What about these post parameters instead:
action=add
tracklist=trackid1,trackid2
releaselist=releaseid1

would add trackid1,trackid2 and releaseid1

action=remove
tracklist=trackid1,trackid2

would remove trackid1,trackid2

I guess the following idea has probably been thrown out already but a simpler alternative approach would could be just be for the server to parse tags entities that are currently being tagged with the &#039;owned&#039; tag using the folksonomy service</description>
		<content:encoded><![CDATA[<p>I dont quite follow the example data , are you advocating sending a physical data file rather then sending the data as post parameters. If so I don&#8217;t agree you shouldnt impose this restriction some applications may not have access a filesystem, and creating a file is an unneccssary step anyway..</p>
<p>What about these post parameters instead:<br />
action=add<br />
tracklist=trackid1,trackid2<br />
releaselist=releaseid1</p>
<p>would add trackid1,trackid2 and releaseid1</p>
<p>action=remove<br />
tracklist=trackid1,trackid2</p>
<p>would remove trackid1,trackid2</p>
<p>I guess the following idea has probably been thrown out already but a simpler alternative approach would could be just be for the server to parse tags entities that are currently being tagged with the &#8216;owned&#8217; tag using the folksonomy service</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: niklas</title>
		<link>http://niklasbe.wordpress.com/2008/05/24/data-file-format-and-response-format/#comment-9</link>
		<dc:creator>niklas</dc:creator>
		<pubDate>Thu, 29 May 2008 19:44:09 +0000</pubDate>
		<guid isPermaLink="false">http://niklasbe.wordpress.com/?p=5#comment-9</guid>
		<description>Im not going to write an update. Not much to change.</description>
		<content:encoded><![CDATA[<p>Im not going to write an update. Not much to change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: niklas</title>
		<link>http://niklasbe.wordpress.com/2008/05/24/data-file-format-and-response-format/#comment-8</link>
		<dc:creator>niklas</dc:creator>
		<pubDate>Thu, 29 May 2008 12:26:44 +0000</pubDate>
		<guid isPermaLink="false">http://niklasbe.wordpress.com/?p=5#comment-8</guid>
		<description>Thank you for the replies. Will write a small update hopefully by tonight.
Will include some more GET parameters, alternatively divide into more resources.

Nikki: good

mafr: yes, this was the idea with having the error entity with sub-entities. dont know why I did not include it right away. thanks! looked into REST, but not sure how to make this more &quot;RESTful&quot;

kuno: will move it. I want to &quot;finalize&quot;(for now) this as soon as possible. school is coming to an end and I want to start coding :)</description>
		<content:encoded><![CDATA[<p>Thank you for the replies. Will write a small update hopefully by tonight.<br />
Will include some more GET parameters, alternatively divide into more resources.</p>
<p>Nikki: good</p>
<p>mafr: yes, this was the idea with having the error entity with sub-entities. dont know why I did not include it right away. thanks! looked into REST, but not sure how to make this more &#8220;RESTful&#8221;</p>
<p>kuno: will move it. I want to &#8220;finalize&#8221;(for now) this as soon as possible. school is coming to an end and I want to start coding <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kuno</title>
		<link>http://niklasbe.wordpress.com/2008/05/24/data-file-format-and-response-format/#comment-7</link>
		<dc:creator>kuno</dc:creator>
		<pubDate>Tue, 27 May 2008 13:04:37 +0000</pubDate>
		<guid isPermaLink="false">http://niklasbe.wordpress.com/?p=5#comment-7</guid>
		<description>I would move the version into the URL, like the current musicbrainz webservices have.  For example if you stick to your current protocol, you can easily move to XML later if the version is part of the URL and not part of the data being sent.

Something else which is probably import to mention:

Do not dwell on this too long, it is something which can easily be changed later on in the project.  You will quickly discover things you missed as you start implementing, so do not try to think of everything in advance.</description>
		<content:encoded><![CDATA[<p>I would move the version into the URL, like the current musicbrainz webservices have.  For example if you stick to your current protocol, you can easily move to XML later if the version is part of the URL and not part of the data being sent.</p>
<p>Something else which is probably import to mention:</p>
<p>Do not dwell on this too long, it is something which can easily be changed later on in the project.  You will quickly discover things you missed as you start implementing, so do not try to think of everything in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mafr</title>
		<link>http://niklasbe.wordpress.com/2008/05/24/data-file-format-and-response-format/#comment-6</link>
		<dc:creator>mafr</dc:creator>
		<pubDate>Sun, 25 May 2008 07:20:49 +0000</pubDate>
		<guid isPermaLink="false">http://niklasbe.wordpress.com/?p=5#comment-6</guid>
		<description>XMLWebService uses the REST architectural schema (see wikipedia or Fieldings&#039; dissertation), so it&#039;s not quite as easy as posting something to an URL. I designed that web service and it wasn&#039;t entirely trivial, I can tell you ;-)

Regarding the response format: You might want to use an XML namespace and expand the error element a bit. Client libraries probably want to raise different types of exceptions depending on the type of error, so a machine-readable error code would make sense. A free-text error string is still good and useful.</description>
		<content:encoded><![CDATA[<p>XMLWebService uses the REST architectural schema (see wikipedia or Fieldings&#8217; dissertation), so it&#8217;s not quite as easy as posting something to an URL. I designed that web service and it wasn&#8217;t entirely trivial, I can tell you <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Regarding the response format: You might want to use an XML namespace and expand the error element a bit. Client libraries probably want to raise different types of exceptions depending on the type of error, so a machine-readable error code would make sense. A free-text error string is still good and useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nikki</title>
		<link>http://niklasbe.wordpress.com/2008/05/24/data-file-format-and-response-format/#comment-5</link>
		<dc:creator>Nikki</dc:creator>
		<pubDate>Sat, 24 May 2008 18:55:02 +0000</pubDate>
		<guid isPermaLink="false">http://niklasbe.wordpress.com/?p=5#comment-5</guid>
		<description>While I&#039;m not entirely sure what &#039;release&#039; will mean exactly in NGS, we moved away from using &#039;album&#039; so I can&#039;t see people going back to using it.</description>
		<content:encoded><![CDATA[<p>While I&#8217;m not entirely sure what &#8216;release&#8217; will mean exactly in NGS, we moved away from using &#8216;album&#8217; so I can&#8217;t see people going back to using it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
