W3C home > Mailing lists > Public > public-esw-thes@w3.org > November 2003

Thesaurus API

From: Miles, AJ (Alistair) <A.J.Miles@rl.ac.uk>
Date: Tue, 4 Nov 2003 12:42:04 -0000
Message-ID: <350DC7048372D31197F200902773DF4C04943F8B@exchange11.rl.ac.uk>
To: "Nikki Rogers (E-mail)" <Nikki.Rogers@bristol.ac.uk>, "Dave Beckett (E-mail)" <dave.beckett@bristol.ac.uk>
Cc: "'public-esw-thes@w3.org'" <public-esw-thes@w3.org>

Not going near the multilingual problem yet, I suggest this for a core API -

getConcept(URI uniqueidentifier)

getConcept(Literal descriptor, URI thesaurus)

getConcept(Literal externalID, URI thesaurus)

	--> Returns a single 'Concept' datastructure, including all the

matchConcepts(String regularExpression)

matchConcepts(String regexp, URI thesaurus)

	--> Returns a list of possible concepts, ordered according to
likelihood of match


getSupportedSemanticRelations(URI thesaurus)

	--> Return a list of supported semantic relations (e.g. broader,
narrower, is-a, etc.), each with a unique uri and a description of their

getConceptRelatives(URI conceptURI)

getConceptRelatives(Literal descriptor, URI thesaurus)

getConceptRelatives(Literal externalID, URI thesaurus)

getConceptRelatives(URI conceptURI, SemanticRelation rel)

getConceptRelatives(Literal descriptor, URI thesaurus, SemanticRelation rel)

getConceptRelatives(Literal externalID, URI thesaurus, SemanticRelation rel)

	--> Returns list of relatives of concept as specified.   

This API is designed to be consistent with the way thesaurus data is
modelled in the schemas in 



CCLRC - Rutherford Appleton Laboratory
Building R1 Room 1.60
Fermi Avenue
Oxfordshire OX11 0QX
United Kingdom

Email:        a.j.miles@rl.ac.uk
Telephone: +44 (0)1235 445440
Received on Tuesday, 4 November 2003 07:46:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:45:08 UTC