Two waist widths can look like a contradiction when their labels disappear. In Rina Nkulu’s condition report for a Boutique Christian Dior Paris dress, one entry is 13.5 inches and another is 12 inches. The difference becomes useful only when each number stays attached to its component. This is a current retrospective reading of the document, which bears the literal date 12/02/2024 and identifies the object as FITGSC.1998.14, circa the late 1950s. The question is how to read those entries together, rather than which one to promote into the dress’s single definitive waist measurement.
| Report field | Reported across-width | Reading scope |
|---|---|---|
| Bodice waistline | 13.5 inches | Component-specific field, not a body circumference |
| Underskirt/dress waistline | 12 inches | Distinct component label; not a correction of the row above |
| Difference between these fields | 1.5 inches | Original subtraction only, not ease or a fit verdict |
Begin with two records, not one disputed number
The report’s measurement list distinguishes the width across the bodice waistline from the width across the underskirt/dress waistline. The former is 13.5 inches; the latter is 12 inches. A note headed simply “waist: 13.5 or 12” would remove the very information that makes the pair intelligible. It turns two labelled fields into competing answers to a question the document has not asked in that form.
A better transcription has a separate row for each component, keeps inches as the unit, and retains “across” as the measurement direction. The table below does that. Its purpose is not to improve or correct the examiner’s record. It preserves the distinctions that a shortened reading note would otherwise lose. The report identifier and literal date keep the two rows connected to the same document without assuming a particular calendar convention for that date.
Read the construction paragraph beside the measurements
The nearby construction account supplies a reason to resist treating the dress as one undifferentiated shell. Nkulu describes a separate sleeveless over-bodice and the main body of the dress, and records a snap-button fastening at CB. These are the report’s attributed construction statements. They give the component labels context without requiring a speculative drawing of the unseen interior.
That is a different operation from reconstructing how every piece meets. A connection between components does not establish that all of their edges have equal dimensions, and the presence of a fastening does not supply a new measurement. The reader can put construction and measurement in conversation while leaving the exact physical relationship unresolved. The two waist entries remain useful even though they do not amount to a pattern, an assembly sequence or a complete inventory of pieces.
What the 1.5-inch difference actually compares
The arithmetic is straightforward: 13.5 minus 12 equals 1.5 inches. The interpretation needs more care. This is a difference between two reported across-width fields with different component labels. Calling it an extra 1.5 inches of room for a wearer would add an unestablished relationship between the recorded garment and a body. Calling it a measurement error would instead assume the two rows should describe the same place in the same way.
Neither assumption is necessary to make the subtraction informative. It tells a reader who has copied both fields that they should not silently collapse them into one. If a later discussion refers to the larger number, ask which component that statement concerns. If someone calls the smaller number the complete dress size, restore its original label before following the argument. The error to catch is the loss of the referent, not the presence of two numbers.
Doubling each value would produce two new arithmetic results, but would not establish two measured circumferences. The report entries used here describe across-widths. Without a separately justified measurement method and a clear question, converting them into an imagined body-fit recommendation would make the record look more complete while making its meaning less secure.
A usable record keeps the names visible
The completed reading record is deliberately compact: object FITGSC.1998.14; examiner Rina Nkulu; literal report date 12/02/2024; two component-labelled rows; and a note that the 1.5-inch subtraction compares those rows only. This allows another reader to follow the comparison without searching for which garment part a detached number once named. It also provides an obvious place to attach a later, properly sourced clarification instead of rewriting the original entry.
Compare that with an attractive but weak caption such as “a tiny Dior waist.” The caption encourages a judgment about a wearer and suppresses the layered object that the report describes. A labelled record invites a more interesting fashion question: how do the named parts relate within the documented construction? That question can remain open while the two reported measurements remain exact. Curiosity about structure need not depend on turning an archival garment into a contemporary sizing example.
Let this document remain a dated examination
This reading uses the retained report text; it does not involve handling the dress or examining its source photographs. The report’s later date is stated plainly here. The measurements belong to Nkulu’s document. Nor does a dated condition report establish the object’s condition today or authorize a repair, fastening test or attempt to reproduce it.
The productive result is a more faithful comparison. Read the measurement label as part of the evidence, not as a caption that can be discarded once the number has been copied. In this case, keeping two component names visible makes a layered construction legible without pretending that two widths explain the whole garment.
Sources & further reading
Published sources for the details and examples discussed in this story.



