Skip to main content

4.5. Events

4.5. Events

This data structure represents events that have occurred on an instance of an object class (see Section 5 regarding object classes).

This is an example of an "events" array:

"events" :
[
{
"eventAction" : "registration",
"eventActor" : "SOMEID-LUNARNIC",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventActor" : "OTHERID-LUNARNIC",
"eventDate" : "1991-12-31T23:59:59Z"
}
]

The "events" array consists of objects, each with the following members:

  • "eventAction" -- a REQUIRED string denoting the reason for the event

  • "eventActor" -- an OPTIONAL identifier denoting the actor responsible for the event

  • "eventDate" -- a REQUIRED string containing the time and date the event occurred

  • "links" -- OPTIONAL; see Section 4.2

Events can be future dated. One use case for future dating of events is to denote when an object expires from a registry.

The "links" array in this data structure is provided for references to the event actor. In order to reference an RDAP entity, a "rel" of "related" and a "type" of "application/rdap+json" is used in the link reference.

See Section 10.2.3 for a list of values for the "eventAction" string. See Appendix B regarding the various ways events can be modeled.