Changes between Version 3 and Version 4 of registers
- Timestamp:
- Oct 25, 2011, 7:47:36 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
registers
v3 v4 13 13 A register as defined in ISO19135 is a list of items that have been assigned an identifier. ISO19135 has models of a register and describes the roles and procedures necessary for registering an item. An registered item may be any piece of geographic information. For the purposes of this proposal the items in the register will be the codelists or vocabularies associated with a metadata record. This proposal describes: 14 14 15 * the addition of the XML schema implementation of ISO19135 to GeoNetwork as a plugin schema16 * how codelists, vocabularies and thesaurii will be implemented as ISO19135 records (registers) in GeoNetwork15 * the addition of the XML schema implementation of ISO19135 to !GeoNetwork as a plugin schema 16 * how codelists, vocabularies and thesaurii will be implemented as ISO19135 records (registers) in !GeoNetwork 17 17 * how metadata records in a metadata schema will be linked to these registers 18 18 … … 24 24 === Links === 25 25 * '''Documents''': ISO19135: Geographic information - Procedures for item registration (unfortunately this must be purchased from ISO) 26 * '''ISO19135 Plugin Schema Implementation ''': http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/schemaPlugins/trunk/iso19135/26 * '''ISO19135 Plugin Schema Implementation for !GeoNetwork''': http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/schemaPlugins/trunk/iso19135/ 27 27 28 28 === Voting History === … … 33 33 Currently: 34 34 35 * Vocabularies, codelists and thesauri are held in static files external to the GeoNetwork catalog. The process by which items in these registers are modified, updated, superseded or retired are invisible as the formats they are held in do not support capture of this information.35 * Vocabularies, codelists and thesauri are held in static files external to the !GeoNetwork catalog. The process by which items in these registers are modified, updated, superseded or retired are invisible as the formats they are held in do not support capture of this information. 36 36 * Metadata records that use items from these registers usually do so by referencing an external document (eg. http://asdd.ga.gov.au/asdd/profileinfo/anzlic-theme.xml) 37 * Often the codelist has been converted to yet another format for use in the GeoNetwork editor (eg. the ISO19139 codelists in http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml are converted to a codelists.xml file for use in GeoNetwork). Recording and propagating changes to a codelist in this environment is difficult to say the least.37 * Often the codelist has been converted to yet another format eg. for use in the !GeoNetwork editor the ISO19139 codelists in http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml are converted to a codelists.xml file and stored in the localized GeoNetwork directory. Recording and propagating changes to a codelist in this environment is difficult to say the least. 38 38 39 39 The motivation for this proposal is to capture register changes in the register, make registers transportable between catalogs through harvesting, and converge access to one register format. … … 41 41 == Proposal == 42 42 43 * Implement ISO19135 register models (implemented as a draft XML schema at http://www.isotc211.org/2005/grg/register.xsd) as a plugin schema for GeoNetwork43 * Implement ISO19135 register models (implemented as a draft XML schema at http://www.isotc211.org/2005/grg/register.xsd) as a plugin schema for !GeoNetwork 44 44 * Develop an XSLT to convert the ISO19139 CT_CodelistCatalog format to ISO19135 register format 45 * Add ISO19135 register records to ISO metadata schemas and profiles (to be loaded with the schema/profile intoGeoNetwork category 'Registers')46 * 45 * Add ISO19135 register records to ISO metadata schemas and profiles (to be loaded with the schema/profile or regularly harvested into !GeoNetwork category 'Registers') 46 * GeoNetwork looks up the codelist item in the list of register records associated with the metadata schema of the metadata record being edited 47 47 48 48 === Backwards Compatibility Issues === 49 49 50 None - if the ISO19135 register records for a metadata schema don't exist then the code for this proposal won't be used. 51 50 52 === New libraries added === 51 Explain which and why new libraries are required for that proposal ... 53 54 None. 52 55 53 56 == Risks == 54 57 58 Everything involves some element of risk.... 59 55 60 == Participants == 56 * List of participants and role (if necessary) in current GIP 61 62 * Simon Pigot 63 * Others?
