Copy a block straight into the paper. The tables carry the paper's own wording, which differs from the schema's in places. The JSON figure is cut down from the format's sample file to the fields the schema requires, so its field names always match the validator. All blocks are regenerated from format version 0.3.2 whenever the schemas change.
\begin{table}[H]
\centering
\caption{Description of mandatory Skeletal Tracking CDF fields recorded for each frame. Any description ending with a $^\star$ is repeated once per player per frame. Any description ending with a $^\diamond$ is repeated once per player per frame per landmark (e.g knee\_left, hip\_right, ear\_right etc.). Note that \{i\} and \{j\} are used as indices for items in lists. Landmark names should follow snake-case with any direction indicator as a suffix. Any type ending with a $^\ddagger$ may be null when the subject is occluded, off-camera or otherwise not captured in that frame.}
\label{tab:cdf-limb-tracking-required}
\begin{adjustbox}{max width=\textwidth}
\begin{tabular}{lp{1.5cm}p{8cm}l}
\hline
Root & Field & Description & Type \\ \hline
& frame\_id & Unique frame identifier & Integer \\
& timestamp & Timestamp of the frame in UTC & String \\
& period & Period of the match which can be first\_half, second\_half, first\_half\_extratime, second\_half\_extratime, or shootout & String \\
match & id & Unique match identifier & String \\
teams/\{home\text{\textbar}away\} & id & Unique identifier for the home or away team$^\star$ & String \\
teams/\{home\text{\textbar}away\}/players/\{i\} & id & Unique identifier for a player$^\star$ & String \\
teams/\{home\text{\textbar}away\}/players/\{i\}/landmarks/\{j\} & name & Name for a landmark$^\diamond$ & String \\
teams/\{home\text{\textbar}away\}/players/\{i\}/landmarks/\{j\} & x & Relative x coordinate of landmark in relation to the point of origin (m)$^\diamond$ & Float / null$^\ddagger$ \\
teams/\{home\text{\textbar}away\}/players/\{i\}/landmarks/\{j\} & y & Relative y coordinate of landmark in relation to the point of origin (m)$^\diamond$ & Float / null$^\ddagger$ \\
teams/\{home\text{\textbar}away\}/players/\{i\}/landmarks/\{j\} & z & Relative z coordinate of landmark in relation to the point of origin (m)$^\diamond$ & Float / null$^\ddagger$ \\
teams/\{home\text{\textbar}away\}/players/\{i\}/landmarks/\{j\} & is\_visible & If landmark is detected (true) or inferred (false) $^\diamond$ & Boolean \\
\end{tabular}
\end{adjustbox}
\end{table}
\begin{table}[H]
\centering
\caption{Description of optional Skeletal Tracking CDF fields that would be recorded once per frame. Any description ending with a $^\star$ is repeated once per person (e.g., player, referee) per frame. Note that \{i\} is used as an index for the items in a list. Any type ending with a $^\ddagger$ may be null when the subject is occluded, off-camera or otherwise not captured in that frame.}
\label{tab:cdf-limb-tracking-optional}
\begin{adjustbox}{max width=\textwidth}
\begin{tabular}{lp{2.5cm}p{7cm}l}
\hline
Root & Field & Description & Type \\ \hline
ball & x & x location of the ball on the pitch (m). & Float / null$^\ddagger$ \\
ball & y & y location of the ball on the pitch (m). & Float / null$^\ddagger$ \\
ball & z & z location of the ball on the pitch (m). & Float / null$^\ddagger$ \\
ball & status & Indicates if the ball is either in play (true) or out of play (false) & Boolean \\
ball & poss\_team\_id & Unique identifier of the team that currently possesses the ball & String \\
ball & poss\_status & Contextual description of the level of control (e.g., controlled, contested,...) & String \\
officials/\{i\} & id & Unique identifier for an official & String \\
officials/\{i\} & x & x location of the official on the pitch (m)$^\star$ & Float / null$^\ddagger$ \\
officials/\{i\} & y & y location of the official on the pitch (m)$^\star$ & Float / null$^\ddagger$ \\
officials/\{i\} & z & z location of the official on the pitch (m)$^\star$ & Float / null$^\ddagger$ \\
officials/\{i\} & vel & Speed of the official (m/s)$^\star$ & Float \\
officials/\{i\} & acc & Acceleration of the official (m/s\textsuperscript{2})$^\star$ & Float \\
officials/\{i\} & lat & Latitude of the official's position if the data is collected by GNSS or GPS$^\star$ & Float \\
officials/\{i\} & long & Longitude of the official's position if the data is collected by GNSS or GPS$^\star$ & Float \\
officials/\{i\} & is\_visible & Denotes if an official was visible (in view of the camera) (true) or not (false)$^\star$ & Boolean \\
\end{tabular}
\end{adjustbox}
\end{table}
\begin{center}
\begin{minipage}{0.8\linewidth}
\begin{lstlisting}
{
"frame_id": 0,
"timestamp": "2023-10-01T12:00:00Z",
"period": "first_half",
"match": {"id": "match_20230415_team1_team2"},
"teams": {
"home": {
"id": "team1",
"players": [
{
"id": "player_h1",
"landmarks": [
{
"name": "head",
"x": 23.45,
"y": 15.67,
"z": 1.82,
"is_visible": true
},
{
"name": "neck",
"x": 23.48,
"y": 15.7,
"z": 1.65,
"is_visible": true
},
{
"name": "shoulder_right",
"x": 23.3,
"y": 15.75,
"z": 1.65,
"is_visible": true
},
...
]
},
...
]
},
"away": {...}
}
}
\end{lstlisting}
\captionof{figure}{Example of the JSON Lines ({$.jsonl$}) for the Landmark Tracking Data. One frame is shown, with the first three landmarks of one home team player. The coordinate system is the same used in \ref{p:coords}.}
\label{fig:skeletal-hierarchy}
\end{minipage}
\end{center}