search

OntoUML / ontouml-vp-plugin

A plugin for Visual Paradigm to add support for OntoUML modeling and model intelligence services
Apache License 2.0
36 stars 15 forks source link

How to solve "The class X is missing the 'allowed' natures meta-property." #82

Closed brunogcarneiro closed 3 years ago

brunogcarneiro commented 3 years ago

Hello

When trying to check a gUFO model the OntoUML output console displayed some erros:

"The class X is missing the 'allowed' natures meta-property."

What does it means?

claudenirmf commented 3 years ago

Hi @brunogcarneiro, could you please tell us which version of the plugin you have installed on Visual Paradigm? Have you recently updated the plugin you are using?

In order to use the model transformation, your model (or the part of the model you are trying to transform) cannot have any syntactical errors.

This specific error refers to a class missing a meta-property (a.k.a. tagged value in UML) "restrictedTo" that we have introduced in the language in the previous updates. The model you have was probably developed with a previous version of the plugin and that is why the class has the stereotype but lacks the associated meta-property.

The easiest way to fix this issue is to apply again to the class the same stereotype it already has. This will correctly add to the class the meta-property.

In case the class is specialized by something other than an object class/functional-complex, and the class has one of the following stereotypes «category», «mixin», «phaseMixin», «roleMixin», or «historicalRoleMixin», you will need to update the value of "restrictedTo" by right-clicking the class and going to Meta-Properties > Restrict Ontological Nature.

TIP: you can select multiple classes or associations in order to apply the same stereotype or change some meta-property to all of them at once.

Have in mind that we are constantly working to improve our tools and it is important to be up-to-date with our latest release to be sure that everything is working correctly.

brunogcarneiro commented 3 years ago

Hello @claudenirmf !

I am getting this error message: "Incompatible allowed natures. The < < role > > class Criterion has 'allowed' natures incompatible with its stereotype. For this stereotypes, the compatible natures are: collective, functional-complex, intrinsic-mode, extrinsic-mode, quality, quantity, relator".

The class < < role > >Criterion specializes the class < < type > >Intrinsic Moment Type.

The stereotype < < role > > should not accept the nature type too?

claudenirmf commented 3 years ago

At the moment we are not supporting the specialization of «type» classes into «subkind», «phase», or «role» in order to provide full compatibility with gUFO.

You should convert the class Criterion to «role» for the moment.

Also, could you confirm which version of the plugin you are using? If you are in the latest version, you can right-click the class Criterion and go to Suggested Stereotypes where Type should be the only enabled option (due to the specialization of the «type» class Intrinsic Moment Type).

In addition, bear in mind that when exporting your model to gUFO, Intrinsic Moment Type will also be exported. This may be an issue depending on your application. I would avoid adding UFO-A concepts to OntoUML models whenever possible.

brunogcarneiro commented 3 years ago

Thank you for the suggestion!

I am using the plugin version 0.4.0.