commentson - europa · web viewensure that cross-references to other documents point to actual...
TRANSCRIPT
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
DK-5
All ed Some of the chapters prior to chapter 1 have headlines in clear text and no numbering. Why? – It would make the layout of the document more consistent if each chapter was assigned a number.
Add a number to each chapter. Accepted in principle. The document structure was harmonised with other existing TGs.
UK-1
All ed Editing required to ensure all text complete (no empty headers) and remove highlighted text sections
Complete text and check for odd formatting. Accepted. To be done once the document is in final draft.
UK-2
All ed Ensure that cross-references to other documents point to actual document fragments that provide meaning to the text.
Check all cross references and external dependencies in document are ‘live’ and resolvable.
Accepted.To be done once the document is in final draft.
UK-3
All ed Formatting - ensure consistency in capitalization, numbering and abbreviations used.
Ensure consistency in capitalization, numbering and abbreviations used.
Accepted.To be done once the document is in final draft.
ES Revision history
15th point ed Duplicate “and” Delete “and” Accepted.
ES Revision history
29th point ed “Has bee” Include “Has been” Accepted.
DE (all) (all) ed of the ISO 19115 of the ISO 19115; at places where ISO is abstractly mentioned; please align through the whole document
Accepted
DE 1.1. Introduction
third paragraph
ed In the context of metadata for spatial data and Spatial Data Services, the standards [ISO 19115], [ISO 19119], [ISO 19139] and ISO 15836 (Dublin Core) have been identified as important standards.
add paranthesis for ISO 15836 Accepted.
DE 1.1. Introduction
sixth paragraph
ed "... refers to the abovementioned Regulation." "... refers to the abovementioned regulation." Accepted.
CZ 1.1.1. Figure 1 ed Double “of” in legend for grey and black circle … VII of of IR-ISDSS (incl. metadata) Accepted.
NL 1.2 ed along with 19115-2, regarding the extensions for imagery and gridded data
Name will be changed to Extensions for acquisition and processing
Accepted.
DE 1.2. XML Encoding of ISO metadata
first paragraph
ed "To provide an XML encoding also for the INSPIRE service metadata, XML Schemas implementing the [ISO 19119] model have been published by the OGC"
reference to actual schema is missing; add reference to http://schemas.opengis.net/csw/2.0.2/profiles/apiso/1.0.0/apiso.xsd
Accepted.
DE 1.3. INSPIRE Validator Service
first paragraph
ed "The validator accepts metadata that follow the Metadata Technical Guidelines encoded in EN ISO 19139 schema."
reference to particular schema is missing Accepted with modification.Since the validator is not supporting validation of v2.0 of the guidelines, and a new validator is currently being developed, this section has been
1 Type of comment: ge = general te = technical ed = editorial page 1 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
condensed.
NL 1.4 ed Typo; The purpose of this specification is to provide a standards compliant and
The purpose of this specification is to provide a standards compliant and
Not accepted. Standards-compliant is correct.
NL 1.4 ed the section 2. Common requirements for ISO/TC 19139:2007based INSPIRE metadata records, contains TG Requirements and Recommendations describingmetadata elements that shall be used in the same way in more than one of the mentioned…Should the common elements not be used in all requirement classes?
Change to …contains TG Requirements and Recommendations describingmetadata elements that shall be used in the same way in all of the mentioned…
Not accepted. The wording is fine. Not all requirements are applicable to all requirements classes.
AT 2.1. ed Although [ISO 19115] and [ISO 19119] models allow extending of metadata, this version of theTechnical Guidelines requires using the only the original, unmodified [ISO 19139] and the OGCservice metadata XML Schemas for encoding INSPIRE metadata records.
… this version of theTechnical Guidelines requires using only the original, unmodified [ISO 19139] …
Accepted
DE 2.3.2. Metadata point of contact
TG Requirement C.5
ed "The value of gmd:role/gmd:CI_RoleCode shall point to the value "pointOfContact" of ISO 19139 code list CI_RoleCode20."
add paranthesis for ISO 19139 Accepted.
ES 2.4.5 1st paragraf below TG Recommendation C.9
ed There is a working comment that should be deleted “Add TG Recommendation for using gmx:Anchor elements for referring to keywords which have a URI to point to.”
Delete comment :“Add TG Recommendation for using gmx:Anchor elements for referring to keywords which have a URI to point to.”
Accepted.
ES 2.4.5 Example C7 ed The example is included before the explanations, it is confused.
Move the Example C.7 to end of the section and delete the sentence “An example XML fragment with two keywords from the same vocabulary (GEMET INSPIRE themes) isprovided as Example C.7.”
Accepted.
ES 2.4.6 Foot note 25 ed Link http://inspire.ec.europa.eu/registry/metadata-codelist/LimitationsOnPublicAccess/ does not work
Include the Link correct The link should be http://inspire.ec.europa.eu/metadata-codelist/ L imitationsOnPublicAccess/ .
ES 2.4.6 2º paragraph of page 44
ed It is not included reference to Annex D.1 “Limitations on public access”
Change “anINSPIRE code list” by“anINSPIRE code list (Annex D.1 “Limitations on
Accepted.
1 Type of comment: ge = general te = technical ed = editorial page 2 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
public access)”
ES 2.4.6 Example C.8 ed Link http://inspire.ec.europa.eu/registry/metadata-codelist/LimitationsOnPublicAccess/INSPIRE_Directive_Article13_1a does not work
Include the Link correct The link should be http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess/INSPIRE_Directive_Article13_1a/
DE 2.4.6. Limitations on public access
first paragraph
ed "Concerning providing the metadata for the data sets and services though Discovery services..."
"Concerning providing the metadata for the data sets and services through Discovery services..."
Accepted.
DE 2.4.6. Limitations on public access
sentence following TG Requirement C.16
ed "The make the references to the allowed..." "To make the references to the allowed..." Accepted.
ES 2.4.7 Requirement C.19
ed Mistake in Codelist value Change “code list value"otherConstraints” by “code list value"otherRestrictions”
Accepted.
ES 2.4.7 Foot note 27 ed Link http://inspire.ec.europa.eu/registry/metadata-codelist/ConditionsApplyingToAccessAndUse/noConditionsApply does not work
Wait until registry is implemented and check it then again.
Accepted.
ES 2.4.7 Foot note 28 ed Link http://inspire.ec.europa.eu/registry/metadata-codelist/ConditionsApplyingToAccessAndUse/conditionsUnknown does not work
Include the Link correct Accepted.
ES 2.4.7 Example C.9 ed Links http://inspire.ec.europa.eu/registry/metadata-codelist/LimitationsOnPublicAccess/NoLimitations and http://inspire.ec.europa.eu/registry/metadata-codelist/ConditionsApplyingToAccessAndUse/NoConditionsApply do not work
Include the Link correct Accepted.
ES 2.5.1 Requirement C.21
ed The redaction of this requirement is not clear We propose add an example with several declarations of conformity
Accepted.
CZ 2.5.1. Page 49 ed Double “is” in sentence. In this specification the above Implementing Rule text is is interpreted …
Accepted.
CZ 2.5.1. Last paragraph on page 49
ed Wrong preposition. The specific TG Requirements for adding these conformity declarations are included in the corresponding Requirement Classes …
Accepted.
1 Type of comment: ge = general te = technical ed = editorial page 3 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
DE 2.5.1. Conformity
third paragraph
ed "In this specification the above Implementing Rule text is is interpreted to mean in that the conformity shall..."
rephrase for better understanding Accepted.
DE 2.5.1. Conformity
TG Requirements C.21 and C.22
ed "... with each INSPIRE Implementing Rule, specification document, its Requirements Class or similar part, shall be given..."
clarify "similar part" Accepted. "Similar part" has been removed. The requirements now refer to "INSPIRE Implementing Rule, specification document or Conformance Class".
ES 3.1 Requierements Class 1
ed Link http://inspire.ec.europa.eu/specification/RC/TG-Metadata/2.0/dataset-baselineThe does not work
Wait until specifications are published and check it then again.
Accepted with modification.All conformance classes now have a unique id, which will be used to create persistent unique ids following the patterns for ATS agreed in the context of the MIWP-5 work and the implementation of the INSPIRE test framework (http://inspire.ec.europa.eu/id/ats/<ats-id>/<version>).
DE 3.1. Baseline metadata for data sets and data set series
Requirements Class 1
ed "Metadata record fulfilling all the TG Requirements..."
"A Metadata record fulfilling all the TG Requirements..."
Accepted.
CZ 3.1.1.1. Paragraph above TG Req 1.1
ed Missing space. … sets and data set series. The … Accepted.
ES 3.1.2.1 Example 1.2 ed Link http://paikkatiedot.fi/so/1002001%3C/gmx:Anchor does not work
Change it to http://paikkatiedot.fi/so/1002001 Accepted. Correct the wrong hyperlink.
NL 3.1.2.1 Recommendation 1.2
ed In the case of HTTP URIs….prevent excluding HTTPS
in the case of HTTP or HTTPS URIs… Accepted in principle.Include a footnote for the 1st mention of HTTP URI in the text that these also include HTTPS URIs.
DE 3.1.2.1. Unique resource identifier
TG Recommendation 1.2
ed "It's recommended to make..." "It is recommended to make..." Accepted.
IT 3.1.2.2. TG Requirement
Ed The content of the footnote 33 is already included Remove the footnote 33 Accepted.
1 Type of comment: ge = general te = technical ed = editorial page 4 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
1.4 in the text of the TG Requirement 1.4
DE 3.1.2.2. Keywords for Spatial Data Theme(s)
TG Requirement 1.4
ed "... at least one keyword from the Inspire Spatial Data Themes vocabulary..."
"... at least one keyword from the INSPIRE Spatial Data Themes vocabulary..."
Accepted.
DE 3.1.2.3. Spatial resolution
Example 1.4 and 1.5
ed "Spatial resolution of a data sets expressed..." "Spatial resolution of a data sets expressed..." Accepted.
DE 3.1.2.4. Resource language
sentence following TG Requirement 1.6
ed "Table 1 contained in Part C of Regulation 1205/2008] defines..."
add paranthesis for 1205/2008 Accepted.
DE 3.1.2.4. Resource language
TG Requirement 1.7
ed more information on multi-lingual encoding would be useful
add a link to section 2.2 Not accepted.Section 3.1.2.4 discusses the resource language element, i.e. the language used in the data set or service, while section 2.2 discusses how to encode textual elements in the metadata.
CZ 3.1.2.5. Paragraph under TG Req 1.8
ed Wrong article. … references to an external code list … Accepted.
NL 3.1.2.5. Topic category
ed Please add a reference to the existing mapping between topics and INSPIRE themes
Add reference Accepted.
ES 3.1.3.1 Example 1.8 ed Link http://data.acme.org/wfs? Does not work Acme.org seems to be a domain example. If it is, better to change it to example.com?
Accepted.
ES 3.2 Requieremnts Class 2
ed http://inspire.ec.europa.eu/specification/RC/TG-Metadata/2.0/datasetinteroperability does not work
Wait until specifications are published and check it then again
Accepted with modification.All conformance classes now have a unique id, which will be used to create persistent unique ids following the patterns for ATS agreed in the context of the MIWP-5 work and the implementation of the INSPIRE test framework (http://inspire.ec.europa.eu/id/ats/<ats-id>/<version>).
CZ 3.2.1.1. TG Req. 2.2 ed Double “be” in sentence. The gmd:codeSpace element shall not be be used in this case.
Accepted.
CZ 3.2.2. and 3.2.4.1.1.
TG Req. 2.4 ed Double “of” in sentence. gmd:MD_SpatialRepresentationTypeCode referring to one of the values of of ISO 19139
Accepted.
1 Type of comment: ge = general te = technical ed = editorial page 5 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
code list
CZ 3.2.2.2. Last paragraph on page 70
ed Wrong article. UTF-8 is an 8-bit variable size Universal Coded Accepted.
CZ 3.2.2.2. TG Req. 2.5 ed Double “of” in sentence. gmd:characterSet/gmd:MD_CharacterSetCode referring to one of the values of of ISO 19139 code list
Accepted.
ES 3.2.3.1 Example 2.5 ed Link http://inspire.ec.europa.eu/media-types/application/x-shapefile does not work
The valid link is http://inspire.ec.europa.eu/media-types and application/x-shapefile is a tag. Should it be linked to the valid link?
Not accepted.The id for “application/x-shapefile” in the Atom feed at http://inspire.ec.europa.eu/media-types/ is indeed: http://inspire.ec.europa.eu/media-types/application/x-shapefile but this URI does not resolve.This issue needs to be addressed in the media types register.
ES 3.2.4.1.1 Example 2.6 ed Link http://www.opengis.net/def/uom/OGC/1.0/unity"/ does not work
Change to http://www.opengis.net/def/uom/OGC/1.0/unity
Accepted.
ES 4.1 Requirements Class 3
ed Link http://inspire.ec.europa.eu/specification/RC/TG-Metadata/2.0/SDSbaseline does not work
Include the Link correct Accepted with modification.All conformance classes now have a unique id, which will be used to create persistent unique ids following the patterns for ATS agreed in the context of the MIWP-5 work and the implementation of the INSPIRE test framework (http://inspire.ec.europa.eu/id/ats/<ats-id>/<version>).
CZ 4.1.2.3. TG Req. 3.5 ed Double “be” in sentence. Data Service type shall be be given using element srv:serviceType/gco:LocalName.
Accepted.
ES 4.1.2.4 Requirement 3.6
ed Drafting error? URI pointing… URI= URL#id
URL pointing Comment unclear
ES 4.1.2.4 Example 3.4 ed Link http://vap-xgeodev.jrc.ec.europa.eu/geonetwork/srv/eng/csw?SERVICE=CSW& does not work
Domain seems not to work. Change example? Not accepted.
In general readers should not expect URL's in examples to resolve. Even if they would resolve today, there is no guarantee they will be maintained and still resolve in 2-3 years time.
ES 4.1.3.1 Recommenda ed Mistake in “gmd:MD_DataIdentifier” Change by “gmd:MD_DataIdentification” This recommendation has been removed.
1 Type of comment: ge = general te = technical ed = editorial page 6 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
tion 3.5
ES 4.1.3.1 Example 3.5 ed Link http://data.acme.org/wfs? Does not work Acme.org seems to be a domain example. If it is, better to change it to example.com?
Accepted
ES 4.2 Requirements Class 4
ed Link http://inspire.ec.europa.eu/specification/RC/TG-Metadata/2.0/networkservices does not work
Wait until specifications are published and check it then again
Accepted with modification.All conformance classes now have a unique id, which will be used to create persistent unique ids following the patterns for ATS agreed in the context of the MIWP-5 work and the implementation of the INSPIRE test framework (http://inspire.ec.europa.eu/id/ats/<ats-id>/<version>).
ES 4.2.1 Requirement 4.1
ed Mistake duplicated“be” Delete “be” Accepted
CZ 4.2.1.1. TG Req. 4.1 ed Double “be” in sentence. Spatial Data Service type shall be be given encoded …
Accepted
CZ 4.2.2.1. TG Req. 4.2 ed Wrong preposition. Metadata for an INSPIRE Network Services shall declare the conformity to the Network Services Implementation Rules, and it shall be encoded …
Accepted
CZ 4.3 Req. Class 5 ed Missing apostrophe. … amendment [Regulation 1312/2014] to [Regulation 1089/2010] adding it’s Annex V.
Not accepted. “its” is correct.
ES 4.3 Requirements Class 5
ed Link http://inspire.ec.europa.eu/RequirementsClass/TG-Metadata/2.0/SDSinvocable does not work
Wait until specifications are published and check it then again
Accepted with modification.All conformance classes now have a unique id, which will be used to create persistent unique ids following the patterns for ATS agreed in the context of the MIWP-5 work and the implementation of the INSPIRE test framework (http://inspire.ec.europa.eu/id/ats/<ats-id>/<version>).
CZ 4.3.1.1. TG Req. 5.1 ed Double “be” in sentence. Spatial Data Service type shall be be given Accepted
ES 4.3.2.1 Foot note 55 ed Link http://inspire.ec.europa.eu/registry/metadata-codelist/OnLineDescriptionCode/accessPoint does not work
Include the Link correct Accepted
ES 4.3.2.1 Example 5.1 ed Link http://inspire.ec.europa.eu/registry/metadata-codelist/OnLineDescriptionCode/accessPoint
Include the Link correct Accepted
ES 4.3.2.1 Table 5.1 ed Links do not work Review the links Accepted
1 Type of comment: ge = general te = technical ed = editorial page 7 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
ES 4.3.2.1 Example 5.3 ed Link http://inspire.ec.europa.eu/RequirementsClass/TG-Metadata/2.0/SDS-invocable does not work
Include the Link correct Accepted with modification.All conformance classes now have a unique id, which will be used to create persistent unique ids following the patterns for ATS agreed in the context of the MIWP-5 work and the implementation of the INSPIRE test framework (http://inspire.ec.europa.eu/id/ats/<ats-id>/<version>).
CZ 4.4 Req. Class 6 ed Missing apostrophe. … amendment [Regulation 1312/2014] to [Regulation 1089/2010] adding it’s Annex VI.
Not accepted. “its” is correct
ES 4.4 Requirements Class 6
ed Link http://inspire.ec.europa.eu/RequirementsClass/TG-Metadata/2.0/SDSinteroperable does not work
Include the Link correct Accepted with modification.All conformance classes now have a unique id, which will be used to create persistent unique ids following the patterns for ATS agreed in the context of the MIWP-5 work and the implementation of the INSPIRE test framework (http://inspire.ec.europa.eu/id/ats/<ats-id>/<version>).
AT 4.4.1.1. TG Requirement 6.2
ed The gmd:codeSpaceelement shall not be be used in this case.
The gmd:codeSpaceelement shall not be used in this case.
Accepted
CZ 4.4.1.1. TG Req. 6.2 ed Double “be” in sentence. … The gmd:codeSpace element shall not be be used in this case.
Accepted
NL 4.4.1.1. ed An editors comment TODO is still there Delete TODO Accepted
ES 4.4.3.1 Foot note 60 ed Link http://inspire.ec.europa.eu/RequirementsClass/TG-Metadata/2.0/SDSinteroperable does not work
Include the Link correct Accepted with modification.All conformance classes now have a unique id, which will be used to create persistent unique ids following the patterns for ATS agreed in the context of the MIWP-5 work and the implementation of the INSPIRE test framework (http://inspire.ec.europa.eu/id/ats/<ats-id>/<version>).
ES 4.4.3.1 Table 6.1 ed Links http://inspire.ec.europa.eu/registry/metadata-codelist/ and http://inspire.ec.europa.eu/registry/metadata-codelist/QualityOfServiceCriteriaCode/minimumPerformance and
Include the Link correct Accepted
1 Type of comment: ge = general te = technical ed = editorial page 8 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
http://inspire.ec.europa.eu/registry/metadata-codelist/ do not work
ES 4.4.3.1 Example 6.1 ed Link http://inspire.ec.europa.eu/registry/metadata-codelist/QualityOfServiceCriteriaCode/minimumPerformance does not work
Include the Link correct Accepted
ES 4.4.3.1 Example 6.1 ed Link http://www.opengis.net/def/uom/SI/second"/ does not work
Change to http://www.opengis.net/def/uom/SI/second
Accepted
CZ 4.5 Req Class 7 ed Missing apostrophe. … amendment [Regulation 1312/2014] to [Regulation 1089/2010] adding it’s Annex VII.
Not accepted. “its” is correct
ES 4.5 Requirements Class 7
ed Link http://inspire.ec.europa.eu/RequirementsClass/TG-Metadata/2.0/SDS-harmonisedThe does not work
Include the Link correct Accepted with modification.All conformance classes now have a unique id, which will be used to create persistent unique ids following the patterns for ATS agreed in the context of the MIWP-5 work and the implementation of the INSPIRE test framework (http://inspire.ec.europa.eu/id/ats/<ats-id>/<version>).
ES 4.5.1.1 Requirement 7.3
ed Mistake in:srv:name/gco:aNamesrv:valueType/gco:TypeName/gco:aName
Change:srv:name/gco:Namesrv:valueType/gco:TypeName/gco:Name
Accepted
CZ 4.5.1.1. TG Req. 7.1 ed Double “the” in sentence. … TG Requirement 5.5 shall fulfil the the invocation metadata requirements.
Accepted
ES Acknowledgements
Contact Information
ed Link http://ies.jrc.ec.europa.eu/ does not work Change to https://ec.europa.eu/jrc/en/institutes/ies Correct link added
FR Acknowledgements
ed French members are not listed Please add Marc Léobet and Marie Lambois Accepted
NL aknowledgements
ed Missing by MIWP-8 group;Peter Kochman, Eliane Roos, Marie Lambois, Marc Leobert, Ine de Visser,…
Add names and check for other missing Accepted
AT Annex C 1.4. ed 1.4. Resource locator Header is not at the top of the chapter Accepted
AT Annex C 4.1. ed 4.1. Bounding box Should be consistent to the document; WGS84 is requested
Not clear what should be added. Current content is identical to TG v1.
NL Annex C 2 1.3
ed Also the resource locator table is in this part Delete resource locator table Accepted
NL Annex C 2 ed Replace the identifier lakes with a more used Not accepted, unless alternative is specified
1 Type of comment: ge = general te = technical ed = editorial page 9 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
1.6 identifier
ES Annex C.2 1.3 Resource Type
ed Link http://edo.jrc.ec.europa.eu/chm/ows.php?VERSION=1.3.0&SERVICE=WMS&REQUEST=GetCapabilities incorrect and does not work
Change Example? Accepted
UK-10
Annex C.2 1.6 Coupled resource
ed Only one example of use given add an example using URI Accepted
UK-11
Annex C.2 all ed In general many of the cross-references cited are incorrect or missing; also need further examples and need checked
Check citation consistency and add additional examples
Accepted.To be done once the document is in final draft.
DE Annex C.2 1.4 Resource locator
ed Heading to 1.4 is between the tables of Resource locator for “datasets and series” and “services”
Shift heading before first table Accepted
DE Annex C.2 1.5 Unique resource identifier, Example
ed namespace and identifier seem to be part of MD_Identifier. Have it more clear that this is a semantic distinguishing only, but storing is in element code only.We had this shown in a much clearer way in a former draft (based on v055)
The Unique resource identifier semantically consisting ofnamespace: https://example.org/and identifier: ab749859 and is provided together in element code:https://example.org/ab749859
Accepted
DE Annex C.2 1.5 Unique resource identifier, Comments
ed link to 2.2.6 is wrong change link to 4.1.2.4 Accepted
DE Annex C.2 1.6 Coupled resource
ed example does not consider both alternatives for data service coupling
add an example using URI for data service coupling according to in 4.1.2.4
Accepted
DE Annex C.2 1.6 Coupled resource, Comments
ed link to 2.2.5 is wrong change link to 3.1.2.1 Accepted
DE Annex C.2 1.7 Resource language, Comments
ed reference to A.11 is not suitable; there's no corresponding content in this document
delete comment Accepted
DE Annex C.2 2.2 Spatial data service type, Domain
ed link to 1.3.1 is wrong change link to Annex D.3 Accepted
DE Annex C.2 4.1 Geographic bounding box, Comments
ed link to SC13 is wrong remove this sentence due to SCxx being erased Accepted
1 Type of comment: ge = general te = technical ed = editorial page 10 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
DE Annex C.2 8.1 Conditions applying to access and use, second table, Domain
ed there are designated codelist values for these texts add a link to Annex D.2 Accepted
DE Annex C.2 8.2 Limitations on public access, second table, Domain
ed there are designated codelist values for the reasons to limit public access
add a link to Annex D.1 Accepted
DE Annex C.2 10.3 Metadata language, Comments
ed reference to A.11 is not suitable; there's no corresponding content in this document
delete comment Accepted
DE Annex C.3 Coordinate Reference System, Domain
ed The mentioned table isn't listed below! The content is in Annex D.5 now.
add link to Annex D.5 Accepted
NL Annex C.4 Part B 1 degree
ed Add a comment that the domain in this case can only have the value true
Add a comment that the domain in this case can only have the value true
“In this case” refers to “if conformant” ?
NL Annex C.4 Part D 2 degree
ed Add a comment that the domain in this case can only have the value true
Add a comment that the domain in this case can only have the value true
“In this case” refers to “if conformant” ?
NL Annex C.5 Part B 3 CRS
ed Add a comment that despite the definition of the ISO element, this is used to provide the CRS of the service
Add a comment that despite the definition of the ISO element, this is used to provide the CRS of the service
Comment added, but meaning unclear
NL Annex C.5 Part B 3 CRS
ed Codespace shall not be used if it is an well-known CRS in a register
Delete in the example the codespace and add the URI
Accepted.
NL Annex C.6 Part B 3 connectPoint
ed Datatype and domain are missing Add Data type (and ISO 19115 no.) URLDomain URL (IETF RFC1738 and IETF RFC 2056)
Domain?
DE Annex C.7 <all>, Example
ed There are no XML examples for theme-specific metadata in the document.
add examples or remove statement Accepted.The references to XML examples have been removed.
1 Type of comment: ge = general te = technical ed = editorial page 11 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
DE Annex C.7 Digital transfer options information, Comments
ed link to 2.2.4 is wrong change link to 3.1.3.1 Accepted
DE Annex C.7 Extent, Domain
ed link to 2.5.1 is wrong change link to 2.4.8 Accepted
UK-12
Annex D.1 Code list URI (general)
ed Registry link does not resolve Update with correct registry URI Accepted
DE Annex D.1 Code list URI ed The URI http://inspire.ec.europa.eu/registry/metadata-codelist/LimitationsOnPublicAccess is unavailable.
If URI is accessable till publication of the document nothing has to be done, if not state shall be described in e.g. footer.
Accepted, URI corrected
DE Annex D.2 Code list URI ed The URI http://inspire.ec.europa.eu/registry/metadata-codelist/ is unavailable.
If URI is accessable till publication of the document nothing has to be done, if not state shall be described in e.g. footer.
Accepted, URI corrected
DE Annex D.4 Code list URI ed The URI http://inspire.ec.europa.eu/registry/metadata-codelist/QualityOfServiceCriteriaCode is unavailable.
If URI is accessable till publication of the document nothing has to be done, if not state shall be described in e.g. footer.
Accepted, URL corrected
NL Annex E ed Not complete for instance see Service type Add requirement number and sections for service type4.2.1.1 TG Requirement 4.14.3.1.1 TG Requirement 5.1Check the other elements on completeness
Accepted
NL Annex E ed Be consequent, provide all IR element numbers and TG requirements.
Add missing IR element numbers annex V D.1 and D.2 annex VI part A.1 and A.2 (and their requirements)
ES C.2 1.6 Coupled resource
ed Link http://vap-xgeodev.jrc.ec.europa.eu/geonetwork/srv/eng/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=f9ee6623-cf4c-11e1-9105-017085a97ab&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ELEMENTSETNAME=full#lakes does not work
Change example? Not accepted. In general readers should not expect URL's in examples to resolve. Even if they would resolve today, there is no guarantee they will be maintained and still resolve in 2-3 years time.
1 Type of comment: ge = general te = technical ed = editorial page 12 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
NL C.5 Implementing Rules for Interoperable
ed Be consequent in the tables provided;C.4 provided tables for all elements, also the elements described in the metadata regulation, C5 provide only the tables with additional elements.
Add table C.5 part A.1 and A.2 orRemove C.4 part D.1 and D.2
Which of the 2 options do we implement?
SE C3 Coordinate Reference system
ed In the Domain row the text “table is listed below” needs to be edited.
Update the text Accepted
NL Changes from the version 1.3 to 2.0
ed Can the changes split in different parts?Deleted requirements/recommendations,Added requirements/recommendationsChanged requirements/recommendationsAnd renumbered, moved etc.
split in different parts; Deleted requirements/recommendations,Added requirements/recommendationsChanged requirements/recommendationsAnd renumbered, moved etc.
Accepted
DK-13
Chapter 1.1
Para 1 ed In the text it is stated that some documents have been identified as important standards. However, one of them is not a standard but a Technical Specification.
Adjust the text accordingly. Accepted
DK-15
Chapter 2.3.2
TG recommendation A.4
ed In the recommendation it is stated that the most important details shall be included in the first 100 first characters. However, if we are talking about very complex data set this can be very difficult to compress a large amount of important information into 100 characters.
We suggest expanding from 100 to 256 characters. This expansion will make increase the possibility to contain the required information, even for complex data sets.
Since this comment is in the EDITORIAL resolutions, I suppose it is accepted by MIWP-8?
Changed in the doc.
DK-19
Chapter 2.3.8
Para 2 ed The answer to the question if bounding box for services only is required if there is an explicit extent is yes. It is clearly stated in table 2 in “COMMISSION REGULATION (EC) No 1205/2008 of 3 December 2008 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata”.
Delete the question mark and the yellow marking. Accepted
DK-24
Chapter 3.1.4.1
TG Req 1.10,Example 1.10
ed The wording of TG Requirement 1.10 and the associated note 33 mentions "service" but section 3 is about data set requirements classes. Likewise, Example 1.10 considers services.
Reformulate the section to consider data set and data set series.
Accepted
DK-26
Chapter 3.2
Para 1 ed There are references to section 4.1 and 4.2-4.4. We would expect it to be 3.2.1 and 3.2.2-3.2.4.
Correct references. Accepted
DK-27
Chapter 4.1.1.1
Para 3 ed The paragraph reads "Table 2 contained in Part C of the same document defines the multiplicity of this element to exactly one for data sets and data
Correct "data sets and data set series" to "spatial data services".
Something wrong with the numbering: 4.1.1.1 is empty.
1 Type of comment: ge = general te = technical ed = editorial page 13 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
set series". Chapter 4 in the TG draft and Table 2 in [Regulation 1205/2008] considers spatial data services.
Content in text corrected as suggestd.
NL Example 1.10
ed This example is in the wrong paragraph Move to 3.1.4.2. Conformity What is the logic with the example numbering? Example 2.* in section 3.* etc.
Section 3.1.4.2 does not exist, example moved to section 3.1.3.2 Conformity.
All numbering to be checked
NL Example 1.9
ed This example is in the wrong paragraph Move to 3.1.4.1. Scope No section 3.1.4.* Check numbering
Example moved to the correct section
NL Example 7.1
ed and it's invocable at connection point address…Please use the defined terms
Replace connection point with end point No example 7.1 exists. Could not find the text.
NL Figure 1 ed Make clear that the requirement is a metadata requirement
Add; Metadata for Invocable Spatial Data Services
Edit figure
SE Foreword Third paragraph
ed In the first sentence. Replace “expressed” with “expressing” or similar. Accepted
SE Foreword Fourth paragaraph
ed In the last sentence. Replace “no that” with “to what” or similar. Accepted
DE Foreword third paragraph
ed "This new version aims at clarifying and expressed technical requirements"
"This new version aims at clarifying and expressing technical requirements"
Accepted
DE Foreword fourth paragraph
ed "... led to some confusion no that is actually ..." please clarify wording Accepted
DE Foreword Fourth paragraph:
ed “The mapping from the ISO 19115/19115 elements …”
“The mapping from the ISO 19115/19119 elements …“
Accepted
DE Foreword last paragraph
ed "The goal has been to only to clarify the existing..." "The goal has been to only to clarify the existing..." Accepted
ES Foreword to this version
Foot note 1 ed Link https://ies-svn.jrc.ec.europa.eu/attachments/download/780/Inspire%20MIG%20ToR%20Update%20TG%20Metadata%20final.pdf does not work
Change to https://ies-svn.jrc.ec.europa.eu/attachments/download/780/Inspire%20MIG%20ToR%20Update%20TG%20Metadata%20final.pdf
Accepted
NL Foreword, ed The mapping from the ISO 19115/19115 The mapping from the ISO 19115/19119 elements Accepted
1 Type of comment: ge = general te = technical ed = editorial page 14 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
4th paragraph
elements…typo
NL Foreword, 4th paragraph
ed …led to some confusion no that is actually required by the technical specification.Not a correct sentence
Delete last part; no that is actually required by the technical specification.
Accepted
NL Foreword, 5th paragraph
ed are presented with the context thecorresponding INSPIRE Regulations…missing word
are presented with the context of thecorresponding INSPIRE Regulations
Accepted
NL Normative references
ed Is it for readability possible to reference to the INSPIRE regulations with a abbreviation of the title instead of the number? [Regulation 1205/2008]
Change [Regulation 1205/2008] to [IR Metadata] etc.
Not accepted. References such as [Regulation 1205/2008] uniquely identify the reference, while references such as [IR Metadata] might lead to confusion.
DE Normative references
ed Work uniform with other similar documents (see e.g. Draft “Technical Guidance for INSPIRE Spatial Data Services and services allowing spatial data services to be invoked”).
e.g. [INSPIRE DIRDirective] INSPIRE, Implementing Directive 2007/2/EC … or[Verordnung 1205/2008/EG INS MD] Verordnung 1205/2008/EC etc.
Not accepted. The proposal makes sense, but requires harmonisation over all TG’s which is out of scope for this document. The current approach is at least consistent within this document.
ES Other References
[TG SDS] ed Link http://inspire.ec.europa.eu/documents/Network_Services/ does not work
Change to http://inspire.ec.europa.eu/documents/Spatial_Data_Services/TG_for_INSPIRE_SDS_3_1.pdf
Add reference when v4.0 is published.
ES Other References
[TG DiscoveryS]
ed Link http://inspire.ec.europa.eu/documents/Network_Services/ does not work
Change to http://inspire.ec.europa.eu/documents/Network_Services/TechnicalGuidance_DiscoveryServices_v3.1.pdf
Accepted
DE Other references
ed Technical Guidance for INSPIRE Discovery Services, version 3.1, http://inspire.jrc.ec.europa.eu/documents/Network_Services/TechnicalGuidance_DiscoveryServices_v3.1.pdf
Link is referenced incomplete and shall be fixed. Accepted.
AT p. 10 ed As the structure of the document structure and the expressions have changed…
As the structure of the document and the expressions have changed…
Accepted
AT p. 10 ed The first section of this annex contains on overview table for these elements…
The first section of this annex contains an overview table for these elements…
Not accepted. Don’t see the difference
AT p.10 ed A new TG Requirement C.3 has been added to specify encoding the the Non-empty Free Text Elements.
A new TG Requirement C.3 has been added to specify encoding the Non-empty Free Text Elements.
Accepted
1 Type of comment: ge = general te = technical ed = editorial page 15 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
AT p.12 ed TG Recommendation 12 has bee split into TG Recommendations 1.4
has been split Accepted
AT p.15 ed Requirements class is a set is related technical requirements defining the mandatory aspects
… is a set of related technical requirements Accepted
AT p.15 ed Data set is an identifiable data that can be accessed separately. A datasetcanbe a partof a whole(series) or a segregate resource.
a segregated resource Not accepted. Cannot find this text in doc.
AT p.17 ed …and numbered as show below: …and numbered as shown below: Accepted.
AT p.49 ed In this specification the above Implementing Rule text is is interpreted to mean in that the conformityshall be declared at least to the following regulations depending on the described INSPIRE resource type
In this specification the above Implementing Rule text is interpreted to mean that the conformityshall be declared at least to the following regulations depending on the described INSPIRE resource type
Accepted
UK-8
Pg 8 Acknowledgments
ed The UK MWIP8 representative is not included Include “James Reid (UK)”. Accepted
ES Reading guidance and transition period
4th paragraph ed It is not describe the section “Annex D” Include a paragraph with the characteristic of Annex D”
Accepted
DE Reading guidance and transition period
first sentence ed "As the structure of the document structure..." "As the structure of the document structure..." Accepted
DE Reading guidance and transition period
first sentence ed "the following sections have been to help..." "the following sections have been <filled in / added ?> to help..."
Accepted
DE Reading guidance and transition period
third bullet point
ed "... and the TG Requirements on sections ..." please clarify wording Accepted
DE Reading guidance
fourth bullet ed "...TG Requirement and Recommendations of contained in the version
"...TG Requirement and Recommendations of contained in the version
Accepted
1 Type of comment: ge = general te = technical ed = editorial page 16 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
and transition period
point 1.3..." 1.3..."
DE Reading guidance and transition period
first paragraph, fourth bullet point
ed Write all references bold and be therefore uniform with other documents.
…[TG SDS]… Accepted
NL Reading guidance, 1th paragraph
ed As the structure of the document structure and the expressions have changed…Not a correct sentence
Delete 2 nd structure; As the structure of the document structure and the expressions have changed …
Accepted
NL Reading guidance, 1th paragraph
ed The informative annex B contains the mapping between the ISO 19115:2003 Core elementsand INSPIRE Implementing Rules for metadata contained in the section 1.1 of the version1.3.Not a clear sentence
Delete 2 nd contains; The informative annex B contains the mapping between the ISO 19115:2003 Core elementsand INSPIRE Implementing Rules for metadata contained in the section 1.1 of the version 1.3.
Accepted
CZ Revision history
page 10 ed Double “the” in sentence (TG Requirement C.3). A new TG Requirement C.3 has been added to specify encoding the the Non-empty Free Text Elements.
Accepted
CZ Revision history
page 11 in the middle
ed Double “and” in sentence (TG Requirement 5). … The IR Requirement for providing both the code and and the code space has been interpreted as integrated parts of a single URI character string.
Accepted
CZ Revision history
page 12 ed Missing letter. TG Recommendation 12 has been split into TG Recommendations …
Accepted
DE Revision history
third bullet point
ed "...to specify encoding the the Non-empty..." "...to specify encoding the the Non-empty..." Accepted
DE Revision history
ninth bullet point
ed "The hierachyLevel element required..." "The hierachyLevel element required..."; we propose to align this font family for ISO element names through the whole document for better readability
Accepted
DE Revision history
15th bullet point
ed The IR Requirement for providing both the code and and the code space has been interpreted as integrated parts of a single URI character string.
The IR Requirement for providing both the code and and the code space has been interpreted as integrated parts of a single URI character string.
Accepted
DE Revision history
29th bullet point
ed TG Recommendation 12 has bee split into TG Recommendations 1.4 (for data sets and data set
TG Recommendation 12 has been split into TG Recommendations 1.4 (for data sets and dataset
Accepted
1 Type of comment: ge = general te = technical ed = editorial page 17 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
series) and 3.3 (for Spatial Data Services). series) and 3.3 (for Spatial Data Services).
DE Revision history
42th bullet point
ed "The TG Requirements 30, 31, 32, 33 and 34 considering the Limitations on public access and the Conditions applying to access and use elements have been revised is TG Requirements C.16 and C.17 about Limitations on public access..."
please clarify wording Accepted
SE Revision history, page 10
Third bullet point from bottom
ed Double ”the” Replace ”encoding the the” with ”encoding of the” Accepted
SE Revision history, page 11
Tenth bullet point from top
ed Unclear wording Replace 2is the TG Requirement” with “is now included in the TG Requirement” or similar
Accepted
DK-7
Terms and abbreviations
ed Typo in definition of “Requirements class”: .. is a set is related …”
Correct typo: “… is a set of related …” Accepted
DE Terms and abbreviations
ed Names of external documents are not flagged flag names of external documents through the whole document for a better readability
Accepted.
DE Terms and abbreviations
paragraph on Requirements class
ed "Requirements class is a set is related technical requirements..."
please clarify wording; "is a set of"? Accepted
NL TG Recommendation C.9
ed Just below this recommendation the comment text “Add TG Recommendation for using gmx:Anchor elements for referring to keywords which have a URIto point to.” is still present
Remove this editor text. Accepted
NL TG Requirement 1.11
ed Can there be some repeating for readability? Repeat or resume C.21, C.22 and C.23 Accepted
NL TG Requirement 2.4
ed gmd:MD_SpatialRepresentationTypeCode referring to one of the valuesof of ISO 19139 code list MD_CharacterSetCode….wrong codelist
Replace with the correct codelist Accepted
NL TG Requirement 4.2
ed Can there be some repeating for readability? Repeat or resume C.21, C.22 and C.23 Accepted
1 Type of comment: ge = general te = technical ed = editorial page 18 of 19
Template for comments Countries: AT, CH, CZ, DE, DK, ES, FR, IT, NL, SE, UK Date: 2016-05-24 Document: TG for Metadata v2.0rc2 Project: MIWP-8
MS Chapter/ Section(e.g. 3.1)
Paragraph/ Figure/ Table/(e.g. Table 1)
Type of comment1
Comments Proposed change Resolution
NL TG Requirement 5.3And TG Requirement 5.4And TG Requirement 5.5
ed Can there be some repeating for readability? Repeat or resume C.21, C.22 and C.23 Accepted
NL TG Requirement 7.1
ed Option 1: All operations and the list of connect points… andOption 2: All operations and the list of connect points…Please use the defined terms
Replace connect points with end points Accepted although the element itself is called srv:connectPoint.
NL TG Requirement 7.2
ed srv:connectPoint/gmd:CI_OnlineResource/gmd:URL shall contain a URLto be used for accessing the service for executing the operation…be more explicit
.. shall contain an endpoint URL Accepted
NL TG Requirement C.16
ed This element shall not be the onesame used for describing conditions applying to access and use….and direct below this requirementThe make the references to the allowed…
Choose the one or same not bothChange the in to
Accepted
DE Verbal forms for expression of provisions
XML examples
ed "The location of the XML elements within the document structure is given using XPath syntax at to top of the text block in bold font"
"The location of the XML elements within the document structure is given using XPath syntax at to top of the text block in bold font"
Accepted
1 Type of comment: ge = general te = technical ed = editorial page 19 of 19