
Nice work, it fits in to the current use of categories while making extensibility easier to understand. A few comments/questions: Each category, defined by schema + term, can have a set of associated attributes. What namespace restrictions/rules are imposed on these attributes? Currently Core&Models says provider defined categories must be in a different namespace but no more. Maybe extend this a bit further as to avoid namespace conflicts while combining many categories? I believe earlier revs of the spec said something like: com.example.<category_term>.<attr_name> I do not quite understand the various Content-type headers used in the examples. Are they of any significance to the definition/use of categories? And just a few notes on the examples, sorry if it sounds picky but consistency really helps understanding: - Category: compute; scheme="http://prov.com/occi#"; Scheme should be "http://prov.com/occi/resource#" right? - Link: </compute/123-123-123;start>; type="application/occi-action"; Is the "type" attribute of the Link header something new? If so, how it is defined? - In Link header: rel="category http://prov.com/occi#action" Is the format rel="category XXX" something new as well? regards, Ralf On Fri, 13 Aug 2010 11:10:18 +0200, Edmonds, AndrewX <andrewx.edmonds@intel.com> wrote:
Hi all, Yesterday Alexander and I spent some time exploring and discussing OCCI categories. These categories make up the type system for OCCI and I've documented our discussion here [1]. We'd love to hear feedback, comments etc!
Andy
[1] http://forge.gridforum.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Categor...
------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg