Currently, Web services (WS-I Basic Profile 1.1) are synchronous.
目前，Web服务(WS - i基本概要1.1)是同步的。
Quite the contrary, work on this profile can lay the groundwork for possible future WS-I profiles.
正相反，针对这个概要开展的工作可以为将来的WS - i概要打下基础。
So, from a WS-I compliance perspective, there should be no case of operation overloading.
因此，从WS-I遵从性角度来看，不应该存在操作重载的情况。
WS-I Test Tools provide an easy way to determine if your services conform to these guidelines.
WS - i测试工具提供了一个简单的方法来确定您的服务是否符合这些指南。
Even if everyone is coding to the same WS-I specifications, there will be mismatches, misinterpretations, and different conventions.
即使每个人都依据相同的WS - I规范开发，仍然会有不匹配、曲解及不同的习惯。
Security is one of the areas WS-I has covered in profiles.
在配置文件中安全性是WS - i所涉及的领域之一。
Part 6 will also cover the requirements and tests involved in WS-I certification.
第6部分还将讨论在WS - i证书中涉及的要求和测试。
In fact, the WS-I has gone so far as to specifically exclude the use of SOAP encoding from their basic interoperability profile.
事实上，WS - I已经到达了这一步，它们明确地将使用SOAP编码排除在它们的基本互操作性概要之外。
To make it WS-I compliant, remove the tag and replace it with tag as shown in listing 17.
要使它满足WS - i依从性，可删除标记并将其替换为标记，如清单17所示。
You may see some WS-I compliance warnings, which you can ignore.
您可能会遇到一些WS - i遵从性警告，您可以忽略它们。
It simply means that following the guidelines of WS-I usage scenarios is one way to ensure profile conformance.
它只意味着遵守WS - I使用情形的指导是确保符合概要文件的一种方式。
Schemas, message parts, and data bindings must be carefully designed in accordance with the WS-I recommendations.
脚本、消息部件和数据绑定必须仔细设计来遵循WS-I 一致性要求。
By running the testing tool, much of the obvious violations of the WS-I Basic Profile 1.0 are reported.
通过运行测试工具，WS - I基本规范1.0的大部分明显的冲突都会被报告。
Most significantly, the WS-I basic profile mandates the use of literal encoding of SOAP request and response messages.
最重要的是，WS- i基本概要文件强制使用SOAP请求和响应消息的文字编码。
This is the final request/response portion of the Basic callback scenario described in the WS-I Usage Scenarios document.
这是WS-I使用情形文档中描述的基本回调情形的最后的请求／响应部分。
A WSDL definition is far less likely to cause interoperability problems if it's WS-I compliant.
如果WSDL定义与WS - i兼容，则导致互操作性问题的可能性会很小。
WS-I has limited the scope of their profiles to adopted industry standards.
WS-I 将其概要的范围限定为已采用的行业标准。
It should be clearly noted that this work is not intended to compete with the work of WS-I.
有一点需要明确说明的是，这项工作并非要与WS - I的工作构成竞争。
Currently, there is no mention of using the extension construct in the WS-I basic profile and, additionally, the WS-I compliance test suite does not cover this case.
目前，在WS - i基本概要中没有提及使用扩展结构，又加之WS - I一致性测试包并未包括这种情况。
Our supplied business scenario sample represents a simplified SCM solution that is based on the WS-I SCM sample scenario.
我们提供的业务场景示例表现出基于WS - ISCM示例场景的简化的SCM解决方案。
Up until now you have seen the WS-I Sample Application from an internal perspective.
至此，您已在内部透视图中看到了 WS-I样本应用程序。
Part 6 covers the requirements and tests involved in WS-I certification.
第6部分还将讨论WS - i证书中涉及的要求和测试。
Also WS-I is a good source for testing tools and sample applications.
同时，WS- i还提供了测试工具和示例应用程序。
WS-I has refined the standard to ensure interoperability.
为确保互操作性，WS - i已细化了该标准。
You may see some WS-I compliance warnings.
您可能会遇到一些WS - i遵从性警告。
Again, a "type" is what WS-I BP restricts for an RPC binding style.
同样，“类型”也是WS - IBP对RPC绑定样式的一个限制。
Finally, I added a custom taxonomy for the WS-I conformance taxonomy.
最后，我添加了一个用于符合WS- I的分类法的自定义分类法。
Instead of HTTP as specified in WS-I BP 1.1, message queues now perform the transport.
与WS - IBP 1.1中指定的HTTP不同，消息队列现在执行传输。
Code generation from the WS-I BP schema for WSDL 1.1 was another option.
从WSDL 1.1的WS - IBP模式生成代码则是另一种方法。
It also conforms to WS-I Basic Profile.
它同样遵守WS - I基本概要。
应用推荐