UPR 1.0 FTF Avatar
  1. OMG Issue

UPR — The way the ComparisonOperator sterotype is used will not work

  • Key: UPR-5
  • Status: closed  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    In Figure 8-1, there is an association directly between the stereotypes ComparisonOperator and OperatorSemantics. The intent seems to be for a stereotyped literal string to provide the name of the comparison operator associated with an operator semantics class. However, while such an association between stereotypes is technically legal syntactically (because stereotypes are kinds of classes), there is no standard way to instantiate it, because the standard does not require a tool to implement stereotyping using actual stereotype instances.

    An alternative would be to associate the OperatorSemantics stereotype directly to LiteralString, requiring that the LiteralString be stereotyped by ComparisonOperator. However, this seems unnecessarily heavyweight. Instead, it would be much simpler to simply give OperatorSemantics a symbol: String property and move the applyTo operation to OperatorSemantics. The ComparisonOperator stereotype would then be entirely unnecessary.

  • Reported: UPR 1.0b1 — Sat, 9 Feb 2019 00:20 GMT
  • Disposition: Duplicate or Merged — UPR 1.0
  • Disposition Summary:

    Merge with UPR-4

    The solution investigated for resolving UPR-4 removed the stereotypes this issue is about

  • Updated: Tue, 8 Oct 2019 17:59 GMT