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'.

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

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

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

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.

resolved