Glossary
Attribute assertion
A single sourced claim about an attribute value, recording the raw label, raw value, unit, source location, method and review status.
Definition
An attribute assertion is one claim, from one source, about the value of one attribute of one product. The accepted value of an attribute is decided from its assertions; the assertions themselves are kept.
Fields
In the MyBearings draft record envelope each assertion records:
| Field | Purpose |
|---|---|
value, unit | The normalized value and unit |
raw_label, raw_value | Exactly what the source said, before normalization |
source_id | Which source document, feed, listing or file |
source_location | Where in the source: page, table, row or cell |
method | How it was obtained: source extraction, documented rule, human entry, or synthetic demo |
review_status | Unreviewed, rule validated, expert reviewed, or synthetic only |
Why it matters
Keeping assertions separate from the accepted value makes three things possible:
- Traceability. Anyone can see where a value came from and check it.
- Conflict handling. When two assertions disagree, the attribute is marked
conflictingand both are kept until a reviewer decides. - Safe re-processing. If a mapping rule is corrected, affected values can be recomputed from the raw label and value.
Example
Illustrative, synthetic values:
| Assertion | Raw label | Raw value | Value | Unit | Source | Method |
|---|---|---|---|---|---|---|
| 1 | B | 15 | 15 | mm | Supplier file A, row 12 | Source extraction |
| 2 | Width (in) | 0.5906 | 15.0 | mm | Supplier file C, row 3 | Documented rule |
Apply it
See assertions in the draft bearing record schema, read about enrichment with evidence, or discuss your catalog.
Sources
- JSON Schema 2020-12 — Specification used to express the draft assertion structure.
Methodology article using synthetic examples only; it states no manufacturer specifications. Independent technical review: not yet assigned. Found an error? Tell us.
