[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue PR021: Allow W3C version of WS-Policy to be used
Issue PR021 From: Marc Goodner PLEASE
DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL THE ISSUE IS
ASSIGNED A NUMBER. The
issues coordinators will notify the list when that has occurred. Protocol:
ws-securitypolicy Artifact:
spec / schema Type:
design Title:
Allow
W3C version of WS-Policy to be used Description: WS-Policy
has progressed quickly at the W3C. WS-SecurityPolicy should be updated to allow
the use of WS-Policy 1.5 in addition to the current reference to WS-Policy 1.2.
Related
issues: None. Proposed
Resolution: 1. Add following text to
WS-SecurityPolicy introduction: “The assertions defined
within this specification have been designed to work independently of a
specific version of WS-Policy. At the time of the publication of this specification
the versions of WS-Policy known to correctly compose with this specification
are WS-Policy 1.2 [current reference] and 1.5 [add reference to CR when
available]. Within this specification the use of the namespace prefix wsp
refers generically to the WS-Policy namespace, not a specific version.” Strike wsp from the namespace
table. 2. Remove the hard dependency
from the WS-SecurityPolicy XML Schema document to a specific version of
WS-Policy: <xs:complexType
name="NestedPolicyType"> <xs:sequence>
<xs:element ref="wsp:Policy" /> <!-- remove this line -->
<xs:any minOccurs="0" maxOccurs="unbounded"
namespace="##other" processContents="lax"/> </xs:sequence> <xs:anyAttribute
namespace="##any" processContents="lax" /> </xs:complexType> The extensibility point that
follows will allow the use of the nested policy. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]