Re: [soa-rm-ra] RE: List of terms in section 3

DEFINITION	Term	Line in Model	Line where's defined	Definition	Comment
DEFINITION	Capability	1080	1107	A capability is an ability to achieve a real world effect.	Not only, capability is also to sutisfy the consumer needs that may be NOT in the RWE but in returned service result (in private state). The problem here is in the definition of RWE.
DEFINITION	Mediator	835	844	A mediator is a role assumed by a participant to facilitate interaction and connectivity in the offering and use of services.	Based on the Note 1 and definition of Participant, Service Registry/Repository or ESB are not mediators. It is OK with me.
DEFINITION	Permission	925	950	A permission is a constraint that prescribes actions that an actor may (or may not) perform and/or the states the actor may (or may not) be in.	The wording is strange IMO: permission does not prescribe, it permits/alowes
DEFINITION	Real World Effect		1181	A real world effect is a measurable change to the shared state of pertinent entities, relevant to and experienced by specific stakeholders of an ecosystem.	Still disagree with this. A consumer and its state are the part of the state of the SOA ecosystem regardeless who can/may access it. If private state of the consumer chnages, it is the change in the overal ecosystem state. If we do not go with this interpretetation, we will end-up with this: a cosumer of the service is interested, first of all, in the returned service result and only then may or may be not interested in the RWE. Examples: 1) I order a book because I am interested in having this book and do not care that somebody has a job to deliver this book to me; 2) I order a cleaning of the street in front of my house becuase I am interested in the clean road in front of my gates and in convenience of my neighbours who pass through this spot , i.e. I am interested in the returned results AND in the RWE avalibale/accessible to other potential consumenrs.
DEFINITION	Sharable State			That part of an entity’s state that is knowable to other actors	Proposal: That part of an entity’s state that MAY BE knowable to and may be accessible to, other actors, while the entity is not necessary aware of this knowlegde and access
DEFINITION	Shared State		907	Shared state is that part of an entity‘s state that is knowable by, and may be accessible to, other actors	Proposal: Shared state is that part of an entity‘s state that is knowable by, and may be accessible to, other actors, which is expected by the entity.
USE INFORMALLY	Service	835			IMO, we have to find a form of expression where we can refer to the RM definition and to append 'realisation of business functionality accessible though defined interfaces' simultanously making this a sort of refined definition.

-----Original Message-----
From: Bashioum, Christopher D <cbashioum@mitre.org>
To: soa-rm-ra@lists.oasis-open.org <soa-rm-ra@lists.oasis-open.org>
Cc: Laskey, Ken <klaskey@mitre.org>
Sent: Wed, Feb 23, 2011 3:08 am
Subject: [soa-rm-ra] RE: List of terms in section 3

Ken,

request that we add an agenda item for tomorrow’s TC: the finalization of the list of terms for definition in Section 3. Since sending out the email below, I have not received any input from the TC on amending the list of what will be formally defined, what will be dropped, and what will be used informally. Would like to formally vote on this tomorrow so we can close it out.

This is important, as Peter and I would like to start the actual writing. We have done some editing, but need to get a solid draft of Section 3 written up and delivered to the TC. This is a necessary step for that to occur.

I will try to make the TC call tomorrow, but may miss it or be late due to work constraints. Peter is planning on making the first part of the TC call, but will have to leave early for a client call, so we would like to have this as an early agenda item if possible.

Thanks!

From: Bashioum, Christopher D
Sent: Monday, February 07, 2011 10:32 AM
To: soa-rm-ra@lists.oasis-open.org
Subject: List of terms in section 3
Importance: High

At our last conf call, we proposed a list of terms that Section 3 will define. Attached is a spreadsheet that contains that list.

The spreadsheet identifies terms that will be formally defined (identified with “DEFINITION” in the first column), terms that will not be used (DELETE) and terms that will *not* be formally defined but will be used and will rely on the reader’s understanding of the english language (USE INFORMALLY). I have sorted the spreadsheet accordingly.

For the terms that will be formally defined, an initial definition is given in the Definition column. For those terms that will be either deleted or used informally, some amplifying text is in the Notes 1 and Notes 2 columns.

So ... first item is to come to agreement on what will be formally defined in section 3. If you think that we missed some terms, or that we have included terms that should not be formally defined, please reply as such. Would like to come to consensus on this by next conference call. Definitions we will debate and refine after coming to agreement on the list of terms.

Michael P, your input has been incorporated in this list – except that i have interpreted your “delete” as “Don’t formally define, just use as normal english language in the text”.

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

soa-rm-ra message