Caribe Scout
REES v0.2 · draft

Changelog & proposals

REES changes in the open. Versions are permanent: a feed that is valid against v0.1 stays valid against v0.1 forever.

Versioning

  • Each version has its own schema URL, e.g. /standard/rees/v0.2/schema.json. Published schemas are never edited — our tests fail if anyone tries.
  • Each feed declares its version in rees and is judged by that version's rules.
  • 0.x versions are drafts. 1.0 will be the first stable version; after it, minor versions only add optional fields.
  • Amenity codes are permanent: never renamed, never removed.

v0.2 — draft, October 2026

  • International. A 154-term amenity vocabulary in 12 categories (including accessibility and sustainability), with RESO/OpenImmo equivalents.
  • Languages. Labels in 7 languages (en, es, fr, de, pt, it, nl) for every amenity and user-facing value; downloadable label packs. Knowledge base in English and Spanish.
  • New optional blocks: energy (EU/UK EPC, LEED, EDGE), rental_terms, short_term (tourist licence, seasonal rates, iCal), commercial, building (floor, orientation, condition, structure, roof, design wind speed, elevation).
  • Areas: usable and gross, and the measurement standard; total rooms.
  • Address privacy with address_visibility.
  • New warnings: missing EU energy certificate, rents priced "total", missing tourist licence, seasons that end before they start, impossible floors, exact pins on hidden addresses.
  • Backwards-compatible: every v0.1 feed stays valid, and relabelled "rees": "0.2" it is a valid v0.2 feed.

v0.1 — draft, September 2026

Feed envelope, money with currency and basis, measures with units, coordinates with precision, provenance, legal block, developments, licences, three levels, 31 amenities. v0.1/schema.json

Being considered

  • A push API (POST with a signed webhook) for publishers who prefer sending to being polled.
  • Price history events inside the feed.
  • Signed feeds, so receivers can verify a feed came from its publisher.
  • Native-speaker reviewers for each label language.

Propose a change

Agencies, developers, portals and CRM vendors are all welcome. Email standard@caribescout.com with what you need, an example of the data, and why the current fields do not cover it. Accepted proposals are credited here.