Menu
▾
▴
[TM4J-users] Some ideas for *cross* TM navigation with TM Nav
|
From: <vt...@ne...> - 2004-08-30 07:04:44
|
Hello, Fist of all, I've just download the latest version of TM Nav : Whaooooo =21= = Real improvement against the 0.2.5 one : I'm really impress by the new =22= abstracting=22 and =22rendering=22 features, which are really very useful. I mail you to know if you plan to include some *cross* TM navigation featu= res in complement to the *direct* TM navigation feature you've implemente= d in the latest release ... I mean : = by *direct* TM navigation : navigation allowing you to know *everything* = about *a unique topic* (id, all name(s), all PSI(s), all occurrence(s) and= all r=F4le(s) player, ...) by *cross* TM navigation : navigation allowing you to know *only few thin= gs*, but about *all the topics of one given topic type* (some name, some o= ccurrence(s) and some r=F4le(s) player), ...) Imagine something which allow you to define sorts of extraction =22pattern= s=22 : One =22pattern=22 define : - 1 : a given topic type to begin the =22cross TM navigation=22 - 2 : the occurrence you want to see via the definition of =22given occur= rence types =5Bof the given topic type=5D) - 3 : the topics you want to see via the definition of =22given role typ= es involved in a given association type where the given topic play a given= role type=22 - and for each topic define again point 2 and point 3 - and so on ... For example : I want to =22extract=22 : = - all topics of the *people* topic type = - with *e-mail* =22occurrence type=22 = - with *telephon* =22occurrence type=22 = - ... And perhaps other kind of =22occurrence type=22 = - and all the topic of =22company type=22 playing the role of =22employer= =22 in a *employ* =22association type=22 where the given people play a *em= ploye* =22role type=22 - with *home page* occurrence type=22 = - ... And perhaps other kind of =22occurrence type=22 = - and for each *company* : all the topic of =22company type=22 playing = the role of =22partner=22 ... - and for each *company* : all the topic of =22company type=22 playing = the role of =22subsidiary=22 ... - ... The idea is to be able to use patterns to navigate TMs (with sort pr=E9-d= efine differents perspectives) ... For one given topic type you have one o= r more pattern defined, if there is only one pattern you take this pattern= otherwise you give the choice to the user (by contextual menu for exemple= ) ... And when the =22view=22 is extract you can apply to the extracted =22= output=22 topics the available pattern(s) according to them type by the sa= me processus I describe for the =22input=22 topic type ... A pattern should be valid for a set of TMs conform to a given ontology. I think if the topic map is driven by a ontology it is more powerful, beca= use topic type are declare =22by intention=22 in the ontology and not =22b= y extention=22 in the KB ... And in this case you can associate a set of =22= pattern=22 to a given ontology and use it for each map conform to this ont= ology ... But it's not mandatory to have the feature I describe above Hope I was clear in my explanations Regards and thank a lot for such wonderful tool Bernard ------------------------------------------------------------- NetCourrier, votre bureau virtuel sur Internet : Mail, Agenda, Clubs, Tool= bar... Web/Wap : www.netcourrier.com T=E9l=E9phone/Fax : 08 92 69 00 21 (0,34 =80 TTC/min) Minitel: 3615 NETCOURRIER (0,16 =80 TTC/min) |
