有一点非常重要，即我们要把它视为一个完整的系统，而不只是一堆独立组件的总和。
It's extremely important for us to think about this as a whole system and not just the sum of a bunch of individual components.
所以，还是每个的设计基础事故都会，有一个组件的单失效，那基本上，就是单失效的标准。
So, again each design basis accident has one single failure of a component which basically is the single failure criteria.
处理标签的一个重要方面是知道哪些组件有哪些状态。
An important aspect of dealing with the tag is knowing which components go with which states.
快照实际上就是基准的集合，工作区中的每个组件有一个基准。
A snapshot is really just a collection of baselines, one for each component in your workspace.
只是有一个问题：当前使用的组件的成本比这个价格要高。
There is just one problem: the cost of the components currently used comes to more than that.
有多种方式我们可以用来标准化一个组件模式。
There are numerous ways in which we can formulate a component model.
正如前面所讨论的，当同步调用异步组件或异步导入时，沿着调用路径有一个异步跃点。
As discussed earlier, when an asynchronous component or asynchronous import is invoked synchronously, there is an asynchronous hop along the invocation path.
UML设计图与实现所需的组件之间有一个紧密的对应关系。
There is a tight correspondence between UML design diagrams and the components needed for the implementation.
每个标签面板有一个标题，其中可以容纳其他组件。
UML设计图与实现所需的基于消息传送的框架应用程序和组件之间有一个紧密的对应关系。
There is a tight correspondence between UML design diagrams and the framework messaging based applications and components needed for the implementation.
此组件有一个函数，在程序调用的最早阶段由提要聚合器调用。
This component has one function, and it is called by the feed aggregator at the very beginning of the program invocation.
在销售趋势跟踪应用程序的SalesLeads页面中，有三个窄栏组件和一个宽栏组件。
In our lead manager application, on the Sales Leads page, we have three narrow column components and one wide column component.
使用ClassicRegistry组件，检查一个有精确服务输入名称的服务描述是否存在于 Classic Registry 之中。
Using Classic Registry component, check if a service description with the exact input name of the service exists in the Classic Registry.
如清单8中所示，提要聚合器组件有一个名为aggregate_rss_feeds的函数。
As shown in Listing 8, the feed aggregator component has one function named aggregate_rss_feeds.
我们可以看到，fileupload组件有一个相应的hx： fileupload标签，通过其属性值该标签可以与模型绑定。
As we can see, the fileupload component has a corresponding tag hx: fileupload that can be bound to the model via its value attribute.
OpenLaszlo支持一个丰富的图形模型，有很多内置的、可重用的组件，以及高级的WYSIWYG文本和图形化编辑工具。
OpenLaszlo supports a rich graphics model with many built-in and reusable components, as well as advanced WYSIWYG text and graphical editing tools.
模板组件有一个IndexFactory类型的属性，该属性是索引引擎的派生物，可能会因索引引擎而满负荷。
The template component has a property of type IndexFactory, a descendent of the indexing engine, which can saturate it.
column组件有一个名为header的facet，它定义了在 header 中显示的内容。
The column component has a facet called header that defines what is displayed in the header.
这个组件拥有保存值绑定的特殊方法，即setValueBinding；可以有不止一个值绑定。
The component has a special method to store value bindings, namely setValueBinding; you can have more than one value binding.
希望您对这些组件如何协同工作已经有了一个很好的理解。
Hopefully, you have gained a better understanding of how these components work together.
示例程序有两个组件：一个内核模块和一个用户空间程序。
The sample program has two components: a kernel module and a user-space program.
已经有一个社区附加组件来执行这些功能。
让我们假设你有九个子系统，每一个都有数量日益增加的组件。
Let's assume that you have nine subsystems, each with increasingly larger Numbers of components.
此组件有一个函数，当所有rss提要条目均被从收到的rss提要内容中解析时，提要聚合器将会调用这个函数。
This component has one function, which is called by the feed aggregator, when all the RSS feed items are parsed from the received RSS feed content.
注意，我们的中介模块有一个导出组件和一个导入组件，当然还有一个中介流程组件。
Notice that our mediation module has one export and one import, and, of course, a mediation flow component.
这包括一个皮肤，在这个皮肤内，有打包为皮肤组件的其他HTML，这些组件可以由皮肤重新使用。
This includes a skin, and within the skin, other HTML packaged as skin components that are reused by the skins.
可以设置一个高级的组件属性，以定义该组件有多少个动作，以及它传播的字段的数量。
An advanced component property can be set to define how many actions that this component consumes and the number of fields that it broadcasts.
树安全标签组件：树是一个元素集合，用于表示有多个节点和分支的复杂层次关系。
Tree security label component: a tree is a collection of elements representing a complex hierarchy having multiple nodes and branches.
一个安全策略中最多可以有16个不同的安全组件。
There can be a maximum of 16 unique security components in a security policy.
一个安全策略中最多可以有16个不同的安全组件。
There can be a maximum of 16 unique security components in a security policy.
应用推荐