doc/man1/htsn-import.1

   1 .TH htsn-import 1
   2
   3 .SH NAME
   4 htsn-import \- Import XML files from The Sports Network into an RDBMS.
   5
   6 .SH SYNOPSIS
   7
   8 \fBhtsn-import\fR [OPTIONS] [FILES]
   9
  10 .SH DESCRIPTION
  11 .P
  12 The Sports Network <http://www.sportsnetwork.com/> offers an XML feed
  13 containing various sports news and statistics. Our sister program
  14 \fBhtsn\fR is capable of retrieving the feed and saving the individual
  15 XML documents contained therein. But what to do with them?
  16 .P
  17 The purpose of \fBhtsn-import\fR is to take these XML documents and
  18 get them into something we can use, a relational database management
  19 system (RDBMS), otherwise known as a SQL database. The structure of
  20 relational database, is, well, relational, and the feed XML is not. So
  21 there is some work to do before the data can be imported into the
  22 database.
  23 .P
  24 First, we must parse the XML. Each supported document type (see below)
  25 has a full pickle/unpickle implementation (\(dqpickle\(dq is simply a
  26 synonym for \(dqserialize\(dq here). That means that we parse the
  27 entire document into a data structure, and if we pickle (serialize)
  28 that data structure, we get the exact same XML document tha we started
  29 with.
  30 .P
  31 This is important for two reasons. First, it serves as a second level
  32 of validation. The first validation is performed by the XML parser,
  33 but if that succeeds and unpicking fails, we know that something is
  34 fishy. Second, we don't ever want to be surprised by some new element
  35 or attribute showing up in the XML. The fact that we can unpickle the
  36 whole thing now means that we won't be surprised in the future.
  37 .P
  38 The aforementioned feature is especially important because we
  39 automatically migrate the database schema every time we import a
  40 document. If you attempt to import a \(dqnewsxml.dtd\(dq document, all
  41 database objects relating to the news will be created if they do not
  42 exist. We don't want the schema to change out from under us without
  43 warning, so it's important that no XML be parsed that would result in
  44 a different schema than we had previously. Since we can
  45 pickle/unpickle everything already, this should be impossible.
  46 .P
  47 A list of supported document types is given in the appendix.
  48 .P
  49 The GameInfo and SportInfo types do not have their own top-level
  50 tables in the database. Instead, their raw XML is stored in either the
  51 \(dqgame_info\(dq or \(dqsport_info\(dq table respectively.
  52
  53 .SH DATABASE SCHEMA
  54 .P
  55 At the top level (with two notable exceptions), we have one table for
  56 each of the XML document types that we import. For example, the
  57 documents corresponding to \fInewsxml.dtd\fR will have a table called
  58 \(dqnews\(dq. All top-level tables contain two important fields,
  59 \(dqxml_file_id\(dq and \(dqtime_stamp\(dq. The former is unique and
  60 prevents us from inserting the same data twice. The time stamp on the
  61 other hand lets us know when the data is old and can be removed. The
  62 database schema make it possible to delete only the outdated top-level
  63 records; all transient children should be removed by triggers.
  64 .P
  65 These top-level tables will often have children. For example, each
  66 news item has zero or more locations associated with it. The child
  67 table will be named <parent>_<children>, which in this case
  68 corresponds to \(dqnews_locations\(dq.
  69 .P
  70 To relate the two, a third table may exist with name
  71 <parent>__<child>. Note the two underscores. This prevents ambiguity
  72 when the child table itself contains underscores. The table joining
  73 \(dqnews\(dq with \(dqnews_locations\(dq is thus called
  74 \(dqnews__news_locations\(dq. This is necessary when the child table
  75 has a unique constraint; we don't want to blindly insert duplicate
  76 records keyed to the parent. Instead we'd like to use the third table
  77 to map an existing child to the new parent.
  78 .P
  79 Where it makes sense, children are kept unique to prevent pointless
  80 duplication. This slows down inserts, and speeds up reads (which are
  81 much more frequent). There is a tradeoff to be made, however. For a
  82 table with a small, fixed upper bound on the number of rows (like
  83 \(dqodds_casinos\(dq), there is great benefit to de-duplication. The
  84 total number of rows stays small, so inserts are still quick, and many
  85 duplicate rows are eliminated.
  86 .P
  87 But, with a table like \(dqodds_games\(dq, the number of games grows
  88 quickly and without bound. It is therefore more beneficial to be able
  89 to delete the old games (through an ON DELETE CASCADE, tied to
  90 \(dqodds\(dq) than it is to eliminate duplication. A table like
  91 \(dqnews_locations\(dq is somewhere in-between. It is hoped that the
  92 unique constraint in the top-level table's \(dqxml_file_id\(dq will
  93 prevent duplication in this case anyway.
  94 .P
  95 The aforementioned exceptions are the \(dqgame_info\(dq and
  96 \(dqsport_info\(dq tables. These tables contain the raw XML for a
  97 number of DTDs that are not handled individually. This is partially
  98 for backwards-compatibility with a legacy implementation, but is
  99 mostly a stopgap due to a lack of resources at the moment. These two
 100 tables (game_info and sport_info) still possess timestamps that allow
 101 us to prune old data.
 102 .P
 103 UML diagrams of the resulting database schema for each XML document
 104 type are provided with the \fBhtsn-import\fR documentation, in the
 105 \fIdoc/dbschema\fR directory. These are not authoritative, but it
 106 should be considered a bug if they are incorrect. The diagrams are
 107 created using the pgModeler <http://www.pgmodeler.com.br/> tool.
 108
 109 .SH XML SCHEMA GENERATION
 110 .P
 111 In order to parse XML, you need to know the structure of your
 112 documents. Usually this is given in the form of a DTD or schema. The
 113 Sports Network does provide DTDs for their XML, but unfortunately many
 114 of them do not match the XML found on the feed.
 115 .P
 116 We need to construct a database into which to insert the XML. How do
 117 we know if <game> should be a column, or if it should have its own
 118 table? We need to know how many times it can appear in the
 119 document. So we need some form of specification. Since the supplied
 120 DTDs are incorrect, we would like to generate them automatically.
 121 .P
 122 The process should go something like,
 123 .IP 1.
 124 Generate a DTD from the first foo.xml file we see. Call it foo.dtd.
 125 .IP 2.
 126 Validate future foo documents against foo.dtd. If they all validate,
 127 great. If one fails, add it to the corpus and update foo.dtd so
 128 that both the original and the new foo.xml validate.
 129 .IP 3.
 130 Repeat until no more failures occur. This can never be perfect:
 131 tomorrow we could get a foo.xml that's wildly different from what
 132 we've seen in the past. But it's the best we can hope for under
 133 the circumstances.
 134 .P
 135 Enter XML-Schema-learner
 136 <https://github.com/kore/XML-Schema-learner>. This tool can infer a
 137 DTD from a set of sample XML files. The top-level \(dqschemagen\(dq
 138 folder (in this project) contains a number of subfolders\(emone for
 139 each type of document that we want to parse. Contained therein are XML
 140 samples for that particular document type. These were hand-picked one
 141 at a time according to the procedure above, and the complete set of
 142 XML is what we use to generate the DTDs used by htsn-import.
 143 .P
 144 To generate them, run `make schema` at the project
 145 root. XML-Schema-learner will be invoked on each subfolder of
 146 \(dqschemagen\(dq and will output the corresponding DTDs to the
 147 \(dqschemagen\(dq folder.
 148 .P
 149 Most of the production schemas are generated this way; however, a few
 150 needed manual tweaking. The final, believed-to-be-correct schemas for
 151 all supported document types can be found in the \(dqschema\(dq folder in
 152 the project root. Having the correct DTDs available means you
 153 don't need XML-Schema-learner available to install \fBhtsn-import\fR.
 154
 155 .SH XML SCHEMA UPDATES
 156 .P
 157 If a new tag is added to an XML document type, \fBhtsn-import\fR will
 158 most likely refuse to parse it, since the new documents no longer
 159 match the existing DTD.
 160 .P
 161 The first thing to do in that case is add the unparseable document to
 162 the \(dqschemagen\(dq directory, and generate a new DTD that matches
 163 both the old and new samples. Once a new, correct DTD has been
 164 generated, it should be added to the \(dqschema\(dq directory. Then,
 165 the parser can be updated and \fBhtsn-import\fR rebuilt.
 166 .P
 167 At this point, \fBhtsn-import\fR should be capable of importing the
 168 new document. But the addition of the new tag will most require new
 169 fields in the database. Fortunately, easy migrations like this are
 170 handled automatically. As an example, at one point, \fIOdds_XML.dtd\fR
 171 did not contain the \(dqHStarter\(dq and \(dqAStarter\(dq elements
 172 associated with its games. Suppose we parse one of the old documents
 173 (without \(dqHStarter\(dq and \(dqAStarter\(dq) using an old version
 174 of \fBhtsn-import\fR:
 175 .P
 176 .nf
 177 .I $ htsn-import --connection-string='foo.sqlite3' \\\\
 178 .I "              schemagen/Odds_XML/19996433.xml"
 179 Migration: CREATE TABLE \(dqodds\(dq ...
 180 Successfully imported schemagen/Odds_XML/19996433.xml.
 181 Processed 1 document(s) total.
 182 .fi
 183 .P
 184 At this point, the database schema matches the old documents, i.e. the
 185 ones without \fIAStarter\fR and \fIHStarter\fR. If we use a new
 186 version of \fBhtsn-import\fR, supporting the new fields, the migration
 187 is handled gracefully:
 188 .P
 189 .nf
 190 .I $ htsn-import --connection-string='foo.sqlite3' \\\\
 191 .I "              schemagen/Odds_XML/21315768.xml"
 192 Migration: ALTER TABLE \(dqodds_games\(dq
 193            ADD COLUMN \(dqaway_team_starter_id\(dq INTEGER;
 194 Migration: ALTER TABLE \(dqodds_games\(dq
 195            ADD COLUMN \(dqaway_team_starter_name\(dq VARCHAR;
 196 Migration: ALTER TABLE \(dqodds_games\(dq
 197            ADD COLUMN \(dqhome_team_starter_id\(dq INTEGER;
 198 Migration: ALTER TABLE \(dqodds_games\(dq
 199            ADD COLUMN \(dqhome_team_starter_name\(dq VARCHAR;
 200 Successfully imported schemagen/Odds_XML/21315768.xml.
 201 Processed 1 document(s) total.
 202 .fi
 203 .P
 204 If fields are removed from the schema, then manual intervention may be
 205 necessary:
 206 .P
 207 .nf
 208 .I $ htsn-import -b Postgres -c 'dbname=htsn user=postgres' \\\\
 209 .I "              schemagen/Odds_XML/19996433.xml"
 210 ERROR: Database migration: manual intervention required.
 211 The following actions are considered unsafe:
 212 ALTER TABLE \(dqodds_games\(dq DROP COLUMN \(dqaway_team_starter_id\(dq
 213 ALTER TABLE \(dqodds_games\(dq DROP COLUMN \(dqaway_team_starter_name\(dq
 214 ALTER TABLE \(dqodds_games\(dq DROP COLUMN \(dqhome_team_starter_id\(dq
 215 ALTER TABLE \(dqodds_games\(dq DROP COLUMN \(dqhome_team_starter_name\(dq
 216
 217 ERROR: Failed to import file schemagen/Odds_XML/19996433.xml.
 218 Processed 0 document(s) total.
 219 .fi
 220 .P
 221 To fix these errors, manually invoke the SQL commands that were
 222 considered unsafe:
 223 .P
 224 .nf
 225 .I $ psql -U postgres -d htsn \\\\
 226 .I "       -c 'ALTER TABLE odds_games DROP COLUMN away_team_starter_id;'"
 227 ALTER TABLE
 228 .I $ psql -U postgres -d htsn \\\\
 229 .I "       -c 'ALTER TABLE odds_games DROP COLUMN away_team_starter_name;'"
 230 ALTER TABLE
 231 .I $ psql -U postgres -d htsn \\\\
 232 .I "       -c 'ALTER TABLE odds_games DROP COLUMN home_team_starter_id;'"
 233 ALTER TABLE
 234 .I $ psql -U postgres -d htsn \\\\
 235 .I "       -c 'ALTER TABLE odds_games DROP COLUMN home_team_starter_name;'"
 236 ALTER TABLE
 237 .fi
 238 .P
 239 After manually adjusting the schema, the import should succeed.
 240
 241 .SH XML SCHEMA ODDITIES
 242 .P
 243 There are a number of problems with the XML on the wire. Even if we
 244 construct the DTDs ourselves, the results are sometimes
 245 inconsistent. Here we document a few of them.
 246
 247 .IP \[bu] 2
 248 \fIOdds_XML.dtd\fR
 249
 250 The <Notes> elements here are supposed to be associated with a set of
 251 <Game> elements, but since the pair
 252 (<Notes>...</Notes><Game>...</Game>) can appear zero or more times,
 253 this leads to ambiguity in parsing. We therefore ignore the notes
 254 entirely (although a hack is employed to facilitate parsing). The same
 255 thing goes for the newer <League_Name> element.
 256
 257 .IP \[bu]
 258 \fIweatherxml.dtd\fR
 259
 260 There appear to be two types of weather documents; the first has
 261 <listing> contained within <forecast> and the second has <forecast>
 262 contained within <listing>. While it would be possible to parse both,
 263 it would greatly complicate things. The first form is more common, so
 264 that's all we support for now. An example is provided as
 265 schemagen/weatherxml/20143655.xml.
 266
 267 .SH OPTIONS
 268
 269 .IP \fB\-\-backend\fR,\ \fB\-b\fR
 270 The RDBMS backend to use. Valid choices are \fISqlite\fR and
 271 \fIPostgres\fR. Capitalization is important, sorry.
 272
 273 Default: Sqlite
 274
 275 .IP \fB\-\-connection-string\fR,\ \fB\-c\fR
 276 The connection string used for connecting to the database backend
 277 given by the \fB\-\-backend\fR option. The default is appropriate for
 278 the \fISqlite\fR backend.
 279
 280 Default: \(dq:memory:\(dq
 281
 282 .IP \fB\-\-log-file\fR
 283 If you specify a file here, logs will be written to it (possibly in
 284 addition to syslog). Can be either a relative or absolute path. It
 285 will not be auto-rotated; use something like logrotate for that.
 286
 287 Default: none
 288
 289 .IP \fB\-\-log-level\fR
 290 How verbose should the logs be? We log notifications at four levels:
 291 DEBUG, INFO, WARN, and ERROR. Specify the \(dqmost boring\(dq level of
 292 notifications you would like to receive (in all-caps); more
 293 interesting notifications will be logged as well. The debug output is
 294 extremely verbose and will not be written to syslog even if you try.
 295
 296 Default: INFO
 297
 298 .IP \fB\-\-remove\fR,\ \fB\-r\fR
 299 Remove successfully processed files. If you enable this, you can see
 300 at a glance which XML files are not being processed, because they're
 301 all that should be left.
 302
 303 Default: disabled
 304
 305 .IP \fB\-\-syslog\fR,\ \fB\-s\fR
 306 Enable logging to syslog. On Windows this will attempt to communicate
 307 (over UDP) with a syslog daemon on localhost, which will most likely
 308 not work.
 309
 310 Default: disabled
 311
 312 .SH CONFIGURATION FILE
 313 .P
 314 Any of the command-line options mentioned above can be specified in a
 315 configuration file instead. We first look for \(dqhtsn-importrc\(dq in
 316 the system configuration directory. We then look for a file named
 317 \(dq.htsn-importrc\(dq in the user's home directory. The latter will
 318 override the former.
 319 .P
 320 The user's home directory is simply $HOME on Unix; on Windows it's
 321 wherever %APPDATA% points. The system configuration directory is
 322 determined by Cabal; the \(dqsysconfdir\(dq parameter during the
 323 \(dqconfigure\(dq step is used.
 324 .P
 325 The file's syntax is given by examples in the htsn-importrc.example file
 326 (included with \fBhtsn-import\fR).
 327 .P
 328 Options specified on the command-line override those in either
 329 configuration file.
 330
 331 .SH EXAMPLES
 332 .IP \[bu] 2
 333 Import newsxml.xml into a preexisting sqlite database named \(dqfoo.sqlite3\(dq:
 334
 335 .nf
 336 .I $ htsn-import --connection-string='foo.sqlite3' \\\\
 337 .I "              test/xml/newsxml.xml"
 338 Successfully imported test/xml/newsxml.xml.
 339 Imported 1 document(s) total.
 340 .fi
 341 .IP \[bu]
 342 Repeat the previous example, but delete newsxml.xml afterwards:
 343
 344 .nf
 345 .I $ htsn-import --connection-string='foo.sqlite3' \\\\
 346 .I "              --remove test/xml/newsxml.xml"
 347 Successfully imported test/xml/newsxml.xml.
 348 Imported 1 document(s) total.
 349 Removed processed file test/xml/newsxml.xml.
 350 .fi
 351 .IP \[bu]
 352 Use a Postgres database instead of the default Sqlite. This assumes
 353 that you have a database named \(dqhtsn\(dq accessible to user
 354 \(dqpostgres\(dq locally:
 355
 356 .nf
 357 .I $ htsn-import --connection-string='dbname=htsn user=postgres' \\\\
 358 .I "              --backend=Postgres test/xml/newsxml.xml"
 359 Successfully imported test/xml/newsxml.xml.
 360 Imported 1 document(s) total.
 361 .fi
 362
 363 .SH BUGS
 364
 365 .P
 366 Send bugs to michael@orlitzky.com.
 367
 368 .SH APPENDIX: SUPPORTED DOCUMENT TYPES
 369 .P
 370 The XML document types obtained from the feed are uniquely identified
 371 by their DTDs. We currently support documents with the following DTDs:
 372 .IP \[bu] 2
 373 AutoRacingResultsXML.dtd
 374 .IP \[bu]
 375 Auto_Racing_Schedule_XML.dtd
 376 .IP \[bu]
 377 Heartbeat.dtd
 378 .IP \[bu]
 379 Injuries_Detail_XML.dtd
 380 .IP \[bu]
 381 injuriesxml.dtd
 382 .IP \[bu]
 383 jfilexml.dtd
 384 .IP \[bu]
 385 newsxml.dtd
 386 .IP \[bu]
 387 Odds_XML.dtd
 388 .IP \[bu]
 389 scoresxml.dtd
 390 .IP \[bu]
 391 weatherxml.dtd
 392 .IP \[bu]
 393 GameInfo
 394 .RS
 395 .IP \[bu] 2
 396 CBASK_Lineup_XML.dtd
 397 .IP \[bu]
 398 cbaskpreviewxml.dtd
 399 .IP \[bu]
 400 cflpreviewxml.dtd
 401 .IP \[bu]
 402 Matchup_NBA_NHL_XML.dtd
 403 .IP \[bu]
 404 MLB_Fielding_XML.dtd
 405 .IP \[bu]
 406 MLB_Gaming_Matchup_XML.dtd
 407 .IP \[bu]
 408 MLB_Lineup_XML.dtd
 409 .IP \[bu]
 410 MLB_Matchup_XML.dtd
 411 .IP \[bu]
 412 MLS_Preview_XML.dtd
 413 .IP \[bu]
 414 mlbpreviewxml.dtd
 415 .IP \[bu]
 416 NBA_Gaming_Matchup_XML.dtd
 417 .IP \[bu]
 418 NBA_Playoff_Matchup_XML.dtd
 419 .IP \[bu]
 420 NBALineupXML.dtd
 421 .IP \[bu]
 422 nbapreviewxml.dtd
 423 .IP \[bu]
 424 NCAA_FB_Preview_XML.dtd
 425 .IP \[bu]
 426 NFL_NCAA_FB_Matchup_XML.dtd
 427 .IP \[bu]
 428 nflpreviewxml.dtd
 429 .IP \[bu]
 430 nhlpreviewxml.dtd
 431 .IP \[bu]
 432 recapxml.dtd
 433 .IP \[bu]
 434 WorldBaseballPreviewXML.dtd
 435 .RE
 436 .IP \[bu]
 437 SportInfo
 438 .RS
 439 .IP \[bu] 2
 440 CBASK_3PPctXML.dtd
 441 .IP \[bu]
 442 Cbask_All_Tourn_Teams_XML.dtd
 443 .IP \[bu]
 444 CBASK_AssistsXML.dtd
 445 .IP \[bu]
 446 Cbask_Awards_XML.dtd
 447 .IP \[bu]
 448 CBASK_BlocksXML.dtd
 449 .IP \[bu]
 450 Cbask_Conf_Standings_XML.dtd
 451 .IP \[bu]
 452 Cbask_DivII_III_Indv_Stats_XML.dtd
 453 .IP \[bu]
 454 Cbask_DivII_Team_Stats_XML.dtd
 455 .IP \[bu]
 456 Cbask_DivIII_Team_Stats_XML.dtd
 457 .IP \[bu]
 458 CBASK_FGPctXML.dtd
 459 .IP \[bu]
 460 CBASK_FoulsXML.dtd
 461 .IP \[bu]
 462 CBASK_FTPctXML.dtd
 463 .IP \[bu]
 464 Cbask_Indv_Scoring_XML.dtd
 465 .IP \[bu]
 466 CBASK_MinutesXML.dtd
 467 .IP \[bu]
 468 Cbask_Polls_XML.dtd
 469 .IP \[bu]
 470 CBASK_ReboundsXML.dtd
 471 .IP \[bu]
 472 CBASK_ScoringLeadersXML.dtd
 473 .IP \[bu]
 474 Cbask_Team_ThreePT_Made_XML.dtd
 475 .IP \[bu]
 476 Cbask_Team_ThreePT_PCT_XML.dtd
 477 .IP \[bu]
 478 Cbask_Team_Win_Pct_XML.dtd
 479 .IP \[bu]
 480 Cbask_Top_Twenty_Five_XML.dtd
 481 .IP \[bu]
 482 CBASK_TopTwentyFiveResult_XML.dtd
 483 .IP \[bu]
 484 Cbask_Tourn_Awards_XML.dtd
 485 .IP \[bu]
 486 Cbask_Tourn_Champs_XML.dtd
 487 .IP \[bu]
 488 Cbask_Tourn_Indiv_XML.dtd
 489 .IP \[bu]
 490 Cbask_Tourn_Leaders_XML.dtd
 491 .IP \[bu]
 492 Cbask_Tourn_MVP_XML.dtd
 493 .IP \[bu]
 494 Cbask_Tourn_Records_XML.dtd
 495 .IP \[bu]
 496 LeagueScheduleXML.dtd
 497 .IP \[bu]
 498 minorscoresxml.dtd
 499 .IP \[bu]
 500 Minor_Baseball_League_Leaders_XML.dtd
 501 .IP \[bu]
 502 Minor_Baseball_Standings_XML.dtd
 503 .IP \[bu]
 504 Minor_Baseball_Transactions_XML.dtd
 505 .IP \[bu]
 506 mlbbattingavgxml.dtd
 507 .IP \[bu]
 508 mlbdoublesleadersxml.dtd
 509 .IP \[bu]
 510 MLBGamesPlayedXML.dtd
 511 .IP \[bu]
 512 MLBGIDPXML.dtd
 513 .IP \[bu]
 514 MLBHitByPitchXML.dtd
 515 .IP \[bu]
 516 mlbhitsleadersxml.dtd
 517 .IP \[bu]
 518 mlbhomerunsxml.dtd
 519 .IP \[bu]
 520 MLBHRFreqXML.dtd
 521 .IP \[bu]
 522 MLBIntWalksXML.dtd
 523 .IP \[bu]
 524 MLBKORateXML.dtd
 525 .IP \[bu]
 526 mlbonbasepctxml.dtd
 527 .IP \[bu]
 528 MLBOPSXML.dtd
 529 .IP \[bu]
 530 MLBPlateAppsXML.dtd
 531 .IP \[bu]
 532 mlbrbisxml.dtd
 533 .IP \[bu]
 534 mlbrunsleadersxml.dtd
 535 .IP \[bu]
 536 MLBSacFliesXML.dtd
 537 .IP \[bu]
 538 MLBSacrificesXML.dtd
 539 .IP \[bu]
 540 MLBSBSuccessXML.dtd
 541 .IP \[bu]
 542 mlbsluggingpctxml.dtd
 543 .IP \[bu]
 544 mlbstandxml.dtd
 545 .IP \[bu]
 546 mlbstandxml_preseason.dtd
 547 .IP \[bu]
 548 mlbstolenbasexml.dtd
 549 .IP \[bu]
 550 mlbtotalbasesleadersxml.dtd
 551 .IP \[bu]
 552 mlbtriplesleadersxml.dtd
 553 .IP \[bu]
 554 MLBWalkRateXML.dtd
 555 .IP \[bu]
 556 mlbwalksleadersxml.dtd
 557 .IP \[bu]
 558 MLBXtraBaseHitsXML.dtd
 559 .IP \[bu]
 560 MLB_Pitching_Appearances_Leaders.dtd
 561 .IP \[bu]
 562 MLB_ERA_Leaders.dtd
 563 .IP \[bu]
 564 MLB_Pitching_Balks_Leaders.dtd
 565 .IP \[bu]
 566 MLB_Pitching_CG_Leaders.dtd
 567 .IP \[bu]
 568 MLB_Pitching_ER_Allowed_Leaders.dtd
 569 .IP \[bu]
 570 MLB_Pitching_Hits_Allowed_Leaders.dtd
 571 .IP \[bu]
 572 MLB_Pitching_Hit_Batters_Leaders.dtd
 573 .IP \[bu]
 574 MLB_Pitching_HR_Allowed_Leaders.dtd
 575 .IP \[bu]
 576 MLB_Pitching_IP_Leaders.dtd
 577 .IP \[bu]
 578 MLB_Pitching_Runs_Allowed_Leaders.dtd
 579 .IP \[bu]
 580 MLB_Pitching_Saves_Leaders.dtd
 581 .IP \[bu]
 582 MLB_Pitching_Shut_Outs_Leaders.dtd
 583 .IP \[bu]
 584 MLB_Pitching_Starts_Leaders.dtd
 585 .IP \[bu]
 586 MLB_Pitching_Strike_Outs_Leaders.dtd
 587 .IP \[bu]
 588 MLB_Pitching_Walks_Leaders.dtd
 589 .IP \[bu]
 590 MLB_Pitching_WHIP_Leaders.dtd
 591 .IP \[bu]
 592 MLB_Pitching_Wild_Pitches_Leaders.dtd
 593 .IP \[bu]
 594 MLB_Pitching_Win_Percentage_Leaders.dtd
 595 .IP \[bu]
 596 MLB_Pitching_WL_Leaders.dtd
 597 .IP \[bu]
 598 NBA_Team_Stats_XML.dtd
 599 .IP \[bu]
 600 NBA3PPctXML.dtd
 601 .IP \[bu]
 602 NBAAssistsXML.dtd
 603 .IP \[bu]
 604 NBABlocksXML.dtd
 605 .IP \[bu]
 606 nbaconfrecxml.dtd
 607 .IP \[bu]
 608 nbadaysxml.dtd
 609 .IP \[bu]
 610 nbadivisionsxml.dtd
 611 .IP \[bu]
 612 NBAFGPctXML.dtd
 613 .IP \[bu]
 614 NBAFoulsXML.dtd
 615 .IP \[bu]
 616 NBAFTPctXML.dtd
 617 .IP \[bu]
 618 NBAMinutesXML.dtd
 619 .IP \[bu]
 620 NBAReboundsXML.dtd
 621 .IP \[bu]
 622 NBAScorersXML.dtd
 623 .IP \[bu]
 624 nbastandxml.dtd
 625 .IP \[bu]
 626 NBAStealsXML.dtd
 627 .IP \[bu]
 628 nbateamleadersxml.dtd
 629 .IP \[bu]
 630 nbatripledoublexml.dtd
 631 .IP \[bu]
 632 NBATurnoversXML.dtd
 633 .IP \[bu]
 634 NCAA_Conference_Schedule_XML.dtd
 635 .IP \[bu]
 636 nflfirstdownxml.dtd
 637 .IP \[bu]
 638 NFLFumbleLeaderXML.dtd
 639 .IP \[bu]
 640 NFLGiveTakeXML.dtd
 641 .IP \[bu]
 642 NFLInside20XML.dtd
 643 .IP \[bu]
 644 NFLKickoffsXML.dtd
 645 .IP \[bu]
 646 NFLMondayNightXML.dtd
 647 .IP \[bu]
 648 NFLPassLeadXML.dtd
 649 .IP \[bu]
 650 NFLQBStartsXML.dtd
 651 .IP \[bu]
 652 NFLSackLeadersXML.dtd
 653 .IP \[bu]
 654 nflstandxml.dtd
 655 .IP \[bu]
 656 NFLTeamRankingsXML.dtd
 657 .IP \[bu]
 658 NFLTopPerformanceXML.dtd
 659 .IP \[bu]
 660 NFLTotalYardageXML.dtd
 661 .IP \[bu]
 662 NFL_KickingLeaders_XML.dtd
 663 .IP \[bu]
 664 NFL_NBA_Draft_XML.dtd
 665 .IP \[bu]
 666 NFL_Roster_XML.dtd
 667 .IP \[bu]
 668 NFL_Team_Stats_XML.dtd
 669 .IP \[bu]
 670 Transactions_XML.dtd
 671 .IP \[bu]
 672 Weekly_Sched_XML.dtd
 673 .IP \[bu]
 674 WNBA_Team_Leaders_XML.dtd
 675 .IP \[bu]
 676 WNBA3PPctXML.dtd
 677 .IP \[bu]
 678 WNBAAssistsXML.dtd
 679 .IP \[bu]
 680 WNBABlocksXML.dtd
 681 .IP \[bu]
 682 WNBAFGPctXML.dtd
 683 .IP \[bu]
 684 WNBAFoulsXML.dtd
 685 .IP \[bu]
 686 WNBAFTPctXML.dtd
 687 .IP \[bu]
 688 WNBAMinutesXML.dtd
 689 .IP \[bu]
 690 WNBAReboundsXML.dtd
 691 .IP \[bu]
 692 WNBAScorersXML.dtd
 693 .IP \[bu]
 694 wnbastandxml.dtd
 695 .IP \[bu]
 696 WNBAStealsXML.dtd
 697 .IP \[bu]
 698 WNBATurnoversXML.dtd
 699 .RE