MHonArc v2.5.2 -->

















wsia message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]








Subject: [wsia] 'post conditions'




From: bill parducci <bill@parducci.net>
To: Rich Thompson <richt2@us.ibm.com>
Date: Thu, 28 Mar 2002 15:48:33 -0800






we initially used the term in 'post condition' in XACML, however decided
to change it to 'obligation' for a number of reasons.

first, there may be a temporal aspect to an obligation that makes it
impractical to perform an action after the specified event (e.g. 'expire
information in 30 days')

second, with distributed systems it may be impratical from an
enforcement and performance perspective to ensure that something occurs
after an event on a remote system.

third, the term 'post condition' typically refers to the state of system
after an event rather than an action to be performed (in languages such
as UML).

b



On Thu, 2002-03-28 at 06:20, Rich Thompson wrote:
> Here is the current state of the Embedded Use Case document for review in
> todays telecon.
>  (See attached file: WSIA Embedded Use Case.DOC)
> 
> I have also begun the collection of CSS classes various portals use today
> for use in defining a set that all services at the WSIA Embedded level
> could depend on being defined by a Consumer. This certainly needs input
> from additional portal providers.
> 
> (See attached file: CSS classes.doc)










References:

[wsia] Todays use case telecon
From: Rich Thompson <richt2@us.ibm.com>






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]


  









Powered by eList eXpress LLC