On 31/12/06, <b class="gmail_sendername">Mikkel Kamstrup Erlandsen</b> <<a href="mailto:mikkel.kamstrup@gmail.com">mikkel.kamstrup@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2006/12/24, Jean-Francois Dockes <<a href="mailto:jean-francois.dockes@wanadoo.fr" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">jean-francois.dockes@wanadoo.fr</a>>:<span class="gmail_quote">
</span><br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><span class="q"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Oops, yes, you're right the URI can change too.</blockquote></span><div><br>
Whether an uri can "change" or not is merely a matter of definition.</div></div></blockquote><div><br>I agree, but it is fairly important which way around the definition is. Not because it's a URI<->Object is a bad idea, just that we need to be aware that we're making that decision.
<br><br>URIs not being able to change and being a 1:1 mapping makes some things easier, like not having to retrieve the URI for all the hits. On the other hand, it means that any application that wants/needs persistent identifiers for things that can move must implement it themselves.
<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div>If an object changes uri it might as well be regarded as another object all together. The end user will see it as a rename/move but in the api I think we should go for the delete-create metafor. Meaning that the is a one-to-one correspondence between objects and uris.
<br></div></div></blockquote></div><br>One place where the API could be used, and is the area I'm most familiar with, is a music playing application. The search API would be useful to be able to say "give me all the user's music", rather than the "importing" step that you need to do in many music apps.
<br><br>Many music apps also hold extra metadata about the user's music (play counts, etc), and having the extra metadata lost when the user moves some files around is annoying. If the URI of something could change (and the backend implementation supported it), we could keep track of the metadata across file renames or moves.
<br><br><br>Being able to do thing like that may not be worth the extra complication of URIs and objects not being one-to-one - as long as we realise we've decided that.<br><br>Not having it would mean either not having the above functionality in the app, it being implemented on top (probably duplicating stuff implemented in some backends), or not using the API and just talking to backends that support it directly.
<br><br>Cheers,<br> James "Doc" Livingston<br>