Changes between Version 49 and Version 50 of ComposedMetadataRecords

Timestamp:

04/27/10 15:40:12 (15 years ago)

Author:

simonp

Comment:

--

ComposedMetadataRecords

@@ -78 +78 @@
  * These are interpreted as a link to a metadata fragment within the same document. However, from discussions with the deegree developers (who have an advanced xlink implementation in their WFS), it appears that some organisations are interpreting such a link as being a fragment in any document within the local database?
 
- * Since this proposal and the fragment based harvester included allow xlink attributes on any element in the metadata record, composed metadata records with unresolved xlinks (something which may happen if links are not in the cache) may fail validation. This issue is present anyway (ie. it doesn't just happen when using composed metadata records) as !GeoNetwork does not (at present) provide any config options or other controls for an administrator to limit what can be done with records that do not validate.  
+ * Since this proposal and the fragment based harvester included allow xlink attributes on any element in the metadata record, composed metadata records with unresolved xlinks (something which may happen if links are not in the cache) may fail validation. This issue is already present anyway (ie. it doesn't just happen when using composed metadata records) as !GeoNetwork does not provide any config options or other controls for an administrator to limit what can be done with records that do not validate.  
 
 == Participants ==