On Apr 25, 2005, at 10:03 AM, Mark Little wrote:
> I came a little late to this group, so haven't fully caught up yet, so
> apologies if what I'm about to describe is out of place. Firstly I
> think context and it's use (which is wider than one-way message
> correlation) is a requirement throughout the architecture:
> transactions, security, correlation, workflow, reliable messaging etc.
> all have a notion of context. I'm always in favour of referencing
> standards/specifications that are available elsewhere, rather than
> reinventing the wheel.
Be careful about normative references to drafts. These will invariably
cause more confusion than they solve.
> In that case, I'd define the requirement in the model ("we need
> context; this is what context is, ..." and then say it comes from
> WS-Context). I would assume that we would do the same with other
> things, e.g., WS-Security?
>
> Mark.
>
>
------------------------------------------------------------------------
------------------
Ken Laskey
MITRE Corporation, M/S H305 phone: 703-983-7934
7515 Colshire Drive fax: 703-983-1379
McLean VA 22102-7508
