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-198) Query example include 'Project'

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

Paul Bruton commented on COEL-198:

Discussed at meeting 16 Mar.

We recognise that there are a number of inconsistencies between the schema, text and example for aggregate/group-by queries and held a discussion on the best resolution

We agreed that the most useful output from an aggregate query is the number of atoms per time period (e.g. number of sleep atoms per day). The current specification does not support using group-by on time so it does not deliver what we want.

Outline Proposal:
- Remove Group-By from the Aggregate section of the query
- Add optional Block-By to the top level of a query (i.e. peer element to TimeWindow). Value is a block-duration in seconds
- Change query output: Currently this is either Atoms = <array-of-Atoms> or Table = <array-of-array-of-Aggregates>. We will change this so that it is always Blocks = <array-of block> and where a block has a start-time and either an array-of-atoms or an array-of-aggregates. Note that the output from a query is either atoms or aggregates but not mixed.
- An atom appears in a block if its start time would appear in the time range specified by the start-time + n*block-duration

> Query example include 'Project'
> -------------------------------
>                 Key: COEL-198
>                 URL: https://issues.oasis-open.org/browse/COEL-198
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Bug
>            Reporter: David Snelling
>            Assignee: David Snelling
> See Group by example in section Changes needed in the query and the response.
> In the response, each row should be an object with tag "Row" for the array.
> Atoms example is also wrong. Has Atoms as an object with an untagged array inside it. Should just be the array.
> Non-substantial change.

This message was sent by Atlassian JIRA

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