[occi-wg] JSON collection rendering

[Jean Parpaillon]

If I understand correctly, a collection does not contain the detailed
representation of resources, only their id, which can have huge
consequences on implementation performances.
That's why I was looking for a representation of a list of resources (or
links) ids.

Basically, it may be:
{ entities:  [ id1, id2 ] }                               (1)
or
{ collection: [ id1, id2 ] }                              (2)
or
{ 
  resources: [ id1, id2 ],
  links:     [ id3, id4 ]
 }                                                        (3)
or
{ 
  resources: [ { id: id1 }, { id: id2 } ],
  links:     [ { id: id3 }, { id: id4 } ]
}                                                         (4)

Any of these is fine for me, but I really think we should agree on a
representation of collection without resources details. Order is my
preference order.

Any idea on this ?
Jean


Le vendredi 17 janvier 2014 à 11:11 +0100, Boris Parak a écrit :
> Yes :)
> 
> {
>   resources : [
>     RESOURCE1_JSON_HERE,
>     RESOURCE2_JSON_HERE,
>     RESOURCE3_JSON_HERE
>   ]
> }
> 
> where RESOURCE*_JSON_HERE might look something like this:
> 
> {
>   "kind": "http://schemas.ogf.org/occi/infrastructure#compute",
>   "mixins": [
>     "http://www.example.org/occi/my_scheme#my_term"
>   ],
>   "attributes": {
>     "occi": {
>       "core": {
>         "id": "1f975fd3-71f7-43e2-bffd-9fdee3825b55",
>         "title": "Cmpt1"
>       }
>     }
>   },
>   "id": "1f975fd3-71f7-43e2-bffd-9fdee3825b55",
>   "links": [
>     "/link/storagelink/b2d46a50-ad9f-415a-ac0c-ae7cfed9533c",
>     "/link/networkinterface/66195ffb-5162-4c14-aaf3-426c5aafc1ae"
>   ]
> }
> 
> Cheers, Boris
> 
> On Fri, Jan 17, 2014 at 9:41 AM, Jean Parpaillon
> <jean.parpaillon at free.fr> wrote:
> > Hi Boris,
> > May I understand it implies the 2nd approach ? :)
> >
> > { resources: { id: ...
> >
> > Cheers
> > Jean
> >
> > Le jeudi 16 janvier 2014 à 22:42 +0100, Boris Parak a écrit :
> >> Hi Jean,
> >>
> >> rOCCI is built on top of the JSON spec and we are using the latter. At
> >> least for me, the document implies this approach, although it's not
> >> explicitly mentioned there.
> >>
> >> Cheers, Boris
> >>
> >> On Thu, Jan 16, 2014 at 3:02 PM, Jean Parpaillon
> >> <jean.parpaillon at free.fr> wrote:
> >> > Hi all,
> >> > I have found no description of collection rendering in JSON draft.
> >> > For those who implemented it, how do you achieve it ?
> >> >
> >> > If collection is a type on its own, we could have the following
> >> > notation:
> >> > { collection : [ id1, id2, id3, ... ]}
> >> >
> >> > We can also imagine the following:
> >> > { resources: [ { id: ...}, { id: ... } ] }
> >> > or
> >> > { links: [ { id: ... }, { id: ... }] }
> >> >
> >> >
> >> > Cheers,
> >> > --
> >> > Jean Parpaillon
> >> > Open Source Consultant
> >> > Phone: +33 6 30 10 92 86
> >> > im: jean.parpaillon at gmail.com
> >> > skype: jean.parpaillon
> >> > linkedin: http://www.linkedin.com/in/jeanparpaillon/en
> >> >
> >> > _______________________________________________
> >> > occi-wg mailing list
> >> > occi-wg at ogf.org
> >> > https://www.ogf.org/mailman/listinfo/occi-wg
> >
> > --
> > Jean Parpaillon
> > Open Source Consultant
> > Phone: +33 6 30 10 92 86
> > im: jean.parpaillon at gmail.com
> > skype: jean.parpaillon
> > linkedin: http://www.linkedin.com/in/jeanparpaillon/en
> >

-- 
Jean Parpaillon
Open Source Consultant
Phone: +33 6 30 10 92 86
im: jean.parpaillon at gmail.com
skype: jean.parpaillon
linkedin: http://www.linkedin.com/in/jeanparpaillon/en