Interoperability — the problem of the xsi: type attribute.
互操作性——xsi：type属性的问题。
Fallback To declared type - use declared type if xsi: type is unknown.
回退到声明类型——如果xsi：type未知则使用声明类型。
In XML Schema 1.0, xsi: type was introduced as a mechanism for type substitution.
在XMLSchema 1.0中，xsi：type被作为一种类型替换机制引入。
The simplest is to add an xsi: type attribute to the control element. For example.
最简单的办法就是在控件元素中添加xsi：type属性。
To address the shortcomings of xsi: type, you can use the type alternative mechanism.
为了克服xsi：type的缺陷，可以使用类型替换机制。
The default SOAP encoding scheme USES the xsi: type attribute to indicate an XSD type.
缺省的SOAP编码模式使用xsi：type属性来表示一个xsd类型。
It can also be cast to a more specific type derived from anyAtomicType using xsi: type.
也可以使用xsi：type将其转换为一种由anyatomictype派生而来的特定类型。
Note the xsi: type attribute points to the complex type that ProductElement refers too.
请注意，xsi：type属性指向ProductElement所引用的复杂类型。
And Apache has removed the restriction that requires the xsi: type attribute to be present.
而Apache也已解除需要存在xsi：type属性的限制。
More specifically, it should not depend on documents having the appropriate xsi: schemaLocation attribute.
更具体地说，它不应当靠拥有正确的xsi：schemalocation属性的文档。
Xsi: type is specified on an element in the instance document to replace the declared type with a derived one.
要在实例文档中对元素指定xsi：type，使用派生类型替换声明的类型。
Alternately, you can place the xsi: type attribute on the relevant element in the model, as shown in Listing 7.
也可以将xsi：type属性放在模型中对应的元素上，如清单7所示。
What's more, using XSI means that we can be confident that our work will always be of exceptional quality and realism.
而且，使用了XSI，就意味着我们总是可以自信地拿出具有超高质量的成果，制作异常逼真的效果出来。
This conveys that cost has a type, and by type I mean type as defined by XSI, and that the type is float as defined by XSD.
这表明cost有一个类型，所谓类型指的是xsi定义的类型，而这个类型又是XSD中定义的浮点数。
Sometimes a type name is used in an instance document, such as when the type of a concrete element is specified with xsi: type.
有时候类型名称在一个实例文档中使用，比如当用xsi： type指定一个具体元素的类型时。
Microsoft also did not include any mechanism to easily add the xsi: type attribute to the SOAP envelopes generated by the tools.
同时Microsoft也没有包含任何机制能方便地把xsi：type属性添加到工具生成的SOAP信封上。
Because this attribute is not xsi: type, it is impossible to write a schema which models Atom using the XML schema 1.0 language.
由于该属性不是xsi：type，因此无法编写使用XMLSchema 1.0语言建模atom的模式。
Although anything is possible in the world of 3d, XSI needs to use physics based on the real world in order to calculate forces properly.
尽管在3d世界中没有什么是不可能实现的。XSI还是需要使用基于真实世界中的物理学以便正确计算力场的数值。
If, however, you write an XML schema for a vocabulary which already has its own notion of type substitution, then xsi: type will not work.
然而，如果针对已经具有自己的类型替换的词汇表编写XML模式，那么xsi：type不会起作用。
If you are using business objects defined as an element, you may not need the xsi: type attribute since you are already dealing with elements.
如果您使用作为元素定义的业务对象，可能不需要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属性)。
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属性。
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实现类型替换。
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属性，并且不同的事件实例具有不同的类型，则所需做的工作就是测试此属性。
An important point is that the xsi: type attribute is used to tell WebSphere Process Server how to construct the business object by indicating what complex type you are referring to.
一个重点是，xsi：type属性用于通过指示所引用的复杂类型来告知WebSphereProcessServer如何构造业务对象。
But I also think that choosing XSI for the development of this next-generation title, which involves such high quality images and large data sizes, may have been a factor in our success.
但我也认为，选择XSI来开发新产品，包括如高品质的影像和大量的数据，可能是我们成功的一个因素。
But I also think that choosing XSI for the development of this next-generation title, which involves such high quality images and large data sizes, may have been a factor in our success.
但我也认为，选择XSI来开发新产品，包括如高品质的影像和大量的数据，可能是我们成功的一个因素。
应用推荐