[OASIS Issue Tracker] (COEL-15) Operator renaming in the DE.

[ https://issues.oasis-open.org/browse/COEL-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61472#comment-61472 ] 

David Snelling commented on COEL-15:
------------------------------------

This seems to be explicity a disable operation. 
IE: Can't register consumers, Can't register devices (in the futire), Possibly reject Atoms for that operator's consumers.

Consider raising a issue to shut down a consumer's ability to post atoms. Is this a SP function or a DE internal concern.

> Operator renaming in the DE.
> ----------------------------
>
>                 Key: COEL-15
>                 URL: https://issues.oasis-open.org/browse/COEL-15
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: New Feature
>            Reporter: David Snelling
>            Assignee: David Snelling
>            Priority: Critical
>
> Paul suggested something like this for the MMI:
> PATCH /service-provider/operator(id1,id2) – disable an operator by giving it a new ID. This is to allow exsiting operators to be disabled without losing any of their data or altering the hierarchy. 
> I'm not sure it is justified in the MINIMAL MI. Let's discuss it.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)