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 ge harvesting the registry information, the Requirement harvester will check the URL of the register Note that with. TG Req 10 it is important to 5 descriptors provided in the Registry have consistency between the forward and descriptor. If it is not resolvable, it is not backward links from registry to register and imported. register to registry. Will the harvester reject submissions where they are inconsistent? 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 ed the system will check if”… Difficult to Please consider to reformulate Updated “If TG Req 6 understand many (Too many “if´s” conditions…) 6.1.1 Note below ed A question: We thought that the media type is This is a custom media type, set up following TG Req 6 bound to a controlled vocabulary () the guideline used by IANA. We may be wrong? It will be to the new INSPIRE media type register currently being tested. DE 6.1.1 TG ed Generalization of the TG Requirements Remove from TG To be discussed „mandatory/optional“ Requirement Requirements 6.1.2 3,4 TG Requirement 9 6.1.1 Table page ed Notes would be appreciated especially for Please consider to add. Notes added – 30 properties not mentioned in the text; e.g. foaf:mbox 6.1.2 Table te Make note, that there can be only one The RoR currently does not support – property skos:prefLabel for each language. 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
• 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
inspire-tg-registers-and-register-federation-mig-t-comment-resolution.docx