VOSpace service specification: Request for Comments | ||||||||
Changed: | ||||||||
< < | This document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. | |||||||
> > | This document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. | |||||||
Review period: 23 July 2007 - 20 August 2007
In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.
Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.
Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)I approveChristophe Arviset (TCG vice Chair)I approve this document. The detailed description of all the Web Services operations is really useful.Bob Hanisch (Data Curation & Preservation IG)I approve.Gerard Lemson (Theory IG)i approve.Mireille Louys (Data Models WG)I approve the documentKeith Noddle (DAL WG)I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved.Francois Ochsenbein (VOTable WG)I approve the document.Pedro Osuna (VOQL WG)I approve.Ray Plante (Resource Registry WG)I see that my comments from the RFC period were addressed; therefore, I approve this document.Andrea Preite-Martinez (Semantics WG)I approve.Roy Williams (VOEvent WG)I approve this document. While this document does not give all the detail necessary to build a full implementation (schemas not defined, etc), it does provide a clear description of how the system works. Response from MatthewGraham: This document gives a full description of the interface and the request and response messages that it uses and is perfectly sufficient to build a full implementation. However, what Roy is alluding to is that the IVOA usage policy for VOSpace 1.0 is not defined in this document. This relates to what URIs identify the core metadata and the registry extension schema for registering descriptions of these. We have addressed these points in the comments above and the document does note that these are ongoing activities but not necessary for approval of the interface. As mentioned in the latest version of the spec (1.02), GWS WG is working on an ancillary document which will provide this information. |
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)I approveChristophe Arviset (TCG vice Chair) | ||||||||
Added: | ||||||||
> > | I approve this document. The detailed description of all the Web Services operations is really useful. | |||||||
Bob Hanisch (Data Curation & Preservation IG)I approve.Gerard Lemson (Theory IG)i approve.Mireille Louys (Data Models WG)I approve the documentKeith Noddle (DAL WG)I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved.Francois Ochsenbein (VOTable WG)I approve the document.Pedro Osuna (VOQL WG)I approve.Ray Plante (Resource Registry WG)I see that my comments from the RFC period were addressed; therefore, I approve this document.Andrea Preite-Martinez (Semantics WG)I approve.Roy Williams (VOEvent WG)I approve this document. While this document does not give all the detail necessary to build a full implementation (schemas not defined, etc), it does provide a clear description of how the system works. Response from MatthewGraham: This document gives a full description of the interface and the request and response messages that it uses and is perfectly sufficient to build a full implementation. However, what Roy is alluding to is that the IVOA usage policy for VOSpace 1.0 is not defined in this document. This relates to what URIs identify the core metadata and the registry extension schema for registering descriptions of these. We have addressed these points in the comments above and the document does note that these are ongoing activities but not necessary for approval of the interface. As mentioned in the latest version of the spec (1.02), GWS WG is working on an ancillary document which will provide this information.<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)I approveChristophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)I approve.Gerard Lemson (Theory IG)i approve.Mireille Louys (Data Models WG)I approve the documentKeith Noddle (DAL WG)I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved.Francois Ochsenbein (VOTable WG)I approve the document.Pedro Osuna (VOQL WG) | ||||||||
Added: | ||||||||
> > | I approve. | |||||||
Ray Plante (Resource Registry WG)I see that my comments from the RFC period were addressed; therefore, I approve this document.Andrea Preite-Martinez (Semantics WG)I approve.Roy Williams (VOEvent WG)I approve this document. While this document does not give all the detail necessary to build a full implementation (schemas not defined, etc), it does provide a clear description of how the system works. Response from MatthewGraham: This document gives a full description of the interface and the request and response messages that it uses and is perfectly sufficient to build a full implementation. However, what Roy is alluding to is that the IVOA usage policy for VOSpace 1.0 is not defined in this document. This relates to what URIs identify the core metadata and the registry extension schema for registering descriptions of these. We have addressed these points in the comments above and the document does note that these are ongoing activities but not necessary for approval of the interface. As mentioned in the latest version of the spec (1.02), GWS WG is working on an ancillary document which will provide this information.<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)I approveChristophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)I approve.Gerard Lemson (Theory IG)i approve.Mireille Louys (Data Models WG)I approve the documentKeith Noddle (DAL WG)I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved.Francois Ochsenbein (VOTable WG) | ||||||||
Added: | ||||||||
> > | I approve the document. | |||||||
Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)I see that my comments from the RFC period were addressed; therefore, I approve this document.Andrea Preite-Martinez (Semantics WG)I approve.Roy Williams (VOEvent WG)I approve this document. While this document does not give all the detail necessary to build a full implementation (schemas not defined, etc), it does provide a clear description of how the system works. Response from MatthewGraham: This document gives a full description of the interface and the request and response messages that it uses and is perfectly sufficient to build a full implementation. However, what Roy is alluding to is that the IVOA usage policy for VOSpace 1.0 is not defined in this document. This relates to what URIs identify the core metadata and the registry extension schema for registering descriptions of these. We have addressed these points in the comments above and the document does note that these are ongoing activities but not necessary for approval of the interface. As mentioned in the latest version of the spec (1.02), GWS WG is working on an ancillary document which will provide this information.<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)I approveChristophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)I approve.Gerard Lemson (Theory IG) | ||||||||
Added: | ||||||||
> > | i approve. | |||||||
Mireille Louys (Data Models WG)I approve the documentKeith Noddle (DAL WG)I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved.Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)I see that my comments from the RFC period were addressed; therefore, I approve this document.Andrea Preite-Martinez (Semantics WG)I approve.Roy Williams (VOEvent WG)I approve this document. While this document does not give all the detail necessary to build a full implementation (schemas not defined, etc), it does provide a clear description of how the system works. Response from MatthewGraham: This document gives a full description of the interface and the request and response messages that it uses and is perfectly sufficient to build a full implementation. However, what Roy is alluding to is that the IVOA usage policy for VOSpace 1.0 is not defined in this document. This relates to what URIs identify the core metadata and the registry extension schema for registering descriptions of these. We have addressed these points in the comments above and the document does note that these are ongoing activities but not necessary for approval of the interface. As mentioned in the latest version of the spec (1.02), GWS WG is working on an ancillary document which will provide this information.<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)I approveChristophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)I approve.Gerard Lemson (Theory IG)Mireille Louys (Data Models WG) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | I approve the document | |||||||
Keith Noddle (DAL WG)I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved.Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)I see that my comments from the RFC period were addressed; therefore, I approve this document.Andrea Preite-Martinez (Semantics WG)I approve.Roy Williams (VOEvent WG)I approve this document. While this document does not give all the detail necessary to build a full implementation (schemas not defined, etc), it does provide a clear description of how the system works. Response from MatthewGraham: This document gives a full description of the interface and the request and response messages that it uses and is perfectly sufficient to build a full implementation. However, what Roy is alluding to is that the IVOA usage policy for VOSpace 1.0 is not defined in this document. This relates to what URIs identify the core metadata and the registry extension schema for registering descriptions of these. We have addressed these points in the comments above and the document does note that these are ongoing activities but not necessary for approval of the interface. As mentioned in the latest version of the spec (1.02), GWS WG is working on an ancillary document which will provide this information.<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)I approveChristophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)I approve.Gerard Lemson (Theory IG)Mireille Louys (Data Models WG)Keith Noddle (DAL WG)I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved.Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG) | ||||||||
Added: | ||||||||
> > | I see that my comments from the RFC period were addressed; therefore, I approve this document. | |||||||
Andrea Preite-Martinez (Semantics WG)I approve.Roy Williams (VOEvent WG)I approve this document. While this document does not give all the detail necessary to build a full implementation (schemas not defined, etc), it does provide a clear description of how the system works. Response from MatthewGraham: This document gives a full description of the interface and the request and response messages that it uses and is perfectly sufficient to build a full implementation. However, what Roy is alluding to is that the IVOA usage policy for VOSpace 1.0 is not defined in this document. This relates to what URIs identify the core metadata and the registry extension schema for registering descriptions of these. We have addressed these points in the comments above and the document does note that these are ongoing activities but not necessary for approval of the interface. As mentioned in the latest version of the spec (1.02), GWS WG is working on an ancillary document which will provide this information.<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG) | ||||||||
Added: | ||||||||
> > | I approve | |||||||
Christophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)I approve.Gerard Lemson (Theory IG)Mireille Louys (Data Models WG)Keith Noddle (DAL WG)I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved.Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)Andrea Preite-Martinez (Semantics WG)I approve.Roy Williams (VOEvent WG)I approve this document. While this document does not give all the detail necessary to build a full implementation (schemas not defined, etc), it does provide a clear description of how the system works. Response from MatthewGraham: This document gives a full description of the interface and the request and response messages that it uses and is perfectly sufficient to build a full implementation. However, what Roy is alluding to is that the IVOA usage policy for VOSpace 1.0 is not defined in this document. This relates to what URIs identify the core metadata and the registry extension schema for registering descriptions of these. We have addressed these points in the comments above and the document does note that these are ongoing activities but not necessary for approval of the interface. As mentioned in the latest version of the spec (1.02), GWS WG is working on an ancillary document which will provide this information.<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)Christophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)I approve.Gerard Lemson (Theory IG)Mireille Louys (Data Models WG)Keith Noddle (DAL WG)I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved.Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)Andrea Preite-Martinez (Semantics WG)I approve.Roy Williams (VOEvent WG)I approve this document. While this document does not give all the detail necessary to build a full implementation (schemas not defined, etc), it does provide a clear description of how the system works. | ||||||||
Added: | ||||||||
> > | Response from MatthewGraham: This document gives a full description of the interface and the request and response messages that it uses and is perfectly sufficient to build a full implementation. However, what Roy is alluding to is that the IVOA usage policy for VOSpace 1.0 is not defined in this document. This relates to what URIs identify the core metadata and the registry extension schema for registering descriptions of these. We have addressed these points in the comments above and the document does note that these are ongoing activities but not necessary for approval of the interface. As mentioned in the latest version of the spec (1.02), GWS WG is working on an ancillary document which will provide this information. | |||||||
<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)Christophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)I approve.Gerard Lemson (Theory IG)Mireille Louys (Data Models WG)Keith Noddle (DAL WG)I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved.Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)Andrea Preite-Martinez (Semantics WG)I approve.Roy Williams (VOEvent WG) | ||||||||
Added: | ||||||||
> > | I approve this document. While this document does not give all the detail necessary to build a full implementation (schemas not defined, etc), it does provide a clear description of how the system works. | |||||||
<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)Christophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)I approve.Gerard Lemson (Theory IG)Mireille Louys (Data Models WG)Keith Noddle (DAL WG)I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved.Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)Andrea Preite-Martinez (Semantics WG) | ||||||||
Added: | ||||||||
> > | I approve. | |||||||
Roy Williams (VOEvent WG)<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)Christophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG) | ||||||||
Added: | ||||||||
> > | I approve. | |||||||
Gerard Lemson (Theory IG)Mireille Louys (Data Models WG)Keith Noddle (DAL WG)I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved.Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)Andrea Preite-Martinez (Semantics WG)Roy Williams (VOEvent WG)<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)Christophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)Gerard Lemson (Theory IG)Mireille Louys (Data Models WG)Keith Noddle (DAL WG) | ||||||||
Added: | ||||||||
> > | I approve this document. VOSpace V1.0 is the foundation upon which the IVOA can build truly useful data storage services. I hope we see such services and an enhanced standard (V1.1?) emerge quickly once VOSpace V1.0 has been approved. | |||||||
Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)Andrea Preite-Martinez (Semantics WG)Roy Williams (VOEvent WG)<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)Christophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)Gerard Lemson (Theory IG)Mireille Louys (Data Models WG)Keith Noddle (DAL WG)Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)Andrea Preite-Martinez (Semantics WG)Roy Williams (VOEvent WG)<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
-- DougTody - 20 Aug 2007
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)Christophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)Gerard Lemson (Theory IG)Mireille Louys (Data Models WG)Keith Noddle (DAL WG)Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)Andrea Preite-Martinez (Semantics WG)Roy Williams (VOEvent WG)<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Added: | ||||||||
> > | (DaveMorris) | |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)Christophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)Gerard Lemson (Theory IG)Mireille Louys (Data Models WG)Keith Noddle (DAL WG)Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)Andrea Preite-Martinez (Semantics WG)Roy Williams (VOEvent WG)<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
| ||||||||
Added: | ||||||||
> > |
Comments by TCGChairs should add their comments under their name.Mark Allen (Applications WG)Christophe Arviset (TCG vice Chair)Bob Hanisch (Data Curation & Preservation IG)Gerard Lemson (Theory IG)Mireille Louys (Data Models WG)Keith Noddle (DAL WG)Francois Ochsenbein (VOTable WG)Pedro Osuna (VOQL WG)Ray Plante (Resource Registry WG)Andrea Preite-Martinez (Semantics WG)Roy Williams (VOEvent WG) | |||||||
<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
Added: | ||||||||
> > | ||||||||
More detailed comments (these are representative, I am not attempting
to be uniform and complete at this point):
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
-- DougTody - 20 Aug 2007
<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
From RayPlante - 20 Aug 2007 Nice job on this document; it has the proper level of specificity for a service specfication.
| ||||||||
Added: | ||||||||
> > |
From DougTody - 20 Aug 2007 It is good to see progress on VOSpace, as we badly need this to add flexible data management capabilities to our services, and provide for more than just basic client-server data access. My comments are mostly fairly basic. I won't try to comment upon whether these should be addressed in this version or the next one. My apologies if I misunderstand aspects of the specification. General comments:
| |||||||
<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
| ||||||||
Changed: | ||||||||
< < | Although not fully documented, the Caltech VOSpace implements all features of the VOSpace 1.0 specification including StructuredDataNodes and the ability to request different views. | |||||||
> > | Although not fully documented, the Caltech VOSpace implements all features of the VOSpace 1.0 specification including StructuredDataNodes and the ability to request different views. | |||||||
Two VOSpace clients have also been produced at Caltech - one to talk to secure VOSpace services using digital signatures (WS-Security) and one to talk to unsecure services. These clients utilize a different underlying web service infrastructure to the one that the Caltech VOSpace implementation is based on (Apache Axis 1.2.1 Final vs. XFire 1.2.2).
The secure client has successfully negotiated data storage at the ESO VOSpace, including a third party data transfer into the VOSpace from a cone search service. This demonstrates sufficient interoperability of the implementations.
Comments from the Community
Comments from MarkTaylor
| ||||||||
Added: | ||||||||
> > | From RayPlante - 20 Aug 2007 | |||||||
Added: | ||||||||
> > | Nice job on this document; it has the proper level of specificity for a service specfication. | |||||||
Added: | ||||||||
> > |
| |||||||
<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
Comments from MarkTaylor
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
-- MarkTaylor - 01 Aug 2007
<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
Comments from the Community
| ||||||||
Added: | ||||||||
> > |
Comments from MarkTaylor
| |||||||
<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. Review period: 23 July 2007 - 20 August 2007 In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.Implementation detailsThree implementations of VOSpace 1.0 have been produced:
| ||||||||
Changed: | ||||||||
< < | Comments | |||||||
> > | Comments from the Community | |||||||
<--
|
VOSpace service specification: Request for Comments | ||||||||
Changed: | ||||||||
< < | This document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.00. | |||||||
> > | This document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.01. There is also an accompanying WSDL and schema. | |||||||
Added: | ||||||||
> > | Review period: 23 July 2007 - 20 August 2007 | |||||||
In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. | ||||||||
Added: | ||||||||
> > |
Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.
Implementation detailsThree implementations of VOSpace 1.0 have been produced:
| |||||||
Comments
<--
|
VOSpace service specification: Request for CommentsThis document will act as RFC centre for the VOSpace service specification Proposed Recommendation V1.00. In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.Comments
<--
|