...
We will want resources identified and linked with PIDS to be indexed in popular search engines (Google, Yahoo!, msn, etc.). The URL that the resource is indexed under should be the PID and not the final server (true?). What requirements for redirection etc. should be fulfilled? I think this means that 302 redirect would be appropriate.
Play nicely with
...
services such as VIVO that do content-negotiation to provide data and human views of resources
A client makes a request for a resource identified with a PID indicating that it wants some particular formats (say data (in RDF/XML) in the Accept header. Should this be supported at the resolver level (return via 303 some description of the resource, its ids and any public metadata in the resolver?) or should we consider this not a function of the resolver and instead leave metadata query to some other interface? The potential value of this is not limited to Semantic Web applications - what is described is similar to the OAI getcapabilities request.Or should the resolver pass the request header to the permanent resource and let the permanent resource respond with data? We may have 2 use cases here – one a request for the metadata of the PID itself and the other for data from the identified resource* headers. The client should still get redirected to the appropriate resource which can then support the content-negotiation.
There should probably be some other mechanism (via some other request interface) to get metadata from the resolver (ala handle)
Provide centralized support for Semantic Web / Data views for resources on systems that do not provide for content-negotiation internally
A client makes a request for a resource identified with a PID indicating that it wants some particular formats (say data in RDF/XML) in the Accept* headers. The resolver should understand that it should provide content-negotiation for these resources to either redirect to different URLs depending on the requested type, or to provide an internally generated data view.client should still get redirected to the appropriate resource which can then support the content-negotiation.
Retrofitting a CUL web site with PID's
...