...
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/@timestamp> | 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 |
...