[occi-wg] Simple JSON rendering for OCCI

[Sam Johnston]

On Fri, May 15, 2009 at 6:08 AM, Gary Mazz <garymazzaferro at gmail.com> wrote:

> Agreed.... ANd plugfests are a good way to help identify those extensions.
>

Exactly. If OCCI gets anything more than modest adoption (it certainly
should provided we deliver on time) then we probably won't even have to
organise these ourselves... organisations like the Open Cloud Consortium
sound more geared up for this kind of thing anyway.

OTOH sounds like a useful addition to the OGF27/28 agenda.

Sam


> Randy Bias wrote:
> > Yes. Extensions do not need to be interoperable. If it becomes clear
> > that a given extension *does* need to be interoperable (e.g. widely
> > adopted or lots of variations of the same theme) then that’s a red
> > flag indicating we need to evaluate it for inclusion in the core.
> >
> >
> > On 5/14/09 12:42 PM, "Sam Johnston" <samj at samj.net> wrote:
> >
> >     Whoever said extensions need to be interoperable? We can do what
> >     we can (e.g. registries) but beyond that extensions are just
> >     somewhere for people to put stuff, like trunk space.
> >
> >
> >
> > --
> > Randy Bias, VP Technology Strategy, GoGrid
> > randyb at gogrid.com, (415) 939-8507 [mobile]
> > BLOG: http://neotactics.com/blog, TWITTER: twitter.com/randybias
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > occi-wg mailing list
> > occi-wg at ogf.org
> > http://www.ogf.org/mailman/listinfo/occi-wg
> >
>
> _______________________________________________
> occi-wg mailing list
> occi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/occi-wg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/occi-wg/attachments/20090515/236d5e19/attachment.html