BUS-2 clause 9 — References — Building Understanding Standard

9 References§

Normative except where marked. BUS-1’s references apply wherever this part uses BUS-1 machinery.

The list is short because the part is: everything this document builds on that is not listed here reaches it through [BUS-1], whose clause 3 carries the full normative set — the container, the digest algorithms, the timestamp grammar, the schema dialect. A reader implementing BUS-2 alone is implementing it wrong, and the reference list is shaped to say so.

Reference	Title and note
[BUS-1]	BUS-1: Core Information Model, Portable Presentation, and Exchange Package, version 0.3. Part 1 of this standard. This part is not free-standing (1.2).
[RFC2119]	Bradner, S., Key words for use in RFCs to Indicate Requirement Levels, BCP 14, RFC 2119, March 1997.
[RFC8174]	Leiba, B., Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words, BCP 14, RFC 8174, May 2017.
[RFC3339]	Klyne, G., Newman, C., Date and Time on the Internet: Timestamps, RFC 3339, July 2002.
[RFC4180]	Shafranovich, Y., Common Format and MIME Type for Comma-Separated Values (CSV) Files, RFC 4180, October 2005. Profiled by clause 4; the LF deviation is stated in 4.2.
[HAYSTACK]	Project Haystack, version 4.0.0. Informative. The `hisMode` vocabulary 3.5 follows, and the live-service history model 1.1 declines.
[BRICK]	Brick Schema, version 1.4.4, the `ref:` namespace. Informative. The external-pointer history model 1.1 declines.

Thirty years of what the building did, in a file the owner holds.
Not a live service. Not a database pointer. Rows a text editor can open in 2056, with a digest that says nobody touched them.

END OF BUS-2 · VERSION 0.3 · WORKING DRAFT