> For the complete documentation index, see [llms.txt](https://docs.internetobject.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.internetobject.org/appendices/roadmap.md).

# Roadmap

This page outlines the direction of the Internet Object specification and its surrounding ecosystem. It is **informative**, not normative: it describes intended work, not guaranteed features or dates. Items may change as the format and its reference implementation converge during the 1.0 Draft period.

## Specification

* **Converge the spec and the reference implementation.** Where the specification currently describes behavior ahead of the implementation (noted on the affected pages), close the gap in one direction or the other and remove the qualifier.
* **Finalize the formal grammar.** Fold the remaining lexical edge cases — precise open-string termination, the full escape-sequence set, and date/time sub-formats — into the [EBNF grammar](/appendices/grammar.md) so it is complete and self-contained.
* **Complete the error catalogue.** Give every malformed literal and structural failure a stable, documented [error code](/parsing-and-errors/error-model.md), so tooling can branch on codes for all failures rather than most.
* **Settle the numeric type set.** Confirm the final list of numeric shortcuts and their ranges, and mark any that remain reserved.
* **Finalize streaming.** Specify the framing and collection-merge rules for [streaming collections](/collections/data-streaming.md) once the model stabilizes.

## Conformance

* **Publish a conformance test suite.** A language-independent set of documents and expected outcomes (valid data, error codes, positions) that any implementation can run to demonstrate conformance with the [requirements](/conformance/requirements.md).

## Implementations and tooling

* **Reference implementation to 1.0.** Track the TypeScript/JavaScript implementation to a stable 1.0 aligned with the finalized specification.
* **Implementations in more languages.** Support community libraries for additional languages, each declaring the specification version it conforms to.
* **Authoring tooling.** Encourage formatters, linters, editor support (syntax highlighting, schema-aware completion), and converters to and from JSON, CSV, and YAML.

## See Also

* [Version History](/versioning-and-stability/version-history.md) · [Conformance Requirements](/conformance/requirements.md)
* [Acknowledgments](/appendices/contributors.md) · [FAQs](/appendices/faqs-1.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.internetobject.org/appendices/roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.