Profile only partially imported

[GeertThijs]

There is a package from OMG with a OWL Profile, see https://www.omg.org/spec/ODM/About-ODM/. Importing the package https://www.omg.org/spec/ODM/20131101/OWLProfile.xmi and then saving it as a profile OWLProfile.xml works fine. I can then import the file as a profile, but sadly a lot of elements (eg owlClass) are missing from it. Can someone explain? Is there a limit on the number of elements per profile? Or is there another problem with the profile? Thank you for your help.

[qwerty]

Are you using V14? For me it failed with a (former) V14 for some other OMG meta modesl but V12 imported them without issues.

q.

[Eve]

I believe what you're seeing is that owlClass doesn't have an extension connector and base_Class property. It has generalizations to other types, which indirectly lead to other profiles (specifically to http://www.omg.org/spec/ODM/20131101/RDFProfile.xmi#_16_5_2_630020f_1250725403251_896961_1023). As a consequence the inheritance chain will probably be broken during import.

Are you aware that EA comes with a built-in ODM profile? Is there a reason you're trying to define it yourself?

[GeertThijs]

Thanks for your answer. That will indeed be the problem, a missing exension connector to the metaclass Class. Maybe merging the OWLprofile and the RDFprofile will provide a solution, for some reason the RDFS and OWL elements are provided by OMG in seperate packages which are not standalone. I also figured out that abstract classes do not show up in the profile, but that's logical: an abstract metamodel class should not be instantiated.
Concerning the OMD in EA: it only implements a very small subset of the OMG's Ontology Definition Metamodel, so I cannot use it to model in RDFS/OWL effectively. 

[GeertThijs]

Which brings me to another problem now: tell me if you want a seperate post for it. The topic is: if a stereotype in a profile package has an abstract superclass, this abstract superclass logically does not show in the profile. Only problem: when loading the profile EA goes searching for the missing superclass and if it finds a match somewhere else in a built-in profile your stereotype gets the appearance of that stereotype. Example: I have a stereotype owlClass which in turn has an abstract stereotype Entity as its superclass. When saving the package as a profile the abstract stereotypes are excluded but with owlClass the superclass Entity is mentioned as basestereotype in the xml. After loading the profile and using the stereotype owlClass it has 2 stereotypes: owlClass but also Entity (from some built-in profile) and it takes on the appearance of the latter (which in this case is appearently a Business Class icon = a circle on a line) in stead of the class icon of owlClass. What to do about this?

[Geert Bellekens]

Geert,

The abstract stereotypes should also be exported into the UML profile xml file.
I just checked on one of my UML profiles.

Not sure why it isn't being exported in yours.

Geert

[Eve]

I suspect the issue is still with cross package relationships.

In the owl profile, take every stereotype extending something from rdf, and create a new abstract stereotype in the owlProfile package with the name RDFProfile::<name>. Then move the generalizations to those.