INSPIRE legal requirements for registers and registries What is the specific requirement of COMMISSION REGULATION (EU) No 1089/2010 where a Member State extends a code list, the allowed values of the Art. 6 states "Where extended code lists shall be made available in a register."? Registry federation requirements This page describes the requirements that a resource shall fulfill in order to be part of the INSPIRE Register Federation. There are 3 levels of conformance: the first one is mandatory and contains the minimum information required for the RoR to register the Registry and the Registers in the federation. The second level, contains the information to enable the automatic harvesting of the information. The third one is recommended in order to provide complete information related to each resource. The following paragraphs will describe the to be provided for each required/recommended fields of the classes and the to create the exchange documents (subsequently called format "descriptors"). The idea of the is to provide metadata and data the and to be descriptors registries registers included in the federation in a RDF/XML document (subsequently called "Registry descriptor" or "Register that is publicly available through an http URI. descriptor") The proposed approach is as follows: The (DCAT) is used to model entity (dcat:Catalog). registry The (SKOS) is used to model entity (skos:ConceptScheme) and register item (skos:Concept). At the end of each conformance class there are one example file for the and Registry descriptor one for the (the examples contain also code comments to better understand Register descriptor each of the fields). A useful resource to validate the conformance of the Registry and Register descriptors to the following classes are . Core Conformance This conformance class is good for sharing registry and register metadata in the federation.
INSPIRE legal requirements for registers and registries What is the specific requirement of COMMISSION REGULATION (EU) No 1089/2010 where Art. 6 states "Where a Member State extends a code list, the allowed values of the extended code lists shall be made available in a register."? Registry federation requirements This page describes the requirements that a resource shall fulfill in order to be part of the INSPIRE Register Federation. There are 3 levels of conformance: the first one is mandatory and contains the minimum information required for the RoR to register the Registry and the Registers in the federation. The second level, contains the information to enable the automatic harvesting of the information. The third one is recommended in order to provide complete information related to each resource. The following paragraphs will describe the required/recommended fields to be provided for each of the classes and the format to create the exchange documents (subsequently called "descriptors"). The idea of the descriptors is to provide metadata and data the registries and registers to be included in the federation in a RDF/XML document (subsequently called "Registry descriptor" or "Register descriptor") that is publicly available through an http URI. The proposed approach is as follows: The (DCAT) is used to model entity registry (dcat:Catalog). The (SKOS) is used to model entity register (skos:ConceptScheme) and item (skos:Concept). At the end of each conformance class there are one example file for the Registry descriptor and one for the Register descriptor (the examples contain also code comments to better understand each of the fields). A useful resource to validate the conformance of the Registry and Register descriptors to the following classes are . Core Conformance This conformance class is good for sharing registry and register metadata in the federation.
INSPIRE_Register_Federation_TG.docx