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-149) Section 8.2.3 'Exceptions' in BAP needs clarification


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

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

I think part of (error handling) this has been addresed in my latest revision of the BAP section. However, we should discuss overwrite vs duplicate. In the current DE, the Atom will be overwritten for the User, What, and Time are the same, otherwise it's a new atom. Therefore, it definitely doesn't duplicate, but neither does it always overwrite. Alan ran into this when posting multiple status extensions within a second of eachother.

We need to decide what the spec should say and then I'll address the DE behaviour as required.

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


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