1 Type of Comment:Ge = Generalte = Technical Ed = Editorial
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 / oftheISO 19115 / oftheISO 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] andISO 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 abovementionedRegulation." / "... refers to the abovementionedregulation." / 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 imageryand 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 / 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 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:2007
based INSPIRE metadata records, contains TG Requirements and Recommendations describing
metadata 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 describing
metadata 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 the
Technical Guidelines requires using the only the original, unmodified [ISO 19139] and the OGC
service metadata XML Schemas for encoding INSPIRE metadata records. / … this version of the
Technical 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" ofISO 19139code 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) is
provided as Example C.7.” / Accepted.
ES / 2.4.6 / Foot note 25 / ed / Link does not work / Include the Link correct / The link should be
ES / 2.4.6 / 2º paragraph of page 44 / ed / It is not included reference to Annex D.1 “Limitations on public access” / Change “an
INSPIRE code list” by
“an
INSPIRE code list (Annex D.1 “Limitations on public access)
” / Accepted.
ES / 2.4.6 / Example C.8 / ed / Link does not work / Include the Link correct / The link should be
DE / 2.4.6. Limitations on public access / first paragraph / ed / "Concerning providing the metadata for the data sets and servicesthoughDiscovery services..." / "Concerning providing the metadata for the data sets and servicesthroughDiscovery services..." / Accepted.
DE / 2.4.6. Limitations on public access / sentence following TG Requirement C.16 / ed / "Themake the references to the allowed..." / "Tomake 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 does not work / Wait until registry is implemented and check it then again. / Accepted.
ES / 2.4.7 / Foot note 28 / ed / Link does not work / Include the Link correct / Accepted.
ES / 2.4.7 / Example C.9 / ed / Links and 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.
DE / 2.5.1. Conformity / third paragraph / ed / "In this specification the above Implementing Rule textisis 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 Classor 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 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(
DE / 3.1. Baseline metadata for data sets and data set series / Requirements Class 1 / ed / "Metadata record fulfilling all the TG Requirements..." / "AMetadata 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 does not work / Change it to / 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'srecommended to make..." / "It isrecommended to make..." / Accepted.
IT / 3.1.2.2. / TG Requirement 1.4 / Ed / The content of the footnote 33 is already included in the text of the TG Requirement 1.4 / Remove the footnote 33 / Accepted.
DE / 3.1.2.2. Keywords for Spatial Data Theme(s) / TG Requirement 1.4 / ed / "... at least one keyword from theInspireSpatial Data Themes vocabulary..." / "... at least one keyword from theINSPIRESpatial Data Themes vocabulary..." / Accepted.
DE / 3.1.2.3. Spatial resolution / Example 1.4 and 1.5 / ed / "Spatial resolution of a data setsexpressed..." / "Spatial resolution of a data setsexpressed..." / Accepted.
DE / 3.1.2.4. Resource language / sentence following TG Requirement 1.6 / ed / "Table 1 contained in Part C of Regulation1205/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 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 / 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 (
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 code list / Accepted.
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 does not work / The valid link is 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 is indeed: 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 does not work / Change to / Accepted.
ES / 4.1 / Requirements Class 3 / ed / Link 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 (
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 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 / Recommendation 3.5 / ed / Mistake in “gmd:MD_DataIdentifier” / Change by “gmd:MD_DataIdentification” / This recommendation has been removed.
ES / 4.1.3.1 / Example 3.5 / ed / Link 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 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 (
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 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 (
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 does not work / Include the Link correct / Accepted
ES / 4.3.2.1 / Example 5.1 / ed / Link / Include the Link correct / Accepted
ES / 4.3.2.1 / Table 5.1 / ed / Links do not work / Review the links / Accepted
ES / 4.3.2.1 / Example 5.3 / ed / Link 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 (
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 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 (
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 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 (
ES / 4.4.3.1 / Table 6.1 / ed / Links and and do not work / Include the Link correct / Accepted
ES / 4.4.3.1 / Example 6.1 / ed / Link does not work / Include the Link correct / Accepted
ES / 4.4.3.1 / Example 6.1 / ed / Link does not work / Change to / 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 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 (
ES / 4.5.1.1 / Requirement 7.3 / ed / Mistake in:
srv:name/gco:aName
srv:valueType/gco:TypeName/gco:aName / Change:
srv:name/gco:Name
srv: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 does not work / Change to / 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 1.6 / ed / Replace the identifier lakes with a more used identifier / Not accepted, unless alternative is specified
ES / Annex C.2 / 1.3 Resource Type / ed / Link 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 of
namespace:
andidentifier:ab749859
and is provided together in elementcode: / 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
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