...
Description | The referrer may be categorised on the basis of a limited list of known referrers. All permitted values will be registered in the OpenURL registry. | Warning |
|---|
What worries me that I don't see such a list there. Should this not state: "A referrer name must be uniquely identifier using a Source Identifier (info:sid). Concatenating the info:sid namespace with the internet domain name, subdomain name or host name. "Question: When such list exists, must the application check this string with this list? - maurice |
|
XPath | ctx:referring-entity/ctx:identifier |
Usage | Optional |
Format | A URI that is registered in http://info-uri.info/registry/OAIHandler?verb=GetRecord&metadataPrefix=reg&identifier=info:sid/ |
Example | info:sid/google |
| Warning |
|---|
Peter, the info:sid documentation tells us that this name may refer to an Internet domain name, subdomain name, or host name. The examples at indo-uri.info show - info:sid/amazon.co.uk
- info:sid/oclc.org
- info:sid/amazon.co.uk:books
- info:sid/oclc.org:inspec
Should the example used above not also be info:sid/google.com ?
I am unfamiliar on this terrain, maybe I am wrong and info:sid/google is allowed.
I don't know what is in a apache logfile that can be easily used to transform in an info:sid. Should a real example not be reflecting something like info:sid/www.google.nl/search?q="Who+controls+the+internet" ? (in other words, how intelligent do implementers need to make their software for creating a info:sid ?) - or should this be stripped down to info:sid/www.google.nl
- or even without the subdomain www info:sid/google.nl
- or must the top domain be changed to .com info:sid/google.com
- or indeed only the domain name, without the top-domain info:sid/google
- or only the host info:sid/www
I know I am just out of my league here, but maybe other people who implement these guidelines have similar questions in the future.
Maybe Benoit knows more about this.
All the best,
Maurice
|
4.1.4. <requester>
The user who has sent the request for the file is identified in the <requester> element.
...
