Summary
Proposing we remove all price fields (msrp_usd and the localized msrp_eur/gbp/inr/aed/aud/cad/vnd/chf) from the schema and data.
Why
The pricing data is unreliable and not worth publishing as-is: For a spec database, an inaccurate price is worse than no price — it misleads users and undermines trust in the rest of the data.
What changes
- Remove the 9
msrp_* fields from schema/camera.schema.json.
- Strip them from the 468 affected camera files.
- Remove price from the website (column, filter, sort, CSV export, compare, detail page, and the
Product/offers structured data).
Open question — future pricing
If we want pricing back later, it should be done properly, e.g.:
- a single, sourced, dated price snapshot per camera (
{ amount, currency, date, source }), rather than 8 loose keys;
Feedback welcome before this is done. Does anyone rely on the current price fields?
Summary
Proposing we remove all price fields (
msrp_usdand the localizedmsrp_eur/gbp/inr/aed/aud/cad/vnd/chf) from the schema and data.Why
The pricing data is unreliable and not worth publishing as-is: For a spec database, an inaccurate price is worse than no price — it misleads users and undermines trust in the rest of the data.
What changes
msrp_*fields fromschema/camera.schema.json.Product/offersstructured data).Open question — future pricing
If we want pricing back later, it should be done properly, e.g.:
{ amount, currency, date, source }), rather than 8 loose keys;Feedback welcome before this is done. Does anyone rely on the current price fields?