I have updated the website with the latest version of the documentation.

There is significant enhancements to the data formats to handle nested collections (lists, dicts, and grids). Plus we now have an official mechanism for HTTP authentication. I have rolled the format/protocol version to "3.0" for these enhancements. We have updated the Java Haystack Toolkit which provides nice reference code for the 3.0 formats and auth protocol.

The most significant enhancement on the modeling side is the tagging model for hot water and steam plants. Please note as part of that proposal we made a breaking change to tag a cooling plant as chilledWaterPlant instead of chillerPlant. I have some detailed notes in topic 341 about this enhancement. See new Boilers chapter.

Also we have a new suite of points for weather stations.

Change Log

Version 3.0.1 (13-Jul-2016)*

• Add new Associate members to about
• Added following tags:
  • circ
  • diverting
  • flue
  • gasHeat
  • header
  • level
  • mixing
  • oil
  • tank
• Add file manager to website
• Roll encoding version to "3.0" for Zinc and JSON
• Add Trio chapter
• Renamed chillerPlant to chilledWaterPlant
• Renamed boilerPlant to hotWaterPlant/steamPlant
• Change pump to work as equop or point (like fan)
• New Tanks chapter
• Beef up curStatus enumeration
• 258: JSON new encoding
• 341: heating plants
• 350: new mau tag
• 360: new XStr data type
• 361: nested collection types
• 362: new NA data type
• 383: new HTTP authentication protocol
• 396: remove discharge/entering tag from VAVs
• 418: new weather points

Is it just me or does the new Trio serialisation format looks scarily like YAML?

For reference:

• http://www.project-haystack.org/doc/Trio
• http://www.yaml.org/

It seems Trio is almost close enough it could be converted to YAML by a regex expression.

(And why does the name "Trio" bring to mind a rather repetitive song played on a Casio VL-1? ;-)