opengeospatial / om-swg

10 stars 6 forks source link

No Dates in ISO Names #180

Closed KathiSchleidt closed 3 weeks ago

KathiSchleidt commented 2 years ago

-023 Dates in ISO Names "following the guidance of ISO 19103:2015"
Note that only cross-references to specific parts of a document (e.g. a specific clause, subclause, table, etc.) shall be dated. All more "general" references shall be undated, unless it is necessary to distinguish between different editions of the document.

Seems in contradiction to DE-018 #177 complaining on the lack of a date with 19123

KathiSchleidt commented 2 years ago

**-032 Table 7 — UML package level dependencies Note that as all document references are dated here, it is not necessary to add the edition number afterwards. Please remove "(Edition 1)" etc. from all entries. Please also note that the headings in this table are not very clear. Please see if these can be clarified. An idea could be to relabel the columns "Package 1 // Package 2 // International Standard // Notes" and the add footnotes at the bottom of the table to explain the relationship between package 1 and package 2, and the International Standard listed.

KathiSchleidt commented 2 years ago

-037 (e.g. ISO 19115-1:2014). This cross-reference does not need to be dated.

KathiSchleidt commented 2 years ago

-107 in Edition 1 When referring to Edition 1, please specify "ISO 19156:2011" and when referring to Edition 2, please refer to ISO 19156:2022, even if this makes the wording seem repetitive in places. It is important for maintaining clarity (e.g. if a subclause is cited outside of the whole document).

KathiSchleidt commented 2 years ago

Remove dates from text except for explicit versions, e.g. "ISO 19156:2011" and "ISO 19156:2022" Leave dates in Table 7 — UML package level dependencies Rephrase headings from table, proposal:

KathiSchleidt commented 2 years ago

Agreed