[Volute] r3542 - in trunk/projects: ivoapub/ivoatex registry/RegistryInterface

Volute commit messages volutecommits at g-vo.org
Wed Oct 26 18:05:18 CEST 2016


Author: dower
Date: Mon Sep 12 21:36:37 2016
New Revision: 3542

Log:
RegistryInterface: added support for auxiliary RegTAP capabilities, added note defining aux capabilities to bibliography

Modified:
   trunk/projects/ivoapub/ivoatex/ivoabib.bib
   trunk/projects/registry/RegistryInterface/RegistryInterface.tex

Modified: trunk/projects/ivoapub/ivoatex/ivoabib.bib
==============================================================================
--- trunk/projects/ivoapub/ivoatex/ivoabib.bib	Mon Sep 12 14:49:01 2016	(r3541)
+++ trunk/projects/ivoapub/ivoatex/ivoabib.bib	Mon Sep 12 21:36:37 2016	(r3542)
@@ -774,6 +774,16 @@
 	title = {{IVOA} Architecture},
 	version = {1.0},
 	howpublished = {{IVOA Note}}}
+	
+ at misc{note:DataCollect,
+	year=2016,
+	month=jan,
+	url={{http://www.ivoa.net/documents/Notes/DataCollect}},
+	author={Markus Demleitner, Mark Taylor},
+	editor = {Markus Demleitner},
+	title = {{IVOA}Discovering Data Collections Within Services},
+	version = {1.0},
+	howpublished = {{IVOA Note}}}
 
 @Misc{note:utypeusage,
   author =       {Matthew Graham and Markus Demleitner and Patrick Dowler and Pierre Fernique and Omar Laurino and Gerard Lemson and Mireille Louys and Jesus Salgado},

Modified: trunk/projects/registry/RegistryInterface/RegistryInterface.tex
==============================================================================
--- trunk/projects/registry/RegistryInterface/RegistryInterface.tex	Mon Sep 12 14:49:01 2016	(r3541)
+++ trunk/projects/registry/RegistryInterface/RegistryInterface.tex	Mon Sep 12 21:36:37 2016	(r3542)
@@ -765,7 +765,7 @@
 general registry maintenance with client interfaces to the registry,
 which were found to be in much more need of experimentation.  For a
 discussion of the history of client interfaces in the VO, see
-\citet{paper:regclient}.
+\citep{paper:regclient}.
 
 One second-generation standard search interface to the VO Registry that
 has progressed to become an IVOA recommendation is RegTAP
@@ -774,13 +774,12 @@
 RegTAP services have been made available from several registry providers listed in the Registry of Registries.
 
 An earlier search capability, RISearch, is not removed
-from the schema in order to allow operators to register RI1 registries
-without having to support different versions of the VORegistry schema.
-Also, the type may be useful when other registry search interfaces want to
-define capability types of their own.
+from the schema in order to allow operators to register RI1 registries without having to support different versions of the VORegistry schema.
+Also, the type may be useful when other registry search interfaces want to define capability types of their own.
 
-The concept of a searchable registry versus a publishing one as recognized by the Registry of Registries therefore now encompasses any registry implementing an IVOA standard programmatic interface beyond the interface for OAI harvesting. That is, any vr:Registry resource with an additional capability referencing an IVOA standard and a ParamHTTP interface element to that capability.
+Registry TAP Service capabilities and other additional search capabilities other than the deprecated but allowed RISearch are to be included in the registry self-identification record as an auxiliary capability as described in the IVOA note "Discovering Data Collections Within Services" \citep{note:DataCollect}, with the main capability being the OAI-PMH harvester service endpoint.
 
+The concept of a searchable registry versus a publishing one as recognized by the Registry of Registries therefore now encompasses any registry implementing an IVOA standard programmatic interface beyond the interface for OAI harvesting. That is, any Registry resource with an additional capability or auxiliary capability referencing an IVOA standard and a ParamHTTP interface element to that capability.
 
 \appendix
 
@@ -804,8 +803,7 @@
 in the Registry.  It is unchanged from version 1.0 of this specification
 and therefore does not change its version.
 
-Note that standards defining search interfaces may specify alternative
-or complementary methods of registering the services defined by them.
+Note that standards defining search interfaces may specify alternative or complementary methods of registering the services defined by them, and that auxiliary capabilities for these search capabilities may be listed within the registry record.
 
 \lstinputlisting[language=XML]{VORegistry-1.0.xsd}
 
@@ -823,7 +821,7 @@
 
 \begin{itemize}
 
-\item Corrected reference to OAI-PMH spec in registry interface description to v2.0, which has already been the standard.
+\item Corrected reference to OAI-PMH spec in registry interface description to v2.0.
 
 \item Added requirement for OAI-PMH interface to support seconds granularity, optional in the OAI-PMH 2.0 standard itself. {}
 
@@ -836,6 +834,8 @@
 
 \item Added a requirement to provide VOSI endpoints.
 
+\item Added support for auxiliary Registry TAP Service search interfaces
+
 \item Clarified that the requirement to keep deleted records for six
 months only applies to the transient case; also discouraging registries
 with no support of deleted records.


More information about the Volutecommits mailing list