[occi-wg] Documents for OCCI rev 1.2

[Stanik, Alexander]

Dear Thijs,

I had read the Core and Text Rendering documents and found some mistakes:

OCCI Core:
- 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.
- Figure 2 illustrates that Category has a List of Attributes which is also specified in the text on page 7, but Table 2 does not list the Attribute's property.
- The Attribute's property "type" is in figure 2 of type String, but defined in section 5.3.2 as an enum {Object, List, Hash}. Besides this inconsistency, the type of Attributes can be everything as defined in the other specifications. Therefore I would prefer to String!?
- In table 7 the type of a mixin is Kind? This should be Mixin, right?

OCCI Text Rendering:
- It would be good to write out abbreviations in the beginning (e.g. ABNF, CRLF, etc.).
- In section 6 the first two sentences does not fit together :-)

In general, I think that the HTTP protocol can be used for examples but should not be illustrated as obligated.

Best regards
Alexander

--
M.Sc. Dipl.-Ing. Alexander Stanik

Technische Universität Berlin
Faculty of Electrical Engineering and Computer Science
Department of Telecommunication Systems
Complex and Distributed IT Systems

Secr. EN 59
Einsteinufer 17,
10587 Berlin

Phone:  +49 (30) 314-22616
Fax:    +49 (30) 314-21060
E-Mail: alexander.stanik at tu-berlin.de<mailto:alexander.stanik at tu-berlin.de>
WWW:    http://www.cit.tu-berlin.de

Von: occi-wg-bounces at ogf.org [mailto:occi-wg-bounces at ogf.org] Im Auftrag von Metsch, Thijs
Gesendet: Donnerstag, 19. März 2015 13:33
An: occi-wg at ogf.org
Betreff: [occi-wg] Documents for OCCI rev 1.2

Dear all,

Thanks to the help of many people we are close to putting the documents defining the revision 1.2 of OCCI into public comment!

To do so I want to ask all of you to review the documents as is and raise any possible show stoppers before putting these in public comment.

We propose that the following documents will be put into public comment asap:

As Recommendations:
* OCCI Core rev 1.2 which will obsolete GFD-R 183. A Errata has been attached to the end of the document
* OCCI Infrastructure rev 1.2 which will obsolete GFD-R 184. A Errata has been attached to the end of the document
* OCCI Protocol which is a newly written document describing how OCCI entities are dealt with using HTTP. This will obsolete GFD-R 185.
* OCCI Text rendering which is a newly written document describing how OCCI entities are rendered using a text format. This will obsolete GFD-R 185.
* OCCI Json rendering which is a newly written document describing how OCCI entities are rendered using a JSON format.
* OCCI Platform extension describing how a PaaS boundary interface can be modeled.
* OCCI SLA extension describing how a SLAs can be managed

As Informational documents:
* EGI FedCloud Profile
* Monitoring for OCCI

We will soon decide about the following documents:
* Notifications for OCCI
* OCCI-DRMAA binding (together with DRMAA-wg)

A PDF version of the documents is attached - The source can be found in our git repository on the master branch.

Again many thanks for all contributions and help offered!

Cheers,

-Thijs

Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/occi-wg/attachments/20150324/b19cca8a/attachment.html>