Well, it depends on how picky you are. Albeit, this can be easily fixed by changing REST to CRUD in the core specs – that’s pretty much what we meant when saying „RESTful protocol“.
@Thijs: Correct me if I am wrong (you will, I bet ^^)
-A.--Dr. Alexander Papaspyrouadesso AGHead of IT Operations
From: <Sill>, Alan Sill
Date: Dienstag, 24. März 2015 14:15
To: "Stanik, Alexander"
Cc: "occi-wg@ogf.org"
Subject: Re: [occi-wg] Documents for OCCI rev 1.2
Hi,
Did I miss something in what you are flagging? This is not a contradiction. REST design is not dependent on being implemented in HTTP -- REST can be achieved with any transport.
Alan
On Mar 24, 2015, at 8:04 AM, Stanik, Alexander <alexander.stanik@tu-berlin.de> wrote:
- In the first sentence OCCI is defined as RESTful Protocol, but the text behind the second bullet says that the Core Model is HTTP independent. I think it would be very beneficial to keep the core model HTTP independent, which is also the advantage of having the Redering specifications in separate documents.
-------------------------------------------------------
>>> business. people. technology. <<<
-------------------------------------------------------adesso AG mit Sitz in Dortmund
Vorstand: Christoph Junge, Michael Kenfenheuer (Co-Vors.), Dr. Rüdiger Striemer (Co-Vors.)
Vorsitzender des Aufsichtsrates: Prof. Dr. Volker Gruhn
Amtsgericht Dortmund HRB 20663