TWiki
>
IVOA Web
>
IvoaResReg
>
RI11RFC
(revision 10) (raw view)
Edit
Attach
---+ Registry Interfaces 1.1 Proposed Recommendation: Request for Comments Public discusion page for the IVOA Registry Interfaces 1.1 Proposed Recommendation The latest version of the RI 1.1 specification can be found at: <a target="_self" href="http://www.ivoa.net/documents/RegistryInterface/20170201/">http://www.ivoa.net/documents/RegistryInterface/20170201/</a> In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your TWiki.WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Discussion about any of the comments or responses should be conducted on the __registry__ mailing list, [[mailto: registry@ivoa.net][registry@ivoa.net]] . However, please be sure to enter your initial comments here for full consideration in any future revisions of this document. ---++ Comments from the IVOA Community and TCG members during RFC period: 2017-02-07 - 2017-03-07 ---+++ Comments from Mark Taylor Document looks clear, and I support moving to a version that drops the SOAP-based client interfaces. I fixed some extremely minor typos in volute. One question (just curiosity really): what's the reason for introducing the new requirement for time granularity at the level of seconds that's mentioned in section 2.7? -- IVOA.MarkTaylor - 2017-03-08 * Without this requirement, a client has to retrieve an Identify response from a service to figure out what arguments it can pass. Everyone had implemented seconds granularity anyway, so it seemed reasonable to do away with one "free parameter". -- IVOA.MarkusDemleitner - 2017-04-04 ---++ <br />Comments from the TCG during the TCG Review Period ---++++ TCG Chair & Vice Chair _(Matthew Graham, Pat Dowler)_ ---++++ Applications Working Group _(Pierre Fernique, Tom Donaldson)_ Two minor typos detected: * Page 10 "regiestries" -> registries * page 15 - "theListRecords" -> missing space after "the" Apps approves this document.<em> -- IVOA.PierreFernique - 2017-05-10</em> ---++++ Data Access Layer Working Group _(Francois Bonnarel, Marco Molinaro)_ ---++++ Data Model Working Group _(Mark Cresitello-Dittmar, Laurent Michel)_ ---++++ Grid & Web Services Working Group _(Brian Major, Giuliano Taffoni)_ Since VOSI 1.1 is also near the end of RFC, could we update the reference to the 1.1 version instead of 1.0? It won't put any more burden on this spec than the 1.0 version does. I think, in the capabilities example in Appendix C, it should be maxReturnRecords rather than maxRecords. (See: VOResource http://ivoa.net/documents/VOResource/20170425/PR-VOResource-1.1-20170425.html) Also in the capabilities example: I'm not sure what the extensionSearchSupport element is... I see that it's in the SOAP based schema, but I don't see it in VOResource. -- IVOA.BrianMajor - 2017-05-03 I support the change to VOSI 1.1 since it won't affect existing implementations of this spec and will change it in the RI1.1 document text absent strong objections. In the capabilities examples, "maxRecords" is the element in the vg:Registry extension as defined in v1.0 of Registry Interfaces. I agree from the VOResource spec that MaxReturnRecords would be more appropriate, but we are intending to keep this a backward-compatible v1.x document. Given that maxRecords is used in client and inter-registry harvesting processes, changing this element could break a good deal of infrastructure. If we move to a version 2.0 of this document in the future, I would like to incorporate this change, but not in 1.1. <span style="background-color: transparent;">The extensionSearchSupport element is a deprecated tag from RI 1.0 intended to report whether the SOAP search capability of a searchable registry would handle only core VOResource elements or extension metadata, like capabilities. Since we are dropping the SOAP search capability but remaining a 1.x version document, it is deprecated but not removed. This can also be changed in 2.0.</span> -- IVOA.TheresaDower - 2017-05-10 Okay, thanks Theresa. With the VOSI 1.1 change above I approve this document. -- IVOA.BrianMajor - 2017-05-10 ---++++ Registry Working Group _(Markus Demleitner, Theresa Dower)_ Registry, unsurprisingly, approves. -- IVOA.MarkusDemleitner - 2017-04-04 ---++++ Semantics Working Group _(Mireille Louys, Alberto Accomazzi)_ ---++++ Education Interest Group _(Massimo Ramella, Sudhanshu Barway)_ ---++++ Time Domain Interest Group _(John Swinbank, Mike Fitzpatrick)_ ---++++ Data Curation & Preservation Interest Group _(Francoise Genova)_ ---++++ Operations Interest Group _(Tom McGlynn, Mark Taylor)_
Edit
|
Attach
|
Watch
|
P
rint version
|
H
istory
:
r20
|
r12
<
r11
<
r10
<
r9
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r10 - 2017-05-10
-
PierreFernique
IVOA
Log in
or
Register
IVOA.net
Wiki Home
WebChanges
WebTopicList
WebStatistics
Twiki Meta & Help
IVOA
Know
Main
Sandbox
TWiki
TWiki intro
TWiki tutorial
User registration
Notify me
Working Groups
Applications
Data Access Layer
Data Model
Grid & Web Services
Registry
Semantics
Interest Groups
Data Curation
Education
Knowledge Discovery
Operations
Radio Astronomy
Solar System
Theory
Time Domain
Committees
Stds&Procs
www.ivoa.net
Documents
Events
Members
XML Schema
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback