Comments on: URIs and Objects http://www.subbu.org/blog/2008/04/uris-and-objects HTTP, REST and some Cycling Wed, 07 Jan 2009 02:27:01 +0000 http://wordpress.org/?v=2.7 hourly 1 By: MikeA http://www.subbu.org/blog/2008/04/uris-and-objects/comment-page-1#comment-251 MikeA Mon, 07 Apr 2008 19:57:18 +0000 http://wp.subbu.org/2008/04/uris-and-objects/#comment-251 Yep. That makes sense. And I enjoy reading your posts. I think like this: You have some data. You design a resource that exposes (some of) that data. You design a URI that points to the resource. You implement one or more media types to represent that resource. Not a perfect story, but it gets me closer, anyway. Yep. That makes sense. And I enjoy reading your posts.

I think like this:
You have some data.
You design a resource that exposes (some of) that data.
You design a URI that points to the resource.
You implement one or more media types to represent that resource.

Not a perfect story, but it gets me closer, anyway.

]]> By: Subbu Allamaraju http://www.subbu.org/blog/2008/04/uris-and-objects/comment-page-1#comment-250 Subbu Allamaraju Mon, 07 Apr 2008 18:08:03 +0000 http://wp.subbu.org/2008/04/uris-and-objects/#comment-250 Thanks for noticing the subtle point. I used "representation" to emphasize that each representation may need to be designed to meet whatever that needs to exposed for a given media type. Thanks for noticing the subtle point. I used “representation” to emphasize that each representation may need to be designed to meet whatever that needs to exposed for a given media type.

]]> By: MikeA http://www.subbu.org/blog/2008/04/uris-and-objects/comment-page-1#comment-249 MikeA Mon, 07 Apr 2008 17:20:35 +0000 http://wp.subbu.org/2008/04/uris-and-objects/#comment-249 Nice post. I'm not a fan of the "object->URI" pattern and you've just scratched the surface on the challenges. BTW - small thing, but I think of "representation" as the data sent over the wire (text/html, application/json, etc.) and the "resource" as the item described by the URI. In that light, your rule #2 might be better phrased as "Design resources to meet your data needs." Or possibly I've missed something in the post? Nice post. I’m not a fan of the “object->URI” pattern and you’ve just scratched the surface on the challenges.

BTW - small thing, but I think of “representation” as the data sent over the wire (text/html, application/json, etc.) and the “resource” as the item described by the URI. In that light, your rule #2 might be better phrased as “Design resources to meet your data needs.”

Or possibly I’ve missed something in the post?

]]>