XML Standards for Pipe Tobacco Applications

XML standards for pipe tobacco applications are a set of open schemas proposed to prevent the records enthusiasts have accumulated over the years from being locked inside a single program. The problem they try to solve is a familiar one: a list of jars in a cellar, the measurement data of a collection, or hundreds of smoking notes can become inaccessible once the program used to record them is abandoned or loses support. A shared file format allows the same data to be exported and reopened in another tool. The schemas are published on the site of ThePipeTool, which presents itself as an open-format initiative; as of September 2025, all three are at version 1.0 and each is offered as its own XSD file along with a sample XML file.

The Inventory Side

Two legs of the set deal directly with cataloging. The pipe inventory schema records the profile of each individual pipe: brand, carver, model and model number, stamp, shape, finish, mouthpiece material, country of origin, and dates of manufacture and acquisition. Measurements are gathered into a separate internal structure — length, bowl height, outer diameter, bowl diameter, bowl depth, and weight — so they remain orderable without mixing into free text. A separate notes block, meanwhile, carries which blend the pipe has been set aside for and its current status (for example, resting).

The tobacco inventory schema is for the cellar. It includes fields for blend name and brand, country, weight, storage form and quantity, batch number, the party that prepared the blend, dates of production and acquisition, condition, and short notes. These fields make it possible to trace retrospectively which batch was jarred when during tobacco aging.

The Review Side

The third schema is the counterpart of a tasting journal. Context fields — parent brand, brand, blend, place of purchase, the pipe used for the smoke, even that day's weather — come together with more than twenty rating fields. Headings such as depth, complexity, sweetness, and room note are graded from one to five; a free-text comment field and an overall score round these out. Because the blend's contents and tobacco cuts are entered as multiple selections, the same record can list Virginia alongside Latakia; similar flexibility exists on the pipe side too, where a pipe combining briar and bamboo in its body can report both materials at once.

Scope and Limits

Leaving nearly all the fields optional is a deliberate choice: a user with incomplete information can still produce a valid file. The fact that names such as brand, blend, and status appear in a similar form across all three schemas makes it easier to attach a review to a particular jar and to the pipe used that day. The files can be validated with common tools that support XSD, and the schema can be extended when needed.

Even so, the text leaves the impression of a draft. All three schemas' namespaces are defined under the example address example.org, reserved for illustrative purposes; this signals that no permanent identity has been assigned. When the schemas were first published and by whom is not explained. Nor is there consistency in the date fields: one schema expects the ISO-8601 format, while the others use readable month-day-year notation. Even so, for collectors who take record-keeping seriously, such a shared format is considered the most practical route toward making data outlive any single application.