Add SportInfo support for CBASK_AssistsXML.dtd.

[dead/htsn-import.git] / doc / man1 / htsn-import.1

diff --git a/doc/man1/htsn-import.1 b/doc/man1/htsn-import.1
index 29aa4d3317801fb308737a7b01d1527cac23b9cf..9bc682a2425c95aec59cdf2ddc369813e5a77e38 100644 (file)
--- a/doc/man1/htsn-import.1
+++ b/doc/man1/htsn-import.1
@@ -95,16 +95,30 @@ nbapreviewxml.dtd
 .IP \[bu]
 NCAA_FB_Preview_XML.dtd
 .IP \[bu]
 .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
 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

 .RE
 .P
 .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
 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
 
 .SH DATABASE SCHEMA
 .P


@@ -149,11 +163,11 @@ unique constraint in the top-level table's \(dqxml_file_id\(dq will
 prevent duplication in this case anyway.
 .P
 The aforementioned exceptions are the \(dqgame_info\(dq and
 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
 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
 us to prune old data.
 .P
 UML diagrams of the resulting database schema for each XML document