DRAFT DOCUMENTATION
Please note that this documentation is in draft and is not finalised.
We would encourage you provide any comments, questions, or suggestions for changes by use in-line commenting on this page. To do so simply highlight a section of text and then click on the "Comment" option that appears.
1. What is a Person?
The Person entity is used to represent any individual involved in tennis. This is most often a player but can also be a coach, a parent, an umpire, an organiser, an officer in a national association - anyone with a role in tennis. Sources can use a Person entity to keep a single reference to a person throughout his or her tennis life - for example from junior player, through to professional player, then coach, umpire, club chairperson, and senior's circuit player. This person entity can include multiple roles, for example senior player, professional umpire and parent of a junior player.
2. Person Schema
To see a graphical representation of the data model (schema) for the Person entity please expand the link below:
3. Creating a Person
The minimum information required to create a Person entity is an ID and a name (PreferredFamilyName or PreferredGivenName, both where available).
4. PersonID
In PersonID you must supply your unique identifier for the Person.
The value of PersonID must be unique within your data. To make IDs unique globally TODS uses a URN-style system, so the full globally unique tournament ID is:
Tennis:Person:<SourceID>:<PersonID>
World Tennis ID
Where it is known we strongly recommend using the Tennis ID as the globally unique ID for any player or other person. This can be provided by the ITF for any individual and is the easiest way to ensure that a single unique record for a person is maintained across multiple systems and sources.
5. Person Names
TODS allows for different names for a Person to be provided so that clients can use the best one for their situations.
• PreferredGivenName/PreferredFamilyName
: the name, in latin script, that the person is usually known by. For example Andy Murray rather than Andrew Murray.
• PassportGivenName/PassportFamilyName
: the name, as listed in the person's passport.
• NativeGivenName/Native
: the name written in the local script of source/client (as agreed between parties). For example might be a Japanese transliteration of the name, アンディ[Andy]FamilyName
6. Adding more information
Once the minimum information has been supplied you can add additional information if it is available or as it becomes available. There are attributes for key information like date of birth, gender, nationality.
There are attributes defined for providing links to a person's social media profiles, web site and other contact information. Finally there is a section to provide more general biographical information about a person such as hobbies, interests, sporting career and so forth.
TODS defines a set of standard attributes that are widely used within tennis. If you need to supply some extra information that doesn’t fit one of the standard attributes you can use an extension. See ‘How to include additional information using Extensions’ for more information.
Related Information:
Go back to Tennis Open Data Standards home page.