For what it is worth, I do not think this issue needs to be resolved
before PR.
-Eric.
Eric Johnson wrote:
4A3BCDC4.4050607@tibco.com" type="cite">
Logged as: http://www.osoa.org/jira/browse/BINDINGS-82
-Eric.
Eric Johnson wrote:
4A3BC3AF.405@tibco.com" type="cite">Target:
sca-binding-ws-spec-cd02-rev3.pdf
Description:
Line 265 - 266 (Section 2.5) of the spec has the
text:
"SCA runtime implementations MAY provide additional
metadata that is associated with a web service binding."
Unfortunately,
it is difficult to figure
out what it was actually referring to. The consensus on the mailing
list took this to mean that an SCA binding.ws element
might contain additional metadata to help configure non-SCA aspects of
a web-services binding. However, that's not a necessary normative
constraint
on the runtime or the document, as the document already has normative
constraints about the schema.
Proposal:
Change the wording to: "SCA runtime
implementations can provide additional
metadata that is associated with a web service binding."
-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
---------------------------------------------------------------------
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
|