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-160) Move Include to Aggregate

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

David Snelling commented on COEL-160:

Paul and Dave discussed this.

For Atom responses, we could provide Inc, Exl, or Inc xo Exc and deliver the same functionality. Removing the Project element completely only results in the DE returning smaller Atoms. Because the Atom is JSON, this in invisible (except for data volume) to the user.

In the Aggregate case, Include is implied by the Grouby element. Including other fields from the Atom makes no sense as all field in the Atom are orthogonal. 

Similarly, Exclude make no sense in the Aggregate case.

Hence the proposal to drop the Project element.

> Move Include to Aggregate 
> --------------------------
>                 Key: COEL-160
>                 URL: https://issues.oasis-open.org/browse/COEL-160
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Bug
>         Environment: PQI
>            Reporter: David Snelling
>            Assignee: David Snelling
> Paul comments:
> Is Include ignored if Aggregate is NOT present? In which case it would be better as part of the Aggregate element itself.

This message was sent by Atlassian JIRA

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