Changes between Version 4 and Version 5 of ExtendedRegions

Timestamp:

Oct 24, 2012, 7:44:12 AM (12 years ago)

Author:

jesseeichar

Comment:

--

ExtendedRegions

@@ -105 +105 @@
 }}}
 
-The XmlSearch API will be modified so the geom parameter can either be WKT or have the form: region:id, where id is the id of the region to use as a geometry.  If the region has a geometry then that geometry will be loaded otherwise the bbox will be used to create a polygon geometry.
+The !XmlSearch API will be modified so the geom parameter can either be WKT or have the form: region:id, where id is the id of the region to use as a geometry.  If the region has a geometry then that geometry will be loaded otherwise the bbox will be used to create a polygon geometry.
 
-The CatalogSearcher (part of Csw GetRecords) will be modified to replace elements with the attribute gml:id which have the form: region:id
+The !CatalogSearcher (part of Csw !GetRecords) will be modified to replace elements with the attribute gml:id which have the form: region:id
 
-The actual implementation will consist of the services and a strategy object that can be configured the geonetwork configuration files.  The intention is that for a particular application the strategy object can be implemented and configured for use.  The default implementation will be the same as
+The actual implementation will consist of the services and a strategy object that can be configured the geonetwork configuration files.  The intention is that for a particular application the strategy object can be implemented and configured for use.  The default implementation will be the current implementation factored out into the strategy object.
 
 === Backwards Compatibility Issues ===