Comments on: A description language for RESTful web services http://blog.kevburnsjr.com/web-service-description-languages Web Application Engineer Sun, 18 Dec 2011 02:08:36 -0800 http://wordpress.org/?v=2.8 hourly 1 By: KevBurnsJr http://blog.kevburnsjr.com/web-service-description-languages/comment-page-1#comment-2109 KevBurnsJr Fri, 13 Nov 2009 12:37:59 +0000 http://blog.kevburnsjr.com/?p=436#comment-2109 Yes, I've read that subbu article many times over. I like that AtomPub comes with <link rel="edit" />. I have yet to find a suitable link convention for JSON. I suppose the most obvious would be a top-level "links" : [{"rel":"self","url":"http://example/123"},{"rel":"edit","url":"http://example/123/edit"}] Regarding the Service Document, I like the looks of SMD (Service Map Description) http://groups.google.com/group/json-schema/web/service-mapping-description-proposal Yes, I’ve read that subbu article many times over.

I like that AtomPub comes with <link rel=”edit” />. I have yet to find a suitable link convention for JSON. I suppose the most obvious would be a top-level “links” : [{"rel":"self","url":"http://example/123"},{"rel":"edit","url":"http://example/123/edit"}]

Regarding the Service Document, I like the looks of SMD (Service Map Description)
http://groups.google.com/group/json-schema/web/service-mapping-description-proposal

]]> By: Bradley Holt http://blog.kevburnsjr.com/web-service-description-languages/comment-page-1#comment-2107 Bradley Holt Tue, 10 Nov 2009 22:27:49 +0000 http://blog.kevburnsjr.com/?p=436#comment-2107 One thing that's important to keep in mind is that REST is really an architectural style and does not provide any specific protocol or even architecture. For this reason I like to use AtomPub as a model of how to create and define RESTful architecture. It's the most well known RESTful *protocol* which means we can start talking in specifics instead of theory. I like the ideas for describing RESTful applications put forth in this article: http://www.infoq.com/articles/subbu-allamaraju-rest To apply this to AtomPub: * Define a minimal number of starting URIs: in AtomPub this would be the Service Document. * Define the link relations: in AtomPub this includes alternate, edit, edit-media and self. * Define the media types: AtomPub has application/atomsvc+xml, application/atomcat+xml and application/atom+xml. The combination of starting URI(s), link relations and media types should give you everything needed to describe a RESTful service. One thing that’s important to keep in mind is that REST is really an architectural style and does not provide any specific protocol or even architecture. For this reason I like to use AtomPub as a model of how to create and define RESTful architecture. It’s the most well known RESTful *protocol* which means we can start talking in specifics instead of theory.

I like the ideas for describing RESTful applications put forth in this article:

http://www.infoq.com/articles/subbu-allamaraju-rest

To apply this to AtomPub:

* Define a minimal number of starting URIs: in AtomPub this would be the Service Document.
* Define the link relations: in AtomPub this includes alternate, edit, edit-media and self.
* Define the media types: AtomPub has application/atomsvc+xml, application/atomcat+xml and application/atom+xml.

The combination of starting URI(s), link relations and media types should give you everything needed to describe a RESTful service.

]]>