Four ways in
Comment on the draft. Cite the section, describe the ambiguity, and provide an example that exposes it.
Propose a capability. Supply a dotted path, description, required actions, and applicable extension.
Propose an extension. Supply the field schema, extra checks, freshness rules, and an operator willing to implement the proposal.
Build a reference implementation. Publish a record and implement the actions. The first target is a real, independently evidenced booking completed end-to-end, starting in one dense market.
Ground rules
- Discuss the specification and concrete implementation needs.
- Back proposals with an implementer and realistic data.
- Keep industry-specific fields in extensions.
- Submit specification text under CC BY 4.0 and reference schemas under MIT.
- Favor additive compatibility. A breaking change needs an explicit migration case.
Get in touch
Send draft feedback, extension proposals, or implementation questions through Hottub, Inc.. A public RFC repository and issue process have not been announced in this preview.
Read the specification first · See the first-booking roadmap.