<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<blockquote style="margin-left: 0.8ex; padding-left: 1ex; border-left: 3px solid rgb(200, 200, 200);">
<div class="elementToProof" style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Perhaps, before the major protagonists retire, we should write a<br>
history of the first 25 years of the VO Registry and dig up what<br>
memories and documents there still are? I'd say we certainly could<br>
collect a fair number of lessons learnt...</div>
</blockquote>
<div class="elementToProof" style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I think this is an excellent idea to add to the Registry road map. Not likely for the Spring interop but for the not too distant future. In fact, I think it might be a good idea more broadly, and the 25 year mark is as good an excuse as any. </div>
<div class="elementToProof" style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature" class="elementToProof" style="color: inherit;">
<div style="text-align: left; font-family: Helvetica; font-size: 12px; color: rgb(0, 0, 0);">
- - - - </div>
<div style="text-align: left; font-family: Helvetica; font-size: 12px; color: rgb(0, 0, 0);">
Dr. Tess Jaffe (she/her)</div>
<div style="text-align: left; font-family: Helvetica; font-size: 12px; color: rgb(0, 0, 0);">
NASA Goddard Space Flight Center, Greenbelt, MD, USA</div>
<div style="text-align: left; font-family: Helvetica; font-size: 12px; color: rgb(0, 0, 0);">
<br>
</div>
<span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"><br>
</span></div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> registry <registry-bounces@ivoa.net> on behalf of Markus Demleitner via registry <registry@ivoa.net><br>
<b>Sent:</b> Tuesday, November 26, 2024 2:07 AM<br>
<b>To:</b> WG Registry IVOA <registry@ivoa.net><br>
<b>Subject:</b> [EXTERNAL] [BULK] Re: VODataService 1.3: productTypeServed</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">CAUTION: This email originated from outside of NASA. Please take care when clicking links or opening attachments. Use the "Report Message" button to report suspicious messages to the NASA SOC.<br>
<br>
<br>
<br>
<br>
Hi Paul,<br>
<br>
On Mon, Nov 25, 2024 at 12:00:35PM +0000, Paul Harrison wrote:<br>
> However, this (along with the 'stay of execution’ on<br>
> DataCollection) does remind me that is was not originally meant to<br>
> be this way. The original design of the registry schema did have as<br>
<br>
Perhaps, before the major protagonists retire, we should write a<br>
history of the first 25 years of the VO Registry and dig up what<br>
memories and documents there still are? I'd say we certainly could<br>
collect a fair number of lessons learnt...<br>
<br>
> If this normalisation had been done in the early days as new<br>
> DataServices were created, then the registry name for things like<br>
> DataCollections, Instruments, Facilities would have been the name<br>
<br>
While I do agree that data and services need to be separated -- and I<br>
think DDC <<a href="https://ivoa.net/documents/discovercollections/">https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fivoa.net%2Fdocuments%2Fdiscovercollections%2F&data=05%7C02%7Ctess.jaffe%40nasa.gov%7Cf7a688c2a5904de2a9ab08dd0df4f5b6%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638682067938873765%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=jgmFoNxAtC5B764I5Kxw3%2FR1YcLCfbVY599d049awkw%3D&reserved=0</a>>
and the<br>
new VODataService 1.2 types DataResource and CatalogResource let<br>
people do this without breaking much --, I think for instruments and<br>
facilities this has been a lost cause; we still don't have enough<br>
buy-in or even tooling to make the operators of facilities and<br>
instruments register themselves, and we don't have the staff to<br>
curate such registrations from within the VO.<br>
<br>
I give you it's a charming idea, though. With the caveat that we'd<br>
have to introduce some persistence tech (presumably an ivoa-managed<br>
publishing registry of instruments and facilities) in order to make<br>
that properly work. But never mind: This is now clearly outside of<br>
the Registry.<br>
<br>
> While it might be too late to save DataCollection, and in any case<br>
> if the actual number of registrations has become vanishingly small,<br>
> perhaps rather ineffectual - it should be remembered that the<br>
> majority registry entries are dominated by rather a small number of<br>
> of providers so a change of direction is not entirely unfeasible.<br>
<br>
It's certainly not, and it's been going on for a long time already.<br>
Still, VizieR will most definitely not create an extra 25'000 records<br>
to separate their cone searches from their data collection records.<br>
But if there could be a single cone search service for all of<br>
VizieR's tables and we could have that as an auxiliary capability,<br>
I'd like that a lot for so many reasons. But that needs work on<br>
both SCS and a minor registry extension for auxiliary capabilities,<br>
and hence it's probably not for VODataService 1.2.<br>
<br>
Thanks,<br>
<br>
Markus<br>
<br>
</div>
</span></font></div>
</body>
</html>