Re: [sca-bindings] Attempt #3 to resolve issues 57, 58, and 59

[Simon Holdsworth <simon_holdsworth@uk.ibm.com>]

Eric,

Looks fine to me, thanks for including
my feedback.

Regards, Simon

Simon Holdsworth
STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair
MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK
Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898
Internet - Simon_Holdsworth@uk.ibm.com

Eric Johnson <eric@tibco.com>

04/02/2009 21:41

To	OASIS Bindings <sca-bindings@lists.oasis-open.org>
cc
Subject	[sca-bindings] Attempt #3 to resolve issues 57, 58, and 59

Based on Simon H's feedback, I've incorporated a few changes.

Discussion points (deltas from last email):

• We seem to agree that "jndiUrl" is the acceptable form of an attribute name, so I've removed discussion around that.
• Simon expressed concern around the notion of saying that values of elements and attributes might follow the policy pattern, instead of the naming of attributes and elements.  That seems fine to me.  It doesn't actually change how anything is capitalized.  I've changed the text below.
• Simon expressed editorial concern that changing "JMSDeliveryMode" to "deliveryMode", for example, needs text to map back to the JMS header, so I've added that text.

The following
is the proposed resolution (#3) for issues 57, 58, 59, where underlines
and strikeouts are used to show deltas from the last proposal.

Each specification (ws, jms, jca) adds a section 1.4 - Naming Conventions.

The text of that section as follows (between the two line breaks):

---

This specification follows some naming conventions for artifacts defined
by the specification.  In addition to the conventions defined by section
1.3 of the Assembly [SCA-Assembly] specification, this specification adds
two additional conventions:

• Where the names of elements and attributes consist partially or wholly of acronyms, those acronyms will be treated as if they are words, and use the CamelCase conventions outlined in the Assembly specification.  For example, an attribute might be named "uri", or "jndiUrl".
• For the values of XML Schema elements orand attributes defined in this specification, the values follow the same convention as the names of intents in the Assembly specificationattributes.  If the value is of type QName, the local part of the QName value follows the same convention as the names of intentsattributes.

---

For resolution of http://www.osoa.org/jira/browse/BINDINGS-58,
also apply the following changes to the binding.jca specification:

(In document sca-binding-jca-1.1-spec-cd01-rev4.pdf)

Rename element "jca.outbound.connection" to "outboundConnection",
all occurrences.
Rename element "jca.inbound.connection" to "inboundConnection",
all occurrences.
Rename element "jca.outbound.interaction" to "outboundInteraction",
all occurrences.
Rename element "jca.inbound.interaction" to inboundInteraction",
all occurrences.
Rename attribute "binding.jca/@jndiURL" to "jndiUrl",
all occurrences.
The value "ifnotexist" (multiple attributes) should everywhere
be changed to "ifNotExist".
The values of the "resAuth" element, "Container" and
"Application" should be renamed to "container" and
"application".

---

For resolution of http://www.osoa.org/jira/browse/BINDINGS-59,
also apply the following changes to the binding.jms specification:

(In document sca-binding-jms-1.1-spec-cd01-rev4.pdf)

Rename attribute "binding.jms/jndiURL" to "jndiUrl"
for all occurrences
The value "ifnotexist" should everywhere be changed to "ifNotExist".
The attributes "JMSType", "JMSDeliveryMode", "JMSTimeToLive",
"JMSPriority", and "JMSSelector" are renamed to "type",
"deliveryMode", "timeToLive", "priority",
and "selector", respectively.
Further, in section 3, line 217 - 218, change "specifies
the value to use for the JMS header property" to "specifies the
value to use for the JMS header property JMSType, JMSDeliveryMode, JMSTimeToLive,
JMSPrioirty, and JMSSelector, respectively."
line 252, change " specifies the value to use for the JMS header property"
to "specifies the value to use for the JMS header property JMSType,
JMSDeliveryMode, JMSTimeToLive, and JMSPriority, respectively"
Change "PERSISTENT" value to "persistent"
Change "NON_PERSISTENT" value to "nonpersistent"
Change "sca:MessageId" value to "sca:messageId"
Change "sca:CorrelationID" value to "sca:correlationId"
Rename jndiURL attribute to "jndiUrl"
Rename the element "wireformat.jmsdefault" to "wireFormat.jmsDefault"


The "jms" intent referenced in section 5 of this specification
needs to be capitalized as "JMS" to correspond to the Policy
specification.

---

For resolution of http://www.osoa.org/jira/browse/BINDINGS-57,
also apply the following changes to the binding.ws specification:

Rename the intents (section #4) from "soap", "soap.1_1"
and "soap.1_2" to "SOAP", "SOAP.1_1", and
"SOAP.1_2", respectively.

---

Hopefully, this wraps it up.

-Eric.

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates
this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

---

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU