<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" 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!
<br>
</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:<br>
</p>
<p></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">
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">SIA</a>] and Simple Cone Search [<a href="https://www.ivoa.net/documents/VODataService/20101202/REC-VODataService-1.1-20101202.html#SCS">SCS</a>].
</dd></dl>
</blockquote>
<p></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" class="x_OWAAutoLink" id="LPlnk200929">https://www.ivoa.net/documents/VODataService/20101202/REC-VODataService-1.1-20101202.html#model</a></p>
<p><br>
</p>
<p>***<br>
</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!<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Cheers,</p>
<p>--Theresa<br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><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</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">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?">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<br>
</div>
</span></font>
</body>
</html>