Moving to RDF

Date	2012-10-28
Contact(s)	Simon Pigot
Last edited
Status	draft, being discussed, in progress
Assigned to release	Not yet assigned to a release
Resources	Not allocated yet.
Ticket #	#XYZ

Overview

GeoNetwork converts content from all metadata schemas that it supports to a common XML index document via XSLT. This common XML document is ingested by Lucene, which creates an index of the fields within the document. The Lucene index is used for searching in GeoNetwork.

The common XML index document for each schema could be replaced by an RDF (resource data format) document

Proposal Type

• Type: Core Change
• App: GeoNetwork
• Module: Data Manager, Search Interface

Links

• Documents:
• Email discussions:
• Other wiki discussions:

Voting History

• Not proposed for voting yet.

---

Motivations

The current configuration is .... A change to ....

Proposal

An in depth proposal can be found here : link ...

Unanswered Questions

Object Identifiers: One of the stated key advantages of RDF is that objects are identified once and then reused. In the work done to date, I don't see how converting a record to RDF will identify the individual objects for reuse eg. if a piece of contact info is present in two different metadata records, then how is that object uniquely identified? Perhaps the object identifier could be derived from an md5sum on the content of the object?

Backwards Compatibility Issues

New libraries added

Explain which and why new libraries are required for that proposal ...

Risks

Participants

• Simon Cox, CESRE (CSIRO Australia)
• Wahhaj Ali, Tianyi Chen, Cameron Fitzgerald, Joshua Hollick, Saxon Jensen, Rebecca Papadopoulos - University of Western Australia
• Simon Pigot