From: Kal A. <ka...@te...> - 2004-08-30 17:03:30
|
TMAPI supports XTM 1.0 as well as whatever ISO comes up with for XTM 1.1. Support for XTM 1.0 cannot be removed from TMAPI so regardless of what ISO do to source locators for XTM 1.1, we must allow for a subject locator clash to be reported. On the question of support for multiple subject locators - if it seems that ISO is going to do this anyway (I think it is a *really* bad idea), then we should add support into TMAPI. The question is should we add it now or in a TMAPI 1.1. I would vote for releasing TMAPI 1.0 with only a single subjectLocator value allowed on a Topic. TMAPI 1.1 can be released later to support multiple subjectLocators. Cheers, Kal On Mon, 2004-08-30 at 17:41, Stefan Lischke wrote: > Hi, > > I talked with Lars M. Garshol about this issue in the IRC (#topicmaps on > freenode). > Please have a look at our discussion: > > http://www.ontopia.net/topicmaps/irc/irclog/2004-08-30.html#t17:57:29 > > i think his proposal with multiple source locators, fixes all our > problems with TopicMergeException. > > So i would support his proposal to remove > setSubjectLocator() replace it by add/remove subjectLocator() > and delete TopicMergeException from all TMAPI methods. > > What do others think? > > I also want to see what the topicmap mail community is thinking about > this issue which was decided in amsterdam this year. > > stefan > > Lars Marius Garshol wrote: > > >* Stefan Lischke > >| > >| I think i now have a use case: > >| > >| Topic A with subjectIdentity a and TopicName "topic1" > >| Topic B with subjectIdentity b > >| > >| now someone uses TMAPI with "automerging on" and "TopicName merging > >| on" and calls (Topic B).createTopicName("topic1") > >| > >| what can the user expect? > > > >It depends whether the subject identity is a subject locator or not. > >If it is a subject locator there should be an exception, otherwise > >not. > > > >Note that the current TMAPI departs from the latest TMDM here; topics > >should be able to have multiple subject locators. So maybe we should > >add support for that and ditch the whole exception and the whole > >problem? > > > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > _______________________________________________ > Tmapi-discuss mailing list > Tma...@li... > https://lists.sourceforge.net/lists/listinfo/tmapi-discuss -- Kal Ahmed <ka...@te...> techquila |