public-ws-policy-qa@w3.org from September 2006 by subject

[Bug 3543] Definion of the term "processor" is poorly defined

[Bug 3549] Require assertions to be distinguished from parameter elements

[Bug 3557] Add discussion/examples of domain expressions

[Bug 3559] Conformance Sections needed for both specs

[Bug 3562] Clarify the relation of overlapping definitions in the framework

[Bug 3565] Framework and domain specific policy assertions

[Bug 3577] Semantics of successful intersection determined by domain-specific assertion content

[Bug 3586] Remove misleading reference to a Requester policy.

[Bug 3590] Policy framework should document extensibility points using {any} and @{any} in xpath-like expressions, and define these in Notational Conventions section

[Bug 3599] Need a URI structure to refer to WSDL 1.0 definitions, etc.

[Bug 3602] The absence of an assertion should not mean that the behavior is "explicitly prohibited"

[Bug 3605] Typo wsp:tPolicyURIs in Section 3.3 first example

[Bug 3607] Better describe policy language capabilities in the Introduction

[Bug 3613] Clarify conversion of compact to normal form in Framework section 4.3

[Bug 3616] Policy Negotiation

[Bug 3617] Namespace URI versioning Policy is not clear

[Bug 3619] add an inssue on coordination with other working groups

[Bug 3620] Policy Attachment to WS-Addr EndpointReferences

[Bug 3621] Formal semantics

[Bug 3622] Policy assertion equivalence and generality

[Bug 3623] Relation of Attachment to SAWSDL

[Bug 3638] Need to be able to specify ordering between assertions

[Bug 3656] Using UsingAddressing Extension Element as a WS-Policy assertion

[Bug 3662] Use of element wildcard ##any namespace vs ##other namespace

[Bug 3672] Clarify the policy model for Web Services

[Bug 3694] WS-Policy Attachment for WSDL 2.0

[Bug 3703] Element within policy expression must be an assertion

[Bug 3705] Definition of Interaction

[Bug 3706] editors to clarify the use of the term "domain"

[Bug 3707] Add definition of "nested policy"

[Bug 3708] Updated Security Considerations section in framework document: Add mention of use of XML Signature to sign policy

[Bug 3709] Editorial corrections and clarifications from UDDI TC

[Bug 3710] Clarify that policy assertion parameters are opaque to framework processing

[Bug 3711] Add Cross-Product description to 4.3.3 in Framework

[Bug 3712] wsp:PolicyReference can be used in any place where you can use wsp:Policy

[Bug 3719] Levels of indirection for policy references

[Bug 3720] Terms should be defined/targeted in the appropriate sections of the spec

[Bug 3721] New Attribute keyword to identify 'local' policies

[Bug 3722] Levels of indirection for policy references

[Bug 3723] Non-normative recommendation on how effective polices should be calculated when a policy is associated with an arbitrary XML element.

[Bug 3730] External WS-Policy Attachment to WSDL 2.0 components

[Bug 3752] Clarify restrictions of ID type usage

[Bug 3753] Example 1-1 is not a complete security policy

Last message date: Friday, 29 September 2006 21:22:20 UTC