Hi Jody,
As announced previously, we had a vote to propose GeoNetwork opensource to graduate from the OSGeo incubation process. The vote passed and the milestone release v2.2.0 came out yesterday.
I think the GeoNetwork community has significantly expanded over the last year during the incubation process. The process itself has been instrumental in thinking about a proper governance structure, proposal and release strategy as well as a range of other details that make the project more mature now than it was at the start of the incubation process.
I hope you will agree and will support this request!
Thanks for mentoring us, have a good weekend,
On behalf of the Project Steering Committee, ciao,
Jeroen
Hi Jody,
As announced previously, we had a vote to propose GeoNetwork opensource to graduate from the OSGeo incubation process. The vote passed and the milestone release v2.2.0 came out yesterday.
I think the GeoNetwork community has significantly expanded over the last year during the incubation process. The process itself has been instrumental in thinking about a proper governance structure, proposal and release strategy as well as a range of other details that make the project more mature now than it was at the start of the incubation process.
I hope you will agree and will support this request!
I certainty do support the request; thanks for taking the extra time so we could watch the PSC process tick over in a public manner
I will write up an email later today with the recommendation,
I've posted an official proposal for my changes to support CSW v2.0.2 on the wiki page. I've gotten my changes incorporated into the development version, have tested them against the official test suite from OGC (it passes all of the OWS-5 CITE tests) and am ready to check them into the SVN archive.
--
Archie
-- Archie Warnock warnock@anonymised.com
-- A/WWW Enterprises www.awcubed.com
-- As a matter of fact, I _do_ speak for my employer.
Hi Archie,
Thanks for the proposal. Before giving my OK, I would like to more specifically know what classes and what XSL, XML and XSD files are affected. Could you provide a listing of the affected files? How many files are affected by the change? Does the ISO profile also work with this change?
Cheers,
Jeroen
On Apr 21, 2008, at 10:25 PM, Archie Warnock wrote:
Hi all,
I've posted an official proposal for my changes to support CSW v2.0.2 on the wiki page. I've gotten my changes incorporated into the development version, have tested them against the official test suite from OGC (it passes all of the OWS-5 CITE tests) and am ready to check them into the SVN archive.
--
Archie
-- Archie Warnock warnock@anonymised.com
-- A/WWW Enterprises www.awcubed.com
-- As a matter of fact, I _do_ speak for my employer.
Thanks for the proposal. Before giving my OK, I would like to more specifically know what classes and what XSL, XML and XSD files are affected. Could you provide a listing of the affected files? How many files are affected by the change? Does the ISO profile also work with this change?
Good idea. Here's the output of svn's status command (ignoring transient changes, like to WEB-INF/ and images/):
bash-3.2$ svn status
M src/org/fao/geonet/kernel/csw/CatalogDispatcher.java
M src/org/fao/geonet/kernel/csw/services/DescribeRecord.java
M src/org/fao/geonet/kernel/csw/services/getrecords/CatalogSearcher.java
M src/org/fao/geonet/kernel/csw/services/getrecords/FieldMapper.java
M src/org/fao/geonet/kernel/csw/services/getrecords/SearchController.java
M src/org/fao/geonet/kernel/csw/services/GetRecords.java
M src/org/fao/geonet/kernel/csw/services/GetRecordById.java
M src/org/fao/geonet/csw/common/Csw.java
M src/org/fao/geonet/csw/client/MainFrame.java
M web/geonetwork/xml/schemas/dublin-core/index-fields.xsl
M web/geonetwork/xml/schemas/dublin-core/dc.xsd
S web/geonetwork/xml/validation/gml
S web/geonetwork/xml/validation/filter
S web/geonetwork/xml/validation/ows
M web/geonetwork/xml/validation/readme.txt
A web/geonetwork/xml/validation/csw/2.0.2
A web/geonetwork/xml/validation/csw/2.0.2/rec-dcmes.xsd
A web/geonetwork/xml/validation/csw/2.0.2/rec-dcterms.xsd
A web/geonetwork/xml/validation/csw/2.0.2/csw-2.0.2.xsd
D web/geonetwork/xml/validation/csw/2.0.1
D web/geonetwork/xml/validation/csw/2.0.1/rec-dcmes.xsd
D web/geonetwork/xml/validation/csw/2.0.1/csw-2.0.1.xsd
D web/geonetwork/xml/validation/csw/2.0.1/rec-dcterms.xsd
M web/geonetwork/xml/csw/schemas/iso19139/iso-full.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19139/iso-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19139/iso-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-full.xsl
M web/geonetwork/xml/csw/capabilities.xml
M web/geonetwork/xsl/conversion/import/Convert_CSW-CITE_test_metadata.xsl
M web/geonetwork/index.html
Note that most of the schema changes for the element sets are just changes to the CSW namespace URI.
It ought to work the same with the ISO profile as the 2.0.1 code did but I've only looked at it superficially. The CITE test data is all Dublin Core.
Either before or after check-in (your call) I can put an installation up on my local server here and load it up with the GN sample data for more widespread testing.
--
Archie
-- Archie Warnock warnock@anonymised.com
-- A/WWW Enterprises http://www.awcubed.com
-- As a matter of fact, I _do_ speak for my employer.
Thanks for the proposal. Before giving my OK, I would like to more
specifically know what classes and what XSL, XML and XSD files are
affected. Could you provide a listing of the affected files? How many
files are affected by the change? Does the ISO profile also work with
this change?
Good idea. Here's the output of svn's status command (ignoring
transient changes, like to WEB-INF/ and images/):
bash-3.2$ svn status
M src/org/fao/geonet/kernel/csw/CatalogDispatcher.java
M src/org/fao/geonet/kernel/csw/services/DescribeRecord.java
M src/org/fao/geonet/kernel/csw/services/getrecords/CatalogSearcher.java
M src/org/fao/geonet/kernel/csw/services/getrecords/FieldMapper.java
M src/org/fao/geonet/kernel/csw/services/getrecords/SearchController.java
M src/org/fao/geonet/kernel/csw/services/GetRecords.java
M src/org/fao/geonet/kernel/csw/services/GetRecordById.java
M src/org/fao/geonet/csw/common/Csw.java
M src/org/fao/geonet/csw/client/MainFrame.java
M web/geonetwork/xml/schemas/dublin-core/index-fields.xsl
M web/geonetwork/xml/schemas/dublin-core/dc.xsd
S web/geonetwork/xml/validation/gml
S web/geonetwork/xml/validation/filter
S web/geonetwork/xml/validation/ows
M web/geonetwork/xml/validation/readme.txt
A web/geonetwork/xml/validation/csw/2.0.2
A web/geonetwork/xml/validation/csw/2.0.2/rec-dcmes.xsd
A web/geonetwork/xml/validation/csw/2.0.2/rec-dcterms.xsd
A web/geonetwork/xml/validation/csw/2.0.2/csw-2.0.2.xsd
D web/geonetwork/xml/validation/csw/2.0.1
D web/geonetwork/xml/validation/csw/2.0.1/rec-dcmes.xsd
D web/geonetwork/xml/validation/csw/2.0.1/csw-2.0.1.xsd
D web/geonetwork/xml/validation/csw/2.0.1/rec-dcterms.xsd
M web/geonetwork/xml/csw/schemas/iso19139/iso-full.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19139/iso-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19139/iso-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-full.xsl
M web/geonetwork/xml/csw/capabilities.xml
M web/geonetwork/xsl/conversion/import/Convert_CSW-CITE_test_metadata.xsl
M web/geonetwork/index.html
Note that most of the schema changes for the element sets are just
changes to the CSW namespace URI.
It ought to work the same with the ISO profile as the 2.0.1 code did but
I've only looked at it superficially. The CITE test data is all Dublin
Core.
Either before or after check-in (your call) I can put an installation up
on my local server here and load it up with the GN sample data for more
widespread testing.
Hi Archie,
Thanks! I have two questions/observations that I would like to see resolved
1- The CSW client seems unaffected, except for a version number change. Does it work against the CSW 2.0.2? I would like to make sure it is aligned with the CSW 2.0.2.
2- The CSW harvesting in the current version targets CSW 2.0.1. That harvesting should also be updated to harvest from 2.0.2 nodes. Same thing, I would like to be sure that harvesting is also aligned.
I understand you will be out for a week. I'm OK with you checking in the code to trunk now if the two points above will be resolved. Other PSC members will also need to vote on the proposal in the coming days in order to have it passed. If it does not pass, we'll have to find a solution next week to ensure it will eventually pass.
For now I vote +1 assuming the points above will be resolved.
Cheers,
Jeroen
On Apr 22, 2008, at 5:51 PM, Archie Warnock wrote:
Jeroen Ticheler wrote:
Thanks for the proposal. Before giving my OK, I would like to more specifically know what classes and what XSL, XML and XSD files are affected. Could you provide a listing of the affected files? How many files are affected by the change? Does the ISO profile also work with this change?
Good idea. Here's the output of svn's status command (ignoring transient changes, like to WEB-INF/ and images/):
bash-3.2$ svn status
M src/org/fao/geonet/kernel/csw/CatalogDispatcher.java
M src/org/fao/geonet/kernel/csw/services/DescribeRecord.java
M src/org/fao/geonet/kernel/csw/services/getrecords/CatalogSearcher.java
M src/org/fao/geonet/kernel/csw/services/getrecords/FieldMapper.java
M src/org/fao/geonet/kernel/csw/services/getrecords/SearchController.java
M src/org/fao/geonet/kernel/csw/services/GetRecords.java
M src/org/fao/geonet/kernel/csw/services/GetRecordById.java
M src/org/fao/geonet/csw/common/Csw.java
M src/org/fao/geonet/csw/client/MainFrame.java
M web/geonetwork/xml/schemas/dublin-core/index-fields.xsl
M web/geonetwork/xml/schemas/dublin-core/dc.xsd
S web/geonetwork/xml/validation/gml
S web/geonetwork/xml/validation/filter
S web/geonetwork/xml/validation/ows
M web/geonetwork/xml/validation/readme.txt
A web/geonetwork/xml/validation/csw/2.0.2
A web/geonetwork/xml/validation/csw/2.0.2/rec-dcmes.xsd
A web/geonetwork/xml/validation/csw/2.0.2/rec-dcterms.xsd
A web/geonetwork/xml/validation/csw/2.0.2/csw-2.0.2.xsd
D web/geonetwork/xml/validation/csw/2.0.1
D web/geonetwork/xml/validation/csw/2.0.1/rec-dcmes.xsd
D web/geonetwork/xml/validation/csw/2.0.1/csw-2.0.1.xsd
D web/geonetwork/xml/validation/csw/2.0.1/rec-dcterms.xsd
M web/geonetwork/xml/csw/schemas/iso19139/iso-full.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19139/iso-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19139/iso-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-full.xsl
M web/geonetwork/xml/csw/capabilities.xml
M web/geonetwork/xsl/conversion/import/Convert_CSW-CITE_test_metadata.xsl
M web/geonetwork/index.html
Note that most of the schema changes for the element sets are just changes to the CSW namespace URI.
It ought to work the same with the ISO profile as the 2.0.1 code did but I've only looked at it superficially. The CITE test data is all Dublin Core.
Either before or after check-in (your call) I can put an installation up on my local server here and load it up with the GN sample data for more widespread testing.
--
Archie
-- Archie Warnock warnock@anonymised.com
-- A/WWW Enterprises http://www.awcubed.com
-- As a matter of fact, I _do_ speak for my employer.
Thanks for the proposal. Before giving my OK, I would like to more
specifically know what classes and what XSL, XML and XSD files are
affected. Could you provide a listing of the affected files? How many
files are affected by the change? Does the ISO profile also work with
this change?
Good idea. Here's the output of svn's status command (ignoring
transient changes, like to WEB-INF/ and images/):
bash-3.2$ svn status
M src/org/fao/geonet/kernel/csw/CatalogDispatcher.java
M src/org/fao/geonet/kernel/csw/services/DescribeRecord.java
M src/org/fao/geonet/kernel/csw/services/getrecords/CatalogSearcher.java
M src/org/fao/geonet/kernel/csw/services/getrecords/FieldMapper.java
M src/org/fao/geonet/kernel/csw/services/getrecords/SearchController.java
M src/org/fao/geonet/kernel/csw/services/GetRecords.java
M src/org/fao/geonet/kernel/csw/services/GetRecordById.java
M src/org/fao/geonet/csw/common/Csw.java
M src/org/fao/geonet/csw/client/MainFrame.java
M web/geonetwork/xml/schemas/dublin-core/index-fields.xsl
M web/geonetwork/xml/schemas/dublin-core/dc.xsd
S web/geonetwork/xml/validation/gml
S web/geonetwork/xml/validation/filter
S web/geonetwork/xml/validation/ows
M web/geonetwork/xml/validation/readme.txt
A web/geonetwork/xml/validation/csw/2.0.2
A web/geonetwork/xml/validation/csw/2.0.2/rec-dcmes.xsd
A web/geonetwork/xml/validation/csw/2.0.2/rec-dcterms.xsd
A web/geonetwork/xml/validation/csw/2.0.2/csw-2.0.2.xsd
D web/geonetwork/xml/validation/csw/2.0.1
D web/geonetwork/xml/validation/csw/2.0.1/rec-dcmes.xsd
D web/geonetwork/xml/validation/csw/2.0.1/csw-2.0.1.xsd
D web/geonetwork/xml/validation/csw/2.0.1/rec-dcterms.xsd
M web/geonetwork/xml/csw/schemas/iso19139/iso-full.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19139/iso-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19139/iso-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-full.xsl
M web/geonetwork/xml/csw/capabilities.xml
M web/geonetwork/xsl/conversion/import/Convert_CSW-CITE_test_metadata.xsl
M web/geonetwork/index.html
Note that most of the schema changes for the element sets are just
changes to the CSW namespace URI.
It ought to work the same with the ISO profile as the 2.0.1 code did but
I've only looked at it superficially. The CITE test data is all Dublin
Core.
Either before or after check-in (your call) I can put an installation up
on my local server here and load it up with the GN sample data for more
widespread testing.
Thanks! I have two questions/observations that I would like to see resolved
Seems fair
1- The CSW client seems unaffected, except for a version number change. Does it work against the CSW 2.0.2? I would like to make sure it is aligned with the CSW 2.0.2.
All I've done with the client (so far) is to change the version number and namespace path. It works with the server on a fairly superficial level - I used it a good bit in testing - but there isn't a test suite for clients, so I haven't done any deeper testing.
2- The CSW harvesting in the current version targets CSW 2.0.1. That harvesting should also be updated to harvest from 2.0.2 nodes. Same thing, I would like to be sure that harvesting is also aligned.
I'll try to look at it this morning. I agree that GN should be able to harvest its own nodes
I understand you will be out for a week. I'm OK with you checking in the code to trunk now if the two points above will be resolved. Other PSC members will also need to vote on the proposal in the coming days in order to have it passed. If it does not pass, we'll have to find a solution next week to ensure it will eventually pass.
They _will_ be resolved, but probably not today (since I leave in about 2 hours). I can take the code with me (I think - new laptop and all) to work on this while I'm away but my Internet access will depend on how often I can get to a Starbucks. In the worst case, if the check-in is completely screwed up, we can roll back the archive to today's state. I don't think there are any hidden disasters waiting there, but one never knows without testing.
I apologize that the timing is a little awkward. I know a number of people are quite anxious to get started with the new version and I don't want to hold that up.
--
Archie
-- Archie Warnock warnock@anonymised.com
-- A/WWW Enterprises www.awcubed.com
-- As a matter of fact, I _do_ speak for my employer.
Hi Archie,
Thanks! I have two questions/observations that I would like to see resolved
1- The CSW client seems unaffected, except for a version number change. Does it work against the CSW 2.0.2? I would like to make sure it is aligned with the CSW 2.0.2.
2- The CSW harvesting in the current version targets CSW 2.0.1. That harvesting should also be updated to harvest from 2.0.2 nodes. Same thing, I would like to be sure that harvesting is also aligned.
I understand you will be out for a week. I'm OK with you checking in the code to trunk now if the two points above will be resolved. Other PSC members will also need to vote on the proposal in the coming days in order to have it passed. If it does not pass, we'll have to find a solution next week to ensure it will eventually pass.
As it happens, my trip is now canceled and I'll be in the office this week. I will check the CSW client against the CSW server with the GN sample records loaded and will also check the harvesting before I check in the code. I hope to get the code checked in tomorrow or Friday.
--
Archie
-- Archie Warnock warnock@anonymised.com
-- A/WWW Enterprises www.awcubed.com
-- As a matter of fact, I _do_ speak for my employer.
As it happens, my trip is now canceled and I'll be in the office this week. I will check the CSW client against the CSW server with the GN sample records loaded and will also check the harvesting before I check in the code. I hope to get the code checked in tomorrow or Friday.
I've now tested the CSW 2.0.2 client against two servers - the original CSW 2.0.2 reference implementation with the CITE test data and the development version of GN from subversion with CSW 2.0.2 code (yes, it's self-testing!) and the GN sample data. I got sensible query results from both, although I don't have a comprehensive test suite to run.
I also tested the CSW harvesting using the 2.0.2 code against the same two servers and got results back. As I told Jeroen last night, I believe it's ready to check into the archive so we can begin widespread testing. I'll do that today.
Once it's in, I'll update from subversion on a couple of my machines and run the CITE tests against the server, just to make sure it's fully compliant (ie, that I haven't overlooked anything important), and then test with the CSW standalone and harvesting clients. I'll post when that's done so others can start shooting at it and try to find anything that I may have missed.
Thanks to all for your patience!
--
Archie
-- Archie Warnock warnock@anonymised.com
-- A/WWW Enterprises www.awcubed.com
-- As a matter of fact, I _do_ speak for my employer.
hi Jeroen:
yeah. sorry for this late reply. Now i can process this. how can i submit the code files? can i send the transaction and harvest related files in csw to you?
Thanks for the proposal. Before giving my OK, I would like to more
specifically know what classes and what XSL, XML and XSD files are
affected. Could you provide a listing of the affected files? How
many
files are affected by the change? Does the ISO profile also work
with
this change?
Good idea. Here’s the output of svn’s status command (ignoring
transient changes, like to WEB-INF/ and images/):
bash-3.2$ svn status
M src/org/fao/geonet/kernel/csw/CatalogDispatcher.java
M src/org/fao/geonet/kernel/csw/services/DescribeRecord.java
M src/org/fao/geonet/kernel/csw/services/getrecords/
CatalogSearcher.java
M src/org/fao/geonet/kernel/csw/services/getrecords/
FieldMapper.java
M src/org/fao/geonet/kernel/csw/services/getrecords/
SearchController.java
M src/org/fao/geonet/kernel/csw/services/GetRecords.java
M src/org/fao/geonet/kernel/csw/services/GetRecordById.java
M src/org/fao/geonet/csw/common/Csw.java
M src/org/fao/geonet/csw/client/MainFrame.java
M web/geonetwork/xml/schemas/dublin-core/index-fields.xsl
M web/geonetwork/xml/schemas/dublin-core/dc.xsd
S web/geonetwork/xml/validation/gml
S web/geonetwork/xml/validation/filter
S web/geonetwork/xml/validation/ows
M web/geonetwork/xml/validation/readme.txt
A web/geonetwork/xml/validation/csw/2.0.2
A web/geonetwork/xml/validation/csw/2.0.2/rec-dcmes.xsd
A web/geonetwork/xml/validation/csw/2.0.2/rec-dcterms.xsd
A web/geonetwork/xml/validation/csw/2.0.2/csw-2.0.2.xsd
D web/geonetwork/xml/validation/csw/2.0.1
D web/geonetwork/xml/validation/csw/2.0.1/rec-dcmes.xsd
D web/geonetwork/xml/validation/csw/2.0.1/csw-2.0.1.xsd
D web/geonetwork/xml/validation/csw/2.0.1/rec-dcterms.xsd
M web/geonetwork/xml/csw/schemas/iso19139/iso-full.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19139/iso-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19139/iso-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19139/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/dublin-core/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/fgdc-std/ogc-full.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-brief.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-summary.xsl
M web/geonetwork/xml/csw/schemas/iso19115/ogc-full.xsl
M web/geonetwork/xml/csw/capabilities.xml
M web/geonetwork/xsl/conversion/import/Convert_CSW-
CITE_test_metadata.xsl
M web/geonetwork/index.html
Note that most of the schema changes for the element sets are just
changes to the CSW namespace URI.
It ought to work the same with the ISO profile as the 2.0.1 code
did but
I’ve only looked at it superficially. The CITE test data is all
Dublin
Core.
Either before or after check-in (your call) I can put an
installation up
on my local server here and load it up with the GN sample data for
more
widespread testing.
