Interface

class pyvo.registry.regtap.Interface(access_url, *, standard_id=None, intf_type=None, intf_role=None, capability_description=None)

Bases: object

a service interface.

These consist of an access URL, a standard id for the capability (typically the ivoid of an IVOA standard, or None for free services), an interface type (something like vs:paramhttp or vr:webbrowser) and an indication if the interface is the “standard” interface of the capability.

Such interfaces can be turned into services using the to_service method if pyvo knows how to talk to the interface.

Note that the constructor arguments are assumed to be normalised as in regtap (e.g., lowercased for the standardIDs).

Attributes Summary

service_for_standardid

Methods Summary

supports(standard_id)	returns true if we believe the interface should be able to talk standard_id.
to_service()

Attributes Documentation

service_for_standardid = {'ivo://ivoa.net/std/conesearch': <class 'pyvo.dal.scs.SCSService'>, 'ivo://ivoa.net/std/sia': <class 'pyvo.dal.sia.SIAService'>, 'ivo://ivoa.net/std/sia2': <class 'pyvo.dal.sia2.SIA2Service'>, 'ivo://ivoa.net/std/sla': <class 'pyvo.dal.sla.SLAService'>, 'ivo://ivoa.net/std/ssa': <class 'pyvo.dal.ssa.SSAService'>, 'ivo://ivoa.net/std/tap': <class 'pyvo.dal.tap.TAPService'>}

Methods Documentation

supports(standard_id)

returns true if we believe the interface should be able to talk standard_id.

At this point, we naively check if the interfaces’s standard_id has standard_id as a prefix. At this point, we cut off standard_id fragments for this purpose. This works for all current DAL standards but would, for instance, not work for VOSI. Hence, this may need further logic if we wanted to extend our service generation to VOSI or, perhaps, VOSpace.

Parameters

standard_idstr

The ivoid of a standard.

to_service()