Required service specifications.
需要的服务规范。
Provided service specifications.
提供的服务规范。
The service references specify required service specifications.
服务引用指定所需的服务规范。
Note: The services (ports) are typed with service specifications.
注意：服务(端口)的类型是由服务规范定义的。
Evolutionary changes show a clear heritage to prior service specifications.
渐进的更改表现出对以前服务规范的明显继承。
See "Modeling SOA: Part 2. Service Specifications" for further details.
请参见“soa建模：第二部分服务规范”获得更多细节。
We are now ready to start modeling the details of the service specifications.
我们还没有准备好开始对服务规范的细节进行建模。
These service specifications are an elaboration of the interfaces shown in Figure 2.
这些服务规范在图2中被详细表示为接口。
The rest of this article explains how to model the details of the service specifications.
本文的剩余篇幅还将解释如何对服务规范的细节进行建模。
It has several parts with types that are the service specifications discussed previously.
它具有前面所讨论的服务规范类型中的若干部分。
While we're considering operational containers, where would service specifications be contained?
在考虑操作容器时，服务规范应该放在哪里？
The diagram shows a potential use of each of those service specifications in a particular context.
该图显示了在特定的上下文环境中每一个服务规范的潜在使用。
Figure 2 shows the service specifications that were identified as needed to fulfill the requirements.
图2显示了作为满足需求所需要的被识别的服务规范。
From the start, SOAP web service specifications have offered many choices for implementers and users.
从一开始，SOAPweb服务规范就为实施者和用户提供了很多选择。
A set of implementation models describing the software components realizing the service specifications.
描述实现服务规范的软件组件的实现模型。
The message models developed by the Data Architect are used (or reused) for these service specifications.
数据架构师开发的消息模型用于(或复用于)这些服务规范。
The specification of any services that resolve the required service specifications of the implementation.
任何服务的规范，解析实现需要的服务规范。
Figure 1 shows the service specifications that were identified as needed to fulfill the business requirements.
图1显示了作为满足需求所需要的被识别的服务规范。
Let's start by reviewing the service specifications that were identified and specified in the previous articles.
让我们从评审在前面文章中识别和指定的服务规范开始。
The following subsections elaborate on each of the identified service specifications shown previously in Figure 2.
下面各小节详细描述了每一个在图2 中被识别的服务规范。
In some ways, then, the service registry and repository becomes a container for service specifications (Figure 5).
在某种程度上，服务注册表和存储库是服务规范的容器(图5)。
The following subsections elaborate on each of the identified service specifications shown previously in Figure 1..
图1中显示了每一个服务规范的部分精华。
An XKMS service implementing XKRSS service specifications may choose to offer some, all, or none of these operations.
实现了XKRSS服务规范的XKMS服务可以选择提供一些、所有或者不提供这些操作。
A service model describing both the consumer view (service specifications) and provider view (services, partitions, etc.)
描述客户视角(服务规范)和供应商视角(服务、分区等)的服务模型。
Service specifications define a contract between consumer requisitions and provider services that map needs to capabilities.
服务规范定义了消费者请求和生产者服务之间的契约。
The Software Architect and Designer develop detailed service specifications that include the protocol and policy information.
软件架构师和设计人员开发了包含协议和策略信息的具体服务规范。
With that knowledge, you will be able to create a service design model that includes Messages, service Specifications, and Services.
有了这些知识，您就可以创建一个包含消息、服务规格说明以及服务的服务设计模型。
Service registries provide information such as service specifications and descriptions, usage policies, dependencies and interactions.
服务注册中心提供服务规范与描述、使用策略、依赖关系和交互等信息。
Clear quality of service specifications, stated from a business perspective, help the architect assess where and how to provide services.
清晰的服务质量规范(根据业务远景确定的)有助于架构师评估服务的提供位置和方式。
At this point, we don't have complete service specifications, nor do we know what service participants will provide or require what services.
关于这一点，我们既没有完全的服务规范，也不知道服务参与者将会提供什么或者需要什么服务。
应用推荐