Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
Within a tournament there can be any number of events for players (singly, in pairs or teams) to complete in. The Event entity provides information about each of these events. This section explains the key parts of an Event.

2. Event Schema

To see a graphical representation of the data model (schema) for the Event entity please expand the link below:

Expand
titleView Person Schema Diagram

Image Added

3. Creating an Event

The mandatory information required to create an Event entity is an id and a name. This would be valid but a normal Event will include at a minimum the ID, name, discipline, event type and gender.

...

Code Block
themeConfluence
titleJson
linenumberstrue
collapsetrue
{
  "Event": {
    "EventID": "Tennis:Event:EventId:Event1",
    "Updated": "1900-01-01T01:01:01+00:00",
    "IDs": { "ID": "Tennis:Tournament:TournamentId:349C4B46-9EB6-4E52-9486-38C02911FF03:Event:EventId:Event1" },
    "Name": "Sample Event"
  }
}

...

4. Event ID

In EventID you must supply your unique identifier for the event. The value must be unique within the tournament.

Info
When you’re exchanging information with a client or supplier it is possible that you both have an ID for the Event. To make exchange easier TODS allows for any number of additional IDs to be included with Event. See ‘How to include multiple identifiers’ for more information.


Related Information


Go back to Tennis Open Data Standards home page.