is used, it is clearly stated as e.g. <dcat:dataset>, followed by its properties, however SKOS-objects are stated as a <rdf:Description>, followed by the declaration of its type, using the property rdf:type. could be both a "Concept" and an "INSPIRE theme"). <dcat:dataset> refers to a relationship (between a "dcat:Catalog" and other entities), not an entity itself. all Figures ge When reading the document it seems like the Figure numbering not always match the reference in the text. Check if all the figure numbering matches the figure reference. Updated UK Executive summary and sections ge could make the scope of resources to be included in registers more explicit by giving examples of the kinds of INSPIRE resources with URIs that would not be included in a register. Not accepted. The executive summary and introduction already give some examples of the resources in scope. The document is deliberately open to including different types of resources in national registers and also in the INSPIRE register federation. It will be ultimately up to the national or European control bodies to accept or reject proposals for inclusions of registers. NL Foreword 5 Ed Typo: will improved ‘will improve’ Updated NL 1 1 Ed Typo ‘should reused’ > ‘should re-use’ Updated NL 1 5 Ed Missing verb ‘Within the MIWP 2014-2016, an action and sub-group (MIWP-6) was therefore set up to develop technical guidelines and best practices for setting up register and registries and to work out how European, national or community registers and the links between them can be published in and accessed through a register federation.’ Reworded to "… for setting up register and registries and for publishing and accessing European, national or community registers and the links between them through a register federation." NL 1 7 Ed Broken reference to chapter 6 Fix reference Updated NL 1 7 Ed Broken reference to annex C Fix reference Updated NL 2 Ge Ref to W3C DWBP should not reference the editor’s draft. Editor’s drafts are just the publicly available working version of W3C documents and are continually changing until the document is complete. The URL provided in the Normative Reference is the correct one, Either make this an undated reference, or reference the Candidate Recommendation of 30 August 2016. The date has been updated (15 December 2016). The document is now. W3C Proposed Recommendation.
NL 6.2 Ed Broken references to requirements and recommendations Fix Updated UK 6.1.1 Note: Ed Change “If the system will if the Register descriptor is available at the given URI through an HTTP GET request to the URI with the HTTP Accept header set to Otherwise it will ask for the resource using the standard HTTP GET request.” to The system will check the Register descriptor is available at the given URI through an HTTP GET request to the URI with the HTTP Accept header set to "application/x-ror-rdf+xml". Otherwise it will ask for the resource using the standard HTTP GET request without an Accept header. Text changed 6.1.1 TG Req. 1 te “an http URI”. This may require specification. The address of the document – where to find it – is by it’s nature an URL. But it reasonable to let the address of the document be identical to the HTTP-URI identifier of the document. Updated to HTTp-URI 6.2 Para 1 te “automatically harvested”. So publishing the accrual period is all it takes to become automatically harvestable? Please explain. Yes, the frequency of the harvesting it is the only information required NL 6.1.1 Req 1 Ge By stating it must be an http URI, https is prohibited. Consider allowing https. ‘http(s) URI’ Accepted 6.1.1 Tg 2 te “well-defined”. What does that mean? Who defines? Where is it described? Please consider to add clarification/definition. The examples are provided below in the text 6.1.1 Tg 2 ed (example URI: ) is not dereferentiable at time being The publication office is shortly going to make it dereferenceable. NL 6.1.1 Rec 2 Ge Not the URI of the foaf:Agent class, but the URI of the foaf:Agent individual should be provided Remove ‘class’. Updated UK 6.1.1 TG 2 ge Not clear what "well-defined URI pattern" means here. Same comment for 6.1.2 TG Recommendation 3 Accepted. Reworded to: TG Recommendation 1 The URI of the foaf:Agent should be taken from an organisation register or provided using a URI well-defined URI pattern. EXAMPLE Some examples are provided below:
• URI identifying the "European Commission, Research Centre" in the EU Publications Office's corporate body register : • URI identifying National Geographic Institute Belgium in DBpedia: UK 6.1.1 TG Requirement 5 ge Note that with. TG Req 10 it is important to have consistency between the forward and backward links from registry to register and register to registry. Will the harvester reject submissions where they are inconsistent? harvesting the registry information, the harvester will check the URL of the register descriptors provided in the Registry descriptor. If it is not resolvable, it is not imported. On the hand, while importing the registers information, if the reference to the registry is wrong, it is not imported. 6.1.1 Note below TG Req 6 ed “If the system will check if”… Difficult to understand many “if´s” (Too many conditions…) Please consider to reformulate Updated 6.1.1 Note below TG Req 6 ed A question: We thought that the media type is bound to a controlled vocabulary () We may be wrong? This is a custom media type, set up following the guideline used by IANA. It will be to the new INSPIRE media type register currently being tested. DE 6.1.1 6.1.2 TG Requirement 3,4 TG Requirement 9 ed Generalization of the TG Requirements Remove „mandatory/optional“ from TG Requirements To be discussed 6.1.1 Table page 30 ed Notes would be appreciated – especially for properties not mentioned in the text; e.g. foaf:mbox Please consider to add. Notes added 6.1.2 Table – property te Make note, that there can be only one skos:prefLabel for each language. The RoR currently does not support multilinguality. We have added the following footnote: It is possible to specify more than one skos:prefLabel element, one per language. However, at the time of writing, the RoR does not support multilinguality. Therefore, if available, the English skos:prefLabel element (xml:lang="en"), or else the first