X-Git-Url: http://gitweb.michael.orlitzky.com/?a=blobdiff_plain;f=doc%2Fman1%2Fhtsn-import.1;h=1fb62a20f46cceab477c23cfd12e2aa4b4a7e125;hb=b45f24209ce6f1eb3c24a5f01a71f5940a001c02;hp=d31634f45ff24e350b1aad4f17a5f0e2f88d7432;hpb=206d94d325b1fa31fc3b07841cd55f07c0fcf31a;p=dead%2Fhtsn-import.git

diff --git a/doc/man1/htsn-import.1 b/doc/man1/htsn-import.1
index d31634f..1fb62a2 100644
--- a/doc/man1/htsn-import.1
+++ b/doc/man1/htsn-import.1
@@ -48,6 +48,8 @@ pickle/unpickle everything already, this should be impossible.
 The XML document types obtained from the feed are uniquely identified
 by their DTDs. We currently support documents with the following DTDs:
 .IP \[bu] 2
+AutoRacingResultsXML.dtd
+.IP \[bu]
 Auto_Racing_Schedule_XML.dtd
 .IP \[bu]
 Heartbeat.dtd
@@ -105,10 +107,36 @@ 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
+.IP \[bu]
+Cbask_Conf_Standings_XML.dtd
+.IP \[bu]
+Cbask_DivII_III_Indv_Stats_XML.dtd
+.IP \[bu]
+Cbask_DivII_Team_Stats_XML.dtd
+.IP \[bu]
+Cbask_DivIII_Team_Stats_XML.dtd
+.IP \[bu]
+CBASK_FGPctXML.dtd
+.IP \[bu]
+CBASK_FoulsXML.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
@@ -153,11 +181,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
-\(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