Recent changes to bugs

Invalid Snapshot version for OSGi

2010-09-21T18:05:11Z

The Snapshopts get the version 2.0.3-SNAPSHOT in the manifest.mf .
Eclipse does not recognize the version and trying out a version with - it complains the version is invalid.
Replacing the - with a dot works.

Add clear method to TopicMap

2010-08-31T10:55:08Z

Add a clear method to TopicMap which does the same as:

final Locator loc = tm.getLocator();
tm.remove();
tm = tmSys.createTopicMap(loc);

conflict with FEATURE_TYPE_INSTANCE_ASSOCIATIONS

2010-07-19T12:20:28Z

I think there are different interpretations for the feature FEATURE_TYPE_INSTANCE_ASSOCIATIONS in the context of the addType method of a topic.

@"TestTypeInstanceIndex.testTopic" and "TestTopicRemovableConstraint."testUsedAsTopicType"

The first test checks if the type-instance association was created after calling addType ( topic number increases by 3 because of association and role types)
assertEquals(5, _typeInstanceIdx.getTopics(null).size());

The other test does not check this and expects that the topics are not created.

If the feature FEATURE_TYPE_INSTANCE_ASSOCIATIONS is not set, all works fine, otherwise at least one of the tests failed. I think the second test has to check, too, if the feature is set, right?

Find a patch attached.

More Specs for Variants

2010-02-19T14:16:06Z

http://code.google.com/p/ontopia/issues/detail?id=209 showed that there is a need for more tests regarding scope in variants. The patch attached adds three more. Tinytim currently passes them while Ontopia failes 2 of the 3 new ones.

The failing ones are
org.tmapi.core.TestName.testVariantCreationWithDataTypeIllegalEmptyScope(TestName.java:193)
and
org.tmapi.core.TestName.testVariantCreationWithDataTypeIllegalEmptyArrayScope(TestName.java:217)

Support engines which check for duplicates

2009-06-25T15:43:09Z

Some tests assume that

type = tm.createTopic();
assoc1 = tm.createAssociation(type);
assoc2 = tm.createAssociation(type);

does not cause a merge of assoc1 and assoc2. These tests should be refactored and avoid failures for engines which detect such duplicates and merge them.

Test for type-instance relationships as assoc

2009-06-25T15:40:34Z

The current test suite assumes that the underlying TM engine does not use assocs as for type-instance relationships.
TODO: Check the tests if they work for engines which model the relationships as assoc (take care of topic count / assoc count etc)

Move IRI-specifc tests to a separate package

2009-05-12T13:13:11Z

- Extract the RFC 3986 specific tests from TestLocator and create a separate IRI test (suite)
- Add tests to TestLocator which resolve relative addresses against a base URI which are compatible to RFC 2396 *and* RFC 3986

tmapi.org is not reachable, only www.tmapi.org

2009-03-27T12:58:26Z

Trying to reach http://tmapi.org/ results in a time out, only http://www.tmapi.org/ is reachable. This is bad since all feature IRIs omit the www. prefix.

Adjust tests: isa-relationship as assoc

2009-03-27T12:53:31Z

TMAPI should be liberal and do not force an implementation to model type-instance relationships as
a) property of a topic
b) association

Some tests may fail if type-instance-associations are used, fix them

The tests should try to enable / disable (a) and (b) and check the behavior of the implementation conditionally (without forcing the impl. to provide both options)