Sam,

Good luck with your move today.. I hope its somewhere nice. :-)

I'm hesitant cover this topic in tomorrow's document review. OGF 27 is less than 2 weeks a way, we need to get this document reviewed edit an ready for release. I do not want to spend the time discussing a shift in direction that will result in making the release of this document unachievable for OGF27. This group cannot miss another release date for this specification.

I suggest we table the discussion until after OGF27, and move forward with what we have. If there is significant enough reason and agreement by the group to change the current direction, we can split the document into a reference model and transport models, ala DMTF, SNIA, OMG, T10/SCSI, and ATA  and have enough time to properly analyze the options.

cheers,
gary


Sam Johnston wrote:
Gary,

I'm moving to another country today so it's not particularly convenient for me (which is why I hadn't responded to your poll yet). I'd suggest adjourning such a discussion until I can explain the pros and cons of the three main options which will either be on the call tomorrow (assuming I'm not carting boxes around at the time) or some time after Thursday. I'd explain by email now but it's 02h30 and I've got a big day ahead of me... just quickly the options (bearing in mind the payload/entity-body is effectively opaque) are:

 - use a wrapper format for the metadata like SOAP or Atom (which neuters many nice HTTP features like caching while adding a significant encoding overhead, but it does give us collections)
 - use a separate resource for the metadata e.g. have http://example.com/myvm.ovf as well as http://example.com/myvm.atom, http://example.com/myvm.json, http://example.com/myvm.txt etc. (which is what we had planned until recently, but which requires us to specify renderings in various formats)
 - use the HTTP headers (which avoids the whole format discussion by using a single, standard format which can be sent with [GET] or without [HEAD] the payload/entity-body)

I've spent the last week running around Europe talking about Open Cloud and OCCI too (CloudCamps in Edinburgh, London & Frankfurt among other things) so there's not many changes - at least from me - this week.

Sam

On Tue, Sep 29, 2009 at 1:15 AM, Gary Mazz <garymazzaferro@gmail.com> wrote:

*Although, signup for this meeting was a bit lackluster,  We have the
opportunity to meet  on Wed. Sept 30. 06:00 PDT, 9:00 EDT, 14:00 BST,
15:00 CEST

*cheers,
gary*
*

Thijs Metsch wrote:
> Sounds interesting...but Sept 25 doesn't work for me...
>
> Gary can you Maybe create a doodle for this event?
>
> Thanks,
>
> -Thijs
>
> On Wed, 2009-09-23 at 09:01 -0600, Gary Mazz wrote:
>
>> I' like to schedule a meeting to discuss Sam Johnston's proposal to move
>> OCCI attributes elusively  to HTTP headers.
>>
>> I'd like to schedule this conference on friday Sept 25, 2009, the as
>> time as the weekly call.
>>
>> We need to fully understand the mapping of the attributes to the http
>> protocol structures and the impacts to the specification.
>>
>> cheers,
>>
>> gary mazz
>>
>>
>> _______________________________________________
>> occi-wg mailing list
>> occi-wg@ogf.org
>> http://www.ogf.org/mailman/listinfo/occi-wg
>>

_______________________________________________
occi-wg mailing list
occi-wg@ogf.org
http://www.ogf.org/mailman/listinfo/occi-wg