Changes between Version 2 and Version 3 of 1q2007
- Timestamp:
- Apr 2, 2007, 1:20:46 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
1q2007
v2 v3 13 13 A lot of development has been going over the last 9 months. Many new functions have been added and existing ones have been enhanced. The plan is to release a final version 2.1 of the catalog software towards the end of April 2007. Here's a summary of what has been developed for this release: 14 14 15 * Support for the ISO-19115 metadata standard, formatted and validated against the ISO-19139 implementation schema .15 * Support for the ISO-19115 metadata standard, formatted and validated against the ISO-19139 implementation schema [wiki:115and139Confusion Read more]. 16 16 17 17 The ISO19115-19139 standards seem to confuse many, many people. Here's a short attempt to clarify the situation :-) … … 20 20 To confuse things more, many software started implementing different versions of the ISO-19115 standard :( The !GeoNetwork development team decided back in 2002 to use the Draft International Standard version of ISO-19115 (ISO-19115:DIS). This version of the standard (not yet standard at that point) provided a DTD and was as such the only version that could have a formal checking of its structure. !GeoNetwork used (and still supports) short element names in its XML representation. 21 21 22 For !GeoNetwork 2.1 we have now created a migration procedure to convert the ISO-19115:DIS formatted metadata into a structure that complies with the formal ISO-19115:2003 standard and that validates against the ISO-19139 schema version 0.6 22 For !GeoNetwork 2.1 we have now created a migration procedure to convert the ISO-19115:DIS formatted metadata into a structure that complies with the formal ISO-19115:2003 standard and that validates against the ISO-19139 schema as [http://eden.ign.fr/xsd/isotc211/20060504 released on 4 May 2006] referred to as 'final Release candidate for TS'. 23 24 GeoNetwork opensource still supports the 19115:DIS format for backward compatibility, but it is foreseen that that format will be less exposed to users to facilitate transition to the new format and avoid a bit of confusion :-) 25 26