IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsResponses by BobHanisch reflect the consensus of the Standards and Processes Committee (FrancoiseGenova, ChristopheArviset, BobHanisch) and the Document Coordinator (BrunoRino).
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope"> <soapenv:Header> <soapenv:Body> <PushToVoSpace xmlns="http://www.net.ivoa/xml/VOSpaceContract-v1.0"> ...The namespace on the message body - http://www.net.ivoa/xml/VOSpaceContract-v1.0 - indicates that this is a message to a VOSpace-1.0 compliant service. The same message to a VOSpace 1.1 service would utilise the namespace http://www.net.ivoa/xml/VOSpaceContract-v1.1 instead. A VOSpace-1.0 client cannot be used with a VOSpace-1.1 service and vice versa. So by the rule of thumb VOSpace-1.1 should actually be VOSpace-2.0. The same argument applies, however, to minor changes, e.g. VOSpace-1.13 to VOSpace-1.14. This brings up another point - how should associated schema, WSDLs, etc., in fact anything with a namespace, be versioned? With the version number of the associated document? For example, the change from v1.13 to v1.14 of a standard just reflects a format change in the WSDL document but this is "new incompatible" version. Should all service standards just employ integer versioning? These points remain TBA in the context of the naming and numbering conventions. The above revisions were believed to be sufficiently significant that the Standards and Process Committee has returned the document to a Working Draft. There will be a second RFC period once the document has been republished and promoted to PR. |
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. Comments | ||||||||
Deleted: | ||||||||
< < | Find an example to guide you on how to add comments | |||||||
Changed: | ||||||||
< < |
| |||||||
> > | Responses by BobHanisch reflect the consensus of the Standards and Processes Committee (FrancoiseGenova, ChristopheArviset, BobHanisch) and the Document Coordinator (BrunoRino). | |||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Added: | ||||||||
> > | Agreed. This and other occurrences of "technical report" have been replaced with "document". | |||||||
| ||||||||
Added: | ||||||||
> > | The revised document includes essential text from the Note, and thus should be a complete picture of the IVOA standards process. | |||||||
| ||||||||
Added: | ||||||||
> > | We agreed to adopt the convention suggested by Bruno, so there will be a single URI that points to the document and its history. We are also working with the ADS to incorporate IVOA documents into their system. | |||||||
| ||||||||
Added: | ||||||||
> > | This wording will been changed once we have reached a more general agreement on naming and numbering of IVOA documents. | |||||||
| ||||||||
Added: | ||||||||
> > | We do not see a reason to make the IVOA document extensions more restrictive than those in general use on the Internet. | |||||||
| ||||||||
Added: | ||||||||
> > | A description of auxiliary files (XML schema, RDF vocabularies, and WSDL files) has been added. | |||||||
| ||||||||
Added: | ||||||||
> > | As above, we prefer to simply follow general practices for documents published on the Internet. We also did not feel it was appropriate to ban the use of Word given its widespread use and convenience in terms of tracking revisions to documents. We will, however, insist on every document being available in HTML and suggest that PDF versions also be provided. The text has been updated accordingly. | |||||||
| ||||||||
Added: | ||||||||
> > | We accept Bruno's recommendation to leave things as is. | |||||||
| ||||||||
Added: | ||||||||
> > | This has been clarified in the document. | |||||||
| ||||||||
Added: | ||||||||
> > | The role of the TCG in the review process has been clarified, and all references to TWG have been updated. | |||||||
| ||||||||
Added: | ||||||||
> > | Resolution of this issue is pending further inputs from WG/IG chairs. | |||||||
| ||||||||
Added: | ||||||||
> > | As mentioned above, we require an HTML version and recommend PDF also. | |||||||
| ||||||||
Added: | ||||||||
> > | We have reviewed the text and believe that the distinction between a Working Draft that is internal to a WG and a Working Draft that has been published for wider review is now much clearer. | |||||||
| ||||||||
Added: | ||||||||
> > | We have added the recommendation to include validation tools, though, like two interoperable implementations, this is strongly suggested but not absolutely required. | |||||||
| ||||||||
Added: | ||||||||
> > | We suggest that such interoperability tests be documented as a Note or as text included in the RFC pages. | |||||||
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope"> <soapenv:Header> <soapenv:Body> <PushToVoSpace xmlns="http://www.net.ivoa/xml/VOSpaceContract-v1.0"> ...The namespace on the message body - http://www.net.ivoa/xml/VOSpaceContract-v1.0 - indicates that this is a message to a VOSpace-1.0 compliant service. The same message to a VOSpace 1.1 service would utilise the namespace http://www.net.ivoa/xml/VOSpaceContract-v1.1 instead. A VOSpace-1.0 client cannot be used with a VOSpace-1.1 service and vice versa. So by the rule of thumb VOSpace-1.1 should actually be VOSpace-2.0. The same argument applies, however, to minor changes, e.g. VOSpace-1.13 to VOSpace-1.14. This brings up another point - how should associated schema, WSDLs, etc., in fact anything with a namespace, be versioned? With the version number of the associated document? For example, the change from v1.13 to v1.14 of a standard just reflects a format change in the WSDL document but this is "new incompatible" version. Should all service standards just employ integer versioning? | ||||||||
Added: | ||||||||
> > | These points remain TBA in the context of the naming and numbering conventions. | |||||||
Changed: | ||||||||
< < | ||||||||
> > | The above revisions were believed to be sufficiently significant that the Standards and Process Committee has returned the document to a Working Draft. There will be a second RFC period once the document has been republished and promoted to PR. | |||||||
Deleted: | ||||||||
< < | ||||||||
<--
|
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsFind an example to guide you on how to add comments
| ||||||||
Added: | ||||||||
> > |
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope"> <soapenv:Header> <soapenv:Body> <PushToVoSpace xmlns="http://www.net.ivoa/xml/VOSpaceContract-v1.0"> ...The namespace on the message body - http://www.net.ivoa/xml/VOSpaceContract-v1.0 - indicates that this is a message to a VOSpace-1.0 compliant service. The same message to a VOSpace 1.1 service would utilise the namespace http://www.net.ivoa/xml/VOSpaceContract-v1.1 instead. A VOSpace-1.0 client cannot be used with a VOSpace-1.1 service and vice versa. So by the rule of thumb VOSpace-1.1 should actually be VOSpace-2.0. The same argument applies, however, to minor changes, e.g. VOSpace-1.13 to VOSpace-1.14. This brings up another point - how should associated schema, WSDLs, etc., in fact anything with a namespace, be versioned? With the version number of the associated document? For example, the change from v1.13 to v1.14 of a standard just reflects a format change in the WSDL document but this is "new incompatible" version. Should all service standards just employ integer versioning? | |||||||
<--
|
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsFind an example to guide you on how to add comments
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
<--
|
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsFind an example to guide you on how to add comments
| ||||||||
Added: | ||||||||
> > |
| |||||||
<--
|
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsFind an example to guide you on how to add comments
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
<--
|
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsFind an example to guide you on how to add comments
| ||||||||
Added: | ||||||||
> > |
| |||||||
<--
|
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsFind an example to guide you on how to add comments
| ||||||||
Added: | ||||||||
> > |
| |||||||
<--
|
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsFind an example to guide you on how to add comments
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
<--
|
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsFind an example to guide you on how to add comments
| ||||||||
Added: | ||||||||
> > |
| |||||||
<--
|
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsFind an example to guide you on how to add comments
| ||||||||
Added: | ||||||||
> > |
| |||||||
<--
|
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsFind an example to guide you on how to add comments
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
<--
|
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: 16 September 2008 to 15 October 2008<-- Tcg evaluation: -->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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsFind an example to guide you on how to add comments | ||||||||
Added: | ||||||||
> > |
| |||||||
<--
|
Deleted: | ||||||||
< < | ||||||||
IVOA Document Standards RFC | ||||||||
Changed: | ||||||||
< < | This document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. | |||||||
> > | This document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. | |||||||
Changed: | ||||||||
< < | Review period: ? May 2008 to ? June 2008 | |||||||
> > | Review period: 16 September 2008 to 15 October 2008 | |||||||
<-- Tcg evaluation: --> | ||||||||
Changed: | ||||||||
< < | 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 two examples (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. | |||||||
> > | 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. | |||||||
Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net.
CommentsFind an example to guide you on how to add comments
<--
|
IVOA Document Standards RFCThis document will act as RFC centre for the IVOA Document Standards 1.10 Proposed Recommendation. Review period: ? May 2008 to ? June 2008<-- Tcg evaluation: -->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 two examples (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. Discussion about any of the comments or responses should be conducted on the Standing Committee on Standards & Processes mailing list, stdproc@ivoa.net. CommentsFind an example to guide you on how to add comments
<--
|