Issue Considation for device reasignment.

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Blocker
    • None
    • Environment:

      COEL-MMI

    • Hide

      Plan to use something liks: operator/reasignDevice (DeviceID, ConsumerID).

      Language similar to the following should be included:

      Request that a Device be reasigned to a different Consumer associated with this Operator. This operation MAY not proceed synchronously, as the Data Engine MUST confirm the request with the Service Provider associated with the requesting Operator. The mechanism for confirmation is out of scope of this specification, e.g. email confirmation. Atoms associated with this Device MUST not be added to the Data Engine until the the request is confirmed by the Service Provider.

      Show
      Plan to use something liks: operator/reasignDevice (DeviceID, ConsumerID). Language similar to the following should be included: Request that a Device be reasigned to a different Consumer associated with this Operator. This operation MAY not proceed synchronously, as the Data Engine MUST confirm the request with the Service Provider associated with the requesting Operator. The mechanism for confirmation is out of scope of this specification, e.g. email confirmation. Atoms associated with this Device MUST not be added to the Data Engine until the the request is confirmed by the Service Provider.

      The following function has been identified as 'high risk'. This means that either data may be lost, there is a chance that some privacy constraints may be violated, or some other aspect is at risk. Therefore this function needs a special mechanism to ensure that it proceeds safely and under the authority of the Service Provider.

      Operation to reasign a device to a different user. This operation does not currently exist. Furthermore the Assign Device operation will need revising.

            Assignee:
            David Snelling (Inactive)
            Reporter:
            David Snelling (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: