Hi list,
I've got an answer of Ian, an ASFA thesaurus specialist.
But, I don't understand his questions.
Could you help me to make a good thesaurus for geonetwork ?
This FAO thesaurus is covering the world's literature on the science, technology, management, and conservation of marine, brackish water, and freshwater resources and environments, including their socio-economic and legal aspects.
Here are his questions :
The ASFA subject thesaurus was updated this year as we said earlier. In looking to the future, as well as producing the thesaurus as a Word document, my colleagues and I converted the thesaurus to an XML file. Looking further forward, we decided to try to produce an ontology (using the web ontology standard OWL and based on a simple modelling of that standard ) just to ensure that such conversions could be carried out on the XML file. We did the same with a very simple SKOS model - again just as a proof that the XML file would be OK for this. It proved to be fine for both.
However, there are many different models one could use with the OWL or SKOS standards depending on how one wants to use the terminology tool. For example, the partners in the NeOn project needed to use the ASFA thesaurus as an ontology and remodelled the XML file in a different way to produce an OWL ontology more suitable to their application (in my opinion, it is also a neater model than mine - but it depends on what you want to do with it). My point here is that they used the XML file NOT my OWL or SKOS files.
As far as I am concerned, GeoNetwork is welcome to both my OWL and SKOS files but they might not be as much use to your users as the XML.
Hi Bruno,
I'm not an expert on these other forms of XML but for ISO 19115 metadata the ISO 19139 gmx Schemas should be used for thesauri and code lists. The root element is 'CT_CodelistCatalogue' with multiple 'codelistItem' elements for the dictionaries and multiple 'CodeEntry' elements for each value in that dictionary.
Examples of these can be found at:
http://asdd.ga.gov.au/asdd/profileinfo/
Web page. They include "ANZLIC Geographic Extent Names", "ANZLIC Search Words", "ANZLIC Jurisdictions", "Geoscience Australia's extension of the MD_ScopeCodes" and "OSDM Schedule names for Australian Government Agencies". Although these aren't specific to the topics that your specialist, you can follow the way things are laid out.
Of course the resulting dictionary XML file should be validated against the XSDs to prove compliance to the ISO 19139 and ISO 19115 standard.
I hope that this helps.
John
-----Original Message-----
From: Bruno Granger [mailto:bruno.granger@anonymised.com]
Sent: Friday, 21 November 2008 8:35 AM
To: GeoNetwork-users@lists.sourceforge.net
Subject: [GeoNetwork-users] Thesaurus help
Hi list,
I've got an answer of Ian, an ASFA thesaurus specialist.
But, I don't understand his questions.
Could you help me to make a good thesaurus for geonetwork ?
This FAO thesaurus is covering the world's literature on the science,
technology, management, and conservation of marine, brackish
water, and
freshwater resources and environments, including their socio-economic
and legal aspects.
Here are his questions :
The ASFA subject thesaurus was updated this year as we said
earlier. In looking to the future, as well as producing the
thesaurus as a Word document, my colleagues and I converted
the thesaurus to an XML file. Looking further forward, we
decided to try to produce an ontology (using the web ontology
standard OWL and based on a simple modelling of that standard
) just to ensure that such conversions could be carried out
on the XML file. We did the same with a very simple SKOS
model - again just as a proof that the XML file would be OK
for this. It proved to be fine for both.
However, there are many different models one could use with
the OWL or SKOS standards depending on how one wants to use
the terminology tool. For example, the partners in the NeOn
project needed to use the ASFA thesaurus as an ontology and
remodelled the XML file in a different way to produce an OWL
ontology more suitable to their application (in my opinion,
it is also a neater model than mine - but it depends on what
you want to do with it). My point here is that they used the
XML file NOT my OWL or SKOS files.
As far as I am concerned, GeoNetwork is welcome to both my
OWL and SKOS files but they might not be as much use to your
users as the XML.
--------------------------------------------------------------
-----------
This SF.Net email is sponsored by the Moblin Your Move
Developer's challenge
Build the coolest Linux based applications with Moblin SDK &
win great prizes
Grand prize is a trip for two to an Open Source event
anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork