RE: [ws-caf] Informal raising of issue on context-service/-manager

["Green, Alastair J." <Alastair.Green@choreology.com>]

The issue arises because there is a crude form of access control given
by the use of two separate interfaces to access the same beast, for
different purposes. 

I would be open to fusing the two references, and remaining silent on
access control. However, I think there is a general, and very
Context-specific, set of accesses that can be described, and it would be
at least worthwhile highlighting them in the text, even if no specific
support for controlling them is included.

Alastair

-----Original Message-----
From: Jim Webber [mailto:Jim.Webber@newcastle.ac.uk] 
Sent: 15 July 2004 00:33
To: ws-caf
Subject: RE: [ws-caf] Informal raising of issue on
context-service/-manager

Hey Alastair:

Not being present at the F2F, I might be off-key here but isn't access
control an orthogonal issue w.r.t. WS-CAF? There are other specs out
there that can help you deal with access control and particular
deployments of WS-Context will choose how to use those specs for their
particular domain.

So my "counter proposal" would be to declare access control out of
scope.

Jim
--
http://jim.webber.name