Typos

[KathiSchleidt]

ZA-001-030 Rephrase- This structureenables users to selectively This allow structureenables users to selectively

KS: add missing blank

[KathiSchleidt]

-048 in the Sampling part of section 7 Please refer to a specific subclause.
Pertains to 8.2.6

KS: change reference to 7.2 Sample schema

[KathiSchleidt]

-060 If information on the type of Observation is provided, the constraints defined in the referenced codelist SHALL be used.
Should the word "observation" be written in bold font here?

KS: agreed

[KathiSchleidt]

-065 If the reason for the Deployment is provided, the property deploymentReason:CharacterString SHALL be used. It is not clear why the section of text "deploxmentReason:CharacterString" is written in italic font here. Please review.

-066 If the time of the Deployment is provided, property deploymentTime:TM_Period SHALL be used.
The previous comment concerning the use of italic font also applies here.

[KathiSchleidt]

-106 ex situ Note that Latin text shall be written in italic font.

[KathiSchleidt]

-111 (ex : forecast) "e.g." ?

[KathiSchleidt]

AFNOR-001 Abstract Observation core Abstract Observation Core

KS: capitalize Core

[sgrellet]

• ZA-001-030 Rephrase- This structureenables users to selectively -> "KS: add missing blank" -> agreed
• -048 in the Sampling part of section 7 -> "KS: change reference to 7.2 Sample schema" -> agreed
• -060 If information on the type of Observation is provided, the constraints defined in the referenced codelist SHALL be used. -> "KS: agreed" -> agreed
• -065 If the reason for the Deployment is provided, the property deploymentReason:CharacterString SHALL be used. -> "SG : remove italic"
• -066 If the time of the Deployment is provided, property deploymentTime:TM_Period SHALL be used. -> "SG : remove italic"
• -106 ex situ : -> "SG : indeed in 19156:2011 the term ex situ is written in italic -> make 'ex situ' italic again"
• -111 (ex : forecast) -> "SG : the rest of that chapter uses a lot of e.g -> write "(e.g: forecast)""
• AFNOR-001 Abstract Observation core -> "KS: capitalize Core" -> agreed

[KathiSchleidt]

Short note on e.g., based on the feedback I've received over the years, there should be a comma after

proper English style usually requires commas to follow e.g. to delimit the beginning of that list

Otherwise agreed

[ilkkarinne]

-106: quoting the ISO House Style:

Do not italicize commonly used Latin expressions, e.g. a priori, in situ, in vitro.

now I’m confused, italics or not?

[ilkkarinne]

Oh, now I see: maybe ex situ is not considered ”commonly used”, but in situ is, thus ex situ would fall under ”words used for scientific terms”:

Italicize Latin words used for scientific terms, e.g. species, bacteria, plants. For example, “This document describes a horizontal method for the detection of Salmonella spp. in food”.

Proposing to keep both in situ and ex situ in the same type (either italic or not).

[KathiSchleidt]

If we didn't have in situ, I might be OK with having ex situ not italic, but especially as they're a pair, I'm for including ex situ under the Latin words

[sgrellet]

@KathiSchleidt regarding (e.g., forecast) and your quote above "proper English style usually requires commas to follow e.g. to delimit the beginning of that list" it turns out that in the rest of the doc we have e.g. without comma (for example "(e.g. surface/ground water level, rainfall)" ) right after in the paragraph

-> we need to be consistent on this throughout the document

[KathiSchleidt]

OK, will do this when I do the AbstractCollection update

[KathiSchleidt]

Did a search and replace between "e.g. " to "e.g., "

[sgrellet]

completed with adding one "e.g.," in "7.1.2 Observation", "7.3.1 Model consistency" , '8.6.2 Interface Observer' sections