This is a top level complex type definition.
以下是顶级复杂类型定义。
Build element definitions as necessary to reference a single complex type definition.
根据需要构建元素定义,以引用单个复杂类型定义。
Make sure to define not only complex type definition, but also the element definition.
确保不仅要定义复杂的类型,还要对元素进行定义。
Use element definitions with the same target namespace as their complex type definition.
元素定义与其复杂类型定义使用同一个目标命名空间。
There is no need to explicitly reference the attribute group in either complex type definition.
无需在每个复杂类型定义中显式地引用属性组。
This is a top level anonymous complex type definition, similar to WebSphere Interchange Server 4.x.
以下是顶级匿名复杂类型定义,与WebSphereInterchangeServer 4 . x类似。
The issue with the above complex type definition can be illustrated with the instance document in Listing 2.
上面这个复杂类型定义的问题可以用清单2中的实例文档来演示。
This element declaration and complex type definition have been extracted from the single XForms-Schema.xsd file.
该元素声明和复杂类型定义已经从单独的XForms - Schema . xsd文件中提取出来了。
In Listing 16, the complex type definition contains a sequence of four child elements that are explicitly defined.
在清单16中,复杂类型定义包含一个由4个显式定义的子元素组成的序列。
Similarly, you redefine the existing complex type definition pType to add the any element, which supplies the namespace restriction to the XForms namespace.
类似地,重定义已有的复杂类型定义pType以添加any元素,后者对XForms名称空间提供名称空间限制。
As a consequence, the complex type definition in Listing 1 becomes valid in XML Schema 1.1 because the ambiguity between the element declaration and the wildcard no longer exists.
因此,清单1中的复杂类型定义在XMLSchema 1.1中变得有效,因为元素声明和通配符之间的不确定性已不复存在。
As a consequence, the complex type definition in Listing 1 becomes valid in XML Schema 1.1 because the ambiguity between the element declaration and the wildcard no longer exists.
因此,清单1中的复杂类型定义在XMLSchema 1.1中变得有效,因为元素声明和通配符之间的不确定性已不复存在。
应用推荐