SoaML 1.0 FTF Avatar
  1. OMG Issue

SOAML — Clarify relationship of Port::isService with ServicePoint and RequestPoint

Open Closed All
  • Key: SOAML-26
  • Legacy Issue Number: 13935
  • Status: closed  
  • Source: International Business Machines ( Mr. Jim Amsden)
  • Summary:

    How does the Port “isService” attribute that’s in the UML 2.2 specification relate to SoaML ServicePoint and RequestPoint? This seems like something that might conflict/help the SoaML specification.

    Port::isService is a convention supported by UML that recognizes upward, client-facing services a component might have as distinguished from downward services or requests that are used for implementation purposes and are not intended to be of interest to perspective clients. It is used to distinguish ports that the consumers are expected to be interested in from those that are public, but are mostly concerned with the implementation of the component through interaction with lower-level service providers. This is still useful and valid for SoaML - although it would be a bit strange for a RequestPoint to have isService=ture - but this is simply saying that the RequestPoint is involved in the client-facing value chain, and not something that is just about the implementation of the participant. This needs to be clarified in the SoaML submission.

  • Reported: SoaML 1.0b1 — Mon, 18 May 2009 04:00 GMT
  • Disposition: Resolved — SoaML 1.0
  • Disposition Summary:

    In section 7.1.16 Port, add the following paragraph to the end of the Semantics section:
    Port::isService is a convention supported by UML that recognizes upward, client-facing services a component might have as distinguished from downward services or requests that are used for implementation purposes and are not intended to be of interest to perspective clients. It is used to distinguish ports that the consumers are expected to be interested in from those that are public, but are mostly concerned with the implementation of the component through interaction with lower-level service providers. All these ports are either service or request points, but isService is intended to distinguish those that would be involved in a client-facing value chain, and not something that is about the implementation of the participant or something provided for the detailed implementation of some other participant.
    Resolution: Resolved
  • Updated: Fri, 6 Mar 2015 20:58 GMT