Looks like yet another REST metadata API format. As if we didn't have enough [1] of them already…

Re: your question, it's more a way of describing your API in a (potentially) machine readable format. Obviously, someone is going to raise his/her hand and whisper the forbidden words (*cough* automatic/dynamic client code generation *cough*), but so far it is really more documentation/metadata.

Re: OCCI I think this is orthogonal. While RAML simply describes resources and the base HTTP operations on them (along with their query parameters), OCCI gives resources structure and exposes their behavior. There is nothing against having RAML and OCCI existing next to each other. If there was an OCCI rendering that would solely rely on query parameters, one could render RAML out of it and vice versa.

-A.

[1] http://apiux.com/2013/04/09/rest-metadata-formats/

-- 
adesso mobile solutions GmbH
Dr.-Ing. Alexander Papaspyrou
Senior System Architect
IT Operations

Freie-Vogel-Str. 391 | 44269 Dortmund
T +49 231 930 66480 | F +49 231 930 9317 | M +49 172  209 4739
Mail: papaspyrou@adesso-mobile.de | Web: www.adesso-mobile.de | Mobil-Web: mobil.adesso-mobile.de

 

Vertretungsberechtigte Geschäftsführer: Dr. Josef Brewing, Frank Dobelmann
Registergericht: Amtsgericht Dortmund
Registernummer: HRB 13763
Umsatzsteuer-Identifikationsnummer gemäß § 27 a Umsatzsteuergesetz: DE201541832




Am 02.10.2013 um 18:56 schrieb "Sill, Alan" <alan.sill@ttu.edu>:

Thoughts? (My question is: what can you do with a RAML-formatted API description once you have it? Is it just an exercise and sanity check of your API?)

Topic:
RAML stands for RESTful API Modeling Language. It's a way of describing practically-RESTful APIs in a way that's highly readable by both humans and computers. We say "practically RESTful" because in the real world, very few APIs today actually are. RAML isn't strict: in the end it is only describing HTTP with a few higher-level (optional) constructs.
RAML is a non-proprietary, vendor-neutral open spec. The aim is to help our current API ecosystem and solve immediate problems, and then gently encourage ever-better API patterns.
\

Links:
http://raml.org/about.html
https://github.com/raml-org/raml-spec

Alan

_______________________________________________
occi-wg mailing list
occi-wg@ogf.org
https://www.ogf.org/mailman/listinfo/occi-wg