This reference uses the specific documents linked in the article and listed below. Check their scope, publication dates and the statements they support.
Decide what one entry represents
A timeline entry can represent an observation, a document's publication, an official statement or a correction to an earlier account. Name the entry type before choosing its date. One row called “disease update” can otherwise mix several actions that occurred on different days.
Give the event a stable identifier and the account a revision identifier. Keep a short description, original date wording, date precision, source reference and correction relationship. A revision may describe the same underlying event; it does not automatically add another event to the historical total.
Generate the display and download together
Use the same approved records for the HTML sequence and the CSV or JSON export. Avoid maintaining a separate hand-edited list of dates in the article. Two independent lists can drift when a source is corrected or a caption is shortened.
The public view should retain a readable label for every date. Internally, separate event occurrence, source publication and local recording dates. If a statement has an explicitly documented effective period, keep that period in its own fields. A newly entered account of an old event belongs to the old event's chronology while remaining visible in the site's revision history.
Keep incomplete dates incomplete
The HTML time element supports machine-readable month and date representations. An illustrative month-only entry can use <time datetime="2018-03">March 2018</time>. That markup does not prove the underlying date; the source still determines its precision.
For a range, show the supported interval in ordinary language and store its boundaries with a precision label. Do not invent a first-day occurrence to make sorting convenient. If the system uses a boundary as a sort key, keep that implementation value out of the public event-date field.
Work through a late correction
Consider a fictional bulletin published on April 10 describing observations “during March.” The site records it on May 2. A later document corrects a count on June 6 without narrowing the occurrence date.
The historical entry remains March, with month precision. April 10 remains the bulletin's publication date. May 2 records the local addition. June 6 creates a correction entry linked to the original statement. A release note explains the changed count; neither the addition nor correction is presented as a new June outbreak.
This example is a record-design exercise. It supplies no animal-health event, agency declaration or confirmed count for reuse as factual data.
Make the sequence readable without a chart
Start with a heading that identifies the subject and historical coverage. Use a list or table that includes date wording, event description and source. Readers should reach the same facts when a visual timeline is unavailable or the page is printed.
Keep each source link beside the statement it supports. If a graphic compresses several entries, provide the individual records below it. Avoid color as the only distinction between an occurrence, publication and correction. Include text labels so a black-and-white copy remains interpretable.
Inspect a finished release
Compare several rendered entries with the exported rows, including an uncertain date, a correction and an ordinary dated event. Check IDs, ordering, counts and source links. Confirm that a link to one entry still reaches the same record after a new entry is inserted.
Publish the revision date as the page's revision, separate from its historical coverage. Use the timeline correction guide to preserve changed accounts and the uncertain-date guide to decide what the evidence permits the date field to say.
Preserve an entry's identity when the display changes
A timeline can be sorted, filtered or redesigned without creating new historical events. Keep stable entry identifiers and link correction records to them. If a visual redesign changes the displayed order of uncertain dates, explain the ordering rule rather than silently increasing their apparent precision.
In a second fictional release, two month-only entries share a sort key. An importer assigns successive day numbers to make the chart look orderly. The correction restores month precision and uses a separate internal tie-breaker. Readers see an honest unresolved order rather than invented event dates.
Questions before publishing a timeline
Is the page's revision date an event date?
Keep it separate from the historical entries. A newly revised account can describe old events, and a correction can change the account without representing another occurrence.
Should a visual chart be the only record?
Provide a readable sequence or table with source links and uncertainty visible. A download should match the same approved records. Readers need a way to inspect entries even when the visual display is unavailable.
How can an amended count be checked?
Link the correction to the affected entry, preserve the source and compare the rendered sequence with the exported data. State what the count measures. A revised total should not count both the original account and its correction as independent events.
Cite this reference
LivestockDefense. “Publish a historical animal-health timeline readers can inspect.” Updated 2026-11-03. https://livestockdefense.com/guides/publishing-historical-animal-health-events-as-static-timelines/
Add the date you accessed the page. This identifies the current reference; keep a permitted saved copy if your work depends on its exact wording. A citation alone does not establish support for a claim.
How to cite a page and its revision ↗Sources & boundaries
Read the evidence in context.
These documents support the statements identified in this reference. Check their scope and dates when deciding whether they answer your question.
- WHATWG: HTML Standard: the time element
Source update: 2026-10-26. Most recent check: 2026-10-29.
HTML time element and supported machine-readable date/month formats; does not establish historical event dates or uncertainty models.