ISSUE 68: Authorization Policy language should be optional

[David Booz <booz@us.ibm.com>]

http://www.osoa.org/jira/browse/POLICY-68

Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com

David Booz---02/04/2009 12:03:23 PM---TARGET: Policy spec (section numbers are from cd01-rev13e) DESCRIPTION: Section 7.3 describes a mini

From:	David Booz/Poughkeepsie/IBM@IBMUS
To:	sca-policy@lists.oasis-open.org
Date:	02/04/2009 12:03 PM
Subject:	[sca-policy] NEW ISSUE: Authorization Policy language should be optional

---

TARGET: Policy spec (section numbers are from cd01-rev13e)

DESCRIPTION: Section 7.3 describes a mini authorization language that could be used within a policySet. It is a light weight language, but requiring compliance to it might not be overly useful.

PROPOSAL: At the end of section 7.3 add the following statement:

An SCA runtime is NOT REQUIRED to implement the implementation security policy described in this section and sub-sections.

As an alternative we could discuss removing the section entirely.



Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com