Changes between Version 12 and Version 13 of ComposedMetadataRecords

Timestamp:

08/31/09 21:03:48 (15 years ago)

Author:

simonp

Comment:

--

ComposedMetadataRecords

@@ -48 +48 @@
 Metadata records as traditionally handled by !GeoNetwork should not be affected by the addition of this feature.
 
-Effects on harvesting: Composed metadata records can have their XLinks resolved before they are harvested as a harvester usually updates the set of records harvested from a remote site on a regular basis. If there was a requirement for composed metadata records to be harvested with unresolved XLinks then this could be made as an 
+Effects on harvesting: Composed metadata records can have their XLinks resolved before they are harvested as a harvester usually updates the set of records harvested from a remote site on a regular basis. If there was a requirement for composed metadata records to be harvested with unresolved XLinks then an option could be added to the harvester to prevent XLink resolution before harvesting.
 
-Effects on export (eg. MEF): Composed metadata records exported as MEF files would normally have their XLinks resolved before export. 
+Effects on export (eg. MEF): Composed metadata records exported as MEF files would normally have their XLinks resolved before export. If there was a requirement for composed metadata records to be exported with unresolved XLinks then an option could be added to the MEF export service to prevent XLink resolution before export.
 
 XLinks and metadata records composed from xlink'd fragments can be made optional through the use of a system configuration option.
@@ -60 +60 @@
  * Geocat.ch implementors - have similar requirements including transaction support for metadata fragments
  * Other XLink implementors: Jesse, Francois, Patrick
+ * URN resolver and GeoServer community schema support: AuScope/Spatial Information Services Stack (SISS) team
+ * "Relational" metadata - LISASoft developers?
  * Others?