URI Format - Part 1 - Addressing resources using URI path segments

MSDN Blog Postings » URI Format - Part 1 - Addressing resources using URI path segments

Fri, 21 Sep 2007 21:01:32 GMT

PingBack from http://msdnrss.thecoderblogs.com/2007/09/21/uri-format-part-1-addressing-resources-using-uri-path-segments/

re: URI Format - Part 1 - Addressing resources using URI path segments

Mark Baker — Sat, 22 Sep 2007 08:23:39 GMT

The relationship between "customers" and "23" is a hierarchical one, so "/customers/23" should be the proper way, if you want to avoid using a query. Ditto for "…/Customers/ALFKI/Orders/123".

I don't get the need for quoting. Quotes aren't special in the URI generic syntax (which is why "/" does need escaping), and I can't even see why your examples need them. Is it because of spaces? You could always escape them.

FWIW, you should probably use a query too, because HTML forms (without script hacks) can only build queries, and I fully expect your users will want browser (and HTML, using conneg) access to these parameterized URLs.

Some of the other things you talk about give me the impression that you're exposing too much "database" here. Why should "key" matter? Why are parentheses needed? I think you're making this harder than it needs to be.

re: URI Format - Part 1 - Addressing resources using URI path segments

Mike Flasko — Tue, 25 Sep 2007 10:08:48 GMT

Thanks for the feedback Mark. We'll take this back to the team and discuss. I beleive you are right in that the quotes are not strictly needed in this context. In a future post we will touch on the use of the query string where we need to have quoted literals. Part of the reason we adopted this in the URI path was for consistency between literals in the path and query string

re: URI Format - Part 1 - Addressing resources using URI path segments

Yaron Y. Goland — Thu, 27 Sep 2007 18:30:43 GMT

From a readability perspective it's 'less surprising' to have something like Customers/Customer(ALFKI)/Orders/Order(123) since this lets someone just pick up a URL and have a decent idea of what it's encoding. It's all about the trade offs, in this case between compactness and readability.

Izindaba #11

From the software development trenches — Fri, 28 Sep 2007 08:56:31 GMT

It is time for another weekly roundup of news that focuses on .NET, agile and general development related

Two most Astoria design posts: URIs and data sources

Pablo Castro's blog — Sat, 29 Sep 2007 18:58:54 GMT

We're trying to keep up posting regularly on the design aspects of Astoria we have on the table week

Two most Astoria design posts: URIs and data sources

Noticias externas — Sat, 29 Sep 2007 19:25:16 GMT

We're trying to keep up posting regularly on the design aspects of Astoria we have on the table week

re: URI Format - Part 1 - Addressing resources using URI path segments

Danny — Mon, 01 Oct 2007 18:17:07 GMT

Hmm, one thing I'd suggest bearing in mind is what the URIs identify - web resources may be information resources (things that can be completely represented in a document) or real-world things, concepts etc. Even if a Customer entity would always be a bunch of data, you might want to consider what the relationship between the person and the bunch of data might be.

See http://www.dfki.uni-kl.de/~sauermann/2006/11/cooluris/

SoCal MSDN events for Web Developers - slide deck and links

Contagious Curiosity — Wed, 05 Dec 2007 19:11:15 GMT

Presentations given in Irvine and Riverside, CA - here's the deck and links for more information about

Updates to URL syntax for December CTP of ADO.NET Data Services

Marcelo's WebLog — Wed, 09 Jan 2008 06:55:14 GMT

This post talks a bit about updates from the last post on the URI format . In that post, we discussed

Updates to URL syntax for December CTP of ADO.NET Data Services

Noticias externas — Wed, 09 Jan 2008 07:50:48 GMT

This post talks a bit about updates from the last post on the URI format . In that post, we discussed

$filter Query Option in ADO.NET Data Services

Marcelo's WebLog — Fri, 11 Jan 2008 08:43:05 GMT

Let's say that we have a data service exposing all of Northwind. We can get all customers in the database

$filter Query Option in ADO.NET Data Services

Noticias externas — Fri, 11 Jan 2008 09:30:02 GMT

Let's say that we have a data service exposing all of Northwind. We can get all customers in the