Service Oriented Architecture Modeling Language Avatar
  1. OMG Specification

Service Oriented Architecture Modeling Language — Closed Issues

  • Acronym: SoaML
  • Issues Count: 3
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Descriptions

loading the profile into Eclipse (v3.4, with EMF 2.4.0 and UML2 2.2.0) - error

  • Key: SOAML-35
  • Legacy Issue Number: 13305
  • Status: closed  
  • Source: Peraton ( Brad Kizzort)
  • Summary:

    I have tried loading the profile into Eclipse (v3.4, with EMF 2.4.0 and UML2 2.2.0), but it fails when I try to define the profile with ad/08-11-03.xmi Eclipse errors when invoking UML Editor|Profile|Define... Derived feature needs:RequestPoint should be made transient and volatile. Derived feature capabilities:ServicePoint should be made transient and volatile. Processed feature base_Collaboration:Collaboration as a duplicate of inherited feature 'base_Collaboration:Collaboration'.

  • Reported: SoaML 1.0 — Mon, 19 Jan 2009 05:00 GMT
  • Disposition: Resolved — SoaML 1.0.1
  • Disposition Summary:

    This issue was resolved by other changes. Actions taken: Closed, no change

  • Updated: Sat, 7 Mar 2015 21:10 GMT

The definition of "service" should be refined

  • Key: SOAML-34
  • Legacy Issue Number: 13925
  • Status: closed  
  • Source: Agile Enterprise Design ( Mr. Fred A. Cummins)
  • Summary:

    The definition of "service" should be refined. In several places a service is defined as an offer of value. Instead it should be defined as value delivered. The value is delivered to satisfy a need of one party by another party that has the necessary capability

  • Reported: SoaML 1.0 — Thu, 7 May 2009 04:00 GMT
  • Disposition: Resolved — SoaML 1.0.1
  • Disposition Summary:

    In Section 7.1.7, first paragraph, change
    "To do so, services provide functional capabilities that when implemented and used to provide some real-world effect that has value to potential producers and consumers."
    To
    "To do so, service providers have functional capabilities that, when implemented and used, provide some real-world effect that has value to potential consumers."
    Section 7.3.14, in row 4 of the table under semantics, replace
    "The detailed specification of an interaction providing value as part of a service including "
    With
    "The detailed specification of an interaction providing value as a service including "
    Annex B, row 10, Real World Effect, right column, replace
    "Defined as Effect. Comprises the out-come of the service, and is how it delivers value to its consumers. "
    With
    "Defined as Effect. Comprises the out-come of performance of the service, and is the value delivered."

    Resolution: Resolved

  • Updated: Sat, 7 Mar 2015 21:06 GMT

specification is inconsistent in capitalization regarding defining stereotypes and utilizing the stereotypes in examples

  • Key: SOAML-33
  • Legacy Issue Number: 13189
  • Status: closed  
  • Source: Northrop Grumman ( Mr. Darin J. Supel)
  • Summary:

    The specification is inconsistent in capitalization regarding defining stereotypes and utilizing the stereotypes in examples. Most stereotypes begin with a capitalized letter, however many do not. The group should follow the style guidelines defined by the UML: "The first letter of an applied stereotype should not be capitalized." - UML 2.1.2 Superstructure, Section 18.3.8.

  • Reported: SoaML 1.0 — Mon, 22 Dec 2008 05:00 GMT
  • Disposition: Resolved — SoaML 1.0.1
  • Disposition Summary:

    resolved

  • Updated: Sat, 7 Mar 2015 21:06 GMT