VOConcepts paper
Doug Tody
dtody at nrao.edu
Thu Dec 1 10:22:33 PST 2005
I suspect we are headed towards something like that. Probably what is
needed is to define the information in some simple, stable,
technology-independent fashion which we (IVOA) control, then auto-generate
the namespaces and mappings in several popular forms such as OWL, RDF,
etc., for use at runtime by implementations. Perhaps also in HTML, for
human viewing of the terminology and dictionaries. It should be possible
to use the information without having to adopt some complex inference
framework, but we don't want to prevent people from doing so either. Doug
On Thu, 1 Dec 2005, Elizabeth Auden wrote:
>> We don't want to build this vocabulary (which will evolve constantly) into
>> each service implementation, so it needs to be possible to download these
>> mappings via the network, and cache the translation table in the service.
>> They need to be in a standard form which the service code can deal with,
>> probably something based on XML.
>
> Perhaps OWL or RDF triples?
>
> --
> Elizabeth Auden, MSSL
> Holmbury St. Mary, Dorking RH5 6NT
> Tel: +44 (0)1483 204 276
> eSDO Technical Lead, AstroGrid Developer
>
More information about the voevent
mailing list