Recent changes to bugs

Apply Ontopia's CompactHashSet changes

Lars Heuer — Wed, 13 Jan 2010 13:38:33 -0000

Apply the changes made here: http://code.google.com/p/ontopia/source/detail?r=807

Merging of associations failed

Anonymous — Wed, 06 Jan 2010 16:15:00 -0000

if two topic maps are merge on demand by calling the method Topic.mergeIn, it fails if there are an association type in both topic maps with a merged type ( the same type ). tinyTim throws an ModelConstraint Exception:

Exception in thread "main" org.tmapi.core.ModelConstraintException: All constructs must belong to the same topic map
at org.tinytim.internal.utils.Check._reportModelConstraintViolation(Unknown Source)
at org.tinytim.internal.utils.Check._sameTopicMap(Unknown Source)
at org.tinytim.internal.utils.Check.sameTopicMap(Unknown Source)
at org.tinytim.core.MemoryTopicMap.createAssociation(Unknown Source)
at org.tinytim.core.MemoryTopicMap.createAssociation(Unknown Source)
at TinyTimMergeTest.main(TinyTimMergeTest.java:54)

And because of the fact that I try to merge, the associations don't belong to the same topic map.

equals() in ConstructImpl.java does not compare the Id

Anonymous — Tue, 10 Nov 2009 14:30:09 -0000

I just realised that equals() compare two object using "this == obj" and does not compare the Ids of the constructs (Ontopia does it, though). Is this done by intention? If not, could this be fixed, please?

Uta (Topic Maps Lab)

Same iid at a duplicate statement does not work

Lars Heuer — Tue, 21 Jul 2009 14:41:09 -0000

<http://code.google.com/p/ontopia/issues/detail?id=91>

MapHandler should check if the statement which should get the iid is a
duplicate

Reifier at duplicate construct fails

Anonymous — Tue, 21 Jul 2009 14:39:48 -0000

<http://code.google.com/p/ontopia/issues/detail?id=84>
<http://code.google.com/p/ontopia/issues/detail?id=77>

The MapHandler should check if the statement which should be reified is a
duplicate.

Port the Check class from Ontopia back to tinyTiM

Lars Heuer — Thu, 25 Jun 2009 23:34:09 -0000

tinyTiM's Check class which throws MCEs if something is null was used for Ontopia's TMAPI support.
Ontopia uses this class also to throw IAEs.
Port this feature back to tinyTiM's Check class.

http://ontopia.googlecode.com/svn-history/r146/trunk/ontopia/src/java/net/ontopia/topicmaps/impl/tmapi2/Check.java

MapHandler should keep existing topics

Lars Heuer — Thu, 25 Jun 2009 23:29:42 -0000

The MapHandler should assume that the older topic contains more information than the newer topic and merge the newer topic into the existent and remove the newer topic.
Check also if tinyTiM is also effected by this bug:
http://code.google.com/p/mappa/source/diff?spec=svn165&r=165&format=side&path=/mappa/trunk/tests/test_miohandler.py
and http://code.google.com/p/mappa/source/detail?r=164

Check if it is possible to implement the Ontopia interfaces

Lars Heuer — Sun, 21 Jun 2009 12:02:29 -0000

Now that Ontopia has become open source it may be possible to implement the net.ontopia.topicmaps.core API together with the TMAPI API.

Check if it is possible that all constructs implement org.tmapi.core and net.ontopia.topicmaps.core.

Ensure same topic map constraint

Lars Heuer — Sun, 21 Jun 2009 11:45:39 -0000

Ensure that every factory method checks that all constructs belong to the same topic map:

I.e.:
tm = sys.createTopicMap("http://www.semagia.com/a");
tm2 = sys.createTopicMap("http://www.semagia.com/b");

assoc = tm.createAssociation(tm2.createTopic());

That should not work (MCE / IAE must be thrown).

Reject invalid locators

Lars Heuer — Wed, 11 Mar 2009 16:23:10 -0000

Reject invalid locators, like

tm.createLocator("#fragment");

Either the "#fragment" has to be resolved against the storage address of the tm or a InvalidIRIException should be thrown (depends on a new TMAPI release!). The latter should be preferred since TopicMapSystem.createLocator() does the same as TopicMap.createLocator() and the TopicMapSystem has no locator available which can be used to resolve the fragment against.