Changes between Version 2 and Version 3 of registers


Ignore:
Timestamp:
Oct 25, 2011, 7:38:10 PM (12 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • registers

    v2 v3  
    2424=== Links ===
    2525 * '''Documents''': ISO19135: Geographic information - Procedures for item registration (unfortunately this must be purchased from ISO)
    26  * '''ISO19135 Plugin Schema Implementation''':
     26 * '''ISO19135 Plugin Schema Implementation''': http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/schemaPlugins/trunk/iso19135/
    2727
    2828=== Voting History ===
    … …  
    3333Currently:
    3434
    35  * Vocabularies, codelists and thesaurii 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.
    3636 * 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). Propagating changes to a codelist
     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.
    3838
    3939The 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. 
    … …  
    4141== Proposal ==
    4242
    43 
    44 
     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 GeoNetwork
     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 into GeoNetwork category 'Registers')
     46 * 
     47 
    4548=== Backwards Compatibility Issues ===
    4649