Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | The Vocabularies in the VO 2.1 PR has gone through a thorough review by TCG and community. TCG review and vote has been provided and cast. TCG coordination is fine in approving this PR to move on the REC path for Exec evaluation. (JE added 12/21 - will wait for MM review before moving on to Exec) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The Vocabularies in the VO 2.1 PR only fixes a terminology issue in the text when a vocabulary ends up being recommended and aligns description of the tooling and machinery of vocabularies maintenance with current solutions in use. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The PR has gone through a thorough review by TCG and community. TCG review and vote has been provided and cast; thus TCG coordination is fine in approving this PR to move on the REC path for Exec evaluation. -- JanetEvans - 2022-12-21 -- MarcoMolinaro - 2023-01-11 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Applications Working GroupIt looks good in general. A few comments: A: Should the title of Appendix A say 2022 instead of 2019 (and same for the first sentenced). I don't know exactly if and what has changed in the appendix.
Data Access Layer Working Group- Appendix C1: The phrase "prepared to accept the privacy cost involved with working through github" in the first sentence is extraneous and doesn't add anything to the standard.
Data Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged.
Grid & Web Services Working GroupNo particular comment from GWS. it is good for me. -- GiulianoTaffoni - 2022-12-07Registry Working GroupVery useful standard for the Registry. No particular comment. -- RenaudSavalle - 2022-12-07Semantics Working GroupNo particular comment from Semantics WG -- CarloMariaZwoelf - 2022-12-12Data Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
<!--</p> <ul> <li> <ul> <li> Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup </span> </li> </ul></li> </ul>--> |
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The Vocabularies in the VO 2.1 PR has gone through a thorough review by TCG and community. TCG review and vote has been provided and cast. TCG coordination is fine in approving this PR to move on the REC path for Exec evaluation. (JE added 12/21 - will wait for MM review before moving on to Exec) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Applications Working GroupIt looks good in general. A few comments: A: Should the title of Appendix A say 2022 instead of 2019 (and same for the first sentenced). I don't know exactly if and what has changed in the appendix.
Data Access Layer Working Group- Appendix C1: The phrase "prepared to accept the privacy cost involved with working through github" in the first sentence is extraneous and doesn't add anything to the standard.
Data Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged.
Grid & Web Services Working GroupNo particular comment from GWS. it is good for me. -- GiulianoTaffoni - 2022-12-07Registry Working GroupVery useful standard for the Registry. No particular comment. -- RenaudSavalle - 2022-12-07Semantics Working GroupNo particular comment from Semantics WG -- CarloMariaZwoelf - 2022-12-12Data Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
<!--</p> <ul> <li> <ul> <li> Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup </span> </li> </ul></li> </ul>--> |
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupIt looks good in general. A few comments: A: Should the title of Appendix A say 2022 instead of 2019 (and same for the first sentenced). I don't know exactly if and what has changed in the appendix.
Data Access Layer Working Group- Appendix C1: The phrase "prepared to accept the privacy cost involved with working through github" in the first sentence is extraneous and doesn't add anything to the standard.
Data Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged.
Grid & Web Services Working GroupNo particular comment from GWS. it is good for me. -- GiulianoTaffoni - 2022-12-07Registry Working GroupVery useful standard for the Registry. No particular comment. -- RenaudSavalle - 2022-12-07Semantics Working GroupNo particular comment from Semantics WG -- CarloMariaZwoelf - 2022-12-12Data Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
<!--</p> <ul> <li> <ul> <li> Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup </span> </li> </ul></li> </ul>--> |
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupIt looks good in general. A few comments: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | A: Sould the title of Appendix A say 2022 instead of 2019 (and same for the first sentenced). I don't know exactly if and what changed in the appendix. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | A: Should the title of Appendix A say 2022 instead of 2019 (and same for the first sentenced). I don't know exactly if and what has changed in the appendix. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A2: Is the draft field still necessary if the VEP are dealt with in PRs? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | C1: I too think that the VEP process is a bit overly complicated. Since separate lists of approved and abandoned VEPs already exist, maintainers could pre-assign a VEP number to authers so that they can name the file properly in the initial PR and avoid C2 all together. These VEPs are not frequent so I see no difficulty in keeping track of the pre-assigned numbers with the Twiki page. The proposed process currently works too, but a simpler one makes it less prone to errors. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | C1: I too think that the VEP process is a bit overly complicated. Since separate lists of approved and abandoned VEPs already exist, maintainers could pre-assign a VEP number to authers so that they can name the file properly in the initial PR and avoid C2 all together. These VEPs are not frequent so I see no difficulty in keeping track of the pre-assigned numbers with the Twiki page. The proposed process currently works too, but a simpler one makes it less prone to errors. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
-- AdrianDamian - 2022-12-13
Data Access Layer Working Group- Appendix C1: The phrase "prepared to accept the privacy cost involved with working through github" in the first sentence is extraneous and doesn't add anything to the standard.
Data Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged.
Grid & Web Services Working GroupNo particular comment from GWS. it is good for me. -- GiulianoTaffoni - 2022-12-07Registry Working GroupVery useful standard for the Registry. No particular comment. -- RenaudSavalle - 2022-12-07Semantics Working GroupNo particular comment from Semantics WG -- CarloMariaZwoelf - 2022-12-12Data Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
<!--</p> <ul> <li> <ul> <li> Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup </span> </li> </ul></li> </ul>--> |
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupIt looks good in general. A few comments: A: Sould the title of Appendix A say 2022 instead of 2019 (and same for the first sentenced). I don't know exactly if and what changed in the appendix. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A2: Is the draft field still necessary if the VEP are dealt with in PRs? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
C1: I too think that the VEP process is a bit overly complicated. Since separate lists of approved and abandoned VEPs already exist, maintainers could pre-assign a VEP number to authers so that they can name the file properly in the initial PR and avoid C2 all together. These VEPs are not frequent so I see no difficulty in keeping track of the pre-assigned numbers with the Twiki page. The proposed process currently works too, but a simpler one makes it less prone to errors. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
-- AdrianDamian - 2022-12-13
Data Access Layer Working Group- Appendix C1: The phrase "prepared to accept the privacy cost involved with working through github" in the first sentence is extraneous and doesn't add anything to the standard.
Data Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged.
Grid & Web Services Working GroupNo particular comment from GWS. it is good for me. -- GiulianoTaffoni - 2022-12-07Registry Working GroupVery useful standard for the Registry. No particular comment. -- RenaudSavalle - 2022-12-07Semantics Working GroupNo particular comment from Semantics WG -- CarloMariaZwoelf - 2022-12-12Data Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
<!--</p> <ul> <li> <ul> <li> Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup </span> </li> </ul></li> </ul>--> | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working Group | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | It looks good in general. A few comments:
A: Sould the title of Appendix A say 2022 instead of 2019 (and same for the first sentenced). I don't know exactly if and what changed in the appendix.
A2: Is the draft field still necessary if the VEP are dealt with in PRs?
C1: I too think that the VEP process is a bit overly complicated. Since separate lists of approved and abandoned VEPs already exist, maintainers could pre-assign a VEP number to authers so that they can name the file properly in the initial PR and avoid C2 all together. These VEPs are not frequent so I see no difficulty in keeping track of the pre-assigned numbers with the Twiki page. The proposed process currently works too, but a simpler one makes it less prone to errors. -- AdrianDamian - 2022-12-13 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Data Access Layer Working Group- Appendix C1: The phrase "prepared to accept the privacy cost involved with working through github" in the first sentence is extraneous and doesn't add anything to the standard.
Data Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged.
Grid & Web Services Working GroupNo particular comment from GWS. it is good for me. -- GiulianoTaffoni - 2022-12-07Registry Working GroupVery useful standard for the Registry. No particular comment. -- RenaudSavalle - 2022-12-07Semantics Working GroupNo particular comment from Semantics WG -- CarloMariaZwoelf - 2022-12-12Data Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
<!--</p> <ul> <li> <ul> <li> Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup </span> </li> </ul></li> </ul>--> |
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working Group- Appendix C1: The phrase "prepared to accept the privacy cost involved with working through github" in the first sentence is extraneous and doesn't add anything to the standard.
| ||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||
Otherwise looks good to me.
-- JamesDempsey - 2022-12-12
Data Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged.
Grid & Web Services Working GroupNo particular comment from GWS. it is good for me. -- GiulianoTaffoni - 2022-12-07Registry Working GroupVery useful standard for the Registry. No particular comment. -- RenaudSavalle - 2022-12-07Semantics Working Group | ||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||
> > | No particular comment from Semantics WG -- CarloMariaZwoelf - 2022-12-12 | |||||||||||||||||||||||||||||||||||||||||||||
Data Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
| ||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||
<!--</p> <ul> <li> <ul> <li> Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup </span> </li> </ul></li> </ul>--> |
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working Group- Appendix C1: The phrase "prepared to accept the privacy cost involved with working through github" in the first sentence is extraneous and doesn't add anything to the standard. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- Appendix C2: It seems the process would be simpler if you had the proposer request a VEP number and rename their file before raising the PR. Is this possible? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Otherwise looks good to me.
-- JamesDempsey - 2022-12-12
Data Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged.
Grid & Web Services Working GroupNo particular comment from GWS. it is good for me. -- GiulianoTaffoni - 2022-12-07Registry Working GroupVery useful standard for the Registry. No particular comment. -- RenaudSavalle - 2022-12-07Semantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | <!--</p> <ul> <li> <ul> <li> Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup</span> </li> </ul></li> </ul>--> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | <!--</p> <ul> <li> <ul> <li> Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup </span> </li> </ul></li> </ul>--> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working Group | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | - Appendix C1: The phrase "prepared to accept the privacy cost involved with working through github" in the first sentence is extraneous and doesn't add anything to the standard. - Appendix C2: It seems the process would be simpler if you had the proposer request a VEP number and rename their file before raising the PR. Is this possible? Otherwise looks good to me. -- JamesDempsey - 2022-12-12 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Data Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged.
Grid & Web Services Working GroupNo particular comment from GWS. it is good for me. -- GiulianoTaffoni - 2022-12-07Registry Working GroupVery useful standard for the Registry. No particular comment. -- RenaudSavalle - 2022-12-07Semantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | <--
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | <!--</p> <ul> <li> <ul> <li> Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup</span> </li> </ul></li> </ul>--> | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged.
Grid & Web Services Working Group | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | No particular comment from GWS. it is good for me. -- GiulianoTaffoni - 2022-12-07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Registry Working GroupVery useful standard for the Registry. No particular comment. -- RenaudSavalle - 2022-12-07Semantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
<--
|
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document | |||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||
Comments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged.
Grid & Web Services Working GroupRegistry Working Group | |||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Very useful standard for the Registry. No particular comment. -- RenaudSavalle - 2022-12-07 | ||||||||||||||||||||||||||||||||||||||||||||||||||
Semantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||
<--
| |||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- Appendix A1: Are the multiline description supported (with \n)
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- Appendix C: The git cookbook is very welcome, but a little bit discouraging | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- in general: I do not see the rationale for having 2 distinct GitHub repositories (Vocab + VEP) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
-- LaurentMichel - 2022-10-13 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Thanks for the answers, no need to change the text for so minor comments. -- LaurentMichel - 2022-10-18 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Grid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
<--
|
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupLooks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- Appendix A1: Are the multiline description supported (with \n) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- Appendix C: The git cookbook is very welcome, but a little bit discouraging | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- in general: I do not see the rationale for having 2 distinct GitHub repositories (Vocab + VEP) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
-- LaurentMichel - 2022-10-13
Grid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
<--
|
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working Group | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Looks good, a few minor questions and comments that do not require any change - Appendix A1: Is there some advice about the capitatisation or the term. My feeling is that lower case should be encouraged. - Appendix A1: Are the multiline description supported (with \n) - Appendix C: The git cookbook is very welcome, but a little bit discouraging - in general: I do not see the rationale for having 2 distinct GitHub repositories (Vocab + VEP) -- LaurentMichel - 2022-10-13 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Grid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupYes looks good. -- MarkTaylor - 2022-10-05Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
<--
|
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest Group | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Yes looks good. -- MarkTaylor - 2022-10-05 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Radio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
<--
|
Vocabularies in the VO 2.1 Proposed Recommendation: Request for CommentsThis is a Request for Comments on a minor update on Vocabularies in the VO, just updating the procedural appendices A, B, and C. The remaining material is unchanged. Latest version of VocInVO 2.1 can be found at: See also the source code at https://github.com/ivoa-std/vocinvoReference Interoperable ImplementationsNo changes to the machine-readable aspects; hence, see VocabulariesV20RFC.Implementations ValidatorsNo changes to (potentially) validatable content; hence, see VocabulariesV20RFC.Comments from the IVOA Community during RFC/TCG review period: 2022-09-20 through 2022-11-01The comments from the TCG members during the RFC/TCG review should be included in the next section. 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 Wiki Name so that 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. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2022-09-20 through 2022-11-01WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : 2022-11-01 through 2022-11-XXIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
<--
|