[occi-wg] Categories and Collections
andrewx.edmonds at intel.com
Mon Oct 4 15:56:25 CDT 2010
I've placed my replies inline...
From: occi-wg-bounces at ogf.org [mailto:occi-wg-bounces at ogf.org] On Behalf Of
Sent: Monday, October 04, 2010 5:42 PM
To: Andy Edmonds; occi-wg
Subject: Re: [occi-wg] Categories and Collections
Nice work Andy!
A few comments:
- Could we have some HTTP-rendering examples of how to add/remove Kind
instances to/from a collection other than the defining collection?
AE: I'll get some examples added asap.
- The section on Navigation refer to Links and Actions, is this the Core
base types referred to? The Core Link type has little to do with paging
from my point of view. The Link Header in HTTP on the other hand can be
used for _both_ representing Core Links and paging. I see how Core Actions
can be used to express paging but the way Actions are rendered in HTTP
using Link Headers has again little to do with the Link base type. Please
see "Actions and the Link Header" at the end of  for a full description
of this terminology confusion.
AE: Ooops my mistake - Actions should not have been mentioned (I'll make
that edit). Paging through collections should be accomplished using Links
(e.g. in HTTP header renderings) as you point out. A beginning example can
be found here  in section 126.96.36.199. We need to make sure that the current
incarnation of Links can accommodate this behavior.
- When the http://schemas.ogf.org/occi/core# was introduced I thought it a
good idea to have it reserved for Categories defining the OCCI base types
(i.e. Resource, Link, Action). Although not necessary I think keeping this
distinction make the spec a bit easier to understand. The current
definition of Categories is:
The Category type represent the classification mechanism used by OCCI. It
MUST be implemented. From a system point of view a Category is used for
two different classification purposes. See also section 4.3 "Type System".
1. Taxonomy. A Category is used to assign static type information to each
resource type inheriting Kind or a descendant of Kind. This use of
Categories denotes the OCCI "static type system". A unique Category MUST
be assigned to every descendant of Kind. See the section 188.8.131.52
2. Folksonomy. A Category can be used to assign tags to resource instances
via a mix-in like model. A Category mix-in MUST NOT be related to an OCCI
base type (or any descendent of Kind) and MUST NOT be the unique
identifier thereof. Example use cases are collections, location
information and templates for virtual machine provisioning.
Collections play nicely with 2, the "folksonomy" use of Categories. My
point is that maybe we should have different schemes for Category use case
1 and 2, that is for Categories defined in Core. What do you think? It is
not terribly important though.
I.e. use a different scheme for the "tag" Category.
AE: we could use something like
"http://schemas.ogf.org/occi/core/collections#" as the scheme for tags?
I will annotate the wiki page as well.
On Sun, 03 Oct 2010 17:16:57 +0200, Andy Edmonds <andy at edmonds.be> wrote:
> Hey all,
> I've placed a write up of how categories and collections related to each
> other. Also there is how one can interact with collections. I've tried to
> keep the description as non-rendering-specific as possible.
> If there are comments etc please annotate the wiki page at the
> place or place your questions in the "Open Issues" section.
occi-wg mailing list
occi-wg at ogf.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 5213 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/occi-wg/attachments/20101004/b5485c7d/attachment.bin
-------------- next part --------------
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.
More information about the occi-wg