Author Topic: Unclear meaning of "Ignoring Metaconstraints" startup message for MDG  (Read 4938 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8607
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
When I started up one of the repositories we have this morning, I got the message:

"Ignoring metaconstraints for Stereotype from profile: <our profile>"

Is "Stereotype" the affected element[1]?  Or is the affected stereotype not shown?

TIA,
Paolo


Our profile does have a metaclass called "Stereotype" as shown below.
Code: [Select]
<Metaclass name="Stereotype" notes="">
   <metarelationships>
      <metarelationship metaclass="UML::Extension" constraint="StandardProfileL2::Metaclass"/>
   </metarelationships>
   <stereotypedrelationships>
      <stereotypedrelationship stereotype="PrIME::SeeAlso" constraint="Stereotype"/>
   </stereotypedrelationships>
</Metaclass>
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8085
  • Karma: +118/-20
    • View Profile
Re: Unclear meaning of "Ignoring Metaconstraints" startup message for MDG
« Reply #1 on: January 11, 2022, 01:10:16 pm »
You can't change the UML relationships for the UML types.

Neither the restriction or the warning are new.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8607
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Unclear meaning of "Ignoring Metaconstraints" startup message for MDG
« Reply #2 on: January 11, 2022, 04:43:31 pm »
You can't change the UML relationships for the UML types.

Neither the restriction nor the warning are new.
I knew that neither the restriction nor the warning were new, what was new was I had the system Window open on startup (it's normally not visible) so I saw the message.  (Side note, from a UX point of view, perhaps the System window should be forced open if not visible when such errors are detected) 

It now explains why what I was trying to achieve didn't work!

As you might see from the code snippet, I was trying to fix the lack of the Quicklinker having an Extension relationship between a Stereotype and a Metaclass (which seems to have been fixed in v16β - can anyone confirm?) and also to allow a "See Also" relationship between Stereotypes.  How can I achieve this (in v15.x)?

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8085
  • Karma: +118/-20
    • View Profile
Re: Unclear meaning of "Ignoring Metaconstraints" startup message for MDG
« Reply #3 on: January 12, 2022, 09:04:38 am »
I would expect the see also link to work from that. (I said you can't change the UML relationships)