获得项目类型的定义。
The reference to the type definition.
对类型定义的引用。
Listing 3: Unit type definition snippet.
清单3：单元类型定义代码片段。
This is a top level complex type definition.
以下是顶级复杂类型定义。
Every output type definition has a unique name.
每个输出类型定义都有一个惟一名称。
Listing 3. OperatingSystem port type definition.
清单3. OperatingSystem端口类型定义。
The first type definition defines the type for our script.
首先，类型定义定义了我们脚本的类型。
Document versioning is enabled using document type definition.
通过使用文档类型定义可以进行文档版本控制。
Those operations are exposed using a WSDL port type definition.
那些操作通过使用WSDL端口类型定义而被公开。
Listing 2 contains an example of a service link type definition.
清单2中有一个服务链接类型定义的示例。
The role type definition changes when the privacy requirement changes.
隐私需求改变时，角色类型定义将改变。
The type definition is now global and has the unique name of address.type.
此类型定义现在是全局的了，并且具有独特的名称address.type。
The main method following the enumerated type definition demonstrates the usage.
位于枚举类型定义之后的main方法演示了这种用法。
This updated type definition forbids the above instance with two uri child elements.
这个更新的类型定义防止了上面那个具有两个uri子元素的实例。
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.
元素定义与其复杂类型定义使用同一个目标命名空间。
The next step is to find the declaration for the element from the type definition TypeX.
下一步是查找来自类型定义TypeX的元素的声明。
This interface represents a type definition as a pair consisting of a name and a namespace URI.
这个接口代表一个类型定义，由名称和命名空间uri成对组成。
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类似。
Finally the declaration for the element is located in the type definition TypeY of its parent element.
最后元素的声明位于它的父元素的类型定义TypeY中。
Extend this type definition to include a reference to the XForms global element definition for select.
扩展该类型定义，以包括对X Forms select全局元素定义的引用。
If none of the XPath expressions evaluate to true, the default type definition (xs: string) is selected.
如果没有XPath表达式的值是true，那么选择默认的类型定义(xs：string)。
The older document type definition (DTD) syntax for specifying document structure is not namespace-aware.
指定文档结构的早期文档类型定义（DTD）语法不能识别名称空间。
This completes the attributes and simple type definition, as shown in the fragments presented in Listing 3.
这样属性和简单类型定义就完成了，如列表3中的片段所示。
The issue with the above complex type definition can be illustrated with the instance document in Listing 2.
上面这个复杂类型定义的问题可以用清单2中的实例文档来演示。
Notice that this method does NOT occur anywhere in the complex data type definition, even though it is public.
请注意，尽管此方法是公共的，但它不会出现在复杂数据类型定义中。
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个显式定义的子元素组成的序列。
应用推荐