search

opengeospatial / CityGML3.0-GML-Encoding

CityGML 3.0 GML Encoding
11 stars 4 forks source link

Public Review Comment from Tatjana Kutzner: Clarification and Editorial #8

Closed 3DXScape closed 1 year ago

3DXScape commented 1 year ago

Part A to be completed once. Iterate Part B as needed.

PART A

  1. Evaluator: Tatjana Kutzner, Technical University of Munich

  2. Submission: 21-006, OGC City Geography Markup Language (CityGML) Part 2: GML Encoding Standard

PART B

  1. Requirement: 9, 15, 17, 19, 22, 24, 29, 35, 37, 39, 43

  2. Implementation Specification Section number: 6.2.3, 6.4.3, 6.5.3, 6.6.3, 6.7.3, 6.8.3, 6.10.3, 6.14.3, 6.15.3, 6.16.3, 6.18.3

  3. Criticality: Minor

  4. Comments/justifications for changes: It might be possible to misunderstand the requirements. From the text, as it is written now, the reader might assume that a space element can only have one property core:boundary. I suggest to simply change "the" by "each" in the second part of the second sentence: So instead of "If a space element [...], the property SHALL contain [...]." I think it would be better to write "If a space element [...], each property SHALL contain [...]."

3DXScape commented 1 year ago

Resolution: clarify sentence

3DXScape commented 1 year ago

Resolution: Also change table headings where space boundaries may only be thematic surface boundaries

3DXScape commented 1 year ago

Done