Messages

1

Automation Interface, Add-Ins and Tools / Re: OWL, VOM and UML Profile

« on: February 24, 2010, 06:25:00 pm »

Nice summary Don.
The answer to your last qustion is very simple for me:
We want to create basic concepts and reference lists and links between them all as one foundation for semantic interoperability of dislocated, heterogenous (environmental) data which have to be integrated.
We would be happy if there was  1 plattform for that whole task. But there is not just  1 platform. A lot of data exchange and data integration is still done on XML / XML-Schema level (all the OGC stuff for example).
Much semantic work is done on RDF / OWL and I suppose that one day also data exchange and data integration will be done on that plattform.
Much semantic work is done on UML-level (all the ISO stuff around ISO TC211).
That's the reason why we tremendously need tools for round trip engeneering between those 3 platforms.

Herbert

2

Automation Interface, Add-Ins and Tools / Re: OWL, VOM and UML Profile

« on: February 24, 2010, 01:21:37 am »

I will do so!

So far we have seen that it should be quite simple to generate a .OWL file from the access database of EA.

Did any one do this task already?

herbert

3

Automation Interface, Add-Ins and Tools / Re: OWL, VOM and UML Profile

« on: January 15, 2010, 11:11:19 pm »

So we have got two tasks:
(1) select a common name for that feature - proposed name: OMD-profile

(2) find as many people as possible to support that feature request

Herbert

4

Automation Interface, Add-Ins and Tools / Re: OWL, VOM and UML Profile

« on: January 15, 2010, 09:57:39 pm »

fine - can we move it there?
I wouldn't even mind to reenter the text - if you start a thread at "suggestions and requests" - simply tell me

herbert

5

Automation Interface, Add-Ins and Tools / Re: OWL, VOM and UML Profile

« on: January 15, 2010, 06:06:08 pm »

Additionally:

It was not difficult to copy the imported elements to a created profile. But then the connections to existing stereotypes were missing, as they can be seen when loading the profile  into MagicDraw.(the correct profile, - which I got from the MagicDraw support center)

I think that a lot of other information was lost too.

Herbert

6

Automation Interface, Add-Ins and Tools / Re: OWL, VOM and UML Profile

« on: January 15, 2010, 05:53:14 pm »

I introduced a model and one packaged element before the line starting with <profile.... :

<uml:Model xmi:type="uml:Model" name="EA_Model" visibility="public">
<packagedElement xmi:type="uml:Package" xmi:id="EAPK_3466B606_3DF9_4440_B7E2_55E44FABA47E" name="OWLasUML" visibility="public">


so you also need this at the end:
.......
            </packagedElement>
      </uml:Model>
</xmi:XMI>

then I changed the profiles (OWL and RDF) to packaged Elements:

<packagedElement xmi:type="uml:Package" xmi:id="EAPK_5B1C5D75_36D2_43e8_97E8_2A1CE5194F0C" name="OWL" visibility="public">

(all the EA - GUIDS were taken from an empty EA-dummy project)

I also changed the MagicDraw header to an EA header, but I think this was not really necessary.


@peter: can you send me the profile ?

Herbert

7

Automation Interface, Add-Ins and Tools / Re: OWL, VOM and UML Profile

« on: January 14, 2010, 06:11:04 pm »

so far we just have used UML Tools to model software and OWL / RDF Tools (like Protégé, Swoop, TopBraid Composer, ...) to model data structure and knowledge.

The reason for using an UML Tool to model OWL is the hope to get a platform which allows for different representations of our models:
UML --> serialization to OWL / RDF
UML --> serialization to .XSD /.XML
UML --> TM

we also had a look on the Eclipse plugins for that purpose:

http://www.eclipse.org/m2m/atl/usecases/ODMImplementation/
and
http://www.topquadrant.com/products/TB_Composer.html together with the UML2 plugin http://www.eclipse.org/modeling/mdt/?project=uml2

but I also experienced a lot of things which do not work as awaited in that world.

The conclusion: I am not so sure whether our intention is just theoretically nice or not.

Herbert

8

Automation Interface, Add-Ins and Tools / Re: OWL, VOM and UML Profile

« on: January 14, 2010, 02:03:11 am »

The OWL / RDF profiles would be of high importance to my work too.

I tried to import the OMG profiles - http://www.omg.org/spec/ODM/1.0/ .

This did not work without modifications.
When I did the modifications I could load the stereotypes but they were no longer part of profiles.
Therefore I created a dummy profile and moved the stereotypes to it.
The result was not encouraging.

Next step I purchased MagicDraw which could not load the original OMG files either. But the MagicDraw support team could send the original projects. The result: The contents of the import in EA is correct, with the awaited difference that it is not correctly assigned to existing stereotypes like "class".

Will Sparx work on that issue or will someone have to do the giant work to create the profile by comparison with what can be seen in MagicDraw?

Herbert