...
Each usage event must be described in a separate <context-object> element. All individual <context-object> elements must be wrapped into the <context-objects> root element.
Each <context-object> must have a timestamp attribute, and it may optionally be given an identifier attribute. These two attributes can be used to record the request time and an identification of the usage event. Details are provided below.
<context-object@timestap> | Request Time
...
Description | The exact time on which the usage event took place. |
XPath | ctx:context-object/@timestamp |
Usage | Mandatory |
Format | The format of the request time must conform to ISO8601. The YYYY-MM-DDTHH:MM:SS representation must be used. |
Example | 2009-07-29T08:15:46+01:00 |
<context-object@identifier> | Usage Event ID
| Description | An identification of a specific usage event. |
XPath | ctx:context-object/@identifier | |
Usage | Optional | |
Format | No requirements are given for the format of the identifier. If this optional identifier is used, it must be (1) opaque and (2) unique for a specific usage event. | |
Example | b06c0444f37249a0a8f748d3b823ef2a |
Occurences of child elements in <context-object>
Within a <context-object> element, the following subelements can be used:
...
The <referent> element must provide information on the document that is requested. More specifically, it must record the following data elements.
<referent/identifier> | Location of object file or metadata file
...
Description | The URL of the object file or the metadata record that is requested. Since this document focuses on usage by means of the World Wide Web, there will always be one URL for each usage event. |
XPath | ctx:context-object/ctx:referent/ctx:identifier |
Usage | Mandatory |
Format | URL |
Example | https://openaccess.leidenuniv.nl/bitstream/1887/12100/1/Thesis.pdf Other |
<referent/identifier> | OAI-PMH identifier of
...
requested document
...
Description | A globally unique identification of the resource that is requested must be provided if there is one that is applicable to the document. Identifiers should be independent of the 'communication protocol'-independent as much as possible. In the case of a request for an object file, the identifier should enable the aggregator to obtain the object's associated metadata file. |
XPath | ctx:context-object/ctx:referent/ctx:identifier |
Usage | Mandatory if applicable |
Format | URI |
Example |
...
The <ReferringEntity> provides information about the environment that has forwarded the user to the document that was requested. This referrer can be expressed in two ways.
<referringEntity/identifier> | Referrer URL
...
Description | The entity which has directed the user to the requested resource. As a minimal requirement, this must be the URL provided by the HTTP referrer string. |
XPath | ctx:referring-entity/ctx:identifier |
Usage | Mandatory if applicable |
Format | URL |
Example | http://www.google.nl/search?hl=nl&q=beleidsregels+artikel+4%3A84&meta= " Referrer |
<referringEntity/identifier> | Refferer Name
| 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. |
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 |
...
The user who has sent the request for the file is identified in the <requester> element.
<requested/identifier> | IP-address of requestor
| Description | The user can be identified by providing the IP-address. Including the full IP-address in the description of a usage event is not permitted by international privacy laws. For this reason, the IP-address needs to be obfuscated. The IP-address must be hashed using MD5 encryption. MD5 encryption of IP addresses can easily be hacked. The question if such MD5 encryption secures the privacy sufficiently warrant further research by legal advisors. |
XPath | ctx:context-object/ctx:requester/ctx:identifier | |
Usage | Mandatory | |
Format | A data-URI, consisting of the prefix "data:", followed by a 32-digit hexadecimal number. | |
Example | data:c06f0464f37249a0a9f848d4b823ef2a |
...
<requested/identifier> | C-class Subnet
...
Description | When the IP-address is obfuscated, this will have the disadvantage that information on the geographic location, for instance, can no longer be derived. For this reason, the C-Class subnet must be provided. The C-Class subnet, which consists of the three most significant bytes from the IP-address, is used to designate the network ID. The final (most significant) byte, which designates the HOST ID, is replaced with a '0'. The C-class Subnet may optionally be hashed using MD5 encryption. |
XPath | ctx:context-object/ctx:requester/ctx:identifier |
Usage | Optional |
Format | A data-URI, consisting of the prefix "data:", followed either by a 32-digit hexadecimal number, or by three hexadecimal numbers separated by a dot, followed by a dot and a '0'. |
Examples | data:118.94.150.0data:ec17f0564f32240c0a9d848d4b823ef2a |
<requester/.../dcterms:spatial> | Geographic location
| Description | The country from which the request originated may also be provided explicitly. |
XPath | ctx:context-object/ctx:requester/ctx:metadata-by-val/ctx:metadata/?dcterms:spatial | |
Usage | Optional | |
Format | A two-letter code in lower case, following the ISO 3166-1-alpha-2 standard. http://www.iso.org/iso/english_country_names_and_code_elements | |
Example | ne |
4.1.5. <service-type>
<service-type/.../dcterms:format> | Request Type
| Description | The request type specifies if the request is for an object file or a metadata record. |
XPath | ctx:context-object/ctx:service-type/ctx:metadata-by-val/ctx:metadata/dcterms:format | |
Inclusion | Mandatory | |
Format | Two values are allowed: "objectFile" or "metadataView" : info:eu-repo/semantics/objectFile or info:eu-repo/semantics/metadataView | |
Example | objectFile |
4.1.6. <resolver> and <referrer>
<resolver/identifier> | Host name
Host name |
|
Description | An identification of the institution that is responsible for the repository in which the requested document is stored. |
XPath | ctx:context-object/ctx:resolver/ctx:identifier |
Usage | Optional |
Format | A unique global identifier taken from the WorldCat registry of institutions, catalogues and OpenURL resolvers. |
Example |
<resolver/identifier> | Location of OpenURL Resolver
| Description | In the case of link resolver usage data, the URL of the OpenURL resolver must be provided. |
XPath | ctx:context-object/ctx:resolver/ctx:identifier | |
Usage | Optional | |
Format | URL | |
Example |
...
<referrer/identifier> | Link resolver Context Identifier
...
Description | The identifier of the context from within the user triggered the usage of the target resource. |
XPath | ctx:context-object/ctx:referrer/ctx:identifier |
Usage | Optional |
Format | URL |
Example | info:sid/dlib.org:dlib</identifier |
...
Code Block | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
<?xml version="1.0" encoding="UTF-8"?> <context-objects xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dcterms="http://dublincore.org/documents/2008/01/14/dcmi-terms/" xmlns:sv="info:ofi/fmt:xml:xsd:sch_svc" xsi:schemaLocation="info:ofi/fmt:xml:xsd:ctx [http://www.openurl.info/registry/docs/info:ofi/fmt:xml:xsd:ctx]" xmlns="info:ofi/fmt:xml:xsd:ctx"> <context-object timestamp="2009-07-29T08:15:46+01:00" identifier="b06c0444f37249a0a8f748d3b823ef2a"> <referent> <identifier>https://openaccess.leidenuniv.nl/bitstream/1887/12100/1/Thesis.pdf</identifier> <identifier>http://hdl.handle.net/1887/12100</identifier> </referent> <referring-entity> <identifier>http://www.google.nl/search?hl=nl&q=beleidsregels+artikel+4%3A84&meta="</identifier> <identifier>info:sid/google</identifier> </referring-entity> <requester> <metadata-by-val> <format>[http<format>http://dini.de/namespace/oas-requesterinfo]<requesterinfo</format> <metadata> <requesterinfo xmlns="http://dini.de/namespace/oas\-requesterinfo"> <hashed-ip>b505e629c508bdcfbf2a774df596123dd001cee172dae5519660b6014056f53a</hashed-ip> <hashed-c>d001cee172dae5519660b6014056f5346d05e629c508bdcfbf2a774df596123d</hashed-c> <hostname>uni-saarland.de</hostname> <classification>institutional</classification> <hashed-session>660b14056f5346d0</hashed-session> <user-agent>mozilla/5.0 (windows; u; windows nt 5.1; de; rv:1.8.1.1) gecko/20061204</user-agent> </requesterinfo> </metadata> </metadata-by-val> </requester> <service-type> <metadata-by-val> <format>http://dublincore.org/documents/2008/01/14/dcmi-terms/</format> <metadata> <dcterms:format>objectFile</dcterms:format> </metadata> </metadata-by-val> </service-type> <resolver> <identifier>http://www.worldcat.org/libraries/53238</identifier> </resolver> <referrer> <identifier>info:sid/dlib.org:dlib</identifier> </referrer> </context-object> </context-objects> |
...