[OASIS Issue Tracker] (OBIX-218) M2M needs definition (or an acronym list entry)

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

William Cox created OBIX-218:
--------------------------------

             Summary: M2M needs definition (or an acronym list entry)
                 Key: OBIX-218
                 URL: https://tools.oasis-open.org/issues/browse/OBIX-218
             Project: OASIS Open Building Information Exchange (oBIX) TC
          Issue Type: Bug
          Components: OBIX 1.1 Specification
    Affects Versions: OBIX 1.1 PR02
            Reporter: William Cox
            Priority: Minor


M2M may not be a clear term/acronym to some readers.
(a) M2M is used with definition (but not reused) in the Abstract
(b) M2M is used with definition in the Introduction, then reused as "M2M Web"
(c) M2M is NOT in the definition of terms. There is no acronym list
(d) M2M is used extensively in 1.8 and 2, but not later.

Consider what "M2M" adds to the discourse. It is not clear to me that it adds much, as most communication we speak of is M2M. If the intent is to separate communication and interactions that are initiated by machine detection (e.g. sensors, state changes) rather than humans, that should be made clear.

Perhaps a rewrite of the non-normative quickstart (e.g. around lines 173-180) would be helpful.

If this is standard terminology in some universe, it should be defined and referenced.




--
This message was sent by Atlassian JIRA
(v6.1.1#6155)