Comments on: A conversation with Pablo Castro about Astoria’s RESTful data services

By: OData is grease to cut data friction « Jon Udell

OData is grease to cut data friction « Jon Udell — Fri, 26 Mar 2010 15:28:07 +0000

[...] | Tags: datafriction, odata | [11] Comments Back in 2007 I talked with Pablo Castro about Astoria, which I described as a way of making data readable and writeable by means of a RESTful interface. [...]

By: folly

folly — Sat, 15 Nov 2008 14:36:32 +0000

Good post.

By: SSIS Junkie : Astoria

SSIS Junkie : Astoria — Mon, 27 Oct 2008 11:56:50 +0000

[...] it just me? -JamieUPDATE: Jon Udell has done an interview with Pablo Castro. Read more here: http://blog.jonudell.net/2007/07/03/a-conversation-with-pablo-castro-about-astorias-restful-data-ser…Posted to SoBI (RSS feed), MDM (RSS feed), Astoria (RSS feed), REST (RSS feed) Published 30 June [...]

By: Being a Citizen Shouldn’t Be So Hard! Part 2: Beyond Government — contentious.com

Wed, 17 Sep 2008 00:28:57 +0000

[...] support them. That’s the idea behind Astoria (ADO.NET Services), which is discussed in this interview with Pablo Castro. If the NYC Department of Health had that kind of access layer sitting on top of its [restaurant [...]

By: Stonewall Farm, Darby Brook Farm, and the collaborative curation of data « Jon Udell

Fri, 02 May 2008 18:11:13 +0000

[...] scenario highlights a subtle but powerful benefit of data-publishing technologies like Astoria. When you aggressively expose record-level URLs, you can enable the same methods that will work for [...]

By: Overcoming data friction « Jon Udell

Overcoming data friction « Jon Udell — Wed, 20 Feb 2008 13:58:19 +0000

[...] them. That’s why I’m so excited about Astoria (ADO.NET Services, which is discussed in this interview with Pablo Castro. If the NYC Department of Health had that kind of access layer sitting on top of its database, it [...]

By: Patrick Logan

Patrick Logan — Thu, 05 Jul 2007 19:04:19 +0000

On verbs — careful Julien — what I think you are calling verbs seem to be demonstrative adjectives. Those are the articles “that julien likes” or “that julien dislikes” or “that julien wrote in Moscow”

I think you are justified to want these in your urls, but just to be clear they are not verbs that might tell the system to do something. They are adjectives that further categorize your resource information space.

By: Julien Boyreau

Julien Boyreau — Thu, 05 Jul 2007 15:25:48 +0000

Hello,

I found your post really interesting especially in its pattern. You set questions in English and TRANSLATE them in URL (or vice&versa).

That points to one of the two biggest challenges coming to RESTafarians :

#1: URL Opacity sucks
=> As everybody embeds natural languages in URLs, let’s do it in a designed way => Let’s fix Operators to mean “proper noun”, “common noun”, “genitive”, “preposition”, “plural”…tobe able to write “the best article about REST by Jon Udell” in URL.

#2: URL need verbs
=> Excluding verbs cut half of the richness of natural languages. To link me to this article, I need to use “like” to post it within “the articles I like” different from “the articles I dislike” or “the articles I wrote when I was in Moscow.”
=> Verbs needs to be accepted in REST. You would POST things TO the “do” URL that will create things at the “Done” one.

Thanks again for your always enlightening post.