Roadmap and open issues
What is settled, what is provisional, what is unspecified, and what is deferred. Deliberately without dates — a standard that misses its own dates teaches people to ignore it.
Named and unspecified
- bus-vector-1 — the neutral vector format used by figure mode is named in clause 13.4.3 and not yet specified. Packages using figure mode are portable only between implementations that agree on it, which today means none.
- Ports — the model describes what connects to what, not where on an asset the connection lands. Open issue H-1.
- Networks and drivers — field bus topology and driver configuration are out of scope in v0.2. Open issue H-2.
- Deployed logic extraction — sequences travel as intent, not as compiled control programs. Extracting the latter is open issue H-3.
Deferred to BUS-2
Time series. The completeness declaration already carries a timeSeries domain
so a v0.2 package can say honestly that it holds history it cannot yet express. That was a
deliberate choice: the domain exists in the vocabulary before the format exists, so the
absence is declarable rather than invisible.
What evidence would change the model
The scale test is the clearest example of evidence changing the document. At 344,285 entities, JSON Schema validation took about a hundred seconds of a hundred-and-two second import; every other stage took seconds. That did not change the wire format — it changed the advice, and the specification now tells implementers to run a fast structural pass separately from schema validation.
The four questions
Annex F.3 asks implementers four questions, and the answers are what will drive v0.3. They are collected on the participate page.