[OASIS Issue Tracker] (ENERGYINTEROP-667) Rolando Herrero Comments

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Toby Considine created ENERGYINTEROP-667:
--------------------------------------------

             Summary: Rolando Herrero Comments
                 Key: ENERGYINTEROP-667
                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-667
             Project: OASIS Energy Interoperation TC
          Issue Type: Bug
          Components: cts
    Affects Versions: CTSPR01
         Environment: Shane Calderwood, NJIT and Energy Mashup Lab
            Reporter: Toby Considine
            Assignee: Toby Considine


Please find below the comments to the CTS draft.Â
Â
Thanks./
Â
Page: 10, Line: 76-80 -> Is SBE the recommended encoding for constrained IoT (embedded) devices ? What determines in what scenario/topology SBE (or JSON/XML) must be used? How is that negotiated?
Â
Page: 16, Line: 267-269 -> Message transport is affected by the topology. SOA is typically client/server while many of the modern IoT topologies are publish/subscribe (relying on MQTT or AMQP session management). This document should take into account the support of this latter scenario.
Â
Page: 18, Line: 307 -> How are PartyIDs assigned? Are they unique? How is uniqueness enforced?
Â
Page: 30, Line: 30 -> Some of these fields (like CURRENCY) should be binary encoded as enumerations (whenever possible). Specifically, many (IoT and non-IoT) devices in constrained environments rely on physical/link layer technologies (like IEEE 802.15.4) that are not designed to handle large payloads (even with upper layer adaptation)
ÂPage: 41, Line: 604 -> How is the transaction ID defined? Some of these tables like 8-2 and 9-2 should specify the data type of each attribute.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)