.IP \[bu]
NCAA_FB_Preview_XML.dtd
.IP \[bu]
+NFL_NCAA_FB_Matchup_XML.dtd
+.IP \[bu]
nflpreviewxml.dtd
.IP \[bu]
nhlpreviewxml.dtd
.IP \[bu]
recapxml.dtd
+.IP \[bu]
+WorldBaseballPreviewXML.dtd
+.RE
+.IP \[bu]
+SportInfo
+.RS
+.IP \[bu]
+CBASK_3PPctXML.dtd
+.IP \[bu]
+Cbask_All_Tourn_Teams_XML.dtd
+.IP \[bu]
+CBASK_AssistsXML.dtd
+.IP \[bu]
+Cbask_Awards_XML.dtd
+.IP \[bu]
+CBASK_BlocksXML.dtd
.RE
.P
-The GameInfo and SportsInfo types do not have their own top-level
+The GameInfo and SportInfo types do not have their own top-level
tables in the database. Instead, their raw XML is stored in either the
-\(dqgame_info\(dq or \(dqsports_info\(dq table respectively.
+\(dqgame_info\(dq or \(dqsport_info\(dq table respectively.
.SH DATABASE SCHEMA
.P
prevent duplication in this case anyway.
.P
The aforementioned exceptions are the \(dqgame_info\(dq and
-\(dqsports_info\(dq tables. These tables contain the raw XML for a
+\(dqsport_info\(dq tables. These tables contain the raw XML for a
number of DTDs that are not handled individually. This is partially
for backwards-compatibility with a legacy implementation, but is
mostly a stopgap due to a lack of resources at the moment. These two
-tables (game_info and sports_info) still possess timestamps that allow
+tables (game_info and sport_info) still possess timestamps that allow
us to prune old data.
.P
UML diagrams of the resulting database schema for each XML document