Date: Thu, 28 Mar 2024 18:28:33 +0000 (UTC) Message-ID: <639661764.25.1711650513626@8681aa4e640e> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_24_2044668890.1711650513626" ------=_Part_24_2044668890.1711650513626 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
DRAFT DOCUMENTATION
Please note that this documentation is in draft and is not finalised.
We would encourage you provide any comments, questions, or sugge= stions for changes by use in-line commenting on this page. To d= o so simply highlight a section of text and then click on the "Comm= ent" option that appears.
When exchanging data betwe= en different sources it is common that each source uses a different identif= ier for the same entity and there is no universal identifier. TODS all= ows entities to contain multiple ids to facilitate easier data transfer.
It is important to identify where data sent in the TODS came from. To do= this, an identifier can be used. For example, every tournament must have a= TournamentId. This is the Id used by the sender of the TODS data and is un= ique. Each Id sits in a URN-style namespace in the following format:
Tennis:<Entity>:<Provider>:<Identifier>
It is= important to note that when, for example, entering a TournamentId, the ent= ity is already a tournament and does not need to be re-entered.
To cl= arify, please see the example below where provider 'The Northern Lawn Tenni= s Club' is sending data using the TODS to the 'LTA':
<Tennis> =09<Header> =09=09<ProviderId>The Northern Lawn Tennis Club</ProviderId> =09=09<Date>2019-04-17</Date> =09=09<DataStandardsVersion>Draft 0.5</DataStandardsVersion> =09</Header> =09=09<Tournament> =09=09=09<TournamentId>T182747</TournamentId> =09=09=09<Name>The Manchester Trophy</Name> =09=09=09=E2=80=A6 =09=09</Tournament> </Tennis>
{ =09"Tennis": { =09=09"Header": { =09=09=09"ProviderId": "The Northern Lawn Tennis Club", =09=09=09"Date": "2019-04-17", =09=09=09"DataStandardsVersion": "Draft 0.5" =09=09}, =09=09"Tournament": { =09=09=09"TournamentId": "T182747", =09=09=09"Name": "The Manchester Trophy" =09=09} =09} }
We can see that The Northern Lawn Tennis Club sent data from a tournamen= t, the Manchester Trophy, with the unique TournamentId of T182747. So, = our Id is Tennis:Tournament:The Northern Lawn Tennis Club:T182747. Thi= s allows the recipient of TODS data to know exactly what it is and where it= came from, in this case the LTA.
It is likely that the LTA would receive this tournament and add it to th= eir own system, generating a new Id in the process. This would change ONLY = the provider name and TournmentId, making their identifier Tennis:Tournament:L= TA:ghttE= RaaI as you can see in the example below. If they wanted to add more data, = sharing it back with The Nothern Lawn Tennis Club, it would be imperative t= o use both provider's unique reference Id to understand that they are sharing= data on the same tournament.
<Tennis> =09<Header> =09=09<ProviderId>LTA/ProviderId> =09=09<Date>2019-04-18</Date> =09=09<DataStandardsVersion>Draft 0.5</DataStandardsVersion> =09</Header> =09=09<Tournament> =09=09=09<TournamentId>ghttERaaI</TournamentId> =09=09=09<Ids> =09=09=09=09<Id>The Northern Lawn Tennis Club:T182747</Id> =09=09=09</Ids> =09=09=09<Name>The Manchester Trophy</Name> =09=09=09=E2=80=A6 =09=09</Tournament> </Tennis>
{ =09"Tennis": { =09=09"Header": { =09=09=09"ProviderId": "LTA", =09=09=09"Date": "2019-04-18", =09=09=09"DataStandardsVersion": "Draft 0.5" =09=09}, =09=09"Tournament": { =09=09=09"TournamentId": "ghttERaaI", =09=09=09"Ids": { =09=09=09=09"Id": "The Northern Lawn Tennis Club:T182747" =09=09=09}, =09=09=09"Name": "The Manchester Trophy", =09=09} =09} }
The Primary Identifier has been set to the LTA's (Tennis:Tournament:LTA:ghttERaaI= ) and The Northern Lawn Tennis Club's identifier has been included t= oo. Both sources now know this is a single Tournament and how each identifi= es it.
This is not limited to two identifiers, other Id's can be included too. = Let's assume that this Tournament is also exchanged with the ITF. The ITF c= ould also include that identifier when sending messages about the Tournamen= t.
<Tennis> =09<Header> =09=09<ProviderId>LTA</ProviderId> =09=09<Date>2019-04-18</Date> =09=09<DataStandardsVersion>Draft 0.5</DataStandardsVersion> =09</Header> =09=09<Tournament> =09=09=09<TournamentId>ghttERaaI</TournamentId> =09=09=09<Ids> =09=09=09=09<Id>The Northern Lawn Tennis Club:T182747</Id> =09=09=09=09<Id>ITF:2019-J-O-NOR</Id> =09=09=09</Ids> =09=09=09<Name>The Manchester Trophy</Name> =09=09=09=E2=80=A6 =09=09</Tournament> </Tennis>
{ =09"Tennis": { =09=09"Header": { =09=09=09"ProviderId": "LTA", =09=09=09"Date": "2019-04-18", =09=09=09"DataStandardsVersion": "Draft 0.5" =09=09}, =09=09"Tournament": { =09=09=09"TournamentId": "ghttERaaI", =09=09=09"Ids": { =09=09=09=09"Id": [ =09=09=09=09=09"The Northern Lawn Tennis Club:T182747", =09=09=09=09=09"ITF:2019-J-O-NOR" =09=09=09=09] =09=09=09}, =09=09=09"Name": "The Manchester Trophy", =09=09} =09} }
Go back to Tennis Open Data S= tandards home page.