[OASIS Issue Tracker] (COEL-149) Section 8.2.3 'Exceptions' in BAP needs clarification

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

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

David Snelling commented on COEL-149:
-------------------------------------

We need to have the ability to store multiple Atoms desribing the same activity in order to include more information than possible in a single atom, e.g. multiple interger extension fields.

Therefore, the DE should not treat these as the same. Likewise, multiple atoms with the same semantic meaning should not be duplicated, e.g. no dounble counting.

ToDo: Find a way to treat two atooms with the same semantic but different textual representation as being the same.

> Section 8.2.3 'Exceptions' in BAP needs clarification
> -----------------------------------------------------
>
>                 Key: COEL-149
>                 URL: https://issues.oasis-open.org/browse/COEL-149
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Task
>            Reporter: Paul Bruton
>            Assignee: David Snelling
>
> See comments in revision 41.
> Let's be sure we make it clear what we mean here: In some of these cases the error response is specified above. The question is whether the DE provides any additional services like quarantining the atoms or post-processing them later to see if the consumer/device ID becomes valid a bit later….
> I don't see how a DE could state that it would return an error in this case: Checking each incoming atom against it's store for duplicates would be quite a burden and what would be the value? I think it is either duplicate or overwrite
> If we mean 'syntactically invalid' – i/e/ not a pseudonymous key, then the DE has to return a 400 in both of these cases. 



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