Legacy Issue Number: 14697
Source: NIST ( Conrad Bock)
Since the term "service" isn't used anymore in the interface and
operation model, it would be better if ServiceTask were renamed, perhaps
From: firstname.lastname@example.org created: Thu, 28 May 2009 17:57:44 -0500 (CDT)
Actually I was just about to open an issue, suggesting we rename "Interface" to "Service Interface", given that "Interface" is generally an overloaded term.
From: conrad.bock created: Fri, 29 May 2009 08:15:35 -0500 (CDT)
True, although I think it's less overloaded than "service", which has a
very different business meaning than in software. I thought "operation"
was more neutral, and it's what is actually invoked by a Service Task
(see the operationRef attribute on ServiceTask).
Reported: BPMN 2.0b1 — Thu, 19 Nov 2009 05:00 GMT
Disposition: Resolved — BPMN 2.0
Business modelers will usually take the term "service" in the business
sense, rather than in the operation invocation sense of WSDL or UML,
which is the current meaning of ServiceTask. However, implementations
are too far along to change the name at this point.
Disposition: Closed, No Change
Updated: Fri, 6 Mar 2015 20:57 GMT