xsi

To address the shortcomings of xsi : type , you can use the type alternative mechanism .

为了克服xsi：type的缺陷，可以使用类型替换机制。

An xsi : type attribute whose value must be soapenc : Array

type属性，它的值必须是soapenc：Array

Xsi : type is specified on an element in the instance document to replace the declared type with a derived one .

要在实例文档中对元素指定xsi：type，使用派生类型替换声明的类型。

In most cases , through the xsi : schemaLocation attribute .

在大多数情况下，可以通过xsi：schemaLocation属性做到这一点。

The schema specification correctly recognizes the lack of robustness due to xsi : schemaLocation .

模式规范正确地认识到了由xsi：schemaLocation所导致的健壮性不够的问题。

I could have also chosen to simply omit the xsi : type attribute and it would still be a valid encoded form .

我本来还可以选择完全省略xsi：type属性，而该SOAP信封将仍为有效的已编码形式。

More specifically , it should not depend on documents having the appropriate xsi : schemaLocation attribute .

更具体地说，它不应当靠拥有正确的xsi：schemaLocation属性的文档。

The validation cannot be robust if it depends on the content of the document , such as xsi : schemaLocation .

如果验证取决于文档内容，如xsi：schemaLocation，那么验证不可能是健壮的。

When Xsi adopted Ma-Fon as his Commander in the field , she was about to marry with a rich family .

当克西任命马芬做为她的战场指挥官时（注：克西其实是女性），她正要嫁入一个富裕的家庭。

This mechanism works well if you design an XML vocabulary specifically for use with XML Schema and you require that instances of your vocabulary use xsi : type for type substitution .

如果特别针对XMLSchema使用设计XML词汇表，那么这种机制非常有用，并且词汇表实例需要使用xsi：type实现类型替换。

The type encoding info ( such as xsi : type = " xsd : int ") is usually just overhead which degrades throughput performance .

类型编码信息（比如xsi：type=“xsd：int”）通常就是降低吞吐量性能的开销。

As these scenarios illustrate , the xsi : schemaLocation attribute works well in small-scale applications , but it becomes increasingly difficult to manage in more distributed environments .

正如上面这些方案所说明的那样，xsi：schemaLocation属性在小型应用程序中工作得很好，而在分布程度越高的环境对其进行管理则越困难。

The attribute is a simple solution for managing XML schemas , but it has one big flaw : It assumes that your application can control the xsi : schemaLocation attribute .

虽然该属性是管理XML模式的一种简单解决方案，但它却有一个大缺陷：它假定您的应用程序可以控制xsi：schemaLocation属性。

According to the specification , xsi : schemaLocation is only a hint to the parser and the parser may use other means to decide which schema to apply .

根据该规范，xsi：schemaLocation仅仅是对解析器的一个提示，解析器可以使用其它方法来确定要应用何种模式。

For example , if an event contains an xsi : type attribute identifying its payload , and different kinds of events have different types , testing this attribute may be all that 's needed .

如果所订阅的事件包含了确定其有效负载的xsi：type属性，并且不同的事件实例具有不同的类型，则所需做的工作就是测试此属性。

The attribute takes pairs of namespace URIs and the associated schema file ( there 's an xsi : noNamespaceSchemaLocation attribute for documents with no namespaces ) .

该属性带有几对名称空间URI和相关联的模式文件（没有名称空间的文档则采用xsi：noNamespaceSchemaLocation属性）。

A Web publishing framework such as XM or Cocoon may expect that writers set the xsi : schemaLocation correctly , which may not be the case if several authors have contributed to the site .

诸如XM或Cocoon之类的Web发布框架可能会期望作者正确地设置xsi：schemaLocation，而当多人参与该站点的开发时，情况可能就不如所愿。

In the case of the retrieval response , the XML document includes the element but uses an xsi : nil = " true " attribute , which is not permitted by the schema , and is again invalid .

对于检索响应，XML文档包括元素，但使用了xsi：nil=“true”属性，这在模式中是不允许的，因此同样也无效。