Thanks for the answers,
Regarding device identification, for us, the following are important:
GTIN (Global trade item number): 48 bit integer, from DALI IEC-62386-102,
Serial number: 64 bit integer, from DALI IEC-62386-102,
MAC address: Typically I will use the mac address as the unique identifier within the name of the device instances, but I think it would be worth including this as a specific property for network equipment,
Regarding real time data references, I was primarily considering this as a means of cross referencing to an external specification containing the schema or payload descriptions.
I can see great value in using Brick as a discovery mechanism to understand the structure of an output stream, even without going into the contents of each payload, since it allows users to apply their existing knowledge of Brick to quickly understand a new custom protocol.
Doing both would be nice though. In our Syncromesh MQTT protocol spec, I describe all the payloads using JSON schema. Specific sensors also include JSON schema descriptions of the telemetry they support in the device discovery payloads.
We publish telemetry payloads as both JSON and simple numeric values to suit the capabilities of different consumers.
Finally, thanks for the invite to the working group meetings, the "A" sessions
suit my timetable and I will try to join the 29th June and 14th July
calls (dates in AU timezone).
I would be happy to show some details of our system and the source data that is used to generate the Brick model if you are interested.
You may also be interested to see a brick model I've
generated - this represents one of our sites here in Sydney. The site
uses Syncromesh for lighting control as well as capturing indoor air
quality and occupancy data. The data from this site is going to a number
of sources (via MQTT) for analysis, including a Willow digital twin.
Brick model is auto generated after querying the gateway to discover
the devices on the network and their configuration. It is not a complete
representation of our network (i.e. not a one to one mapping of
hardware on site and Brick entities), but it is relatively complete in
representing the published data points.