]> gitweb.michael.orlitzky.com - dead/htsn-import.git/blob - doc/man1/htsn-import.1
Change the AutoRacingResults track length to a String (yeah).
[dead/htsn-import.git] / 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 NULL POLICY
110 .P
111 Normally in a database one makes a distinction between fields that
112 simply don't exist, and those fields that are
113 \(dqempty\(dq. Translating from XML, there is a natural way to
114 determine which one should be used: if an element is present in the
115 XML document but its contents are empty, then an empty string should
116 be inserted into the corresponding field. If on the other hand the
117 element is missing entirely, the corresponding database entry should
118 be NULL to indicate that fact.
119 .P
120 This sounds well and good, but the XML must be consistent for the
121 database consumer to make any sense of what he sees. The feed XML uses
122 optional and blank elements interchangeably, and without any
123 discernable pattern. To propagate this pattern into the database would
124 only cause confusion.
125 .P
126 As a result, a policy was adopted: both optional elements and elements
127 whose contents can be empty will be considered nullable in the
128 database. If the element is missing, the corresponding field is
129 NULL. Likewise if the content is simply missing. That means there
130 should never be a (completely) empty string in a database column.
131
132 .SH XML SCHEMA GENERATION
133 .P
134 In order to parse XML, you need to know the structure of your
135 documents. Usually this is given in the form of a DTD or schema. The
136 Sports Network does provide DTDs for their XML, but unfortunately many
137 of them do not match the XML found on the feed.
138 .P
139 We need to construct a database into which to insert the XML. How do
140 we know if <game> should be a column, or if it should have its own
141 table? We need to know how many times it can appear in the
142 document. So we need some form of specification. Since the supplied
143 DTDs are incorrect, we would like to generate them automatically.
144 .P
145 The process should go something like,
146 .IP 1.
147 Generate a DTD from the first foo.xml file we see. Call it foo.dtd.
148 .IP 2.
149 Validate future foo documents against foo.dtd. If they all validate,
150 great. If one fails, add it to the corpus and update foo.dtd so
151 that both the original and the new foo.xml validate.
152 .IP 3.
153 Repeat until no more failures occur. This can never be perfect:
154 tomorrow we could get a foo.xml that's wildly different from what
155 we've seen in the past. But it's the best we can hope for under
156 the circumstances.
157 .P
158 Enter XML-Schema-learner
159 <https://github.com/kore/XML-Schema-learner>. This tool can infer a
160 DTD from a set of sample XML files. The top-level \(dqschemagen\(dq
161 folder (in this project) contains a number of subfolders\(emone for
162 each type of document that we want to parse. Contained therein are XML
163 samples for that particular document type. These were hand-picked one
164 at a time according to the procedure above, and the complete set of
165 XML is what we use to generate the DTDs used by htsn-import.
166 .P
167 To generate them, run `make schema` at the project
168 root. XML-Schema-learner will be invoked on each subfolder of
169 \(dqschemagen\(dq and will output the corresponding DTDs to the
170 \(dqschemagen\(dq folder.
171 .P
172 Most of the production schemas are generated this way; however, a few
173 needed manual tweaking. The final, believed-to-be-correct schemas for
174 all supported document types can be found in the \(dqschema\(dq folder in
175 the project root. Having the correct DTDs available means you
176 don't need XML-Schema-learner available to install \fBhtsn-import\fR.
177
178 .SH XML SCHEMA UPDATES
179 .P
180 If a new tag is added to an XML document type, \fBhtsn-import\fR will
181 most likely refuse to parse it, since the new documents no longer
182 match the existing DTD.
183 .P
184 The first thing to do in that case is add the unparseable document to
185 the \(dqschemagen\(dq directory, and generate a new DTD that matches
186 both the old and new samples. Once a new, correct DTD has been
187 generated, it should be added to the \(dqschema\(dq directory. Then,
188 the parser can be updated and \fBhtsn-import\fR rebuilt.
189 .P
190 At this point, \fBhtsn-import\fR should be capable of importing the
191 new document. But the addition of the new tag will most require new
192 fields in the database. Fortunately, easy migrations like this are
193 handled automatically. As an example, at one point, \fIOdds_XML.dtd\fR
194 did not contain the \(dqHStarter\(dq and \(dqAStarter\(dq elements
195 associated with its games. Suppose we parse one of the old documents
196 (without \(dqHStarter\(dq and \(dqAStarter\(dq) using an old version
197 of \fBhtsn-import\fR:
198 .P
199 .nf
200 .I $ htsn-import --connection-string='foo.sqlite3' \\\\
201 .I " schemagen/Odds_XML/19996433.xml"
202 Migration: CREATE TABLE \(dqodds\(dq ...
203 Successfully imported schemagen/Odds_XML/19996433.xml.
204 Processed 1 document(s) total.
205 .fi
206 .P
207 At this point, the database schema matches the old documents, i.e. the
208 ones without \fIAStarter\fR and \fIHStarter\fR. If we use a new
209 version of \fBhtsn-import\fR, supporting the new fields, the migration
210 is handled gracefully:
211 .P
212 .nf
213 .I $ htsn-import --connection-string='foo.sqlite3' \\\\
214 .I " schemagen/Odds_XML/21315768.xml"
215 Migration: ALTER TABLE \(dqodds_games\(dq
216 ADD COLUMN \(dqaway_team_starter_id\(dq INTEGER;
217 Migration: ALTER TABLE \(dqodds_games\(dq
218 ADD COLUMN \(dqaway_team_starter_name\(dq VARCHAR;
219 Migration: ALTER TABLE \(dqodds_games\(dq
220 ADD COLUMN \(dqhome_team_starter_id\(dq INTEGER;
221 Migration: ALTER TABLE \(dqodds_games\(dq
222 ADD COLUMN \(dqhome_team_starter_name\(dq VARCHAR;
223 Successfully imported schemagen/Odds_XML/21315768.xml.
224 Processed 1 document(s) total.
225 .fi
226 .P
227 If fields are removed from the schema, then manual intervention may be
228 necessary:
229 .P
230 .nf
231 .I $ htsn-import -b Postgres -c 'dbname=htsn user=postgres' \\\\
232 .I " schemagen/Odds_XML/19996433.xml"
233 ERROR: Database migration: manual intervention required.
234 The following actions are considered unsafe:
235 ALTER TABLE \(dqodds_games\(dq DROP COLUMN \(dqaway_team_starter_id\(dq
236 ALTER TABLE \(dqodds_games\(dq DROP COLUMN \(dqaway_team_starter_name\(dq
237 ALTER TABLE \(dqodds_games\(dq DROP COLUMN \(dqhome_team_starter_id\(dq
238 ALTER TABLE \(dqodds_games\(dq DROP COLUMN \(dqhome_team_starter_name\(dq
239
240 ERROR: Failed to import file schemagen/Odds_XML/19996433.xml.
241 Processed 0 document(s) total.
242 .fi
243 .P
244 To fix these errors, manually invoke the SQL commands that were
245 considered unsafe:
246 .P
247 .nf
248 .I $ psql -U postgres -d htsn \\\\
249 .I " -c 'ALTER TABLE odds_games DROP COLUMN away_team_starter_id;'"
250 ALTER TABLE
251 .I $ psql -U postgres -d htsn \\\\
252 .I " -c 'ALTER TABLE odds_games DROP COLUMN away_team_starter_name;'"
253 ALTER TABLE
254 .I $ psql -U postgres -d htsn \\\\
255 .I " -c 'ALTER TABLE odds_games DROP COLUMN home_team_starter_id;'"
256 ALTER TABLE
257 .I $ psql -U postgres -d htsn \\\\
258 .I " -c 'ALTER TABLE odds_games DROP COLUMN home_team_starter_name;'"
259 ALTER TABLE
260 .fi
261 .P
262 After manually adjusting the schema, the import should succeed.
263
264 .SH XML SCHEMA ODDITIES
265 .P
266 There are a number of problems with the XML on the wire. Even if we
267 construct the DTDs ourselves, the results are sometimes
268 inconsistent. Here we document a few of them.
269
270 .IP \[bu] 2
271 \fIOdds_XML.dtd\fR
272
273 The <Notes> elements here are supposed to be associated with a set of
274 <Game> elements, but since the pair
275 (<Notes>...</Notes><Game>...</Game>) can appear zero or more times,
276 this leads to ambiguity in parsing. We therefore ignore the notes
277 entirely (although a hack is employed to facilitate parsing). The same
278 thing goes for the newer <League_Name> element.
279
280 .IP \[bu]
281 \fIweatherxml.dtd\fR
282
283 There appear to be two types of weather documents; the first has
284 <listing> contained within <forecast> and the second has <forecast>
285 contained within <listing>. While it would be possible to parse both,
286 it would greatly complicate things. The first form is more common, so
287 that's all we support for now. An example is provided as
288 schemagen/weatherxml/20143655.xml.
289
290 .SH DEPLOYMENT
291 .P
292 When deploying for the first time, the target database will most
293 likely be empty. The schema will be migrated when a new document type
294 is seen, but this has a downside: it can be months before every
295 supported document type has been seen once. This can make it difficult
296 to test the database permissions.
297 .P
298 Since all of the test XML documents have old timestamps, one easy
299 workaround is the following: simply import all of the test XML
300 documents, and then delete them using whatever script is used to prune
301 old entries. This will force the migration of the schema, after which
302 you can set and test the database permissions.
303 .P
304 Something as simple as,
305 .P
306 .nf
307 .I $ find ./test/xml -iname '*.xml' | xargs htsn-import -c foo.sqlite
308 .fi
309 .P
310 should do it.
311
312 .SH OPTIONS
313
314 .IP \fB\-\-backend\fR,\ \fB\-b\fR
315 The RDBMS backend to use. Valid choices are \fISqlite\fR and
316 \fIPostgres\fR. Capitalization is important, sorry.
317
318 Default: Sqlite
319
320 .IP \fB\-\-connection-string\fR,\ \fB\-c\fR
321 The connection string used for connecting to the database backend
322 given by the \fB\-\-backend\fR option. The default is appropriate for
323 the \fISqlite\fR backend.
324
325 Default: \(dq:memory:\(dq
326
327 .IP \fB\-\-log-file\fR
328 If you specify a file here, logs will be written to it (possibly in
329 addition to syslog). Can be either a relative or absolute path. It
330 will not be auto-rotated; use something like logrotate for that.
331
332 Default: none
333
334 .IP \fB\-\-log-level\fR
335 How verbose should the logs be? We log notifications at four levels:
336 DEBUG, INFO, WARN, and ERROR. Specify the \(dqmost boring\(dq level of
337 notifications you would like to receive (in all-caps); more
338 interesting notifications will be logged as well. The debug output is
339 extremely verbose and will not be written to syslog even if you try.
340
341 Default: INFO
342
343 .IP \fB\-\-remove\fR,\ \fB\-r\fR
344 Remove successfully processed files. If you enable this, you can see
345 at a glance which XML files are not being processed, because they're
346 all that should be left.
347
348 Default: disabled
349
350 .IP \fB\-\-syslog\fR,\ \fB\-s\fR
351 Enable logging to syslog. On Windows this will attempt to communicate
352 (over UDP) with a syslog daemon on localhost, which will most likely
353 not work.
354
355 Default: disabled
356
357 .SH CONFIGURATION FILE
358 .P
359 Any of the command-line options mentioned above can be specified in a
360 configuration file instead. We first look for \(dqhtsn-importrc\(dq in
361 the system configuration directory. We then look for a file named
362 \(dq.htsn-importrc\(dq in the user's home directory. The latter will
363 override the former.
364 .P
365 The user's home directory is simply $HOME on Unix; on Windows it's
366 wherever %APPDATA% points. The system configuration directory is
367 determined by Cabal; the \(dqsysconfdir\(dq parameter during the
368 \(dqconfigure\(dq step is used.
369 .P
370 The file's syntax is given by examples in the htsn-importrc.example file
371 (included with \fBhtsn-import\fR).
372 .P
373 Options specified on the command-line override those in either
374 configuration file.
375
376 .SH EXAMPLES
377 .IP \[bu] 2
378 Import newsxml.xml into a preexisting sqlite database named \(dqfoo.sqlite3\(dq:
379
380 .nf
381 .I $ htsn-import --connection-string='foo.sqlite3' \\\\
382 .I " test/xml/newsxml.xml"
383 Successfully imported test/xml/newsxml.xml.
384 Imported 1 document(s) total.
385 .fi
386 .IP \[bu]
387 Repeat the previous example, but delete newsxml.xml afterwards:
388
389 .nf
390 .I $ htsn-import --connection-string='foo.sqlite3' \\\\
391 .I " --remove test/xml/newsxml.xml"
392 Successfully imported test/xml/newsxml.xml.
393 Imported 1 document(s) total.
394 Removed processed file test/xml/newsxml.xml.
395 .fi
396 .IP \[bu]
397 Use a Postgres database instead of the default Sqlite. This assumes
398 that you have a database named \(dqhtsn\(dq accessible to user
399 \(dqpostgres\(dq locally:
400
401 .nf
402 .I $ htsn-import --connection-string='dbname=htsn user=postgres' \\\\
403 .I " --backend=Postgres test/xml/newsxml.xml"
404 Successfully imported test/xml/newsxml.xml.
405 Imported 1 document(s) total.
406 .fi
407
408 .SH BUGS
409
410 .P
411 Send bugs to michael@orlitzky.com.
412
413 .SH APPENDIX: SUPPORTED DOCUMENT TYPES
414 .P
415 The XML document types obtained from the feed are uniquely identified
416 by their DTDs. We currently support documents with the following DTDs:
417 .IP \[bu] 2
418 AutoRacingResultsXML.dtd
419 .IP \[bu]
420 Auto_Racing_Schedule_XML.dtd
421 .IP \[bu]
422 Heartbeat.dtd
423 .IP \[bu]
424 Injuries_Detail_XML.dtd
425 .IP \[bu]
426 injuriesxml.dtd
427 .IP \[bu]
428 jfilexml.dtd
429 .IP \[bu]
430 newsxml.dtd
431 .IP \[bu]
432 Odds_XML.dtd
433 .IP \[bu]
434 Schedule_Changes_XML.dtd
435 .IP \[bu]
436 scoresxml.dtd
437 .IP \[bu]
438 weatherxml.dtd
439 .IP \[bu]
440 GameInfo
441 .RS
442 .IP \[bu] 2
443 CBASK_Lineup_XML.dtd
444 .IP \[bu]
445 cbaskpreviewxml.dtd
446 .IP \[bu]
447 cflpreviewxml.dtd
448 .IP \[bu]
449 Matchup_NBA_NHL_XML.dtd
450 .IP \[bu]
451 MLB_Fielding_XML.dtd
452 .IP \[bu]
453 MLB_Gaming_Matchup_XML.dtd
454 .IP \[bu]
455 MLB_Lineup_XML.dtd
456 .IP \[bu]
457 MLB_Matchup_XML.dtd
458 .IP \[bu]
459 MLS_Preview_XML.dtd
460 .IP \[bu]
461 mlbpreviewxml.dtd
462 .IP \[bu]
463 NBA_Gaming_Matchup_XML.dtd
464 .IP \[bu]
465 NBA_Playoff_Matchup_XML.dtd
466 .IP \[bu]
467 NBALineupXML.dtd
468 .IP \[bu]
469 nbapreviewxml.dtd
470 .IP \[bu]
471 NCAA_FB_Preview_XML.dtd
472 .IP \[bu]
473 NFL_NCAA_FB_Matchup_XML.dtd
474 .IP \[bu]
475 nflpreviewxml.dtd
476 .IP \[bu]
477 nhlpreviewxml.dtd
478 .IP \[bu]
479 recapxml.dtd
480 .IP \[bu]
481 WorldBaseballPreviewXML.dtd
482 .RE
483 .IP \[bu]
484 SportInfo
485 .RS
486 .IP \[bu] 2
487 CBASK_3PPctXML.dtd
488 .IP \[bu]
489 Cbask_All_Tourn_Teams_XML.dtd
490 .IP \[bu]
491 CBASK_AssistsXML.dtd
492 .IP \[bu]
493 Cbask_Awards_XML.dtd
494 .IP \[bu]
495 CBASK_BlocksXML.dtd
496 .IP \[bu]
497 Cbask_Conf_Standings_XML.dtd
498 .IP \[bu]
499 Cbask_DivII_III_Indv_Stats_XML.dtd
500 .IP \[bu]
501 Cbask_DivII_Team_Stats_XML.dtd
502 .IP \[bu]
503 Cbask_DivIII_Team_Stats_XML.dtd
504 .IP \[bu]
505 CBASK_FGPctXML.dtd
506 .IP \[bu]
507 CBASK_FoulsXML.dtd
508 .IP \[bu]
509 CBASK_FTPctXML.dtd
510 .IP \[bu]
511 Cbask_Indv_Scoring_XML.dtd
512 .IP \[bu]
513 CBASK_MinutesXML.dtd
514 .IP \[bu]
515 Cbask_Polls_XML.dtd
516 .IP \[bu]
517 CBASK_ReboundsXML.dtd
518 .IP \[bu]
519 CBASK_ScoringLeadersXML.dtd
520 .IP \[bu]
521 Cbask_Team_ThreePT_Made_XML.dtd
522 .IP \[bu]
523 Cbask_Team_ThreePT_PCT_XML.dtd
524 .IP \[bu]
525 Cbask_Team_Win_Pct_XML.dtd
526 .IP \[bu]
527 Cbask_Top_Twenty_Five_XML.dtd
528 .IP \[bu]
529 CBASK_TopTwentyFiveResult_XML.dtd
530 .IP \[bu]
531 Cbask_Tourn_Awards_XML.dtd
532 .IP \[bu]
533 Cbask_Tourn_Champs_XML.dtd
534 .IP \[bu]
535 Cbask_Tourn_Indiv_XML.dtd
536 .IP \[bu]
537 Cbask_Tourn_Leaders_XML.dtd
538 .IP \[bu]
539 Cbask_Tourn_MVP_XML.dtd
540 .IP \[bu]
541 Cbask_Tourn_Records_XML.dtd
542 .IP \[bu]
543 LeagueScheduleXML.dtd
544 .IP \[bu]
545 minorscoresxml.dtd
546 .IP \[bu]
547 Minor_Baseball_League_Leaders_XML.dtd
548 .IP \[bu]
549 Minor_Baseball_Standings_XML.dtd
550 .IP \[bu]
551 Minor_Baseball_Transactions_XML.dtd
552 .IP \[bu]
553 mlbbattingavgxml.dtd
554 .IP \[bu]
555 mlbdoublesleadersxml.dtd
556 .IP \[bu]
557 MLBGamesPlayedXML.dtd
558 .IP \[bu]
559 MLBGIDPXML.dtd
560 .IP \[bu]
561 MLBHitByPitchXML.dtd
562 .IP \[bu]
563 mlbhitsleadersxml.dtd
564 .IP \[bu]
565 mlbhomerunsxml.dtd
566 .IP \[bu]
567 MLBHRFreqXML.dtd
568 .IP \[bu]
569 MLBIntWalksXML.dtd
570 .IP \[bu]
571 MLBKORateXML.dtd
572 .IP \[bu]
573 mlbonbasepctxml.dtd
574 .IP \[bu]
575 MLBOPSXML.dtd
576 .IP \[bu]
577 MLBPlateAppsXML.dtd
578 .IP \[bu]
579 mlbrbisxml.dtd
580 .IP \[bu]
581 mlbrunsleadersxml.dtd
582 .IP \[bu]
583 MLBSacFliesXML.dtd
584 .IP \[bu]
585 MLBSacrificesXML.dtd
586 .IP \[bu]
587 MLBSBSuccessXML.dtd
588 .IP \[bu]
589 mlbsluggingpctxml.dtd
590 .IP \[bu]
591 mlbstandxml.dtd
592 .IP \[bu]
593 mlbstandxml_preseason.dtd
594 .IP \[bu]
595 mlbstolenbasexml.dtd
596 .IP \[bu]
597 mlbtotalbasesleadersxml.dtd
598 .IP \[bu]
599 mlbtriplesleadersxml.dtd
600 .IP \[bu]
601 MLBWalkRateXML.dtd
602 .IP \[bu]
603 mlbwalksleadersxml.dtd
604 .IP \[bu]
605 MLBXtraBaseHitsXML.dtd
606 .IP \[bu]
607 MLB_Pitching_Appearances_Leaders.dtd
608 .IP \[bu]
609 MLB_ERA_Leaders.dtd
610 .IP \[bu]
611 MLB_Pitching_Balks_Leaders.dtd
612 .IP \[bu]
613 MLB_Pitching_CG_Leaders.dtd
614 .IP \[bu]
615 MLB_Pitching_ER_Allowed_Leaders.dtd
616 .IP \[bu]
617 MLB_Pitching_Hits_Allowed_Leaders.dtd
618 .IP \[bu]
619 MLB_Pitching_Hit_Batters_Leaders.dtd
620 .IP \[bu]
621 MLB_Pitching_HR_Allowed_Leaders.dtd
622 .IP \[bu]
623 MLB_Pitching_IP_Leaders.dtd
624 .IP \[bu]
625 MLB_Pitching_Runs_Allowed_Leaders.dtd
626 .IP \[bu]
627 MLB_Pitching_Saves_Leaders.dtd
628 .IP \[bu]
629 MLB_Pitching_Shut_Outs_Leaders.dtd
630 .IP \[bu]
631 MLB_Pitching_Starts_Leaders.dtd
632 .IP \[bu]
633 MLB_Pitching_Strike_Outs_Leaders.dtd
634 .IP \[bu]
635 MLB_Pitching_Walks_Leaders.dtd
636 .IP \[bu]
637 MLB_Pitching_WHIP_Leaders.dtd
638 .IP \[bu]
639 MLB_Pitching_Wild_Pitches_Leaders.dtd
640 .IP \[bu]
641 MLB_Pitching_Win_Percentage_Leaders.dtd
642 .IP \[bu]
643 MLB_Pitching_WL_Leaders.dtd
644 .IP \[bu]
645 NBA_Team_Stats_XML.dtd
646 .IP \[bu]
647 NBA3PPctXML.dtd
648 .IP \[bu]
649 NBAAssistsXML.dtd
650 .IP \[bu]
651 NBABlocksXML.dtd
652 .IP \[bu]
653 nbaconfrecxml.dtd
654 .IP \[bu]
655 nbadaysxml.dtd
656 .IP \[bu]
657 nbadivisionsxml.dtd
658 .IP \[bu]
659 NBAFGPctXML.dtd
660 .IP \[bu]
661 NBAFoulsXML.dtd
662 .IP \[bu]
663 NBAFTPctXML.dtd
664 .IP \[bu]
665 NBAMinutesXML.dtd
666 .IP \[bu]
667 NBAReboundsXML.dtd
668 .IP \[bu]
669 NBAScorersXML.dtd
670 .IP \[bu]
671 nbastandxml.dtd
672 .IP \[bu]
673 NBAStealsXML.dtd
674 .IP \[bu]
675 nbateamleadersxml.dtd
676 .IP \[bu]
677 nbatripledoublexml.dtd
678 .IP \[bu]
679 NBATurnoversXML.dtd
680 .IP \[bu]
681 NCAA_Conference_Schedule_XML.dtd
682 .IP \[bu]
683 nflfirstdownxml.dtd
684 .IP \[bu]
685 NFLFumbleLeaderXML.dtd
686 .IP \[bu]
687 NFLGiveTakeXML.dtd
688 .IP \[bu]
689 NFLInside20XML.dtd
690 .IP \[bu]
691 NFLKickoffsXML.dtd
692 .IP \[bu]
693 NFLMondayNightXML.dtd
694 .IP \[bu]
695 NFLPassLeadXML.dtd
696 .IP \[bu]
697 NFLQBStartsXML.dtd
698 .IP \[bu]
699 NFLSackLeadersXML.dtd
700 .IP \[bu]
701 nflstandxml.dtd
702 .IP \[bu]
703 NFLTeamRankingsXML.dtd
704 .IP \[bu]
705 NFLTopPerformanceXML.dtd
706 .IP \[bu]
707 NFLTotalYardageXML.dtd
708 .IP \[bu]
709 NFL_KickingLeaders_XML.dtd
710 .IP \[bu]
711 NFL_NBA_Draft_XML.dtd
712 .IP \[bu]
713 NFL_Roster_XML.dtd
714 .IP \[bu]
715 NFL_Team_Stats_XML.dtd
716 .IP \[bu]
717 Transactions_XML.dtd
718 .IP \[bu]
719 Weekly_Sched_XML.dtd
720 .IP \[bu]
721 WNBA_Team_Leaders_XML.dtd
722 .IP \[bu]
723 WNBA3PPctXML.dtd
724 .IP \[bu]
725 WNBAAssistsXML.dtd
726 .IP \[bu]
727 WNBABlocksXML.dtd
728 .IP \[bu]
729 WNBAFGPctXML.dtd
730 .IP \[bu]
731 WNBAFoulsXML.dtd
732 .IP \[bu]
733 WNBAFTPctXML.dtd
734 .IP \[bu]
735 WNBAMinutesXML.dtd
736 .IP \[bu]
737 WNBAReboundsXML.dtd
738 .IP \[bu]
739 WNBAScorersXML.dtd
740 .IP \[bu]
741 wnbastandxml.dtd
742 .IP \[bu]
743 WNBAStealsXML.dtd
744 .IP \[bu]
745 WNBATurnoversXML.dtd
746 .RE