- From: Miles, AJ (Alistair) <A.J.Miles@rl.ac.uk>
- Date: Tue, 4 Nov 2003 12:42:04 -0000
- 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 labels. matchConcepts(String regularExpression) matchConcepts(String regexp, URI thesaurus) --> Returns a list of possible concepts, ordered according to likelihood of match getSupportedSemanticRelations() 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 meaning. 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 http://www.w3c.rl.ac.uk/SWAD/deliverables/8.1_0_3.html Al. CCLRC - Rutherford Appleton Laboratory Building R1 Room 1.60 Fermi Avenue Chilton Didcot 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