I'd looked into this around a year ago, but it was (and is) still in "working group" status. At a high-level it has some features that may be relevant to TROLIE:
Uses the CIM upper ontology in defining its messaging ("infrastructure") model as well as bits from the EQ & Meas for payloads
Leverages/borrows from/parallels existing standards to define exchange (TASE.2/ICCP, IEC 61968-100)
Uses JSON
Defines messaging patterns for subscriptions, transactions, events, request/reply, etc. along with some data security schemes
Has an IEEE working group
With our early focus on forecasting and simplicity, some of these items were less relevant, but as we develop the spec for RT + Peering, I wanted to revisit. I don't have any sense at all if other vendors are looking at UUDEX.
https://www.osti.gov/servlets/purl/1839599
I'd looked into this around a year ago, but it was (and is) still in "working group" status. At a high-level it has some features that may be relevant to TROLIE:
With our early focus on forecasting and simplicity, some of these items were less relevant, but as we develop the spec for RT + Peering, I wanted to revisit. I don't have any sense at all if other vendors are looking at UUDEX.