HTTP rendering doc out of public comment
Hi @all, Public comment has ended for the HTTP rendering document and we received some comments. I would take care of cleaning up the document, and issues 2, 3. I'll also update the security sections on all documents accordingly. @Andy: can you handle 1, 5? @Ralf: Can you handle 4, 6? Issues which can be edited right away: 1. Add ANTLR grammar as appendix to HTTP rendering doc 2. Add note about actions on a filtered collection 3. update security sections 4. add filtering mechanism based on X-OCCI-Attribute 5. advertise the query interface using the /.well-known mechanism as described in RFC5785 [1]. 6. For consistency OCCI Core attributes should be rendered with "occi.core." prepended. For example 'summary' would be rendered as 'occi.core.summary'. I'm not sure about the following: * Only show mutable attributes in the query interface Thinks to do regardless of the document: * register text/occi Deadline: THIS FRIDAY (April 1st)!!!
I'll look after those 2 requested items. -----Original Message----- From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of Thijs Metsch Sent: Wednesday, March 30, 2011 12:48 PM To: occi-wg@ogf.org Subject: [occi-wg] HTTP rendering doc out of public comment Hi @all, Public comment has ended for the HTTP rendering document and we received some comments. I would take care of cleaning up the document, and issues 2, 3. I'll also update the security sections on all documents accordingly. @Andy: can you handle 1, 5? @Ralf: Can you handle 4, 6? Issues which can be edited right away: 1. Add ANTLR grammar as appendix to HTTP rendering doc 2. Add note about actions on a filtered collection 3. update security sections 4. add filtering mechanism based on X-OCCI-Attribute 5. advertise the query interface using the /.well-known mechanism as described in RFC5785 [1]. 6. For consistency OCCI Core attributes should be rendered with "occi.core." prepended. For example 'summary' would be rendered as 'occi.core.summary'. I'm not sure about the following: * Only show mutable attributes in the query interface Thinks to do regardless of the document: * register text/occi Deadline: THIS FRIDAY (April 1st)!!! _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg ------------------------------------------------------------- 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.
Those items are done now. -----Original Message----- From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of Edmonds, AndrewX Sent: Wednesday, March 30, 2011 1:34 PM To: Thijs Metsch; occi-wg@ogf.org Subject: Re: [occi-wg] HTTP rendering doc out of public comment I'll look after those 2 requested items. -----Original Message----- From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of Thijs Metsch Sent: Wednesday, March 30, 2011 12:48 PM To: occi-wg@ogf.org Subject: [occi-wg] HTTP rendering doc out of public comment Hi @all, Public comment has ended for the HTTP rendering document and we received some comments. I would take care of cleaning up the document, and issues 2, 3. I'll also update the security sections on all documents accordingly. @Andy: can you handle 1, 5? @Ralf: Can you handle 4, 6? Issues which can be edited right away: 1. Add ANTLR grammar as appendix to HTTP rendering doc 2. Add note about actions on a filtered collection 3. update security sections 4. add filtering mechanism based on X-OCCI-Attribute 5. advertise the query interface using the /.well-known mechanism as described in RFC5785 [1]. 6. For consistency OCCI Core attributes should be rendered with "occi.core." prepended. For example 'summary' would be rendered as 'occi.core.summary'. I'm not sure about the following: * Only show mutable attributes in the query interface Thinks to do regardless of the document: * register text/occi Deadline: THIS FRIDAY (April 1st)!!! _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg ------------------------------------------------------------- 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.
nice thanks! leaves us to the discussion of partial/full updates or resources... Cheers, -Thijs -----Original Message----- From: Edmonds, AndrewX [mailto:andrewx.edmonds@intel.com] Sent: Fri 01.04.2011 12:41 To: Edmonds, AndrewX; Thijs Metsch; occi-wg@ogf.org Subject: RE: [occi-wg] HTTP rendering doc out of public comment Those items are done now. -----Original Message----- From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of Edmonds, AndrewX Sent: Wednesday, March 30, 2011 1:34 PM To: Thijs Metsch; occi-wg@ogf.org Subject: Re: [occi-wg] HTTP rendering doc out of public comment I'll look after those 2 requested items. -----Original Message----- From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of Thijs Metsch Sent: Wednesday, March 30, 2011 12:48 PM To: occi-wg@ogf.org Subject: [occi-wg] HTTP rendering doc out of public comment Hi @all, Public comment has ended for the HTTP rendering document and we received some comments. I would take care of cleaning up the document, and issues 2, 3. I'll also update the security sections on all documents accordingly. @Andy: can you handle 1, 5? @Ralf: Can you handle 4, 6? Issues which can be edited right away: 1. Add ANTLR grammar as appendix to HTTP rendering doc 2. Add note about actions on a filtered collection 3. update security sections 4. add filtering mechanism based on X-OCCI-Attribute 5. advertise the query interface using the /.well-known mechanism as described in RFC5785 [1]. 6. For consistency OCCI Core attributes should be rendered with "occi.core." prepended. For example 'summary' would be rendered as 'occi.core.summary'. I'm not sure about the following: * Only show mutable attributes in the query interface Thinks to do regardless of the document: * register text/occi Deadline: THIS FRIDAY (April 1st)!!! _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
On Mar 30, 2011, at 4:48 AM, Thijs Metsch wrote:
Public comment has ended for the HTTP rendering document and we received some comments. ...
Only commenting on this part:
Deadline: THIS FRIDAY (April 1st)!!!
While it's useful to set an internal group deadline, it's probably good to get the responses to the comments right on whatever timescale that this takes. Next Monday we will take up the final review of the core and infrastructure documents as noted earlier; Thijs has agreed to incorporate the modified security considerations sections and we will gather these along with any other feedback from the standards council at that time. If no other changes are proposed and no objections are raised, those will go to final publication. The most we can do with the HTTP Rendering doc if you are ready with it by then would be to initiate the 15-day final GFSG review, so while that would be good to do, if you need more time to address the public and internal comments properly, I encourage you to take it. Alan
This is also done... -Thijs -----Original Message----- From: occi-wg-bounces@ogf.org on behalf of Alan Sill Sent: Wed 30.03.2011 16:04 To: occi-wg@ogf.org Subject: Re: [occi-wg] HTTP rendering doc out of public comment While it's useful to set an internal group deadline, it's probably good to get the responses to the comments right on whatever timescale that this takes. Next Monday we will take up the final review of the core and infrastructure documents as noted earlier; Thijs has agreed to incorporate the modified security considerations sections and we will gather these along with any other feedback from the standards council at that time. If no other changes are proposed and no objections are raised, those will go to final publication. The most we can do with the HTTP Rendering doc if you are ready with it by then would be to initiate the 15-day final GFSG review, so while that would be good to do, if you need more time to address the public and internal comments properly, I encourage you to take it. Alan _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
'Is there a copy ?? I'm trying to get this finished for a demo in a week -gary On 4/1/2011 5:14 AM, Thijs Metsch wrote:
This is also done...
-Thijs
-----Original Message----- From: occi-wg-bounces@ogf.org on behalf of Alan Sill Sent: Wed 30.03.2011 16:04 To: occi-wg@ogf.org Subject: Re: [occi-wg] HTTP rendering doc out of public comment
While it's useful to set an internal group deadline, it's probably good to get the responses to the comments right on whatever timescale that this takes. Next Monday we will take up the final review of the core and infrastructure documents as noted earlier; Thijs has agreed to incorporate the modified security considerations sections and we will gather these along with any other feedback from the standards council at that time. If no other changes are proposed and no objections are raised, those will go to final publication.
The most we can do with the HTTP Rendering doc if you are ready with it by then would be to initiate the 15-day final GFSG review, so while that would be good to do, if you need more time to address the public and internal comments properly, I encourage you to take it.
Alan
_______________________________________________ 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
Sure - all current drafts are here: http://forge.ogf.org/sf/docman/do/listDocuments/projects.occi-wg/docman.root... -Thijs On Apr 3, 2011, at 6:54 AM, Gary Mazz wrote:
'Is there a copy ?? I'm trying to get this finished for a demo in a week
-gary
On 4/1/2011 5:14 AM, Thijs Metsch wrote:
This is also done...
-Thijs
-----Original Message----- From: occi-wg-bounces@ogf.org on behalf of Alan Sill Sent: Wed 30.03.2011 16:04 To: occi-wg@ogf.org Subject: Re: [occi-wg] HTTP rendering doc out of public comment
While it's useful to set an internal group deadline, it's probably good to get the responses to the comments right on whatever timescale that this takes. Next Monday we will take up the final review of the core and infrastructure documents as noted earlier; Thijs has agreed to incorporate the modified security considerations sections and we will gather these along with any other feedback from the standards council at that time. If no other changes are proposed and no objections are raised, those will go to final publication.
The most we can do with the HTTP Rendering doc if you are ready with it by then would be to initiate the 15-day final GFSG review, so while that would be good to do, if you need more time to address the public and internal comments properly, I encourage you to take it.
Alan
_______________________________________________ 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
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
Thanks Thijs, I had Ralf "cook" a pdf from the source. I don't have a linux box setup to build occi docs cheers, gary On 4/4/2011 1:51 AM, Thijs Metsch wrote:
Sure - all current drafts are here: http://forge.ogf.org/sf/docman/do/listDocuments/projects.occi-wg/docman.root...
-Thijs
On Apr 3, 2011, at 6:54 AM, Gary Mazz wrote:
'Is there a copy ?? I'm trying to get this finished for a demo in a week
-gary
On 4/1/2011 5:14 AM, Thijs Metsch wrote:
This is also done...
-Thijs
-----Original Message----- From: occi-wg-bounces@ogf.org on behalf of Alan Sill Sent: Wed 30.03.2011 16:04 To: occi-wg@ogf.org Subject: Re: [occi-wg] HTTP rendering doc out of public comment
While it's useful to set an internal group deadline, it's probably good to get the responses to the comments right on whatever timescale that this takes. Next Monday we will take up the final review of the core and infrastructure documents as noted earlier; Thijs has agreed to incorporate the modified security considerations sections and we will gather these along with any other feedback from the standards council at that time. If no other changes are proposed and no objections are raised, those will go to final publication.
The most we can do with the HTTP Rendering doc if you are ready with it by then would be to initiate the 15-day final GFSG review, so while that would be good to do, if you need more time to address the public and internal comments properly, I encourage you to take it.
Alan
_______________________________________________ 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
occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
Done and commited, including the attribute parameter ABNF and description. /Ralf On Wed, 30 Mar 2011 11:48:08 +0200, Thijs Metsch <tmetsch@platform.com> wrote:
Hi @all,
Public comment has ended for the HTTP rendering document and we received some comments.
I would take care of cleaning up the document, and issues 2, 3. I'll also update the security sections on all documents accordingly.
@Andy: can you handle 1, 5? @Ralf: Can you handle 4, 6?
Issues which can be edited right away:
1. Add ANTLR grammar as appendix to HTTP rendering doc
2. Add note about actions on a filtered collection
3. update security sections
4. add filtering mechanism based on X-OCCI-Attribute
5. advertise the query interface using the /.well-known mechanism as described in RFC5785 [1].
6. For consistency OCCI Core attributes should be rendered with "occi.core." prepended. For example 'summary' would be rendered as 'occi.core.summary'.
I'm not sure about the following:
* Only show mutable attributes in the query interface
Thinks to do regardless of the document:
* register text/occi
Deadline: THIS FRIDAY (April 1st)!!! _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
Great thanks! On Mar 31, 2011, at 10:50 PM, Ralf Nyren wrote:
Done and commited, including the attribute parameter ABNF and description. /Ralf
On Wed, 30 Mar 2011 11:48:08 +0200, Thijs Metsch <tmetsch@platform.com> wrote:
Hi @all,
Public comment has ended for the HTTP rendering document and we received some comments.
I would take care of cleaning up the document, and issues 2, 3. I'll also update the security sections on all documents accordingly.
@Andy: can you handle 1, 5? @Ralf: Can you handle 4, 6?
Issues which can be edited right away:
1. Add ANTLR grammar as appendix to HTTP rendering doc
2. Add note about actions on a filtered collection
3. update security sections
4. add filtering mechanism based on X-OCCI-Attribute
5. advertise the query interface using the /.well-known mechanism as described in RFC5785 [1].
6. For consistency OCCI Core attributes should be rendered with "occi.core." prepended. For example 'summary' would be rendered as 'occi.core.summary'.
I'm not sure about the following:
* Only show mutable attributes in the query interface
Thinks to do regardless of the document:
* register text/occi
Deadline: THIS FRIDAY (April 1st)!!! _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
The HTTP examples are now not up to date - will fix them asap. -Thijs -----Original Message----- From: occi-wg-bounces@ogf.org on behalf of Thijs Metsch Sent: Fri 01.04.2011 08:41 To: Ralf Nyren Cc: occi-wg@ogf.org Subject: Re: [occi-wg] HTTP rendering doc out of public comment Great thanks! On Mar 31, 2011, at 10:50 PM, Ralf Nyren wrote:
Done and commited, including the attribute parameter ABNF and description. /Ralf
On Wed, 30 Mar 2011 11:48:08 +0200, Thijs Metsch <tmetsch@platform.com> wrote:
Hi @all,
Public comment has ended for the HTTP rendering document and we received some comments.
I would take care of cleaning up the document, and issues 2, 3. I'll also update the security sections on all documents accordingly.
@Andy: can you handle 1, 5? @Ralf: Can you handle 4, 6?
Issues which can be edited right away:
1. Add ANTLR grammar as appendix to HTTP rendering doc
2. Add note about actions on a filtered collection
3. update security sections
4. add filtering mechanism based on X-OCCI-Attribute
5. advertise the query interface using the /.well-known mechanism as described in RFC5785 [1].
6. For consistency OCCI Core attributes should be rendered with "occi.core." prepended. For example 'summary' would be rendered as 'occi.core.summary'.
I'm not sure about the following:
* Only show mutable attributes in the query interface
Thinks to do regardless of the document:
* register text/occi
Deadline: THIS FRIDAY (April 1st)!!! _______________________________________________ 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
participants (6)
-
Alan Sill -
Edmonds, AndrewX -
Gary Mazz -
Ralf Nyren -
Thijs Metsch -
Thijs Metsch