I have implemented a simple LSID authority providing both data and metadata from the current (version 3) MIR. This is based on the IBM LSID authority tutorial example and the previous MIR metadata dumping code (extended and refined).

Currently this does a dump of MIR content on startup, exporting metadata to a Jena2 model and making various conversions/mapping to make the information more suitable for exposure as RDF.

It answers metadata queries from this model (returning a dynamic subgraph as an RDF doc), and answers data queries by a nested query direct to the MIR.

It is intended to extend the service at some point to use the notification service to monitor additions to the MIR to allow this to be kept in sync. The current metadata model is also in memory, and the MIR used is compiled in; at some point the Jena2 relational database back-end should be tried, probably when notification support is added.

I have not attempted to expose any of the data within the DataThings^? as metadata, e.g. information solely inside the provenace log or workflow definition, but this would be a relatively simple extension to make (at least to the framework - e.g. using Haystack's strategy of XSL translations to produce RDF from XML file formats).

In CVS the (new) module is mir-lsid-authority. Currently it is statically configured for the MIR on archer2 at Nottingham.

For examples of use, see MirLsidAndHaystack.

-- ChrisGreenhalgh - 21 Nov 2003