This reminded me of drafting electric diagrams in plans and elevations. And of course the notions of a 'plan' and and 'elevation' are also front and center. Wh

This reminded me of drafting electric diagrams in plans and elevations. And of course the notions of a 'plan' and and 'elevation' are also front and center. Why were not graphs embraced by other domains? Plan and elevations by definition are constrained view points. (Hint: for the same reason the highly available and highly consistent flavors of graph databases require paid licenses :) Graphs make for difficult decomposable 'unit' assemblies. Plans and elevations are 'standard units'. (Again: it may help to think of as plans and elevations as tables and reverse indexes, respectively.) Note requirements such as e.g. "show directions from one entity to another" are also present for documenting the electrical systems, or HVAC, in a building. A modular system for representing graphs of arbitrary scale is the minimal and trivial 'one node per modular unit'. The alternative is throwing huge amounts of processing power to allow arbitrary views into a graph at any scale. IoT, as an 'integrated component' of building systems, will find a very happy place on plans and elevations.