Great stuff - Thanks Ralf! Especially of keeping the HTTP stuff out of the Core :-) Looks much better now.

Just wondering if we should move the extensibility sections to one section...but that's just an editorial thought.

Cheers,

-Thijs

-----Original Message-----
From: occi-wg-bounces@ogf.org on behalf of Ralf Nyren
Sent: Sat 04-Sep-10 12:41
To: occi-wg@ogf.org
Subject: [occi-wg] Update of Core & Models and Infrastructure

Hi,

I have finished and uploaded a rather significant update of the Core & 
Models [1] document. The Infrastructure document [2] has been updated 
accordingly while the HTTP Rendering document is still in the works.

The Core & Models changelog:
  - Updated UML diagram. Fixes the issue with Actions.
  - Updated and re-structured description/definition of the base types. 
Please read everything through.
  - Templates definition added, it is just a Category but without the 
requirement to be a type construct.
  - Added full description of the Category base type.
  - Removed all REST and HTTP stuff. This information will reappear in the 
HTTP Rendering document.
  - HTTP related Open Issues will reappear in the HTTP Rendering document.
  - Extension rules properly defined.
  - Discovery mechanism from the Core perspective.

Hopefully the new version should be a lot more consistent and only address 
things relevant to the Core specification. The information which was 
specific to the HTTP rendering will reappear in that document when it is 
completed.

I put some effort into describing how to extend OCCI Core so each base 
type now has its on subsection describing the rules for domain-specific 
extensions.

Comments welcome.

regards, Ralf

[1] 
http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/CoreAndModels
[2] 
http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Infrastructure
_______________________________________________
occi-wg mailing list
occi-wg@ogf.org
http://www.ogf.org/mailman/listinfo/occi-wg