Draft 0.x Fields can still change, be renamed or be dropped. Follow the discussion

Practical examples ยท OTE Spec v0.3

One example per real case

The reference tells you what each field is. This page shows you whole documents: what a small meetup looks like, what changes when it repeats every month, and what to do with a study jam spread over three non-consecutive Saturdays. Copy any of them.

Every document here is read straight from the repository and validated in CI against the JSON Schemas. If one stopped validating, the build would fail โ€” so what you copy is what the validator accepts.

OTE field Prefixed field: someone else's vocabulary, never OTE's

Your case isn't here

Then it's a gap in the examples, or a gap in the spec โ€” and both are worth an issue. Describe how your community runs the event and what you couldn't express; a real case is what moves this spec forward.

Validate your own document before opening the issue: npm install && npm run validate -- my-feed.json