SoaML 1.0 FTF Avatar
  1. OMG Issue

SOAML — ServiceInterface Notation

  • Key: SOAML-19
  • Legacy Issue Number: 13545
  • Status: closed  
  • Source: PTC ( Phillip Astle)
  • Summary:

    ServiceInterfaces require a different notation on diagrams that is dependent on what it’s underlying UML metatype is. The issue relates to the fact that a ServiceInterface can extend a Class or an Interface.

    When you drop a ServiceInterface onto a diagram you cannot tell if the ServiceInterface is really a Class or an Interface. This is a problem when you consider that a Class can have provided/required Interface but an Interface cannot. From a users perspective the two will look identical on a diagram and they won’t be able to tell why they’re not allowed to do what they’re trying to do. Some sort of notational difference would resolve this

  • Reported: SoaML 1.0b1 — Mon, 23 Feb 2009 05:00 GMT
  • Disposition: Resolved — SoaML 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT