Re: Low level API

Hi Leonard

> I don't think that it should be necessary to store "level" information to
> achieve this, and indeed I think that doing so would complicate matters,
> because if a concept is inserted to create a new level of grouping then
> the "levels" of all the subordinate concepts would change.
>
Yes, skos takes the approach of expressing broader/narrower/related 
relationships between concepts. If we are to add what is effectively 
harvesting functionality to the thesaurus, then we would likely return skos 
encoded data as is, from which some client app would be able to build a 
thesaurus browser if required.

If time permits we may demonstrate how this would work against our own demo 
thesaurus service implementation. For example either by layering Protege on 
top of our service for browser-based views on the data, or developing 
prototype viewer implementations that we already have.

Nikki


> Leonard Will
> --
> Willpower Information       (Partners: Dr Leonard D Will, Sheena E Will)
> Information Management Consultants              Tel: +44 (0)20 8372 0092
> 27 Calshot Way, Enfield, Middlesex EN2 7BQ, UK. Fax: +44 (0)870 051 7276
> L.Will@Willpowerinfo.co.uk               Sheena.Will@Willpowerinfo.co.uk
> ---------------- <URL:http://www.willpowerinfo.co.uk/> -----------------
>
>



----------------------
NJ Rogers, Technical Researcher
(Semantic Web Applications Developer)
Institute for Learning and Research Technology (ILRT)
Email:nikki.rogers@bristol.ac.uk
Tel: +44(0)117 9287096 (Direct)
Tel: +44(0)117 9287193 (Office)

Received on Tuesday, 11 May 2004 11:12:52 UTC