Editing TM with Ontoply not posible for merged TM

[GoogleCodeExporter]

Omnigator
Version     4.1.0
Build   2009-05-25 #3847 

After having created and merged two simple topic maps, editing is not
possible with Ontopoly.

The question 

"This is topic map contains an older version of the Ontopoly model, so an
upgrade is necessary. Do you want to upgrade it from version 0.0 to 1.9?"

pops up. Answering "ok" yields the error report form with no further error
description.

Original issue reported on code.google.com by alois.gr...@dlr.de on 16 Jun 2009 at 2:28

[GoogleCodeExporter]

Were these two topic maps both Ontopoly topic maps? If so, it should have 
worked. If 
one of the was not, then it is likely that the topic map lost its topic map 
reifier 
topic that holds the Ontopoly metadata. Hence it no longer recognizing it as an 
Ontopoly topic map.

Original comment by indiapaleale@gmail.com on 17 Jun 2009 at 7:16

[GoogleCodeExporter]

Original comment by indiapaleale@gmail.com on 17 Jun 2009 at 7:19

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by indiapaleale@gmail.com on 17 Jun 2009 at 7:23

• Added labels: Component-Ontopoly

[GoogleCodeExporter]

yes both of them were Ontopoly topic maps.
see attachments for really simple topic maps.

Original comment by alois.gr...@dlr.de on 18 Jun 2009 at 2:20

Attachments:

• tmmergetest2.xtm
• tmmergetest1.xtm

[GoogleCodeExporter]

I think the problem is that the topic map reifier was lost, and therefore 
Ontopoly 
couldn't find the Ontopoly meta-ontology, and so it got confused, and tried to 
add 
it where it already existed.

I think the first question has to be: how did you merge them?

Original comment by lar...@gmail.com on 18 Jun 2009 at 4:37

[GoogleCodeExporter]

- I can browse tmmerge1.xtm in omnigator.
- I choose Merge from the menu.
- in the (Merging and Duplicate Suppression) Merge Another Topic Map selection 
list,
I choose tmmerge2.xtm.
- I can browse tmmergetest1.xtm*tmmergetest2.xtm in omnigator.
- Choosing edit from the menu leads to "This is topic map contains an older 
version
of the Ontopoly model, so an upgrade is necessary. Do you want to upgrade it 
from
version 0.0 to 1.9?"
- Pressing ok yields the error form.

Original comment by alois.gr...@dlr.de on 19 Jun 2009 at 1:41

[GoogleCodeExporter]

The problem here is that in topic maps merged in this way the reifier is not 
preserved (because it's a new topic map). It's possible that what we should do 
in 
this situation is to observe that the ontology-version occurrence is present 
twice, 
merge those two topics, set the merged topic as topic map reifier, and then try 
again.

I guess if the ontology-version values are different we need to give up.

Original comment by lar...@gmail.com on 22 Jun 2009 at 8:02

[GoogleCodeExporter]

This issue is now reported by another user as well. It seems we really do need 
to 
fix this.

A workaround is to export the merged topic map to XTM, and then edit the XTM. 
Find 
one of the two topics in the topic map which used to reify the topic map, and 
then 
reinsert the reification. (Exactly how to do that will depend on whether you 
choose 
XTM 1.0 or 2.0.) Then load the XTM and Ontopoly should be able to process it 
correctly.

Original comment by lar...@gmail.com on 2 Sep 2009 at 5:22

[GoogleCodeExporter]

I have this problem too. Ontopia version 5.0.2  also has this bug.
Best regards

Original comment by mjcolmen...@gmail.com on 23 Sep 2009 at 11:08

[GoogleCodeExporter]

Having needed to do this several times I thought I'd write an XSL 
transformation to
do it. The attached xslt 2.0 transformation will fix an XTM 1.0 topic map that 
was
the result of merging an ontopoly topic map with a non-ontopoly map in 
Omnigator.

Original comment by dan.sp...@gmail.com on 17 Jan 2010 at 8:13

Attachments:

• ontopoly-xtm-fix.xsl

[GoogleCodeExporter]

Thank you for that, Dan! At least that gives people a work-around.

Original comment by lar...@gmail.com on 19 Jan 2010 at 8:11

[GoogleCodeExporter]

Yes, the problem is that the reification of the topic map was lost. I'm leaning 
towards just looking up instances of on:topic-map and their 
on:ted-ontology-version 
occurrence instead. That way we don't have to rely on the reification being in 
place.

Original comment by indiapaleale@gmail.com on 20 Jan 2010 at 12:45

[GoogleCodeExporter]

Got another user reporting this today. We really need to fix this issue soon!

Original comment by lar...@gmail.com on 26 May 2010 at 1:12

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

The actual traceback is:

Caused by: java.lang.NullPointerException: Topic name value must not be null.
    at net.ontopia.topicmaps.impl.basic.TopicName.setValue(TopicName.java:72)
    at 
net.ontopia.topicmaps.nav2.webapps.ontopoly.sysmodel.TopicMapReference.setName
(TopicMapReference.java:88)
    at ontopoly.conversion.ConversionUtils.makeOntopolyTopicMap
(ConversionUtils.java:63)
    at ontopoly.conversion.ConversionUtils.upgradeExisting
(ConversionUtils.java:70)
    at ontopoly.pages.UpgradePage$1.onSubmit(UpgradePage.java:55)
    at org.apache.wicket.markup.html.form.Form.delegateSubmit(Form.java:1351)
    at org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:810)

Original comment by lar...@gmail.com on 3 Jun 2010 at 1:37

[GoogleCodeExporter]

Solved in revision 1086 by looking up the reifier through a query for topics of 
type 
"topic map". That enables us to find the reifier and get the ontology version 
number, 
thus solving the problem.

Original comment by lar...@gmail.com on 3 Jun 2010 at 1:57

• Changed state: Fixed
• Added labels: Release5.1.0