Documentation of CIMTool Mapping

[Sveino]

Do we have any documentation of the "CIMTool Mappings" feature:

Other screen:

[tviegut]

@Sveino : Now you have me very curious. I have never bumped into this mapping screen until right now. I went and tried to do a deep dive into the google group archive for CIMTool. I also scoured the archived legacy website as well as took a look at the context-sensitive help that ships with it. Have found nothing. So it's got me curious.

Now from simply playing around with it, it appears that it creates a corresponding *.mapping-owl file within the Schema folder. I don't have time to dig deeper here now but looks to allow some team of ontological mapping as an Equivalent class or a Super class. The example screenshot has no rhyme or reason I was simply selecting classes and looking at what was produced.

All for now but was quickly responding. You may have already experimented with this as well and if so what I'm saying you may already have looked into.

[Sveino]

I used CIMTool a lot back in 2010, but since I struggle with namespace for extension and nobody maintaining it, I stop using it. I also have to say that I am a bit struggling with the Eclipse way of thinking. Maybe we can check with some of our old timers :-)
I would love to have this functionality being on top of LinkML-map

[admin-cimug]

I used CIMTool a lot back in 2010, but since I struggle with namespace for extension and nobody maintaining it, I stop using it. I also have to say that I am a bit struggling with the Eclipse way of thinking. Maybe we can check with some of our old timers :-)

I would love to have this functionality being on top of LinkML-map

@svein : when I was searching the Google Group archives I ran into a lot of your posts and saw the comments on the namespace extensions. It was interesting as I saw a long email thread from 2014 where Arnold had put out a call for enhancement request for a next release. I saw a host of feature requests, that Tanja, Becky, you & others has made and then suddenly things just went silent. My guess is that other pulls on his time must have made it not feasible to continue (or perhaps discontinued funding?). In any event, the extensions issues that I had discovered independently (and spent significant time debugging/fixing in July and August) should be fixed now. I Thomas and Emilie, in their work using the new LinkML builder, wanted to have properly represented the NC namespaces. So I went to look for the latest CSA 2.3.1 UML model and will apply the appropriate namespacing for them to use as an example for future work. The goal for this is to regenerate the LinkML for them to use that includes the extensions. All for now.