[Requests] Comments on Table Joining Service Standard

[OTCSL.SIG]

PART A

 

1. Evaluator:

    Marta Codinachs

    Diputació de Barcelona

    otcsl.sig at diba.cat

        

2. Submission: 10-070, Table Joining Service IS

 

 

 

PART B

 

COMMENT 1

---------

 

1. Requirement: General

 

2. Implementation Specification Section number: 7.4 GDAS encoding

 

3. Criticality: Minor

 

4. Comments/justifications for changes:

 

In table 23, row 1 (Classes parameter): "Use when attribute purpose is Data" à "Data" does not exists as a possible purpose value. Instead, it should be "Attribute".

 

 

COMMENT 2

---------

 

1. Requirement: General

 

2. Implementation Specification Section number: 7.4 GDAS encoding

 

3. Criticality: Minor

 

4. Comments/justifications for changes:

 

In table 16, notes "a" and "b": Where says "a" should say "b" and vice versa.

 

 

COMMENT 3

---------

 

1. Requirement: General

 

2. Implementation Specification Section number: 12.2.1 GetData request parameters

 

3. Criticality: Minor

 

4. Comments/justifications for changes:

 

In table 53, row2 (Request parameter): "Value is DescribeData" à Value should be "GetData".

 

 

COMMENT 4

---------

 

1. Requirement: General

 

2. Implementation Specification Section number: 12.2.2 GetData request KVP encoding 

 

3. Criticality: Minor

 

4. Comments/justifications for changes:

 

In KVP example: "Request = DescribeData&" à Should be "GetData&" instead.

 

 

COMMENT 5

---------

 

1. Requirement: General

 

2. Implementation Specification Section number: 12.3.1 GetData normal response parameters 

 

3. Criticality: Minor

 

4. Comments/justifications for changes:

 

"The normal response to a valid DescribeData..." à Should say "The normal response to a valid GetData" instead.

 

 

COMMENT 6

---------

 

1. Requirement: General

 

2. Implementation Specification Section number: 15.2.1 JoinData request parameters 

 

3. Criticality: Minor

 

4. Comments/justifications for changes:

 

In table 71, row 2 (Request parameter): "Value is DescribeKey" à Value should be "JoinData".

 

 

COMMENT 7

---------

 

1. Requirement: General

 

2. Implementation Specification Section number: Annex A - A.2.3 DescribeFrameworks operation request 

 

3. Criticality: Minor

 

4. Comments/justifications for changes:

 

"A.2.3 DescribeFrameworks operation request" à Should say "A.2.3 DescribeDatasets operation request" instead.

 

"A.2.3 a) Test Purpose: Verify... for a DescribeFrameworks operation request." à Should say "A.2.3 a) Test Purpose: Verify... for a DescribeDatasets...." instead.

 

"A.2.3 b) Test Method: Generate... DescribeFrameworks..." à Should say "A.2.3 b) Test Method: Generate... DescribeDatasets..." instead.

 

 

COMMENT 8

---------

 

1. Requirement: General

 

2. Implementation Specification Section number: 7.4 GDAS encoding

 

3. Criticality: Minor

 

4. Comments/justifications for changes:

 

In table 14, note "d": When more than one column, the names of the each of the columns in the Dataset/Columnset/FrameworkKey could be different from the equivalent columns in the Framework/FrameworkKey names if the order is maintained. Or, there could be a new tag for each column indicating the order. This would be more flexible about the names of the columns.

 

In table 29, note "a": "The order of the <V> elements inside each <Row> is important".

So, it seams that it should be possible to have different column names if the order is always maintained.

 

 

COMMENT 9

---------

 

1. Requirement: General

 

2. Implementation Specification Section number: 7.4 GDAS encoding

 

3. Criticality: Minor

 

4. Comments/justifications for changes:

 

In table 16, note "a": Maybe it should be useful to recommend also not to use other special characters (except of "_").

 

 

COMMENT 10

----------

 

1. Requirement: General

 

2. Implementation Specification Section number: 14.3.1 DescribeKey normal response parameters 

 

3. Criticality: Major

 

4. Comments/justifications for changes:

 

In table 67, row 3 (Title parameter): "A human readable sentence..." à In general, it should be easy to have one different description for each language for ALL descriptive tags, like Abstract and Title. Please, have a look at the "Need of more than one ABSTRACT for different languages <https://portal.opengeospatial.org/files/?artifact_id=37065> " Change Request at http://www.opengeospatial.org/standards/cr <http://www.opengeospatial.org/standards/cr> .

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opengeospatial.org/pipermail/requests/attachments/20100409/25251ecf/attachment-0001.htm