« AtomPatch, or: Composing Media Types | Main | Getting Link Information: Design Time, Runtime, and on Demand »

Wednesday, September 11, 2013


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


Very good and valid points. Breaking URI schemes is probably almost sufficient to break most clients. Reminds me of the Chaos Monkey and the whole simian army of Netflix. :-)


yup, i guess breaking URIs on purpose already will wreak havoc on many clients. an ideal client might bookmark a URI for more efficient operations. but it still should be able to re-navigate to that resource from whatever a service says the home document location is, and then refresh the bookmark. it would be interesting to know how many clients would be able to do just that. probably not all that many...

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Your Information

(Name is required. Email address will not be displayed with the comment.)