[Volute] r3659 - trunk/projects/registry/regtap

Volute commit messages volutecommits at g-vo.org
Fri Oct 21 14:05:20 CEST 2016


Author: msdemlei
Date: Fri Oct 21 14:05:19 2016
New Revision: 3659

Log:
RegTAP: adding a StandardsRegExt resource record.

Added:
   trunk/projects/registry/regtap/RegTAP.vor
      - copied, changed from r3658, trunk/projects/ivoapub/ivoatex/stdrec-template.xml
Modified:
   trunk/projects/registry/regtap/schema.png

Copied and modified: trunk/projects/registry/regtap/RegTAP.vor (from r3658, trunk/projects/ivoapub/ivoatex/stdrec-template.xml)
==============================================================================
--- trunk/projects/ivoapub/ivoatex/stdrec-template.xml	Fri Oct 21 10:30:09 2016	(r3658, copy source)
+++ trunk/projects/registry/regtap/RegTAP.vor	Fri Oct 21 14:05:19 2016	(r3659)
@@ -1,20 +1,7 @@
-<!-- A template for a registry record for a standard.
-
-See http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord
-for the why and what of this.
-
-It is hoped that the embedded comments will guide you to producing
-a correct and semantically useful registry record.
-
-You will need to change everything marked with ####
--->
-
-<!-- initially, set created and updated to (roughly) UTC of now.
-change updated whenever you re-upload this record. -->
 <ri:Resource 
 	xsi:type="vstd:Standard" 
-	created="####" 
-	updated="####"
+	created="2016-10-21T08:34:00Z" 
+	updated="2016-10-21T08:34:00Z" 
 	status="active"
 	xmlns:vr="http://www.ivoa.net/xml/VOResource/v1.0" 
 	xmlns:vstd="http://www.ivoa.net/xml/StandardsRegExt/v1.0" 
@@ -27,66 +14,63 @@
 	http://www.ivoa.net/xml/VOResource/v1.0
 		http://www.ivoa.net/xml/VOResource/v1.0">
 
-  <title>####</title> <!-- title as given on the standard's title page -->
-	<!-- put the "short name" of your standard after std/: -->
-  <identifier>ivo://ivoa.net/std/####</identifier> 
+  <title>IVOA Registry Relational Schema</title>
+  <identifier>ivo://ivoa.net/std/RegTAP</identifier> 
   <curation>
     <publisher>IVOA</publisher>
 
-    <!-- author name(s), preferably in Last, I. form; one creator
-    element per author -->
     <creator>
-      <name>####</name>
+      <name>Demleitner, M.</name>
+    </creator>
+    <creator>
+      <name>Harrison, P.</name>
+    </creator>
+    <creator>
+      <name>Molinaro, M.</name>
+    </creator>
+    <creator>
+      <name>Greene, G.</name>
     </creator>
     <creator>
-      <name>####</name>
+      <name>Dower, T.</name>
+    </creator>
+    <creator>
+      <name>Perdikeas, M.</name>
     </creator>
 
-		<!-- this should be the date of the last recommendation -->
-    <date role="update">####</date>
-    <version>####</version> <!-- the document version -->
+    <date role="update">2014-12-04</date>
+    <version>1.0</version>
     <contact>
-      <name>####</name> <!-- typcially, the name of the main WG/IG-->
-      <email>####</email> <!-- typically, the mailing list address -->
+      <name>IVOA Registry WG</name>
+      <email>registry at ivoa.net</email>
     </contact>
   </curation>
   <content>
     <subject>Virtual observatory</subject>
-    <!-- you can give further keywords, one per subject element;
-    use the IVOA thesaurus if possible:
-
-    http://www.ivoa.net/rdf/Vocabularies/vocabularies-20091007/IVOAT/IVOAT.html
-    -->
-    <subject>####</subject>
+    <subject>Databasesubject>
 
     <description>
-    	#### (your abstract; no markup here, please)
+Registries provide a mechanism with which VO applications can discover and
+select resources - first and foremost data and services - that are relevant for
+a particular scientific problem. This specification defines an interface for
+searching this resource metadata based on the IVOA's TAP protocol. It specifies
+a set of tables that comprise a useful subset of the information contained in
+the registry records, as well as the table's data content in terms of the XML
+VOResource data model. The general design of the system is geared towards
+allowing easy authoring of queries.
     </description>
-    <referenceURL>#### (the generic landing page URL, e.g.
-    	http://ivoa.net/documents/SAMP/)</referenceURL>
+    <referenceURL>http://www.ivoa.net/documents/RegTAP</referenceURL>
     <type>Other</type>
   	<contentLevel>Research</contentLevel>
   </content>
 
-  <!-- Version(s) of the standard that should be used.  In general,
-  	you'll only have exactly one endorsedVersion with status="rec",
-  	but situations are imaginable where you have multiple endorsed
-  	versions, perhaps even with non-rec status (though you should probably
-  	ask the TCG before going there). -->
-  <endorsedVersion status="rec">####</endorsedVersion>
-
-	<!-- If your standard provides schema file(s), list their canonical
-		URL(s) here.  Only list the most recent versions. Otherwise, just
-		delete this element. -->
-	<schema>####</schema>
-
-	<!-- You can furthermore have as many key-value pairs as you want.
-		Service standard authors will need this to comply with Identifier 2.0's
-		recommendation for standardId 
-		(http://www.ivoa.net/documents/IVOAIdentifiers/20150709/PR-Identifiers-2.0-20150709.html#tth_sEc4.2) -->
+  <endorsedVersion status="rec">1.0</endorsedVersion>
+
 	<key>
-		<name>####</name>
-		<description>####
+		<name>1.0</name>
+		<description>The data model for the tables making up the relational 
+		registriy in version 1.0.  This key is used to locate TAP services
+		implementing RR in TAPRegExt dataModel elements.
 		</description>
 	</key>
 

Modified: trunk/projects/registry/regtap/schema.png
==============================================================================
Binary file (source and/or target). No diff available.


More information about the Volutecommits mailing list