[topicmapmail] Tolog Queries

Premnath Raghavendran premnath.raghav@wipro.com
Sat, 26 Apr 2003 18:15:27 +0530


Hi,

I have some questions on Tolog based on my little understanding on this=
 query language.

We can write efficient tolog queries if we know before-hand, the topic map=
 we are going to query on. If the various associations available in that=
 Topic Map are already known, then the queries can be very specific &=
 efficient.

But in my case, I have dynamically generated Topic Maps repository. Say=
 there are several users who generate Topic Maps on any subject of their=
 interest. Say one user may generate Topic Map on a technical topic, other=
 on a national event, on some sports event , etc.=20

All these Topci maps are to be stored in an Ozone back-end.

My system provides a simple user interface, wherein a user can key-in the=
 topic for which he wishes to retrieve relevant links.

Given this scenario, what parameters should I consider for writing an=
 efficient tolog-rule.

Pre-determining the various associations availabe is ruled out as I do not=
 know what Topic Maps have been generated.

Tolog performs powerful query if the association is known. In my situation,=
 I cannot use them.

I could only think of using
1) has-type=20
2) has-occurrence
rules for querying my Topic Maps.

Are there any other rules using which I can make my queries powerful? Can I=
 retrieve associations by just using the keyword that the user has typed=
 in?

Am using TM4J for generating my Topic Map and for querying the same.

Any suggestions would be very helpful.

Thanks
Prem

**************************Disclaimer************************************

Information contained in this E-MAIL being proprietary to Wipro Limited is=
=20
'privileged' and 'confidential' and intended for use only by the individual
 or entity to which it is addressed. You are notified that any use, copying=
=20
or dissemination of the information contained in the E-MAIL in any manner=20
whatsoever is strictly prohibited.

***************************************************************************