Similarly to the case explained in #257, the IVOA community is using identifiers (ivoid) which are URI not starting with http, like e.g.:
ivo://padc.obspm.maser/tfcat/q/marques_nda_jupiter
Before I start the registration process, I'd like to follow up on the last comment on #257, which states that if we have a resolver interface, then, we could be listed in identifiers.org.
Documentation in IVOA Identifiers: https://www.ivoa.net/documents/IVOAIdentifiers/
And we have a resolver interfaces. One of them is currently available at:
https://registry.euro-vo.org/oai.jsp?verb=GetRecord&identifier={id}&metadataPrefix=oai_dc
where we can replace {id} by the ivoid. As you can see, that interface is an OAI-PMH interface, with a metadata prefix than can be updated to get the metadata in different format (here oai_dc for DublinCore). Other prefixes can be used, such as ivo_vor, to get the native IVOA resource format.
Can you help me on this registration?
Similarly to the case explained in #257, the IVOA community is using identifiers (
ivoid) which are URI not starting with http, like e.g.:Before I start the registration process, I'd like to follow up on the last comment on #257, which states that if we have a resolver interface, then, we could be listed in identifiers.org.
Documentation in IVOA Identifiers: https://www.ivoa.net/documents/IVOAIdentifiers/
And we have a resolver interfaces. One of them is currently available at:
where we can replace
{id}by theivoid. As you can see, that interface is an OAI-PMH interface, with a metadata prefix than can be updated to get the metadata in different format (hereoai_dcfor DublinCore). Other prefixes can be used, such asivo_vor, to get the native IVOA resource format.Can you help me on this registration?