Menu
▾
▴
[Tm4j-commits] tm4j/docs TMDM-support.html,1.3,1.4
|
From: Xuan B. <med...@us...> - 2007-04-20 12:20:29
|
Update of /cvsroot/tm4j/tm4j/docs In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv30825/docs Modified Files: TMDM-support.html Log Message: Deprecate methods which allow moving occurences between different parents. See bug https://sourceforge.net/tracker/?func=detail&atid=391879&aid=1704268&group_id=27895 for more. Index: TMDM-support.html =================================================================== RCS file: /cvsroot/tm4j/tm4j/docs/TMDM-support.html,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** TMDM-support.html 17 Apr 2007 14:57:21 -0000 1.3 --- TMDM-support.html 20 Apr 2007 12:20:20 -0000 1.4 *************** *** 8,11 **** --- 8,12 ---- <body> <h2>Current plans on how to support TMDM</h2> + <h3>TM4J and TMDM</h3> The basic idea is to implement a superset of the current TM4J (0.9.x) and the TMDM. Following issues need to be addressed:<br> *************** *** 59,66 **** <li>TopicMapFlavour.TMDM: behave as TMDM expects (for example, throw exceptions if there will be multiple players per role introduced ! by using the old API)<br> ! </li> </ul> </ul> <h3>Need for test-suite</h3> There is a need for a test-suite.<br> --- 60,81 ---- <li>TopicMapFlavour.TMDM: behave as TMDM expects (for example, throw exceptions if there will be multiple players per role introduced ! by using the old API)</li> </ul> </ul> + <h3>TM4J and TMAPI</h3> + <ul> + <li>In TM4J 0.9.x, you can create an occurence for a topic and then + orphan it by removing it from the set of Occurences from its parent by + calling Topic.setOccurrences(). This orphaned occurence can later be + added to a different Topic. However, orphaned occurences (that is: + occurences without a parent), are not allowed in TMDM. Thus (and + because indexing of these occurences would be more difficult), TM4J 2 + should not support orphaned occurences. Thus, the corresponding API + which allows orphaning occurences and readding occurences to different + topics (maybe even without properly removing them from their previous + parents) should be depreciated and later removed.<br> + </li> + </ul> + <br> <h3>Need for test-suite</h3> There is a need for a test-suite.<br> |
