OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsrp] [CR311] - Reference Event Driven Application methodology?



I have been forgetting to bring this change request up for an approval vote. The consensus on the February 24, 2005 TC call was to approve, but we did not have a quorum. This is a reminder that it will be on the agenda for the next call.

Rich



Rich Thompson/Watson/IBM@IBMUS

02/02/05 11:19 AM

To
<wsrp@lists.oasis-open.org>
cc
Subject
[wsrp] [CR311] - Reference Event Driven Application methodology?






Document:
Spec 2.0

Section:
3.9 Consumer Mediated Coordination

Page/Line:
15/30-33

Requested by:
Yossi Tamari

Old text:

Consumers may implement mechanisms through which portlets react in a coordinated manner. This specification defines two such mechanisms:
1.         Event Distribution: This mechanism provides for portlets generating and consuming events that carry both semantic meaning through their name and data in their payload…

 
New text:

Consumers may implement mechanisms through which portlets react in a coordinated manner. This specification defines two such mechanisms:
1.         Event Distribution: This mechanism enables development of event driven portal applications. It provides for portlets generating and consuming events that carry both semantic meaning through their name and data in their payload…

 
Reasoning:
The change uses the “event driven application” (EDA) tag, which is becoming a well known methodology, to make the intent of the mechanism immediately clear to the reader. The rest of the sentence discusses the technical details of how it is enabled, but not the goal.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]