(r1) SimpleDALRegExtV12RFC < IVOA

IVOA Web>IvoaTCG>SimpleDALRegExtV12RFC (revision 1) (raw view)~~EditAttach~~
---+ <span style="color: #0000ff;"><span style="text-decoration: underline;">SimpleDALRegExt1.2</span></span> Proposed Recommendation: Request for Comments

%TOC{depth="2"}%

<span style="background-color: transparent;">The latest version of <span style="color: #0000ff;"><span style="text-decoration: underline;">SimpleDALRegExt 1.2</span></span></span><span style="background-color: transparent;"> can be found at:</span>
   * https://ivoa.net/documents/SimpleDALRegExt/20201216/index.html
While future versions may be migrated elsewhere, VODataService 1.2 is managed by the legacy volute repository at: http://volute.g-vo.org/svn/trunk/projects/registry/SimpleDALRegExt/
---+++ Summary

SimpleDALRegExt defines a group of registry extensions for describing related "Simple" DAL services: Cone, Image, Spectra, etc. Occasional tweaks to vocabularies and incremental changes to the services' own standards are tracked here to keep potential registry search results in line with actual service capabilities, and to show connections between resources in new ways: in this case, adding auxiliary capability descriptions (see below.)
---+++ Changes since 1.1

Most of the document is unmodified. Some vocabulary cruft has been removed and tested with searches across all current registries to assure backward compatibility.<br /><br />There are three changes which should be reviewed:
   * Section 4, the auxiliary capabilities. Introducing these has been the original motivation for building SRE 1.2.
   * SSAP services can declare which reference frames they support in POS. So far, there has been a list of those in the schema. We now point to a vocabulary developed in the run-up to MCT, <a rel="noopener noreferrer" target="_blank" href="http://www.ivoa.net/rdf/refframe/">http://www.ivoa.net/rdf/refframe/</a><span style="background-color: transparent;">. Accepting this as REC would also make this vocabulary accepted.</span>
   * SSAP services can now declare a productType (sect. 3.3.3). This is to support the growing number of SSAP services publishing time series, but the vocabulary is also intended for re-use in Obscore (from where it comes). Accepting this as REC would also make the vocabulary <a rel="noopener noreferrer" target="_blank" href="http://www.ivoa.net/rdf/product-type">http://www.ivoa.net/rdf/product-type</a><span style="background-color: transparent;"> accepted.</span>
The refframe vocabulary, <a rel="noopener noreferrer" target="_blank" href="http://www.ivoa.net/rdf/refframe/">http://www.ivoa.net/rdf/refframe/</a>, includes a few legacy terms from VOTable COOSYS the intended meaning of which is now uncertain (barycentric, geo_app). We should find some solution for them as part of this review.

<span style="font-size: x-small;"> </span>
---+++ <span style="background-color: transparent;">Reference Interoperable Implementations</span>

The auxiliary capabilities for the S-Protocols are a consequence of the Endorsed Note on discovering data collections. Compared to TAP auxiliary capabilities, they have not been used much yet (there are ivo://org.gavo.dc/lensunion/q/im and ivo://org.gavo.dc/hppunion/q/im, though). Hence, to our knowledge there is no client takeup of them. Consider this change editorial in nature; the standards identifiers from discovering data collections simply needed to be mentioned in this spec.<br /><br />Similarly, using a vocabulary for the reference frames rather than an in-schema list is just intended to cut down on the number of lists of reference frames in the various standards. It has no operational implications (even less so since to date few services or clients actually offer different reference systems in SSAP queries).<br /><br />The declaration of product type, on the other hand, has operational consequences; several services in the VO already declare their product type; try

<literal>SELECT ivoid, res_title, detail_value<br></br><br></br>FROM rr.resource<br></br><br></br>NATURAL JOIN rr.res_detail<br></br><br></br>WHERE detail_xpath='/capability/productType'</literal>

on a RegTAP service. On the client side, version 3.15_3 (beta) of the spectral analysis programme SPLAT uses this to let users select time series services (as opposed to spectral services).

---++ Comments from the IVOA Community during RFC/TCG review period: 2021-03-01 to 2021-04-23

The comments from the TCG members during the RFC/TCG review should be included in the next section.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document

   * Sample comment by TWiki.WikiName 
      * Response (by TWiki.WikiName)

---
---

<span style="background-color: #f6f6f6; color: #630000; font-size: 18.85px;">Comments from TCG member during the RFC/TCG Review Period: 2021-03-01 to 2021-04-23</span>

WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

---+++ TCG Chair & Vice Chair
---+++ [[IvoaApplications][Applications Working Group]]
---+++ [[IvoaDAL][Data Access Layer Working Group]]
---+++ [[IvoaDataModel][Data Model Working Group]]

---+++ [[IvoaGridAndWebServices][Grid & Web Services Working Group]]

---+++ [[IvoaResReg][Registry Working Group]]

---+++ [[IvoaSemantics][Semantics Working Group]]

---+++ [[IvoaDCP][Data Curation & Preservation Interest Group]]

---+++ [[IvoaTheory][Education Interest Group]]

---+++ [[IvoaKDD][Knowledge Discovery Interest Group]]

---+++ [[IvoaSS][Solar System Interest Group]]

---+++ [[IvoaTheory][Theory Interest Group]]

---+++ [[IvoaVOEvent][Time Domain Interest Group]]

---+++ [[IvoaOps][Operations]]

Sec 1:<br />  Some of the external standards referenced are quite old,<br />  e.g. VOResource 1.03. Should these be updated?<br /><br />  Related: "Unlike with the previously mentioned specifications,<br />  this specification may apply to later versions of the RI and<br />  VOSI standards." I don't really understand that - does it mean<br />  you *have* to work with e.g. VOResource 1.03 and not later versions?<br /><br />  "relevence"/"relevent" -&gt; "relevance"/"relevant"<br /><br />Sec 2:<br />  Return of the evil quotes! Reading the HTML version I see e.g.<br />  (cut'n'pasted from the browser):<br /><br />   - the role attribute must be set to ßtd"<br /><br />   - their values should be "GET" and äpplication/x-votable+xml"<br /><br />Sec 3.1.2:<br />  "canoncical" -&gt; "canonical"<br /><br />Sec 3.1.3:<br />  "at least on matched record" -&gt; "at least one matched record"<br /><br />Sec 3.1.4<br />  I don't understand the business about specifying the catalogue<br />  in the test query, since this term doesn't appear in SCS itself.<br />  No doubt this is some hangover from some long-standing wrinkles<br />  in SCS which we don't want to mess with now, but maybe a couple<br />  of words of explanation would be in order?<br /><br />Sec 3.3.3:<br />  In the productType Meaning section, it says<br /><br />     "with each element declaring one of <a rel="noopener noreferrer" target="_blank" href="http://www.ivoa.net/product-type">http://www.ivoa.net/product-type</a>"<br /><br />  That's the wrong URL, and the text is a bit terse.<br />  Change to something like:<br /><br />     "with each element declaring terms taken from the vocabulary<br />       <a rel="noopener noreferrer" target="_blank" href="http://www.ivoa.net/rdf/product-type%22?">http://www.ivoa.net/rdf/product-type"?</a>

--Notes transcribed from IVOA.MarkTaylor - 2021-03-12
---+++ [[IvoaStdsDocsProc][Standards and Processes Committee]]

---++ TCG Vote : Vote_start_date - Vote_end_date

If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.

| Group | Yes | No | Abstain | Comments |
| TCG | | | | |
| Apps | | | | |
| DAL | | | | |
| DM | | | | |
| GWS | | | | |
| Registry | | | | |
| Semantics | | | | |
| DCP | | | | |
| KDIG | | | | |
| SSIG | | | | |
| Theory | | | | |
| TD | | | | |
| Ops | | | | |
| !StdProc | | | | |
Topic revision: r1 - 2021-03-15 - TheresaDower
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
Interest Groups
Committees
Stds&Procs
www.ivoa.net
Documents
Events
Members
XML Schema