ISSUE-20: Statement 3004 lacks context, RFC 2119 keywords

Statement 3004 lacks context, RFC 2119 keywords

Statement 3004 lacks context, RFC 2119 keywords

State:

CLOSED

Product:

SOAP-JMS Binding specification

Raised by:

Eric Johnson

Opened on:

2009-10-26

Description:

From email:
http://lists.w3.org/Archives/Public/public-soap-jms/2009Oct/0027.html

Description:

The supposedly normative statement 3004 currently reads:
"SOAP/JMS properties which are declarable in WSDL 1.1 and WSDL 2.0
documents†"

This doesn't stand on its own, and it doesn't have RFC 2119 keywords.
Further soapAction is not really a SOAP/JMS property.

The point of the statement seems to be (based on WG discussions
http://www.w3.org/2009/10/20-soap-jms-minutes.html) that this
specification only defines what these elements mean in these specific
WSDL locations, and no others. What we want, then, is a normative
statement that says that a conforming implementation MUST use these
properties when found in those specific contexts, while saying nothing
about what they might mean in other contexts.

Proposal:

Replace the text of Section 3.6 with:

The XML elements jndiConnectionFactoryName, jndiInitialContextFactory,
jndiURL, deliveryMode, priority, timeToLive, and replyToName, in the
soapjms namespace, MUST be supported when used in the context of the
WSDL service, port/endpoint, and binding elements. This specification
does not define any use outside of those elements.

Section 3.6.1:
Replace: "For this specification, each property in the table above adds
a WSDL Component Model Property with the same name to the containing
WSDL 2.0 component."

with:
"For this specification, each property in the list
jndiConnectionFactoryName, jndiInitialContextFactory, jndiURL,
deliveryMode, priority, timeToLive, and replyToName, adds a WSDL
Component Model Property with the same name to the containing WSDL 2.0
component.

Related Actions Items:

No related actions

Related emails:

1. Agenda for the 2010-01-12 conference call (from eric@tibco.com on 2010-01-11)
2. Re: Agenda for the 2009-12-15 conference call (from eric@tibco.com on 2009-12-15)
3. RE: Agenda for the 2009-12-15 conference call (from Derek.Rokicki@softwareag.com on 2009-12-15)
4. Re: Agenda for the 2009-11-03 conference call (from phil_adams@us.ibm.com on 2009-12-14)
5. Agenda for the 2009-12-15 conference call (from eric@tibco.com on 2009-12-14)
6. Re: Agenda for the 2009-11-03 conference call (from eric@tibco.com on 2009-12-14)
7. Agenda for the 2009-11-03 conference call (from eric@tibco.com on 2009-12-14)
8. Re: Agenda for 2009-12-08 conference call (from alewis@tibco.com on 2009-12-08)
9. Re: Agenda for 2009-12-08 conference call (from M8PHILLI@uk.ibm.com on 2009-12-08)
10. issue-20: update available (from phil_adams@us.ibm.com on 2009-12-07)
11. Agenda for 2009-12-08 conference call (from phil_adams@us.ibm.com on 2009-12-07)
12. Agenda for the 2009-12-01 conference call (from peaston@progress.com on 2009-11-30)
13. Agenda for the 2009-11-17 conference call (from M8PHILLI@uk.ibm.com on 2009-11-16)
14. Re: Agenda for the 2009-11-03 conference call (from eric@tibco.com on 2009-11-03)
15. RE: Agenda for the 2009-11-03 conference call (from Derek.Rokicki@softwareag.com on 2009-11-03)
16. Agenda for the 2009-11-03 conference call (from eric@tibco.com on 2009-11-02)
17. RE: Agenda for 2009-10-27 conference call (from peaston@progress.com on 2009-10-27)
18. Action-119 - Raised two new issues, action complete. (from eric@tibco.com on 2009-10-26)
19. Agenda for 2009-10-27 conference call (from eric@tibco.com on 2009-10-26)
20. ISSUE-20 (Statement 3004 lacks context, RFC 2119 keywords): Statement 3004 lacks context, RFC 2119 keywords [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2009-10-26)

Related notes:

Display change log