Issues marked as applied

[Eric Johnson <eric@tibco.com>]

Relative to last week, the issues 38, 36, 19, 15, 13 have now also been marked as applied.

Bindings-13 is marked as incomplete.  Can editors enlighten us as to the state - is this because it is not fully applied to the JCA specification?  Do I need to split this issue?

As of today, ~4PM PST, here are the issues listed as applied in Jira:

Key	Summary	Status	Res	Updated
BINDINGS-38	Clarify use of URI vs. uri	Applied	UNRESOLVED	14/Aug/08
BINDINGS-36	Does WSDL binding take precedend over policy intents	Applied	UNRESOLVED	14/Aug/08
BINDINGS-35	Allow topics anywhere that queues can be used	Applied	UNRESOLVED	01/Aug/08
BINDINGS-34	Clarify default function selection and data binding behavior	Applied	UNRESOLVED	01/Aug/08
BINDINGS-33	Correlation property names are odd, and the space of options is not extensible.	Applied	UNRESOLVED	01/Aug/08
BINDINGS-26	JMS binding pseudo-schemas inconsistent with assembly	Applied	UNRESOLVED	28/Apr/08
BINDINGS-20	JMS binding URI should follow JMS IRI scheme submitted to IETF	Applied	UNRESOLVED	01/Aug/08
BINDINGS-19	Web Service binding should allow #wsdl.binding with reference targets	Applied	UNRESOLVED	14/Aug/08
BINDINGS-18	Clarify the rules on which queues are used for responses and callbacks	Applied	UNRESOLVED	28/Apr/08
BINDINGS-17	Rules for Binding compatibility	Applied	UNRESOLVED	02/Apr/08
BINDINGS-16	binding.ws reference to assembly spec for interface mapping is incorrect	Applied	UNRESOLVED	02/Apr/08
BINDINGS-15	Namespace/location for WS-Addressing is incorrect in WebService binding spec/XSD	Applied	UNRESOLVED	14/Aug/08
BINDINGS-13	What namespace(s) do we use for each binding?	Applied	Incomplete	14/Aug/08
BINDINGS-12	Are JMS message selectors supported?	Applied	UNRESOLVED	28/Apr/08
BINDINGS-10	Rules for WSDL generation create invalid WSDL by using "/" where it is not allowed.	Applied	UNRESOLVED	02/Apr/08
BINDINGS-9	Use of wsdli:wsdlLocation does not match WSDL 2.0 specification	Applied	UNRESOLVED	02/Apr/08
BINDINGS-8	No bindingType for binding.ws	Applied	UNRESOLVED	02/Apr/08
BINDINGS-6	JMS bindingType and conversation intent	Applied	UNRESOLVED	28/Apr/08
BINDINGS-5	JMS bindingType and atLeastOne intent overlaps with setting JMSDeliveryMode	Applied	UNRESOLVED	28/Apr/08
BINDINGS-3	portType referred to inconsistently throughout specification	Applied	UNRESOLVED	02/Apr/08
BINDINGS-1	JMSDeliveryMode, JMSTimeToLive and JMSPriority defined as types different from what the JMS specification uses.	Applied	UNRESOLVED	28/Apr/08