« World Wide Web Conference 2013 Poster Track: Call for Posters | Main | Structuring URI Templates »

Tuesday, November 27, 2012


Feed You can follow this conversation by subscribing to the comment feed for this post.

Ruben Verborgh

I'm confused when you say that http://amazon.com/bestsellingbookoftoday is not a (stable) identity. After all, that URL is an identifier, and it identifies a resource. And that resource is thereby the identity.
Since resources are temporarily varying membership functions, I'd say that yes, that URL does identify a stable identity. The fact that the *identity* can correspond to different *entities* at different points in time does not matter—what matters is that it will at any point in time be “the best selling book of today”.


@RubenVerborgh maybe i picked a bad example, and everything you write is correct. the point is that the persistent URIs that may be of more business value when building services around books are probably http://amazon.com/book/42 resources, because there will be important services linking to those when it comes to ordering, relating, managing comments and so forth. what i wanted to show was that some identities that an app may expose are not as core to a business as others, so if they go away or have to be moved, the impact on the business is probably less severe. for other resources, though, they are critical for the business and if they change identity, pretty much every business activity is affected.

Ruben Verborgh

That makes a lot of sense, thanks for clarifying!

The comments to this entry are closed.