BUS-2 v0.3: Time Series
The second part of the standard: how a building's history travels. A declaration entity, a sample format a text editor can open in 2056, and the tests that make the full profile claimable without a dispensation.
Status of this document
This is version 0.3 of BUS-2, the second part of the Building Understanding Standard. It is a working draft published for implementer review, and it is the first version of this part: the time-series domain was named by BUS-1 v0.1, declared in every completeness declaration since, and specified by nothing until now.
BUS-2 specifies the last of the twelve substrate domains, which is the fact that matters most about it. Through v0.2 the full conformance profile could be claimed only under a standing dispensation — declare timeSeries absent, cite deferredToLaterVersion, and claim the profile anyway. That dispensation is withdrawn (2.2). A full claim is now a claim about all twelve domains, and every one of them has a specification to be tested against.
This part is short because most of what it needs already exists. Datatypes, identity, the package container, digests, the completeness declaration, canonical form, and the conformance machinery are all BUS-1’s, used by reference. What BUS-2 adds is exactly two things: an entity that declares a series, and a file format the samples travel in. The design decisions behind both — and the formats rejected, with reasons — are recorded in the clauses that make them, because a reviewer can argue with a decision and has nothing to argue with in an omission.
Maturity labels, editorial conventions, requirement keywords, and the boundary test are BUS-1’s and are not restated here. Where this part cites a clause number without a part name, the clause is in this part; clauses of Part 1 are cited as BUS-1.