<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>Hi Carlos, Theresa,</div><div><br></div><div>Probably DataService is the best match for the FPS. In the Euro-VO Registry you can import directly a free XML created by you, or most user friendly, start with the one created by a form assistant as a template. You can access those there, with a dedicated form for DataService. Please let us know how it looks to you, we would be glad to help with the registration.</div><div><br></div><div><img src="cid:39733b53b077fc4f3d6a8f62e0a59531b2309ef9@zimbra" data-mce-src="cid:39733b53b077fc4f3d6a8f62e0a59531b2309ef9@zimbra" width="517" height="237"></div><div><br></div><div>Regards,</div><div>Juan</div><div><br data-mce-bogus="1"></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Theresa Dower" <dower@stsci.edu><br><b>To: </b>"IVOA Registry" <registry@ivoa.net><br><b>Sent: </b>Monday, October 26, 2020 8:14:58 PM<br><b>Subject: </b>Re: not standard param service</div><div><br></div><div data-marker="__QUOTED_TEXT__"><div dir="ltr"><div dir="ltr" style="font-size: 12pt; color: #000000; font-family: 'calibri' , 'helvetica' , sans-serif;" data-mce-style="font-size: 12pt; color: #000000; font-family: 'calibri' , 'helvetica' , sans-serif;"><p>Carlos,</p><p><br></p><p>Yes, registering web services that do not exactly match VO standard API descriptions is possible!</p><p>One may simply register them as a base type of service that we derive ConeSearch, SIA, etc from, generally DataService or CatalogService. Custom parameters can be defined within a ParamHTTP interface element in the service capabilities. In this case there's just no "standardID" capability/interface.</p><p><br></p><p>From the VODataService 1.1 spec, the difference, fundamentally, is:</p><p><br></p><blockquote><dl><dt><code>vs:DataService</code></dt><dd>Inheriting from <code>vr:Service</code>, this type is for services that access astronomical data. It adds the ability to describe the data's <a href="https://www.ivoa.net/documents/VODataService/20101202/REC-VODataService-1.1-20101202.html#d:coverage" target="_blank" rel="nofollow noopener noreferrer" data-mce-href="https://www.ivoa.net/documents/VODataService/20101202/REC-VODataService-1.1-20101202.html#d:coverage"> coverage</a> of the sky, frequency, and time.</dd><dt><code>vs:CatalogService</code></dt><dd>Inheriting from <code>vs:DataService</code>, this type specifically refers to a service that accesses tabular data. In addition to the coverage information, this type adds the ability to describe the tables and their columns. This is intended for describing services that support the "simple" IVOA data access layer protocols such as Simple Image Access [<a href="https://www.ivoa.net/documents/VODataService/20101202/REC-VODataService-1.1-20101202.html#SIA" target="_blank" rel="nofollow noopener noreferrer" data-mce-href="https://www.ivoa.net/documents/VODataService/20101202/REC-VODataService-1.1-20101202.html#SIA">SIA</a>] and Simple Cone Search [<a href="https://www.ivoa.net/documents/VODataService/20101202/REC-VODataService-1.1-20101202.html#SCS" target="_blank" rel="nofollow noopener noreferrer" data-mce-href="https://www.ivoa.net/documents/VODataService/20101202/REC-VODataService-1.1-20101202.html#SCS">SCS</a>].</dd></dl></blockquote><p><br></p><p>In the VODataService 1.1 specification, there is a (real) example non-standard CatalogService with custom parameters spelled out: <a href="https://www.ivoa.net/documents/VODataService/20101202/REC-VODataService-1.1-20101202.html#model" target="_blank" rel="nofollow noopener noreferrer" data-mce-href="https://www.ivoa.net/documents/VODataService/20101202/REC-VODataService-1.1-20101202.html#model">https://www.ivoa.net/documents/VODataService/20101202/REC-VODataService-1.1-20101202.html#model</a></p><p><br></p><p>***</p><p><br></p><p>That said, this defines the underlying XML-based resource description itself. I don't know how individual publishing registries import these, or build them from a user interface. How Euro-VO registry management interfaces handle these is a question for other folks on this list. I hope this helps!</p><p><br></p><p><br></p><p>Cheers,</p><p>--Theresa</p></div><hr style="display: inline-block; width: 98%;" data-mce-style="display: inline-block; width: 98%;"><div dir="ltr"><span style="font-size: 11pt; color: #000000; font-family: Calibri, sans-serif;" data-mce-style="font-size: 11pt; color: #000000; font-family: Calibri, sans-serif;"><b>From:</b> registry-bounces@ivoa.net <registry-bounces@ivoa.net> on behalf of Carlos Rodrigo <crb@cab.inta-csic.es><br><b>Sent:</b> Monday, October 26, 2020 1:59:58 PM<br><b>To:</b> registry@ivoa.net<br><b>Subject:</b> not standard param service</span><div> </div></div></div><div>External Email - Use Caution<br><br>Hi<br><br>I would like to register a service in a VO registry that does not correspond to any of the typical<br>standard (ssa, sia, cs, tap...) but has a web interface accepting parameters.<br><br>The particular case is a Filter Profile Service. Its base url is:<br><br><a href="http://svo2.cab.inta-csic.es/theory/fps/fps.php?" target="_blank" rel="nofollow noopener noreferrer" data-mce-href="http://svo2.cab.inta-csic.es/theory/fps/fps.php?">http://svo2.cab.inta-csic.es/theory/fps/fps.php?</a><br><br>and accepts some parameters like:<br><br>ID (filter ID)<br>PhotCalID (Phot calibration ID)<br>Instrument<br>Facility<br>WavelengthEff_min<br>WavelengthEff_max<br><br>etc.<br><br>I would like to register it and provide the base url and a list of parameters that are accepted in<br>queries.<br><br>Is this possible? Can somebody please give me some advice about it?<br><br>Carlos</div></div><div><br></div><div data-marker="__SIG_POST__">--</div><div>Dr. Juan González-Núñez<br>ESAC Science Data Centre<br>European Space Agency (ESA) - SERCO<br><br>European Space Astronomy Centre (ESAC)<br>Camino Bajo del Castillo, S/N <br>Villanueva de la Canada,, 28691, Madrid, SPAIN<br>juan.gonzalez.nunez@esa.int | www.esa.int<br>Tel. +34 91 813 14 82 | Fax +34 91 813 13 22<br>---------------------------------------------------------------------</div></div><PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE></body></html>