Versionen im Vergleich

Alte Version 12

changes.mady.by.user Peter Kochmann

Gespeichert am

verglichen mit

Neue Version 13

changes.mady.by.user Peter Kochmann

Gespeichert am

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.

...

Chapter/ Section (e.g. 3.1)Paragraph/ Figure/ Table/ (e.g. Table 1)Type of commentCommentsProposed changeResolutionKommentiert von (nur zur internen Verwendung)
(all)(all)edof the ISO 19115of the ISO 19115; at places where ISO is abstractly mentioned; please align through the whole document Martin Seiler, Peter Kochmann
Acknowledgementslist of members of MIWP-8gelist is incompleteadd: James Resid (UK), Ine de Visser (NL), Marc Leobet (FR), Marie Lambois (FR), Eliane Roos (FR), Peter Kochmann (DE)  
AcknowledgementsContact informationgecontact person Massimo Craglia seems to be outdated?  
Forewordthird paragraphed"This new version aims at clarifying and expressed technical requirements""This new version aims at clarifying and expressing technical requirements"  
Forewordfourth paragraphed

"... led to some confusion no that is actually ..."

please clarify wording  
Forewordlast paragraphed"The goal has been to only to clarify the existing...""The goal has been to only to clarify the existing..."  
Reading guidance and transition periodfirst sentenceed"As the structure of the document structure...""As the structure of the document structure..."  
Reading guidance and transition periodfirst sentenceed"the following sections have been to help...""the following sections have been <filled in / added ?> to help..."  
Reading guidance and transition periodlist of annexesgeAnnexes A and D are not mentionedadd bullet points for Annexes A and D  
Reading guidance and transition periodthird bullet pointed"... and the TG Requirements on sections ..."please clarify wording  
Reading guidance and transition periodfourth bullet pointed

"...TG Requirement and Recommendations of contained in the version 1.3..."

"...TG Requirement and Recommendations of contained in the version 1.3..."  
Reading guidance and transition periodlast paragraphge

"...a transitional period of 3 years has been defined..."

please add information by whom this period was defined  
Revision historythird bullet pointed"...to specify encoding the the Non-empty...""...to specify encoding the the Non-empty..."  
Revision historyninth bullet pointed"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  
Revision history20th bullet pointge

"A new TG Recommendation 3.4 considering using id attributes of the referred MD_DataIdentification elements and URI fragment identifiers for referring to them in the Coupled resource elements has been added."

please clarify that this applies for one of the two alternatives for data service coupling only  
Revision history42th bullet pointed

"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  
Revision history42th bullet pointge

"Referring to the new INSPIRE code lists for the reason of the Limitations on public access as well as Conditions applying to access and use ("no conditions" or "unknown") is now mandatory using the gmx:Anchor element."

while we support the use of gmx:Anchor elements we'd like to point out that currently this can't be validated with schemas given in section 1.2  
Other references geINSPIRE data specifications are not listed though a lot of information is taken from there (e.g. theme-specific metadata)add TG DS ...  
Other references ge

"[TG SDS] Technical Guidance for INSPIRE Spatial Data Services and services allowing spatial data services to be invoked, version 3.1"

deprecated version 3.1 should no longer be referenced here, please reference version 3.2 instead  
Terms and abbreviations edNames of external documents are not flaggedflag names of external documents through the whole document for a better readability  
Terms and abbreviationsparagraph on Requirements classed"Requirements class is a set is related technical requirements..."please clarify wording; "is a set of"?  
Verbal forms for expression of provisionsXML examplesed

"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"  
1.1. Introductionthird paragraphed

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  
1.1. Introductionsixth paragraphed

"... refers to the abovementioned Regulation."

"... refers to the abovementioned regulation."  
1.2. XML Encoding of ISO metadatafirst paragraphed

"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  
1.2. XML Encoding of ISO metadatafirst paragraphte"To provide an XML encoding also for the INSPIRE service metadata, XML Schemas implementing the [ISO 19119] model have been published by the OGC"add a hint that currently gmx: namespace is not included in the referenced schema and hence e.g. gmx:Anchor elements are not valid  
1.3. INSPIRE Validator Servicefirst paragraphed

"The validator accepts metadata that follow the Metadata Technical Guidelines encoded in EN ISO 19139 schema."

reference to particular schema is missing           
1.3. INSPIRE Validator Servicesecond paragraph in Notege

"The validator is a proof of concept that has been developed to test these guidelines. It is not intended to be an operational tool,..."

"The validator is a proof of concept that has been developed to test these guidelines. It is not intended to be an operational tool,...";

this statement refers to the old version of this document

 

  
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       

...