Author: gnaylor
Date: Tue Jul 12 22:02:27 2016
New Revision: 1752355
URL: http://svn.apache.org/viewvc?rev=1752355&view=rev
Log:
Minor edits
Modified:
incubator/taverna/site/trunk/content/documentation/web-service-developers/index.md
Modified:
incubator/taverna/site/trunk/content/documentation/web-service-developers/index.md
URL:
http://svn.apache.org/viewvc/incubator/taverna/site/trunk/content/documentation/web-service-developers/index.md?rev=1752355&r1=1752354&r2=1752355&view=diff
==============================================================================
---
incubator/taverna/site/trunk/content/documentation/web-service-developers/index.md
(original)
+++
incubator/taverna/site/trunk/content/documentation/web-service-developers/index.md
Tue Jul 12 22:02:27 2016
@@ -27,9 +27,9 @@ However, it should be possible to create
particularly the SOAP messaging protocol.
A WSDL SOAP binding can be either a **Remote Procedure Call (RPC)** style
binding or a **document** style binding.
A SOAP binding can also have an **encoded** use or a **literal** use.
Combining these
-options would yield 4 binding styles, except that the document/encoded
combination
+options would yield 4 binding styles, except the document/encoded combination
is not WS-I compliant and is [not
used](https://www.ibm.com/developerworks/library/ws-whichwsdl/).
-However, there is an additional binding style that is commonly referred to as
the
+However, there is an additional binding style commonly referred to as the
document/literal wrapped style.
Thus, developers have 4 binding styles to choose from when creating a WSDL
file.
