[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [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=62044#comment-62044 ] Paul Bruton commented on COEL-15: --------------------------------- David, Matt and Paul discussed this: Is it wise for SP to rename the operator and therefore break the link that the consumer has with their data? Going back to the original need, this is a means to prevent that operator from registering new consumers or new devices - it is a state change rather than a rename / delete. We will discuss this further with Joss present. > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]