Changes between Version 10 and Version 11 of registers

Timestamp:

10/26/11 00:25:35 (13 years ago)

Author:

simonp

Comment:

--

registers

@@ -37 +37 @@
  * The content of a register is often copied into another format for convenience eg. the ISO19139 codelists in http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml is copied into a codelists.xml file and stored in the localized !GeoNetwork directory for use by the !GeoNetwork editor. This should be modified so that the register content is not copied, only the association between the register and an element is held otherwise recording and propagating changes to register content is too difficult. 
 
-The motivation for this proposal is to capture register changes in the register, make registers transportable between catalogs through harvesting, and hold the register content in ISO19135 which is then accessed by everything (hmm).  
+The motivation for this proposal is to:
+ * implement ISO19135 so that register changes and evolution are captured in the ISO19135 register record
+ * make ISO19135 registers transportable between catalogs through harvesting
+ * hold the register content in ISO19135 which is then accessed by all processes needing a register item
+ * allow GeoNetwork to manage ISO19135 registers  
 
 == Proposal ==