WSTF is actually not limited to just SOAP-based Web service testing.
WSTF实际上并不只限于基于SOAP的Web服务测试。
As mentioned above, scenarios are the only things visible to non-WSTF members.
如上所述，场景是非wstf成员可以看到的唯一内容。
For some very important reasons, most of the work within the WSTF is done in private.
由于一些非常重要的原因，WSTF中的大多数工作以秘密方式执行。
The difference is that with WSTF, unpublished scenarios are not visible to non-members.
所不同的是，在WSTF中未发布的场景对非成员不可视。
As the WSTF is being announced, it already has several customers who are part of the group.
当推出WSTF时，它已具有多个客户，这些客户都是该团队的一部分。
The idea of long lived endpoints differentiates WSTF from other Web service testing efforts.
长期存在端点的想法可以将WSTF从其他Web服务测试工作中区分开来。
Members of the WSTF are encouraged to provide the implementation of their sample applications.
鼓励WSTF的成员提供其示例应用程序的实现。
There is nothing that would prevent the WSTF to extend its testing into other Web service testing.
WSTF将其测试扩展到其他Web服务测试不存在任何限制。
The one key difference between WSTF and the typical open-source model is the private nature of the WSTF.
WSTF和典型的开源模型之间的一个主要区别是 WSTF 的隐私特性。
The structure of the WSTF also provides for a much broader benefit to the Web services community at large.
WSTF的结构还总体上为Web服务社区提供了更广泛的好处。
The WSTF members working on the scenario agree that it’s ready for publication—how they decide this is up to them.
处理场景的 WSTF成员同意发布场景——如何决定完全由他们自己负责。
This means that the testing done within the WSTF is not a point in time statement; it's a continuous testing effort.
这意味着在WSTF中完成的测试不是在某个时间点可行，它是一项连续测试工作。
The WSTF was originally formed to perform scenario-based interoperability testing that was not being done elsewhere.
成立WSTF最初的目的是为了执行在其他地方无法执行的基于场景的互操作性测试。
In addition to the WSTF mailing lists for general topic discussions, each scenario provides its own unique mailing list.
除了用于一般主题讨论的WSTF邮件列表外，每个场景还提供其本身的独有邮件列表。
The WSTF can provide a forum where someone can speak to all types and sizes of players within the Web services community.
WSTF可以提供一个论坛，其中任何人都可以与Web服务社区中所有类型和规模的参与者探讨问题。
The WSTF is not a specification development organization, but it does provide a venue for initial discussions to take place.
WSTF不是一个规范制定组织，但它可提供一个进行初始讨论的地方。
In practical terms this means that most of the scenarios that have been tested in the past will gradually be brought into the WSTF.
就实践而言，这意味着过去测试的大多数场景将逐步被带入WSTF。
This article explores what some of those missing pieces might be and introduces a new initiative called the Web Services Test Forum (WSTF).
本文将探索缺少的内容可能是哪些，并介绍一个被称为Web服务测试论坛(WSTF)的新计划。
Unlike other interoperability efforts, the WSTF is not prevented from examining any Web Service specification at any stage of its development.
与其他互操作性工作不同，不阻止WSTF检查其开发的任一阶段的任何Web服务规范。
This article has used the term Web services as a synonym for SOAP, but the WSTF is actually not limited to just SOAP-based Web service testing.
本文使用了术语Web服务作为SOAP的代名词，但WSTF实际上并不只局限在基于SOAP的Web服务测试。
The WSTF could begin such an effort long before the Working Group actually begins its own testing and well before the specification is complete.
WSTF可以在工作组实际开始自己的测试以及规范完成之前就及早开始此项工作。
Published scenarios and unpublished scenarios have the same WSTF features available to them-the only difference is whether non-members can see them.
发布的场景和未发布的场景具有相同的WSTF可用功能——唯一不同是非成员用户是否可以看到它们。
However, a company may have a variety of reasons for wanting to remain private, and the WSTF provides this option in order to address this situation.
不过，公司可能出于各种原因希望不被公众知道，WSTF提供此选项就是为了解决这一问题。
Owners are generally encouraged to make their endpoints public when a scenario is published so that they can benefit from testing by non-WSTF members.
通常鼓励所有者在场景发布后公开他们的端点，以便他们能够从非wstf成员执行的测试中获益。
At its most basic level, the WSTF is a place for all members of the Web services community to discuss testing and any other concerns related to Web services.
在最基本的层次上，WSTF是一个供web服务社区的所有成员讨论测试和任何与Web服务相关的其他问题的地方。
Unlike previous interoperability efforts, the WSTF is specifically designed to verify and examine scenarios and usage patterns that customers will actually use.
与以前的互操作性工作不同，WSTF旨在验证和检查客户实际使用的场景和使用模式。
In addition to the two testing views already discussed (customer centric and specification centric), WSTF also provides a third view: forward looking scenarios.
除已讨论的两个测试视图外(以客户为中心和以规范为中心)，WSTF还提供了第三个视图：前瞻性场景。
Given that Microsoft represents a large part of the Web Services market for many Web Services based integration needs, this can only limit the applicability of WSTF.
鉴于微软代表了针对大量基于Web服务集成需求的Web服务市场的大部分，此举将大大限制WSTF的能力。
The WSTF hopes to start with a business problem, apply the appropriate Web service specification, and then test-almost the opposite of what has happened in the past.
WSTF希望从业务问题开始，应用适当的Web服务规范，然后进行测试——几乎与过去的流程相反。
By providing a common testing ground and location for sharing ideas, the WSTF can fill some of the gaps in the community and open development aspects of Web services.
通过为共同的思想提供公共测试地点和位置，WSTF可以弥补社区和Web服务开放式开发方面的脱节。
应用推荐