TWiki
>
IVOA Web
>
IvoaResReg
>
RegistryInterface
>
RegistryInterfacePre10Discussion
>
GetRegistries
(revision 3) (raw view)
Edit
Attach
---+ Registry Interface Working Draft Discussion Topic ---++ Should we drop getRegistries() or redefine it? As it is currently define, ==<nop>getRegistries()== returns all registries that the registry knows about. Because you can get this information via a simple ADQL-based search, there is a suggestion to drop it from the standard. However, there is a related piece of information that is not strictly available, and that is the list of the registries that the searchable registry harvests from. Since this is not necessarily the same as "all the registries it knows about", there is no other way to get this information. So as an alternative to dropping ==<nop>getRegistries()==, we would make it a part of the harvester interface (or searchable interface; see HarvesterInterface discussion) and have it return a listing of the registries that it harvests from. This would allow other registries to discover where it they should harvest from if they want the same contents. One group that is interested in harvesting VO resource records is the NASA ADS. It wants to incorporate this information into its abstract database. They have expressed an interest in discovering harvestable registries using OAI only. This would presumably be done with Sets. So as a follow-up question, should we define a special set that returns the same thing as our revised ==<nop>getRegistries()==? --- _If you have an opinion, question, or comment about this topic, feel free to append your discussion below. Be sure to indicate your name as the author._ I support redefining getRegistries(). In addition, I think we should look at ways to incorporate this functionality into the OAI interface as well using sets, but I think that it needs some prototyping before we attempt to include it; let's not target the OAI part for RI 1.0. -- IVOA.RayPlante - 30 Mar 2005 --- I tend to like the idea of dropping getRegistries() now. I think it might be easier just having our OAI listRecords (and Sets if we decide to support Sets) return vg:Registry types that it knows about. I think clients might like the idea as well that all they need to call is one OAI method such as <nop>ListRecords and will automatically get Registry types. -- IVOA.KevinBenson - 31 Mar 2005 --- <br><br><br> <!-- * Set ALLOWTOPICRENAME = %MAINWEB%.TWikiAdminGroup -->
Edit
|
Attach
|
Watch
|
P
rint version
|
H
istory
:
r5
<
r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r3 - 2005-03-31
-
RayPlante
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
Distributed Services & Protocols
Registry
Semantics
Interest Groups
Data Curation
Education
Knowledge Discovery
High Energy
Operations
Radio Astronomy
Solar System
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