...
A client makes a request for a resource identified with a PID indicating that it wants data (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.
Retrofitting a CUL web site with PID's
...