[OASIS Issue Tracker] (COEL-138) PQI: Specification of Aggregate element in query is unclear

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

     [ https://issues.oasis-open.org/browse/COEL-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Bruton updated COEL-138:
-----------------------------

    Description: 
 I'm looking at using schema to document the Query and its responses. This is mostly OK, but I've run into a blocker with the Aggregate.

The spec has the following structure:

Aggregate (OPTIONAL)
    - Columns (list)
         -- ColName: column name, see below
         -- Aggregator: aggregator function, one of AVG, 
                                  SUM, COUNT, MIN, MAX, STDDEV
   - GroupBy (list) (OPTIONAL)
         --ColName: column name

That suggests an object containing two lists:

{
    "Aggregate": {
        "Columns": [],
        "GroupBy": []
    }
}

which could expand to something like this: (A)

{
    "Aggregate": {
        "Columns": [{
            "ColName": "a",
            "Aggregator": "SUM"
        }, {
            "ColName": "b",
            "Aggregator": "AVG"
        }],
        "GroupBy": ["a", "b"]
    }
}

of if GroupBy has to have a ColName then it would be this: (B)

{
    "Aggregate": {
        "Columns": [{
            "ColName": "a",
            "Aggregator": "SUM"
        }, {
            "ColName": "b",
            "Aggregator": "AVG"
        }],
        "GroupBy": [{
            "ColName": "a"
        }, {
            "ColName": "b"
        }]
    }
}

We have no examples of GroupBy and the only example of Aggregate (C, below) does not have an array, just a single item:

{
    "Aggregate": {
        "Columns": {
            "ColName": "WHAT_CLUSTER",
            "Aggregator": "COUNT"
        }
    }
}





  was:
 I'm looking at using schema to document the Query and its responses. This is mostly OK, but I've run into a blocker with the Aggregate.

The spec has the following structure:

Aggregate (OPTIONAL)
    - Columns (list)
         -- ColName: column name, see below
         -- Aggregator: aggregator function, one of AVG, 
                                  SUM, COUNT, MIN, MAX, STDDEV
   - GroupBy (list) (OPTIONAL)
         --ColName: column name

That suggests an object containing two lists:

{
	"Aggregate": {
		"Columns": [],
		"GroupBy": []
	}
}

which could expand to something like this: (A)

{
	"Aggregate": {
		"Columns": [{
			"ColName": "a",
			"Aggregator": "SUM"
		}, {
			"ColName": "b",
			"Aggregator": "AVG"
		}],
		"GroupBy": ["a", "b"]
	}
}

of if GroupBy has to have a ColName then it would be this: (B)

{
	"Aggregate": {
		"Columns": [{
			"ColName": "a",
			"Aggregator": "SUM"
		}, {
			"ColName": "b",
			"Aggregator": "AVG"
		}],
		"GroupBy": [{
			"ColName": "a"
		}, {
			"ColName": "b"
		}]
	}
}

We have no examples of GroupBy and the only example of Aggregate (C, below) does not have an array, just a single item:

{
	"Aggregate": {
		"Columns": {
			"ColName": "WHAT_CLUSTER",
			"Aggregator": "COUNT"
		}
	}
}


I'll raise a ticket in JIRA, but thought an email was easier to lay out.



> PQI: Specification of Aggregate element in query is unclear
> -----------------------------------------------------------
>
>                 Key: COEL-138
>                 URL: https://issues.oasis-open.org/browse/COEL-138
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Bug
>            Reporter: Paul Bruton
>
>  I'm looking at using schema to document the Query and its responses. This is mostly OK, but I've run into a blocker with the Aggregate.
> The spec has the following structure:
> Aggregate (OPTIONAL)
>     - Columns (list)
>          -- ColName: column name, see below
>          -- Aggregator: aggregator function, one of AVG, 
>                                   SUM, COUNT, MIN, MAX, STDDEV
>    - GroupBy (list) (OPTIONAL)
>          --ColName: column name
> That suggests an object containing two lists:
> {
>     "Aggregate": {
>         "Columns": [],
>         "GroupBy": []
>     }
> }
> which could expand to something like this: (A)
> {
>     "Aggregate": {
>         "Columns": [{
>             "ColName": "a",
>             "Aggregator": "SUM"
>         }, {
>             "ColName": "b",
>             "Aggregator": "AVG"
>         }],
>         "GroupBy": ["a", "b"]
>     }
> }
> of if GroupBy has to have a ColName then it would be this: (B)
> {
>     "Aggregate": {
>         "Columns": [{
>             "ColName": "a",
>             "Aggregator": "SUM"
>         }, {
>             "ColName": "b",
>             "Aggregator": "AVG"
>         }],
>         "GroupBy": [{
>             "ColName": "a"
>         }, {
>             "ColName": "b"
>         }]
>     }
> }
> We have no examples of GroupBy and the only example of Aggregate (C, below) does not have an array, just a single item:
> {
>     "Aggregate": {
>         "Columns": {
>             "ColName": "WHAT_CLUSTER",
>             "Aggregator": "COUNT"
>         }
>     }
> }



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