If you have difficulty in submitting comments on draft standards you can use a commenting template and email it to admin.start@bsigroup.com. The commenting template can be found here.
Standards Development
The Point API provides a mapping of HBES AL data to a RESTful resource model and CBOR/JSON based data representation that is used to communicate over IP. Using this API, a client can read/write values or can subscribe to Point events (e.g., switch on/off). The HBES IoT Point API is based on the following building blocks: 1. Discovery 2. S- Mode Messaging 3. Point Read, Write and Publish/Subscribe 4. Security This version of the HBES IoT Point API specification solely considers the use of CoAP as application protocol. Compared to the previous 2024 version, this version has been brought in line with the state of affairs of the specifications at the CLC cooperating partner, KNX.
The HBES protocol as enshrined in the EN50090 series is a well described protocol that is used by many manufacturers worldwide. The EN50090 series includes a possibility to tunnel or route HBES telegrams across an IP network: this solution is however limited to IPv4 and also routes/tunnels the entire HBES protocol again in an IP frame. The HBES IoT Point API remedies these shortcomings: it is a solution for IPv6 networks and uses CoAP as application protocol, hence does no longer rely on a HBES specific application protocol but uses an IETF standardized one.
Required form fields are indicated by an asterisk (*) character.
You are now following this standard. Weekly digest emails will be sent to update you on the following activities:
You can manage your follow preferences from your Account. Please check your mailbox junk folder if you don't receive the weekly email.
You have successfully unsubscribed from weekly updates for this standard.
Comment by: