Inner diameter
20 mm
numeric · mm
PRESENTREQUIREDAgriculture verticalTechnical attributes
Attribute coverage lab / category record
Build Complete Technical Attribute Sets for Agricultural Parts
Technical attributes are the backbone of a useful agricultural spare-parts catalog.
They distinguish similar products, support filters, describe machine-relevant properties and provide the factual base for product content. ENRIVAQ extracts, normalizes and validates those attributes against category-specific schemas.
Attribute Coverage Instrument / One Category4 OF 9 FIELDS PRESENT
Outer diameter
47 mm
numeric · mm
PRESENTREQUIREDInner-ring height
26 mm
numeric · mm
PRESENTREQUIREDMass
0.2 kg
numeric · kg
PRESENTOPTIONALMaterial
Not source-supported
Research if evidence exists.
GAPREQUIREDCompatibility
Not source-supported
Schema says this field matters.
GAPREQUIREDReference relation
Unresolved
Unresolved until evidence exists.
GAPREQUIREDOptional category field
Not required
Optional for this family.
EMPTYOPTIONALAdditional required field
Open until evidence exists
Blocks complete technical coverage.
GAPREQUIREDCompleteness is a ratio against the category schema, not a count of filled cells.REAL ATTRIBUTE SET: KK053090 reference attribute set
Why attributes matter
Filters, compatibility and buying decisions all depend on structured fields
A customer choosing a technical part may need a dimension, material, pressure rating, connection size or another category-specific specification before the description matters at all.
“Will this part fit the required dimension?”
A paragraph can mention the number but the catalog cannot reliably compare it.
Structured answer
inner_diameter = 20 mm
Queryable for filters, comparison and validation.
“What material is the part made from?”
Free text allows inconsistent names and hard-to-reuse wording.
Structured answer
outer_diameter = 47 mm
One field can support technical comparison and content.
“What pressure rating applies?”
The number must belong to the correct field, unit and product context.
Structured answer
inner_ring_height = 26 mm
Explicit field, not a number floating inside prose.
“Which connection size do I need?”
The catalog cannot filter a connection value that only exists in text.
Structured answer
mass = 0.2 kg
Reusable by people and systems.
DESCRIPTION COMES LASTOnce technical decision fields are explicit, content can explain the product without becoming the only place where facts exist.
Attribute groups
Dimensions, materials, specifications and identifiers
The approved architecture highlights several common attribute groups for agriculture.
These groups are a starting framework, not a universal schema.
Technical Record Anatomy / Common GroupsFRAMEWORK ≠ UNIVERSAL SCHEMA
Dimensions
Physical size and geometry
Category-specific measurements that help distinguish and select the part.
inner_diameterouter_diametermm
Materials
What the part is made from
Use a controlled field where material is relevant to the category.
materialgrade when relevant
Specifications
Category-specific properties
Pressure rating, connection size or another required technical value.
pressure_ratingconnection_sizecategory-specific field
Identifiers
Explicit identity fields
Research and matching do not depend on description text.
MPN / OEMcross-reference
PER FAMILYEach product family defines Required / Optional / Not applicable.REAL SCHEMA: KK053090 reference attribute set
Category-specific schemas
A complete bearing record is not a complete hydraulic-hose record
Attribute completeness has to be measured against the correct product category.
The catalog defines a schema per product family so the workflow knows what information it is trying to complete.
Schema stencil A
Bearing
FIELDS DIFFER BY FAMILYdimensionREQUIRED
materialREQUIRED
identifierOPTIONAL
pressure_ratingN/A
Schema stencil B
Hydraulic hose
OTHER FIELD SETconnection_sizeREQUIRED
pressure_ratingREQUIRED
dimensionREQUIRED
materialOPTIONAL
Schema stencil C
Seeding system components
Identifier · mounting side · length · width · thickness · hole distance · hole diameter · hole countIdentity fieldREQUIRED
Dimension fieldOPTIONAL
Optional category fieldN/A
Compatibility fieldREQUIRED
COMPLETENESS SCORE IS COMPUTED PER CATEGORY
Extraction
Convert technical content into attribute, value and unit
Useful data may be present inside product pages, descriptions, tables or documentation.
Extraction turns that information into explicit fields rather than leaving it inside prose.
Source Microscope / Field ExtractionATTRIBUTE · VALUE · UNIT · SOURCE
Source fragment
“… AC671262 has inner diameter 20 mm, outer diameter 47 mm, inner-ring height 26 mm and mass 0.2 kg …”
EXTRACT
+
PIN SOURCE
+
PIN SOURCE
Explicit fields
Every field keeps a pointer back to the fragment it came from, so a reviewer can check it.
Normalization
Use one representation across similar products
The target schema decides the representation. Normalization keeps filters and comparisons from treating one technical meaning as several values.
The Case That Breaks a FilterTARGET SCHEMA DECIDES
Before normalization
One meaning becomes several filter values
4.2 cm42 mm42
Outer ØODOuter diameter
NORMALIZE
After normalization
One field, one catalog representation
42 mm
outer_dimension
4.2 cm is the same size as 42 mm. They must not become separate meanings when the catalog schema requires millimeters.
Validation
A filled field still needs to belong to the right product
An extracted value can be formatted correctly and still be wrong for the product variant. Uncertain information remains visible for review.
Candidate technical value
47 mm
Formatting is correct. Acceptance is not automatic.
Product context
Does it belong to this exact product or variant?
Identity and category context must agree.
PASS → CONTINUESource conflict
Do independent sources disagree?
Correct formatting cannot resolve conflicting evidence.
CONFLICT → REVIEWSchema fit
Is this field valid for the target category?
The value must belong to the approved schema.
PASS → ACCEPTABLEACCEPTEDVISIBLE FOR REVIEWUNRESOLVED
Formatted correctly does not mean accepted. Product context, conflicts and schema fit decide the route.
Real attribute table
Show a category-specific before and after table
This is a real product-data table, not a decorative infographic.
Required Attribute / Before / After / ChangeSLOTS FOR REAL DATA
| Required attribute | Before enrichment | After enrichment | Change |
|---|---|---|---|
| Inner diameter | Unstructured/source-specific field | Canonical attribute/value/unit | ADDED |
| Outer diameter | Unstructured/source-specific field | Canonical attribute/value/unit | UNCHANGED |
| Inner-ring height | Unstructured/source-specific field | Canonical attribute/value/unit | NORMALIZED |
| Mass | Unstructured/source-specific field | Canonical attribute/value/unit | REVIEW |
| Material | Unstructured/source-specific field | Canonical attribute/value/unit | ADDED |
| Compatibility | Unstructured/source-specific field | Canonical attribute/value/unit | UNCHANGED |
| Reference relation | Unstructured/source-specific field | Canonical attribute/value/unit | UNRESOLVED |
Use real category-specific product data before publication.ATTRIBUTE COVERAGE BEFORE / AFTER: KK053090 reference attribute set
Controlled next step
Measure the attribute gap in one product family
One family, one schema, one coverage figure — that is enough to see where enrichment pays off.