1 <!ELEMENT XML_File_ID (#PCDATA)>
2 <!ELEMENT heading (#PCDATA)>
3 <!ELEMENT category (#PCDATA)>
4 <!ELEMENT sport (#PCDATA)>
5 <!ELEMENT Title (#PCDATA)>
6 <!ELEMENT Line_Time (#PCDATA)>
7 <!ELEMENT Notes (#PCDATA)>
8 <!ELEMENT GameID (#PCDATA)>
9 <!ELEMENT Game_Date (#PCDATA)>
10 <!ELEMENT Game_Time (#PCDATA)>
11 <!ELEMENT AwayTeamID (#PCDATA)>
12 <!ELEMENT AwayRotationNumber (#PCDATA)>
13 <!ELEMENT AwayAbbr (#PCDATA)>
14 <!ELEMENT AwayTeamName (#PCDATA)>
15 <!ELEMENT Casino (#PCDATA)>
16 <!ELEMENT AwayTeam ( ( AwayTeamID, AwayRotationNumber, AwayAbbr, AwayTeamName, Casino* ) )>
17 <!ELEMENT HomeTeamID (#PCDATA)>
18 <!ELEMENT HomeRotationNumber (#PCDATA)>
19 <!ELEMENT HomeAbbr (#PCDATA)>
20 <!ELEMENT HomeTeamName (#PCDATA)>
21 <!ELEMENT HomeTeam ( ( HomeTeamID, HomeRotationNumber, HomeAbbr, HomeTeamName, Casino* ) )>
22 <!ELEMENT Over_Under ( Casino* )>
23 <!ELEMENT Game ( ( GameID, Game_Date, Game_Time, AwayTeam, HomeTeam, Over_Under ) )>
24 <!ELEMENT time_stamp (#PCDATA)>
27 The generated message schema is too general; it allows any number
28 of anything in any order. We know that the first couple of elements
29 are required and appear in a fixed order.
32 Warning: the TSN DTD suggests the existence of an optional League_Name
33 element that would appear next to the Notes*.
35 <!ELEMENT message ( XML_File_ID, heading, category, sport, Title, Line_Time, ( Notes*, Game+)*, time_stamp )>
37 <!ATTLIST Casino ClientID CDATA #REQUIRED>
38 <!ATTLIST Casino Name CDATA #REQUIRED>