A schema that defines extensions to the NIEM model, known as the extension schema.
一个定义NIEM模型的扩展的模式，称为扩展模式。
Depending on the complexity of your IEPD, you might have one extension schema or many.
根据IEPD的复杂性，可能具有一个或很多个扩展架构。
For the Theft Report example, because it is simple, I choose to create one extension schema.
对于TheftReport例子，由于比较简单，我选择创建一个扩展架构。
The beginning of a typical NIEM schema document-in this case, the extension schema for the Theft Report example-is in Listing 1.
一个典型NIEM架构文档的开头部分—本例中是TheftReport例子的扩展架构—展示在清单1中。
You are not required to have separate exchange and extension schemas; you can put all of your extensions in the same schema document.
您不需要具有单独的交换架构和扩展架构；可以将您的所有扩展放在同一个架构文档中。
This avoids the need to prefix the extension schema elements with a namespace, meaning that the configuration can look "native" and not Spring-centric.
这样避免需要通过命名空间给扩展schema元素加上前缀，意味着这样的配置看起来更自然一些，而非以spring为中心的。
In most Information exchange Package Documentations (IEPDs) you create, you will need to write an extension schema that adds types and properties that are unique to your exchange.
在您创建的大多数信息交换包文档(Information Exchange Package Documentation,IEPD)中，您将需要编写一个扩展架构(extension schema)，用于添加对交换是惟一的类型和属性。
Schema authors often need to add the same kind of wildcard to a large number of complex types to allow future extension.
模式作者通常需要将同一种通配符添加到大量复杂类型以允许进一步的扩展。
Note: Complete extension and exchange schema documents that include all of the listings in this article are available in Downloads.
注意：完整的扩展和交换架构文档包含本文中的所有清单，可在下载处得到。
However, you design an extension field into the schema to accommodate additional values.
然而，您要在模式中设计一个扩展字段来容纳附加值。
This is an XML schema capability to allow for extension in the future by letting authors add additional attributes to these standard types.
通过允许作者向标准类型中添加额外的属性来引进未来的扩展，这是XML模式的一个能力。
All you can do is leave extension points in the schema to allow future extensions.
我们所能做的就是在模式中留下扩展点，以允许未来进行扩展。
Of course, there are other ways to do that; depending on your specific plan, those ways might have advantages over the extension point schema.
当然，还可以使用其他方法实现这一点；根据您的特定计划，这些方法可能在某些方面优于扩展点模式。
To understand better how to specify the schema location and use the default namespace, consider the extension to the example in Listing 5.
为了更好地理解如何指定模式的位置和使用默认名称空间，看一看清单5中扩展的例子。
In data customization aspect, there are also various degrees of flexibility for a multi-tenant application that ranges from complex schema customization to simple field extension.
在数据定制方面，多租户应用程序也有多种选择，从复杂的模式定制到简单的字段扩展，这些方法的灵活性各不相同。
The schema for this extension point, like that for completion contributors, consists primarily of a element.
这个扩展点的模式和补全贡献器的模式相似，主要包含一个 元素。
The target namespace defines the unique identifier for the XML schema file and its domain extension.
目标名字域为XML方案文件及其域扩展定义了独一的标识符。
A sample of valid data associated with this schema that USES the generic element extension is in Listing 2.
清单2展示了与这个使用通用元素扩展的模式关联的有效数据的样例。
The extension point schema defines how a plug-in called an extender plug-in can modify the host plug-in by declaring an extension.
扩展点模式定义了一个名为扩展器插件的插件如何通过声明扩展而修改主插件。
The first basic change presented in Listing 4 is the extension of the ACORD schema by adding an optional element for a party's social security number (SSN).
清单4中的第一种基本变化是ACORD模式的扩展，增加了一个可选元素表示参与者的社会安全号码(SSN)。
This silence is odd, considering that there is a simple mechanism in XML Schema that can be used to provide the same effect as implementation inheritance: the extension mechanism.
这种沉默是暂时的，因为XMLSchema中有一种简单的机制可以用来达到与实现继承同样的目的：扩展机制。
Section 5.4.1 of the JAX-RPC spec describes how a JAX-RPC compliant Web services implementation should use the XML Schema extension construct to relate inherited value objects together in the WSDL.
JAX-RPC规范的第 5.4.1节描述了符合 JAX-RPC 的Web服务实现应该如何使用XMLSchema扩展构造来使 WSDL中的继承值对象关联起来。
Beyond this, XML schema is incapable of handling many types of easily stated constraints on documents (such as alternative attributes, or required extension elements from separate schemas).
除此之外，XML模式还无法处理许多很容易规定文档约束的类型(如替代属性，或从另一个模式上使用扩展元素)。
Listing 1 contains the Batch extension point's schema definition.
清单1包括了Batch扩展点的模式定义。
The extension point schema defines how a plug-in, called an extender plug-in, can modify the host plug-in by declaring an extension.
扩展点模式定义了某一插件(称为extender插件)如何通过声明扩展来修改主机插件。
Binding customization files are also XML schema documents with a typical extension of.xjb.
绑定定制文件也是XML模式文档，扩展名通常是.xjb。
As you can see, the schema does not define elements with the names purple or orange, but these names were included in the data instance and parsed as valid because of the extension technique used.
如您所见，这个模式并不使用purple或orange等名称来定义元素，由于使用了扩展技术，这些名称包含在数据实例中并解析为有效值。
The extension implementer USES the schema in the plugin.xml file for his or her plug-in.
扩展实现者在自己的插件中使用plugin . xml文件中的模式。
With Spring 2.0, this problem went away, as XML schema, unlike DTD, allows for extension.
随着Spring 2.0的出现，这样的问题没有了，因为XMLschema并不像DTD，它允许扩展。
The extension point specifies the data in an XML Schema.
扩展点在XMLSchema中指定数据。
应用推荐