Hi,
I am interested in how signposting can be best deployed by repositories (but also, potentially, other similar systems) to satisfy the use case of a client wishing to find machine-readable metadata which uses a particular "profile".
I see that the specification now has a "profile" attribute for links, so I feel confident that this is possible, but I just want to test my understanding.
In OAI-PMH (ubiquitously used by repositories) we have the concept of "metadata formats", where a repository's OAI-PMH API can typically be invoked to return a metadata record which conforms to what we might these days call a "profile". In that context, an example of such a profile is Rioxx[^1]
If I understand correctly, in signposting we might specify a link which resolves to a Rioxx metadata record (serialised as XML) something like this:
<
https://eprints.lincoln.ac.uk/cgi/oai2?verb=GetRecord&metadataPrefix=rioxx&identifier=oai:eprints.lincoln.ac.uk:4> ;
rel="item" ;
type="application/xml" ;
profile="
http://www.rioxx.net/schema/v2.0/rioxx/"
Is my understanding correct?
(note - the use of the OAI-PMH URL in this is a side-issue, but I wanted a link that actually resolved for the example).
Thanks,
Paul
[^1]:
https://www.rioxx.net/profiles/v2-0-final/
-------------------------------------------
Paul Walk
http://www.paulwalk.net
Founder and Director, Antleaf Ltd
http://www.antleaf.com
-------------------------------------------