Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap, http://voparis-cdpp.obspm.fr/tap, and http://gavo.aip.de/tap (the basic underlying software is identical for those); there is reg.g-vo.org that does DNS-based failover between these. Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. In particular, the ESAC implementation has been internally available in ESAC since at least 2014Q1 and has: (a) been validated against the vadlidation suite mentioned above (b) tested / accessed using the TopCAT client. On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )-- By this time, is there a second compliant implementation? If so, approved - SeverinGaudet - 2014-10-02Applications Working Group ( _Pierre Fernique, Tom Donaldson )Good document. Easy to read, easy to understand.One minor point and a small incoherence - related to this version http://www.ivoa.net/documents/RegTAP/20140627/PR-RegTAP-1.0-20140627.html#changes-20140227]] 1) In 1.2, the document cites the RegTAP-STC IVOA standard but without providing a reference, and I did not found it on the IVOA site. Is it a future note ? a future draft ? At this stage, I suggest to just remove this citation to this possible (but hypothetical) future standard extension. 2) There is an incoherence in 1.2, "ADQL, v2.0 (...) we give three functions ..." and in section 9, four user functions are defined. The standard RegTAP is approved by the chair and the vice-chair of the Application WG. -- PierreFernique - 2014-09-19 Removed RegTAP-STC reference, fixed the three vs. four. Thanks for pointing this out -- MarkusDemleitner - 2014-10-08 Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )I apologize for so late a comment which if I understand should have came sooner according to our rules. But IF it's not too much work I would recommend to replace xpath namespace by the original VO Resourse or VODataService xml schema namespace, which is used as the underlying model. This is a consistent mode of operation with what we have in DAL for ssa/obscore/siav2. xpath tells us how it is written but not what is the underlying model. By the way a diagram such as the one in RelationalRegistryDM would be very usefull for understanding of articulation between the tables - FrancoisBonnarel Approved - MarcoMolinaroData Model Working Group ( _Jesus Salgado, Omar Laurino ) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Added: | ||||||||
> > | Current specification is a clear simplification of the old registry interface that allows easier implementation, a clearer interface and, almost sure, better query performance. Maybe, a totally specific REST interface could have been defined but the reuse of the IVOA TAP is also useful to guarantee a fast implementation. There is not impact on DM activities so I approved the document -- JesusSalgado - 2014-11-11 | |||||||
Grid & Web Services Working Group ( André Schaaff, Brian Major )Looks good. Just a few comments about securityMethod, section 8.8: The interface Table:
Registry Working Group ( _Markus Demleitner, Pierre Le Sidaner)Not surpringly, we approve. -- MarkusDemleitner - 2014-11-10Semantics Working Group ( _Norman Gray, Mireille Louys)This is an admirably clear and well thought-through document. I particularly like the contextualising effect of Sect. 2, 'Design Considerations'. Sect. 4: This section discusses standard prefixes for certain namespaces. Is it possible for any other namespaces to appear in RegTAP queries? My impression is that this would be unusual but not impossible. Supposing that I wanted to use a different namespace, how would I pick a prefix that I was sure would avoid colliding with a future version of this document? Might it be reasonable to require people to pick prefixes starting 'x-' in this case? The Semantics WG Chair/Vice-Chair can see no interactions between this PR and the Semantics WG. The Semantics WG approves this document. Author Response: No -- extra namespace prefixes are not at all uncommon. They occur every time someone prototypes a Registry extension or distributes registry records referring to custom VOResource types. Hence, you're right that the question of collisions needs consideration. The answer I'd offer is that (a) the more typical case would probably be that prototype interfaces become standard, and with the current informal process of prefix minting no updates are necessary as a standard moves to REC and (b) a certain rate of false positives is acceptable, as real-world Registry clients will encounter (fairly large numbers of) misbehaving resources in what they discover anyway. Does that address your concerns? -- MarkusDemleitner - 2014-10-08Data Curation & Preservation Interest Group ( Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )The document is fine for me. No interference with Theory. Approved.Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick )Standards and Processes Committee ( Françoise Genova )<-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap, http://voparis-cdpp.obspm.fr/tap, and http://gavo.aip.de/tap (the basic underlying software is identical for those); there is reg.g-vo.org that does DNS-based failover between these. Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. In particular, the ESAC implementation has been internally available in ESAC since at least 2014Q1 and has: (a) been validated against the vadlidation suite mentioned above (b) tested / accessed using the TopCAT client. On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )-- By this time, is there a second compliant implementation? If so, approved - SeverinGaudet - 2014-10-02Applications Working Group ( _Pierre Fernique, Tom Donaldson )Good document. Easy to read, easy to understand.One minor point and a small incoherence - related to this version http://www.ivoa.net/documents/RegTAP/20140627/PR-RegTAP-1.0-20140627.html#changes-20140227]] 1) In 1.2, the document cites the RegTAP-STC IVOA standard but without providing a reference, and I did not found it on the IVOA site. Is it a future note ? a future draft ? At this stage, I suggest to just remove this citation to this possible (but hypothetical) future standard extension. 2) There is an incoherence in 1.2, "ADQL, v2.0 (...) we give three functions ..." and in section 9, four user functions are defined. The standard RegTAP is approved by the chair and the vice-chair of the Application WG. -- PierreFernique - 2014-09-19 Removed RegTAP-STC reference, fixed the three vs. four. Thanks for pointing this out -- MarkusDemleitner - 2014-10-08 Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )I apologize for so late a comment which if I understand should have came sooner according to our rules. But IF it's not too much work I would recommend to replace xpath namespace by the original VO Resourse or VODataService xml schema namespace, which is used as the underlying model. This is a consistent mode of operation with what we have in DAL for ssa/obscore/siav2. xpath tells us how it is written but not what is the underlying model. By the way a diagram such as the one in RelationalRegistryDM would be very usefull for understanding of articulation between the tables - FrancoisBonnarel Approved - MarcoMolinaroData Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( André Schaaff, Brian Major )Looks good. Just a few comments about securityMethod, section 8.8: The interface Table:
Registry Working Group ( _Markus Demleitner, Pierre Le Sidaner) | ||||||||
Added: | ||||||||
> > | Not surpringly, we approve. -- MarkusDemleitner - 2014-11-10 | |||||||
Semantics Working Group ( _Norman Gray, Mireille Louys)This is an admirably clear and well thought-through document. I particularly like the contextualising effect of Sect. 2, 'Design Considerations'. Sect. 4: This section discusses standard prefixes for certain namespaces. Is it possible for any other namespaces to appear in RegTAP queries? My impression is that this would be unusual but not impossible. Supposing that I wanted to use a different namespace, how would I pick a prefix that I was sure would avoid colliding with a future version of this document? Might it be reasonable to require people to pick prefixes starting 'x-' in this case? The Semantics WG Chair/Vice-Chair can see no interactions between this PR and the Semantics WG. The Semantics WG approves this document. Author Response: No -- extra namespace prefixes are not at all uncommon. They occur every time someone prototypes a Registry extension or distributes registry records referring to custom VOResource types. Hence, you're right that the question of collisions needs consideration. The answer I'd offer is that (a) the more typical case would probably be that prototype interfaces become standard, and with the current informal process of prefix minting no updates are necessary as a standard moves to REC and (b) a certain rate of false positives is acceptable, as real-world Registry clients will encounter (fairly large numbers of) misbehaving resources in what they discover anyway. Does that address your concerns? -- MarkusDemleitner - 2014-10-08Data Curation & Preservation Interest Group ( Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )The document is fine for me. No interference with Theory. Approved.Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick )Standards and Processes Committee ( Françoise Genova )<-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap, http://voparis-cdpp.obspm.fr/tap, and http://gavo.aip.de/tap (the basic underlying software is identical for those); there is reg.g-vo.org that does DNS-based failover between these. Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. | ||||||||
Changed: | ||||||||
< < | Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. | |||||||
> > | Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. In particular, the ESAC implementation has been internally available in ESAC since at least 2014Q1 and has: (a) been validated against the vadlidation suite mentioned above (b) tested / accessed using the TopCAT client. | |||||||
On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend.
Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )-- By this time, is there a second compliant implementation? If so, approved - SeverinGaudet - 2014-10-02Applications Working Group ( _Pierre Fernique, Tom Donaldson )Good document. Easy to read, easy to understand.One minor point and a small incoherence - related to this version http://www.ivoa.net/documents/RegTAP/20140627/PR-RegTAP-1.0-20140627.html#changes-20140227]] 1) In 1.2, the document cites the RegTAP-STC IVOA standard but without providing a reference, and I did not found it on the IVOA site. Is it a future note ? a future draft ? At this stage, I suggest to just remove this citation to this possible (but hypothetical) future standard extension. 2) There is an incoherence in 1.2, "ADQL, v2.0 (...) we give three functions ..." and in section 9, four user functions are defined. The standard RegTAP is approved by the chair and the vice-chair of the Application WG. -- PierreFernique - 2014-09-19 | ||||||||
Changed: | ||||||||
< < | Removed RegTAP-STC reference, fixed the three vs. four. Thanks for | |||||||
> > | Removed RegTAP-STC reference, fixed the three vs. four. Thanks for pointing this out | |||||||
Deleted: | ||||||||
< < | pointing this out | |||||||
-- MarkusDemleitner - 2014-10-08
Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )I apologize for so late a comment which if I understand should have came sooner according to our rules. But IF it's not too much work I would recommend to replace xpath namespace by the original VO Resourse or VODataService xml schema namespace, which is used as the underlying model. This is a consistent mode of operation with what we have in DAL for ssa/obscore/siav2. xpath tells us how it is written but not what is the underlying model. By the way a diagram such as the one in RelationalRegistryDM would be very usefull for understanding of articulation between the tables - FrancoisBonnarel Approved - MarcoMolinaroData Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( André Schaaff, Brian Major )Looks good. Just a few comments about securityMethod, section 8.8: The interface Table:
| ||||||||
Changed: | ||||||||
< < | Agreed on associating securityMethod with interface; if multiple | |||||||
> > | Agreed on associating securityMethod with interface; if multiple securityMethods will be possible on a single interface, a new table will probably be necessary. But let's wait how these technologies will look like in the wild. Thanks for the review. | |||||||
Deleted: | ||||||||
< < | securityMethods will be possible on a single interface, a new table will probably be necessary. But let's wait how these technologies will look like in the wild. Thanks for the review. | |||||||
-- MarkusDemleitner - 2014-10-08 | ||||||||
Deleted: | ||||||||
< < | ||||||||
Registry Working Group ( _Markus Demleitner, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)This is an admirably clear and well thought-through document. I particularly like the contextualising effect of Sect. 2, 'Design Considerations'. Sect. 4: This section discusses standard prefixes for certain namespaces. Is it possible for any other namespaces to appear in RegTAP queries? My impression is that this would be unusual but not impossible. Supposing that I wanted to use a different namespace, how would I pick a prefix that I was sure would avoid colliding with a future version of this document? Might it be reasonable to require people to pick prefixes starting 'x-' in this case? The Semantics WG Chair/Vice-Chair can see no interactions between this PR and the Semantics WG. The Semantics WG approves this document. | ||||||||
Changed: | ||||||||
< < | Author Response: No -- extra namespace prefixes are not at all uncommon. | |||||||
> > | Author Response: No -- extra namespace prefixes are not at all uncommon. They occur every time someone prototypes a Registry extension or distributes registry records referring to custom VOResource types. Hence, you're right that the question of collisions needs consideration. The answer I'd offer is that (a) the more typical case would probably be that prototype interfaces become standard, and with the current informal process of prefix minting no updates are necessary as a standard moves to REC and (b) a certain rate of false positives is acceptable, as real-world Registry clients will encounter (fairly large numbers of) misbehaving resources in what they discover anyway. Does that address your concerns? | |||||||
Deleted: | ||||||||
< < | They occur every time someone prototypes a Registry extension or distributes registry records referring to custom VOResource types. Hence, you're right that the question of collisions needs consideration. The answer I'd offer is that (a) the more typical case would probably be that prototype interfaces become standard, and with the current informal process of prefix minting no updates are necessary as a standard moves to REC and (b) a certain rate of false positives is acceptable, as real-world Registry clients will encounter (fairly large numbers of) misbehaving resources in what they discover anyway. Does that address your concerns? | |||||||
-- MarkusDemleitner - 2014-10-08 | ||||||||
Deleted: | ||||||||
< < | ||||||||
Data Curation & Preservation Interest Group ( Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )The document is fine for me. No interference with Theory. Approved.Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick )Standards and Processes Committee ( Françoise Genova )<-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz | ||||||||
Changed: | ||||||||
< < | An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). | |||||||
> > | An implementation of this is available on the TAP services at http://dc.g-vo.org/tap, http://voparis-cdpp.obspm.fr/tap, and http://gavo.aip.de/tap (the basic underlying software is identical for those); there is reg.g-vo.org that does DNS-based failover between these. | |||||||
Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one.
Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon.
On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend.
Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )-- By this time, is there a second compliant implementation? If so, approved - SeverinGaudet - 2014-10-02Applications Working Group ( _Pierre Fernique, Tom Donaldson )Good document. Easy to read, easy to understand.One minor point and a small incoherence - related to this version http://www.ivoa.net/documents/RegTAP/20140627/PR-RegTAP-1.0-20140627.html#changes-20140227]] 1) In 1.2, the document cites the RegTAP-STC IVOA standard but without providing a reference, and I did not found it on the IVOA site. Is it a future note ? a future draft ? At this stage, I suggest to just remove this citation to this possible (but hypothetical) future standard extension. 2) There is an incoherence in 1.2, "ADQL, v2.0 (...) we give three functions ..." and in section 9, four user functions are defined. The standard RegTAP is approved by the chair and the vice-chair of the Application WG. -- PierreFernique - 2014-09-19 Removed RegTAP-STC reference, fixed the three vs. four. Thanks for pointing this out -- MarkusDemleitner - 2014-10-08 Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )I apologize for so late a comment which if I understand should have came sooner according to our rules. But IF it's not too much work I would recommend to replace xpath namespace by the original VO Resourse or VODataService xml schema namespace, which is used as the underlying model. This is a consistent mode of operation with what we have in DAL for ssa/obscore/siav2. xpath tells us how it is written but not what is the underlying model. By the way a diagram such as the one in RelationalRegistryDM would be very usefull for understanding of articulation between the tables - FrancoisBonnarel Approved - MarcoMolinaroData Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( André Schaaff, Brian Major )Looks good. Just a few comments about securityMethod, section 8.8: The interface Table:
Registry Working Group ( _Markus Demleitner, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)This is an admirably clear and well thought-through document. I particularly like the contextualising effect of Sect. 2, 'Design Considerations'. Sect. 4: This section discusses standard prefixes for certain namespaces. Is it possible for any other namespaces to appear in RegTAP queries? My impression is that this would be unusual but not impossible. Supposing that I wanted to use a different namespace, how would I pick a prefix that I was sure would avoid colliding with a future version of this document? Might it be reasonable to require people to pick prefixes starting 'x-' in this case? The Semantics WG Chair/Vice-Chair can see no interactions between this PR and the Semantics WG. The Semantics WG approves this document. Author Response: No -- extra namespace prefixes are not at all uncommon. They occur every time someone prototypes a Registry extension or distributes registry records referring to custom VOResource types. Hence, you're right that the question of collisions needs consideration. The answer I'd offer is that (a) the more typical case would probably be that prototype interfaces become standard, and with the current informal process of prefix minting no updates are necessary as a standard moves to REC and (b) a certain rate of false positives is acceptable, as real-world Registry clients will encounter (fairly large numbers of) misbehaving resources in what they discover anyway. Does that address your concerns? -- MarkusDemleitner - 2014-10-08Data Curation & Preservation Interest Group ( Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )The document is fine for me. No interference with Theory. Approved.Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick )Standards and Processes Committee ( Françoise Genova )<-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )-- By this time, is there a second compliant implementation? If so, approved - SeverinGaudet - 2014-10-02Applications Working Group ( _Pierre Fernique, Tom Donaldson )Good document. Easy to read, easy to understand.One minor point and a small incoherence - related to this version http://www.ivoa.net/documents/RegTAP/20140627/PR-RegTAP-1.0-20140627.html#changes-20140227]] 1) In 1.2, the document cites the RegTAP-STC IVOA standard but without providing a reference, and I did not found it on the IVOA site. Is it a future note ? a future draft ? At this stage, I suggest to just remove this citation to this possible (but hypothetical) future standard extension. 2) There is an incoherence in 1.2, "ADQL, v2.0 (...) we give three functions ..." and in section 9, four user functions are defined. The standard RegTAP is approved by the chair and the vice-chair of the Application WG. -- PierreFernique - 2014-09-19 | ||||||||
Added: | ||||||||
> > | Removed RegTAP-STC reference, fixed the three vs. four. Thanks for pointing this out -- MarkusDemleitner - 2014-10-08 | |||||||
Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )I apologize for so late a comment which if I understand should have came sooner according to our rules. But IF it's not too much work I would recommend to replace xpath namespace by the original VO Resourse or VODataService xml schema namespace, which is used as the underlying model. This is a consistent mode of operation with what we have in DAL for ssa/obscore/siav2. xpath tells us how it is written but not what is the underlying model. By the way a diagram such as the one in RelationalRegistryDM would be very usefull for understanding of articulation between the tables - FrancoisBonnarel Approved - MarcoMolinaroData Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( André Schaaff, Brian Major )Looks good. Just a few comments about securityMethod, section 8.8: The interface Table:
| ||||||||
Added: | ||||||||
> > | Agreed on associating securityMethod with interface; if multiple securityMethods will be possible on a single interface, a new table will probably be necessary. But let's wait how these technologies will look like in the wild. Thanks for the review. -- MarkusDemleitner - 2014-10-08 | |||||||
Registry Working Group ( _Markus Demleitner, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)This is an admirably clear and well thought-through document. I particularly like the contextualising effect of Sect. 2, 'Design Considerations'. Sect. 4: This section discusses standard prefixes for certain namespaces. Is it possible for any other namespaces to appear in RegTAP queries? My impression is that this would be unusual but not impossible. Supposing that I wanted to use a different namespace, how would I pick a prefix that I was sure would avoid colliding with a future version of this document? Might it be reasonable to require people to pick prefixes starting 'x-' in this case? The Semantics WG Chair/Vice-Chair can see no interactions between this PR and the Semantics WG. The Semantics WG approves this document. | ||||||||
Added: | ||||||||
> > | Author Response: No -- extra namespace prefixes are not at all uncommon. They occur every time someone prototypes a Registry extension or distributes registry records referring to custom VOResource types. Hence, you're right that the question of collisions needs consideration. The answer I'd offer is that (a) the more typical case would probably be that prototype interfaces become standard, and with the current informal process of prefix minting no updates are necessary as a standard moves to REC and (b) a certain rate of false positives is acceptable, as real-world Registry clients will encounter (fairly large numbers of) misbehaving resources in what they discover anyway. Does that address your concerns? -- MarkusDemleitner - 2014-10-08 | |||||||
Data Curation & Preservation Interest Group ( Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )The document is fine for me. No interference with Theory. Approved.Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick )Standards and Processes Committee ( Françoise Genova )<-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham ) | ||||||||
Added: | ||||||||
> > | -- By this time, is there a second compliant implementation? If so, approved - SeverinGaudet - 2014-10-02 | |||||||
Applications Working Group ( _Pierre Fernique, Tom Donaldson )Good document. Easy to read, easy to understand.One minor point and a small incoherence - related to this version http://www.ivoa.net/documents/RegTAP/20140627/PR-RegTAP-1.0-20140627.html#changes-20140227]] 1) In 1.2, the document cites the RegTAP-STC IVOA standard but without providing a reference, and I did not found it on the IVOA site. Is it a future note ? a future draft ? At this stage, I suggest to just remove this citation to this possible (but hypothetical) future standard extension. 2) There is an incoherence in 1.2, "ADQL, v2.0 (...) we give three functions ..." and in section 9, four user functions are defined. The standard RegTAP is approved by the chair and the vice-chair of the Application WG. -- PierreFernique - 2014-09-19 Data Access Layer Working Group ( François Bonnarel, Marco Molinaro ) | ||||||||
Deleted: | ||||||||
< < | I apologize for so late a comment which if I understand should have came sooner according to our rules. But IF it's not too much work I would recommend to replace xpath namespace by the original VO Resourse or VODataService xml schema namespace, which is used as the underlying model. This is a consistent mode of operation with what we have in DAL for ssa/obscore/siav2. xpath tells us how it is written but not what is the underlying model. By the way a diagram such as the one in RelationalRegistryDM would be very usefull for understanding of articulation between the tables - FrancoisBonnarel | |||||||
Added: | ||||||||
> > | I apologize for so late a comment which if I understand should have came sooner according to our rules. But IF it's not too much work I would recommend to replace xpath namespace by the original VO Resourse or VODataService xml schema namespace, which is used as the underlying model. This is a consistent mode of operation with what we have in DAL for ssa/obscore/siav2. xpath tells us how it is written but not what is the underlying model. By the way a diagram such as the one in RelationalRegistryDM would be very usefull for understanding of articulation between the tables - FrancoisBonnarel | |||||||
Approved - MarcoMolinaro
Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( André Schaaff, Brian Major )Looks good. Just a few comments about securityMethod, section 8.8: The interface Table:
| ||||||||
Deleted: | ||||||||
< < | ||||||||
Registry Working Group ( _Markus Demleitner, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys) | ||||||||
Changed: | ||||||||
< < | This is an admirably clear and well thought-through document. I | |||||||
> > | This is an admirably clear and well thought-through document. I particularly like the contextualising effect of Sect. 2, 'Design Considerations'. | |||||||
Deleted: | ||||||||
< < | particularly like the contextualising effect of Sect. 2, 'Design Considerations'. | |||||||
Changed: | ||||||||
< < | Sect. 4: This section discusses standard prefixes for certain | |||||||
> > | Sect. 4: This section discusses standard prefixes for certain namespaces. Is it possible for any other namespaces to appear in RegTAP queries? My impression is that this would be unusual but not impossible. Supposing that I wanted to use a different namespace, how would I pick a prefix that I was sure would avoid colliding with a future version of this document? Might it be reasonable to require people to pick prefixes starting 'x-' in this case? | |||||||
Deleted: | ||||||||
< < | namespaces. Is it possible for any other namespaces to appear in RegTAP queries? My impression is that this would be unusual but not impossible. Supposing that I wanted to use a different namespace, how would I pick a prefix that I was sure would avoid colliding with a future version of this document? Might it be reasonable to require people to pick prefixes starting 'x-' in this case? | |||||||
Changed: | ||||||||
< < | The Semantics WG Chair/Vice-Chair can see no interactions between this | |||||||
> > | The Semantics WG Chair/Vice-Chair can see no interactions between this PR and the Semantics WG. The Semantics WG approves this document. | |||||||
Deleted: | ||||||||
< < | PR and the Semantics WG. The Semantics WG approves this document. | |||||||
Data Curation & Preservation Interest Group ( Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner ) | ||||||||
Changed: | ||||||||
< < | The document is fine for me. No interference with Theory. Approved. | |||||||
> > | The document is fine for me. No interference with Theory. Approved. | |||||||
Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick )Standards and Processes Committee ( Françoise Genova )<-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Pierre Fernique, Tom Donaldson )Good document. Easy to read, easy to understand.One minor point and a small incoherence - related to this version http://www.ivoa.net/documents/RegTAP/20140627/PR-RegTAP-1.0-20140627.html#changes-20140227]] 1) In 1.2, the document cites the RegTAP-STC IVOA standard but without providing a reference, and I did not found it on the IVOA site. Is it a future note ? a future draft ? At this stage, I suggest to just remove this citation to this possible (but hypothetical) future standard extension. 2) There is an incoherence in 1.2, "ADQL, v2.0 (...) we give three functions ..." and in section 9, four user functions are defined. The standard RegTAP is approved by the chair and the vice-chair of the Application WG. -- PierreFernique - 2014-09-19 Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )I apologize for so late a comment which if I understand should have came sooner according to our rules. But IF it's not too much work I would recommend to replace xpath namespace by the original VO Resourse or VODataService xml schema namespace, which is used as the underlying model. This is a consistent mode of operation with what we have in DAL for ssa/obscore/siav2. xpath tells us how it is written but not what is the underlying model. By the way a diagram such as the one in RelationalRegistryDM would be very usefull for understanding of articulation between the tables - FrancoisBonnarel Approved - MarcoMolinaroData Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( André Schaaff, Brian Major )Looks good. Just a few comments about securityMethod, section 8.8: The interface Table:
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Registry Working Group ( _Markus Demleitner, Pierre Le Sidaner) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Semantics Working Group ( _Norman Gray, Mireille Louys) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Added: | ||||||||
> > | This is an admirably clear and well thought-through document. I particularly like the contextualising effect of Sect. 2, 'Design Considerations'. Sect. 4: This section discusses standard prefixes for certain namespaces. Is it possible for any other namespaces to appear in RegTAP queries? My impression is that this would be unusual but not impossible. Supposing that I wanted to use a different namespace, how would I pick a prefix that I was sure would avoid colliding with a future version of this document? Might it be reasonable to require people to pick prefixes starting 'x-' in this case? The Semantics WG Chair/Vice-Chair can see no interactions between this PR and the Semantics WG. The Semantics WG approves this document. | |||||||
Data Curation & Preservation Interest Group ( Françoise Genova ) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Education Interest Group ( _Massimo Ramella, Sudhanshu Barway ) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Knowledge Discovery in Databases Interest Group ( George Djorgovski ) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Theory Interest Group ( _Franck Le Petit, Rick Wagner )The document is fine for me. No interference with Theory. Approved.Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick ) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Standards and Processes Committee ( Françoise Genova )<-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Pierre Fernique, Tom Donaldson )Good document. Easy to read, easy to understand.One minor point and a small incoherence - related to this version http://www.ivoa.net/documents/RegTAP/20140627/PR-RegTAP-1.0-20140627.html#changes-20140227]] 1) In 1.2, the document cites the RegTAP-STC IVOA standard but without providing a reference, and I did not found it on the IVOA site. Is it a future note ? a future draft ? At this stage, I suggest to just remove this citation to this possible (but hypothetical) future standard extension. 2) There is an incoherence in 1.2, "ADQL, v2.0 (...) we give three functions ..." and in section 9, four user functions are defined. The standard RegTAP is approved by the chair and the vice-chair of the Application WG. -- PierreFernique - 2014-09-19 Data Access Layer Working Group ( François Bonnarel, Marco Molinaro ) | ||||||||
Added: | ||||||||
> > | I apologize for so late a comment which if I understand should have came sooner according to our rules. But IF it's not too much work I would recommend to replace xpath namespace by the original VO Resourse or VODataService xml schema namespace, which is used as the underlying model. This is a consistent mode of operation with what we have in DAL for ssa/obscore/siav2. xpath tells us how it is written but not what is the underlying model. By the way a diagram such as the one in RelationalRegistryDM would be very usefull for understanding of articulation between the tables - FrancoisBonnarel | |||||||
Approved - MarcoMolinaro
Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( André Schaaff, Brian Major )Looks good. Just a few comments about securityMethod, section 8.8: The interface Table:
Registry Working Group ( _Markus Demleitner, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )The document is fine for me. No interference with Theory. Approved.Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick )Standards and Processes Committee ( Françoise Genova )<-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Pierre Fernique, Tom Donaldson )Good document. Easy to read, easy to understand.One minor point and a small incoherence - related to this version http://www.ivoa.net/documents/RegTAP/20140627/PR-RegTAP-1.0-20140627.html#changes-20140227]] 1) In 1.2, the document cites the RegTAP-STC IVOA standard but without providing a reference, and I did not found it on the IVOA site. Is it a future note ? a future draft ? At this stage, I suggest to just remove this citation to this possible (but hypothetical) future standard extension. 2) There is an incoherence in 1.2, "ADQL, v2.0 (...) we give three functions ..." and in section 9, four user functions are defined. The standard RegTAP is approved by the chair and the vice-chair of the Application WG. -- PierreFernique - 2014-09-19 Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Approved - MarcoMolinaroData Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( André Schaaff, Brian Major )Looks good. Just a few comments about securityMethod, section 8.8: The interface Table:
Registry Working Group ( _Markus Demleitner, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner ) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Added: | ||||||||
> > | The document is fine for me. No interference with Theory. Approved. | |||||||
Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick )Standards and Processes Committee ( Françoise Genova )<-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Pierre Fernique, Tom Donaldson ) | ||||||||
Added: | ||||||||
> > |
Good document. Easy to read, easy to understand. One minor point and a small incoherence - related to this version http://www.ivoa.net/documents/RegTAP/20140627/PR-RegTAP-1.0-20140627.html#changes-20140227]] 1) In 1.2, the document cites the RegTAP-STC IVOA standard but without providing a reference, and I did not found it on the IVOA site. Is it a future note ? a future draft ? At this stage, I suggest to just remove this citation to this possible (but hypothetical) future standard extension. 2) There is an incoherence in 1.2, "ADQL, v2.0 (...) we give three functions ..." and in section 9, four user functions are defined. The standard RegTAP is approved by the chair and the vice-chair of the Application WG. -- PierreFernique - 2014-09-19 | |||||||
Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Approved - MarcoMolinaroData Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( André Schaaff, Brian Major ) | ||||||||
Changed: | ||||||||
< < | Looks good. Just a few comments about securityMethod, section 8.8: The interface Table:
| |||||||
> > | Looks good. Just a few comments about securityMethod, section 8.8: The interface Table:
| |||||||
Deleted: | ||||||||
< < | ||||||||
Approved - BrianMajor
Registry Working Group ( _Markus Demleitner, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick )Standards and Processes Committee ( Françoise Genova )<-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Pierre Fernique, Tom Donaldson )Data Access Layer Working Group ( François Bonnarel, Marco Molinaro ) | ||||||||
Added: | ||||||||
> > | ||||||||
Approved - MarcoMolinaro
Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( André Schaaff, Brian Major ) | ||||||||
Added: | ||||||||
> > |
Looks good. Just a few comments about securityMethod, section 8.8: The interface Table:
| |||||||
Registry Working Group ( _Markus Demleitner, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick )Standards and Processes Committee ( Françoise Genova )<-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham ) | ||||||||
Changed: | ||||||||
< < | Applications Working Group ( _Mark Taylor, Pierre Fernique ) | |||||||
> > | Applications Working Group ( _Pierre Fernique, Tom Donaldson ) | |||||||
Changed: | ||||||||
< < | Data Access Layer Working Group ( François Bonnarel, Marco Molinaro ) | |||||||
> > | Data Access Layer Working Group ( François Bonnarel, Marco Molinaro ) | |||||||
Added: | ||||||||
> > | Approved - MarcoMolinaro | |||||||
Data Model Working Group ( _Jesus Salgado, Omar Laurino ) | ||||||||
Changed: | ||||||||
< < | Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff ) | |||||||
> > | Grid & Web Services Working Group ( André Schaaff, Brian Major ) | |||||||
Changed: | ||||||||
< < | Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner) | |||||||
> > | Registry Working Group ( _Markus Demleitner, Pierre Le Sidaner) | |||||||
Semantics Working Group ( _Norman Gray, Mireille Louys) | ||||||||
Changed: | ||||||||
< < | Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova ) | |||||||
> > | Data Curation & Preservation Interest Group ( Françoise Genova ) | |||||||
Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner ) | ||||||||
Changed: | ||||||||
< < | Time Domain Interest Group ( _Matthew Graham, John Swinbank ) | |||||||
> > | Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick ) | |||||||
Standards and Processes Committee ( Françoise Genova )<-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. | ||||||||
Changed: | ||||||||
< < | On the client side, newer versions of TOPCAT already query against | |||||||
> > | On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend. | |||||||
Deleted: | ||||||||
< < | RegTAP. Also WIRR uses RegTAP as a backend. | |||||||
Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique ) | ||||||||
Changed: | ||||||||
< < | Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick ) | |||||||
> > | Data Access Layer Working Group ( François Bonnarel, Marco Molinaro ) | |||||||
Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova ) | ||||||||
Changed: | ||||||||
< < | <!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> | |||||||
> > | <-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. | ||||||||
Changed: | ||||||||
< < | Implementations are also being worked on at ESAC and STScI; these were | |||||||
> > | Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. | |||||||
Deleted: | ||||||||
< < | reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. | |||||||
Added: | ||||||||
> > | On the client side, newer versions of TOPCAT already query against RegTAP. Also WIRR uses RegTAP as a backend. | |||||||
Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. | ||||||||
Changed: | ||||||||
< < | RFC Review period: March 14, 2014 - April 15, 2014 TCG Review period: Exec Approved for REC: | |||||||
> > | RFC Review period: March 14, 2014 - April 15, 2014 TCG Review period: July 28, 2014 - August 28, 2014 Exec Approved for REC: | |||||||
To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document
Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. | ||||||||
Added: | ||||||||
> > | Implementations are also being worked on at ESAC and STScI; these were reported on in the Registry sessions of the Heidelberg, Waikoloa, and Madrid interops and should become public fairly soon. | |||||||
Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
| ||||||||
Added: | ||||||||
> > | Yes, making the type for the _index columns implementation specific is sufficient. Thanks. -- PatrickDowler - 2014-07-24 | |||||||
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and Validaters | ||||||||
Changed: | ||||||||
< < | A provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-03.tar.gz | |||||||
> > | A provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-06.tar.gz | |||||||
An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those).
Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one.
Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
| ||||||||
Changed: | ||||||||
< < | In Volute rev. 2646, I dropped requirements on the artificial foreign | |||||||
> > | In Volute rev. 2646, I dropped requirements on the artificial foreign keys. Pat (and others interested in this) -- please review http://volute.googlecode.com/svn/trunk/projects/registry/regtap/RegTAP-fmt.html#primarykeys and the diff (this necessitated changes in several places). Does this fix things as far as you are concerned? | |||||||
Deleted: | ||||||||
< < | keys. Pat (and others interested in this) -- please review http://volute.googlecode.com/svn/trunk/projects/registry/regtap/RegTAP-fmt.html#primarykeys and the diff (this necessitated changes in several places). Does this fix things as far as you are concerned? | |||||||
-- MarkusDemleitner - 2014-06-03
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-03.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
| ||||||||
Changed: | ||||||||
< < | We did consider surrogate keys in the very earliest relational registry data models - see RelationalRegistryDM - However, it was decided that ease of writing queries was the primary goal of the design, and therefore it was useful to have the IVORN in as many tables as possible - so for certain queries fewer joins would be necessary. The smallint part of the composite key is generally easily generated on ingestion from the child index in its parent of the main modelled XML element for that table. | |||||||
> > | We did consider surrogate keys in the very earliest relational registry data models - see RelationalRegistryDM - However, it was decided that ease of writing queries was the primary goal of the design, and therefore it was useful to have the IVORN in as many tables as possible - so for certain queries fewer joins would be necessary. The smallint part of the composite key is generally easily generated on ingestion from the child index in its parent of the main modelled XML element for that table. | |||||||
-- PaulHarrison - 2014-05-23 | ||||||||
Added: | ||||||||
> > | The slap prefix went in in Volute rev. 2645 -- thanks for catching this. In Volute rev. 2646, I dropped requirements on the artificial foreign keys. Pat (and others interested in this) -- please review http://volute.googlecode.com/svn/trunk/projects/registry/regtap/RegTAP-fmt.html#primarykeys and the diff (this necessitated changes in several places). Does this fix things as far as you are concerned? -- MarkusDemleitner - 2014-06-03 | |||||||
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-03.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Late commentsSome technically late comments:
| ||||||||
Added: | ||||||||
> > | We did consider surrogate keys in the very earliest relational registry data models - see RelationalRegistryDM - However, it was decided that ease of writing queries was the primary goal of the design, and therefore it was useful to have the IVORN in as many tables as possible - so for certain queries fewer joins would be necessary. The smallint part of the composite key is generally easily generated on ingestion from the child index in its parent of the main modelled XML element for that table. -- PaulHarrison - 2014-05-23 | |||||||
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersA provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-03.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one.Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
| ||||||||
Added: | ||||||||
> > |
Late commentsSome technically late comments:
| |||||||
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and Validaters | ||||||||
Changed: | ||||||||
< < | There is currently a validator test suite created for this standard, http://docs.g-vo.org/regtapval-2014-03.tar.gz | |||||||
> > | A provisional validation suite as available at http://docs.g-vo.org/regtapval-2014-03.tar.gz | |||||||
An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those).
Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one.
Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
| ||||||||
Changed: | ||||||||
< < | Thanks for the useful comments. I hope they're all considered in volute rev. 2497. On the question of precedence of xpaths, I'm now | |||||||
> > | Thanks for the useful comments. I hope they're all considered in volute rev. 2497. On the question of precedence of xpaths, I'm now declaring XML schema xpaths as normative and promise Errata in case contradictions go unnoticed. -- MarkusDemleitner - 2014-04-01 | |||||||
Deleted: | ||||||||
< < | declaring XML schema xpaths as normative and promise Errata in case contradictions go unnoticed. -- MarkusDemleitner - 2014-04-01 | |||||||
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersThere is currently a validator test suite created for this standard, http://docs.g-vo.org/regtapval-2014-03.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). | ||||||||
Added: | ||||||||
> > | Another implementation (out of date with respect to XPath/utypes and some DB fields) is available as a TAP service at http://ia2-vo.oats.inaf.it:8080/registry . Even if not fully compliant, the IA2 team (VObs.it) plans to update it to the REC version and fix some other compliance problems to keep it at least as an independent mirror of the GAVO service. This implementation uses both a programming language (Java) and RDBMS (MySQL) different from the GAVO one. | |||||||
Comments from the communityComments from MarkTaylorGreat job Markus et al. A few minor comments:
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersThere is currently a validator test suite created for this standard, http://docs.g-vo.org/regtapval-2014-03.tar.gz | ||||||||
Changed: | ||||||||
< < | An implementation of this is available on the TAP services at | |||||||
> > | An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). | |||||||
Deleted: | ||||||||
< < | http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). | |||||||
Deleted: | ||||||||
< < | ||||||||
Comments from the community | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Comments from MarkTaylor | ||||||||
Changed: | ||||||||
< < | Great job Markus et al. | |||||||
> > | Great job Markus et al. A few minor comments: | |||||||
Deleted: | ||||||||
< < | A few minor comments: | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Deleted: | ||||||||
< < | ||||||||
-- MarkTaylor - 2014-03-27 | ||||||||
Added: | ||||||||
> > | Thanks for the useful comments. I hope they're all considered in volute rev. 2497. On the question of precedence of xpaths, I'm now declaring XML schema xpaths as normative and promise Errata in case contradictions go unnoticed. -- MarkusDemleitner - 2014-04-01 | |||||||
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersThere is currently a validator test suite created for this standard, http://docs.g-vo.org/regtapval-2014-03.tar.gz An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those).Comments from the community | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > | Comments from MarkTaylorGreat job Markus et al. A few minor comments:
| |||||||
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and Validaters | ||||||||
Changed: | ||||||||
< < | There is currently a validator test suite created for this standard, http://docs.g-vo.org/regtapval-2014-02.tar.gz | |||||||
> > | There is currently a validator test suite created for this standard, http://docs.g-vo.org/regtapval-2014-03.tar.gz | |||||||
Added: | ||||||||
> > | An implementation of this is available on the TAP services at http://dc.g-vo.org/tap and http://gavo.aip.de/tap (the basic underlying software is identical for those). | |||||||
Comments from the community | ||||||||
Deleted: | ||||||||
< < | ||||||||
Comments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
Request for Comment: RegTAP v1.0This document serves as the RFC center for the Proposed Recommendation entitled "Registry Relational Schema, Version 1.0". The version reviewed during the RFC can be found at http://www.ivoa.net/documents/RegTAP/20140227/index.html. RFC Review period: March 14, 2014 - April 15, 2014TCG Review period: Exec Approved for REC: To add a comment on 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 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 Resource Registry mailing list, registry@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document Notes on Implementations and ValidatersThere is currently a validator test suite created for this standard, http://docs.g-vo.org/regtapval-2014-02.tar.gzComments from the communityComments from TCG members during the TCG Review Period:WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham )Applications Working Group ( _Mark Taylor, Pierre Fernique )Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick )Data Model Working Group ( _Jesus Salgado, Omar Laurino )Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff )Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)Semantics Working Group ( _Norman Gray, Mireille Louys)Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Rick Wagner )Time Domain Interest Group ( _Matthew Graham, John Swinbank )Standards and Processes Committee ( Françoise Genova )<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |