OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

coel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (COEL-84) IoT Device Certainity setting


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

David Snelling commented on COEL-84:
------------------------------------

Also, Joss suggested that something might be needed in the PQI, however, it clearly refers back to the Atom. Furthermore, someone implementing the PQI would not need to know this information.

> IoT Device Certainity setting
> -----------------------------
>
>                 Key: COEL-84
>                 URL: https://issues.oasis-open.org/browse/COEL-84
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: New Feature
>            Reporter: David Snelling
>            Assignee: David Snelling
>
> The prototype DE currently divides the certainity (or 100% if missing) by the number of Consumers registered to the device. Then this value is stored as the Certainty for every Consumer associated with the device id listed in the incoming Atom.
> Proposal: 
> Since this section describes the 'state' of an Atom, the language should reflect the state of an Atom in the Data Engine rather than describing the processing. Add the following text (or similar) to section "5.2.5 How"
> If when an Atom was posted from a device (i.e. The DeviceID was present and the ConsumerID was not), the Certainty value (or 100 if the Certainty value was missing) will have been divided by the number of ConsumerIDs associated with the DeviceID at the time the Atom was posted. Thus Certainty represents the probability that the Atom is associated with this consumer.
> Also, since this needs to be clearly apparent to the developer of the Atom protocol, the following text should be included in section 8.2.2 Atom POST. The text could in a second paragraph or at just after the request table.
> When an Atom is posted from a device (i.e. The DeviceID is present and the ConsumerID is not), a copy of the Atom is stored for each ConsumerID associated with that DeviceID. Before being stored, the Certainty value (or 100 if the Certainty value is missing) is divided by the number of ConsumerIDs associated with the DeviceID. Thus Certainty, in a stored Atom, represents the probability that the Atom is associated with this consumer.



--
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]