POLICY-63

intents names defined by SCA should be defined using camel case

POLICY-61

How are mayProvide intents on bindings satisfied

POLICY-60

Clarify scope of ordered intent

POLICY-59

Limit policySet attachment to bindings

POLICY-58

Remove <operation/> elements from the specification

POLICY-56

Intents which conflict with binding configuration

POLICY-55

Clarify the handling of Intents

POLICY-54

Wire validation rules have changed

POLICY-53

How do we tell what a policySet @provides?

POLICY-52

Policy algorithm gets required intents from what interfaces definitions/declarations?

POLICY-46

How to configure policySets

POLICY-44

Need a clear way to distinguish Implementation Intents from Interaction Intents

POLICY-42

Infoset for policySet/@appliesTo

POLICY-40

Fix SCA Policy schema complex types for Qualifier and PolicySet

POLICY-39

Need Support for Mutually exclusive intents

POLICY-38

Improve description of the overides available to the two different hierarchies in SCA

POLICY-37

The URL for the location of the ws-policy.xsd is incorrect.

POLICY-29

Need more precision on when policies in a policySet are in effect

POLICY-26

Security implementation policy should be validate-able by schema schema

POLICY-24

More direct, structural qualifier definition

POLICY-22

Profile intent extension - provides other intents

POLICY-18

Should qualifiable intents have a default qualifier

POLICY-17

Need Transaction Policy Spec

POLICY-15

External mechanism for attaching intents or policySets

POLICY-8

Include definition on 'conversational' intent as mentioned in SCA Assembly

POLICY-7

Implicit addition of intents based on a service or reference's @requires list

BINDINGS-38

Clarify use of URI vs. uri

BINDINGS-36

Does WSDL binding take precedend over policy intents

BINDINGS-35

Allow topics anywhere that queues can be used

BINDINGS-34

Clarify default function selection and data binding behavior

BINDINGS-33

Correlation property names are odd, and the space of options is not extensible.

BINDINGS-26

JMS binding pseudo-schemas inconsistent with assembly

BINDINGS-20

JMS binding URI should follow JMS IRI scheme submitted to IETF

BINDINGS-19

Web Service binding should allow #wsdl.binding with reference targets

BINDINGS-18

Clarify the rules on which queues are used for responses and callbacks

BINDINGS-17

Rules for Binding compatibility

BINDINGS-16

binding.ws reference to assembly spec for interface mapping is incorrect

BINDINGS-15

Namespace/location for WS-Addressing is incorrect in WebService binding spec/XSD

BINDINGS-13

What namespace(s) do we use for each binding?

BINDINGS-12

Are JMS message selectors supported?

BINDINGS-10

Rules for WSDL generation create invalid WSDL by using "/" where it is not allowed.

BINDINGS-9

Use of wsdli:wsdlLocation does not match WSDL 2.0 specification

BINDINGS-8

No bindingType for binding.ws

BINDINGS-6

JMS bindingType and conversation intent

BINDINGS-5

JMS bindingType and atLeastOne intent overlaps with setting JMSDeliveryMode setting JMSDeliveryMode

BINDINGS-3

portType referred to inconsistently throughout specification

BINDINGS-1

JMSDeliveryMode, JMSTimeToLive and JMSPriority defined as types different from what the JMS specification uses.