<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear DALers,<div class=""><br class=""></div><div class="">The SODA standard §4.3 states:</div><div class="">"Resources in the IVOA Registry may include SODA capabilities. However,
in order to
use such services, clients require prior knowledge of suitable
identifiers that are usable with a registered SODA standard service. As a result,
finding and
using a SODA service via the registry is not expected to be a common
usage pattern.”</div><div class=""><br class=""></div><div class="">Because of that many data providers might not register their SODA-capable services.</div><div class=""><br class=""></div><div class="">How can then a user search for cutout services (and not just a mere SIA without cutout)?</div><div class=""><br class=""></div><div class="">I was expecting, for example, that a SIA returning a DataLink that supports SODA would be declared as such in the registry,</div><div class="">that is, listing in its SIA capabilities both DataLink and SODA (using the ivo://ivoa.net/std/SODA#sync−1.0 standard ID (or async) <tt class="">)</tt>.</div><div class=""><br class=""></div><div class="">I tried to query for SODA in the registry, but I could not find any service supporting SODA (but my ability to query the registry might be not that advanced!).</div><div class=""><br class=""></div><div class="">Would not be better to remove that sentence in §4.3 and encourage, if not even require, the data providers to include the SODA standard ID in their SODA-capable services?</div><div class=""><br class=""></div><div class="">Many thanks,</div><div class="">Alberto</div><div class=""><br class=""></div><div class=""> </div></body></html>