Closed cookeac closed 9 months ago
During discussions at the technical meetings on 5 October 2023 and 19 October 2023, we decided that only the manufacturer
needed to be added to the icarDeviceReferenceType
. The other more detail fields can stay in icarDeviceResource
and be retrieved when necessary (if that API is implemented).
Several events have a
device
property which is intended to identify the device that is the source of the event. However, device is anicarDeviceReferenceType
, which derived from anicarResourceReferenceType
is intended to provide the ID and optionally a URL to get details of the resource (in this case the device). It extends this type, addingmodel
(a string) andserial
(a serial number string).There is also
icarDeviceResource
which defines a more useful set of device properties:name
,description
,id
manufacturer
softwareVersion
hardwareVersion
It would be good if this information were available with each event, rather than having to be fetched separately through a dereferenced call to get a device with that ID (particularly if the API to get devices was not implemented!).
A potential solution would be to add the properties of
icarDeviceResource
to thedevice
property in events, perhaps through an allOf. The only required property isid
which is required in a reference type anyway.