Network Working Group B. Bergeson
Request for Comments: 4403 K. Boogert
Category: Informational Novell, Inc.
V. Nanjundaswamy
Oracle India Pvt. Ltd.
February 2006
Network Working Group B. Bergeson
Request for Comments: 4403 K. Boogert
Category: Informational Novell, Inc.
V. Nanjundaswamy
Oracle India Pvt. Ltd.
February 2006
Lightweight Directory Access Protocol (LDAP) Schema for Universal Description, Discovery, and Integration version 3 (UDDIv3)
通用描述、发现和集成版本3（UDDIv3）的轻量级目录访问协议（LDAP）架构
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
This document defines the Lightweight Directory Access Protocol (LDAPv3) schema for representing Universal Description, Discovery, and Integration (UDDI) data types in an LDAP directory. It defines the LDAP object class and attribute definitions and containment rules to model UDDI entities, defined in the UDDI version 3 information model, in an LDAPv3-compliant directory.
本文档定义了轻量级目录访问协议（LDAPv3）模式，用于表示LDAP目录中的通用描述、发现和集成（UDDI）数据类型。它定义了LDAP对象类、属性定义和包含规则，以在LDAPv3兼容目录中对UDDI实体进行建模，这些实体在UDDI版本3信息模型中定义。
Table of Contents
目录
1. Introduction ....................................................2
2. Conventions Used in This Document ...............................2
3. Representation of UDDI Data Structures ..........................2
4. Attribute Type Definitions ......................................6
5. Object Class Definitions .......................................28
6. Name Forms .....................................................32
7. DIT Structure Rules ............................................35
8. Security Considerations ........................................37
9. IANA Considerations ............................................37
10. Normative References ..........................................40
1. Introduction ....................................................2
2. Conventions Used in This Document ...............................2
3. Representation of UDDI Data Structures ..........................2
4. Attribute Type Definitions ......................................6
5. Object Class Definitions .......................................28
6. Name Forms .....................................................32
7. DIT Structure Rules ............................................35
8. Security Considerations ........................................37
9. IANA Considerations ............................................37
10. Normative References ..........................................40
This document defines the Lightweight Directory Access Protocol [LDAPv3] schema elements to represent the core data structures identified in the Universal Description, Discovery, and Integration version 3 [UDDIv3] information model. This includes a businessEntity, a businessService, a bindingTemplate, a tModel, a publisherAssertion, and a Subscription. Portions of [UDDIv3] are repeated here for clarity.
本文档定义了轻量级目录访问协议[LDAPv3]模式元素，以表示通用描述、发现和集成版本3[UDDIv3]信息模型中标识的核心数据结构。这包括businessEntity、businessService、bindingTemplate、tModel、publisherAssertion和订阅。为清楚起见，此处重复[UDDIv3]的部分内容。
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不得”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
All schema definitions are provided using [RFC2252] descriptions, and are line-wrapped for readability only.
所有模式定义都使用[RFC2252]描述提供，并且仅为可读性而换行。
The information that makes up a registration in a UDDI registry consists of these data structure types. This division by information type provides simple partitions to assist in the rapid location and understanding of the different information that makes up a registration.
构成UDDI注册中心中注册的信息由以下数据结构类型组成。这种按信息类型划分的方法提供了简单的分区，有助于快速定位和理解构成注册的不同信息。
The individual instance data managed by a UDDI registry is sensitive to the parent/child relationships found in the schema. A businessEntity object contains one or more unique businessService objects. Similarly, individual businessService objects contain specific instances of bindingTemplate, which in turn contains information that includes pointers to specific instances of tModel objects.
UDDI注册中心管理的单个实例数据对模式中的父/子关系敏感。businessEntity对象包含一个或多个唯一的businessService对象。类似地，单个businessService对象包含bindingTemplate的特定实例，而bindingTemplate又包含指向tModel对象特定实例的指针的信息。
It is important to note that no single instance of a core schema type is ever "contained" by more than one parent instance. This means that only one specific businessEntity object (identified by its unique key value) will ever contain or be used to express information about a specific instance of a businessService object (also identified by its own unique key value).
需要注意的是，核心架构类型的任何单个实例都不会被多个父实例“包含”。这意味着只有一个特定的businessEntity对象（由其唯一键值标识）将包含或用于表示有关businessService对象的特定实例的信息（也由其自身的唯一键值标识）。
The businessEntity object represents all known information about a business or entity that publishes descriptive information about the entity as well as the services that it offers. The businessEntity is the top-level container that accommodates holding descriptive
businessEntity对象表示有关发布有关实体及其提供的服务的描述性信息的业务或实体的所有已知信息。businessEntity是一个顶级容器，用于容纳
information about a business or entity. Service descriptions and technical information are expressed within a businessEntity by a containment relationship.
关于企业或实体的信息。服务描述和技术信息通过包含关系在业务实体中表示。
A businessEntity is represented in the directory by the attributes uddiBusinessKey, uddiAuthorizedName, uddiOperator, uddiDiscoveryURLs, uddiName, uddiDescription, uddiIdentifierBag, uddiCategoryBag, and uddiv3DigitalSignature, along with corresponding v3 keys viz. uddiv3BusinessKey, as defined in Section 4. A businessEntity may contain zero or more instances of uddiContact and uddiBusinessService.
目录中的业务实体由属性uddiBusinessKey、uddiAuthorizedName、uddiOperator、uddiDiscoveryURLs、uddiName、uddiDescription、uddiIdentifierBag、uddiCategoryBag和uddiv3DigitalSignature以及相应的v3密钥表示，即。uddiv3BusinessKey，定义见第4节。一个业务实体可以包含零个或多个uddiContact和uddiBusinessService实例。
A mandatory attribute, uddiBusinessKey, contains the unique identifier for a given instance of a businessEntity.
强制属性uddiBusinessKey包含businessEntity给定实例的唯一标识符。
businessEntity's definition is given in Section 5.
业务实体的定义见第5节。
The businessService instances represent a logical business service. Each businessService object is the logical child of a single businessEntity object. Each businessService element contains descriptive information in business terms outlining the type of technical services found within each businessService instance.
businessService实例表示逻辑业务服务。每个businessService对象都是单个businessEntity对象的逻辑子对象。每个businessService元素都包含业务术语中的描述性信息，概述了在每个businessService实例中找到的技术服务的类型。
In some cases, businesses would like to share or reuse services, e.g., when a large enterprise publishes separate businessEntity structures. This can be established by using the businessService instance as a projection to an already published businessService.
在某些情况下，企业希望共享或重用服务，例如，当大型企业发布单独的businessEntity结构时。这可以通过使用businessService实例作为已发布businessService的投影来建立。
A businessService is represented in the directory by the attributes uddiBusinessKey, uddiServiceKey, uddiName, uddiDescription, uddiCategoryBag, uddiIsProjection, and uddiv3DigitalSignature, along with corresponding v3 keys viz. uddiv3BusinessKey, and uddiv3ServiceKey, as defined in Section 4. A businessService may contain zero or more instances of uddiBindingTemplate.
目录中的业务服务由属性uddiBusinessKey、uddiServiceKey、uddiName、uddiDescription、uddiCategoryBag、uddiIsProjection和uddiv3DigitalSignature以及相应的v3密钥（即）表示。uddiv3BusinessKey和uddiv3ServiceKey，如第4节所定义。businessService可以包含uddiBindingTemplate的零个或多个实例。
The mandatory attribute, uddiServiceKey, contains the unique identifier for a given instance of a businessService.
强制属性uddiServiceKey包含businessService给定实例的唯一标识符。
businessService's definition is given in Section 5.
第5节给出了businessService的定义。
Technical descriptions of Web services are accommodated via individual contained instances of bindingTemplate objects. These instances provide support for determining a technical entry point or optionally support remotely hosted services, as well as a lightweight facility for describing unique technical characteristics of a given implementation. Support for technology and application specific parameters and settings files are also supported.
Web服务的技术描述是通过bindingTemplate对象的各个包含实例来实现的。这些实例提供了确定技术入口点的支持，或者可选地支持远程托管服务，以及描述给定实现的独特技术特征的轻量级工具。还支持特定于技术和应用程序的参数和设置文件。
Since UDDI's main purpose is to enable description and discovery of Web service information, it is the bindingTemplate that provides the most interesting technical data. With UDDIv3, bindingTemplates also can have categorization information.
由于UDDI的主要目的是实现对Web服务信息的描述和发现，因此bindingTemplate提供了最有趣的技术数据。使用UDDIv3，绑定模板还可以具有分类信息。
Each bindingTemplate instance has a single logical businessService parent, which in turn has a single logical businessEntity parent.
每个bindingTemplate实例都有一个逻辑businessService父级，而该父级又有一个逻辑businessEntity父级。
A bindingTemplate is represented in the directory by the attributes uddiBindingKey, uddiServiceKey, uddiDescription, uddiAccessPoint, uddiHostingRedirector, uddiCategoryBag, and uddiv3DigitalSignature, along with corresponding v3 keys viz. uddiv3ServiceKey and uddiv3BindingKey, as defined in Section 4. A bindingTemplate may contain zero or more instances of uddiTModelInstanceDetails.
绑定模板在目录中由属性uddiBindingKey、uddiServiceKey、uddiDescription、uddiAccessPoint、uddiHostingRedirector、uddiCategoryBag和uddiv3DigitalSignature以及相应的v3密钥表示，即。uddiv3ServiceKey和uddiv3BindingKey，如第4节所定义。bindingTemplate可以包含uddiTModelInstanceDetails的零个或多个实例。
The mandatory attribute, uddiBindingKey, contains the unique identifier for a given instance of a bindingTemplate.
强制属性uddiBindingKey包含bindingTemplate给定实例的唯一标识符。
BindingTemplate's definition is given in Section 5.
BindingTemplate的定义在第5节中给出。
The tModel object takes the form of keyed metadata (data about data). In a general sense, the purpose of a tModel within the UDDI registry is to provide a reference system based on abstraction. Thus, the kind of data that a tModel represents is pretty nebulous. In other words, a tModel registration can define just about anything, but in the current revision, two conventions have been applied for using tModels: as sources for determining compatibility and as keyed namespace references.
tModel对象采用键控元数据（关于数据的数据）的形式。在一般意义上，UDDI注册中心内的tModel的目的是提供一个基于抽象的参考系统。因此，tModel表示的数据类型非常模糊。换句话说，tModel注册几乎可以定义任何内容，但在当前版本中，使用tModel应用了两个约定：作为确定兼容性的源和作为键控命名空间引用。
The information that makes up a tModel is quite simple. There are a key, a name, an optional description, and a Uniform Resource Locator [URL] that points somewhere--presumably somewhere where the curious can go to find out more about the actual concept represented by the metadata in the tModel itself.
组成tModel的信息非常简单。有一个键、一个名称、一个可选描述和一个统一的资源定位器[URL]，它指向某个地方——可能是好奇者可以去的地方，以了解更多关于tModel本身中元数据所表示的实际概念。
A tModel is represented in the directory by the attributes uddiTModelKey, uddiAuthorizedName, uddiOperator, uddiName, uddiDescription, uddiOverviewDescription, uddiOverviewURL, uddiIdentifierBag, uddiCategoryBag, uddiIsHidden, and uddiv3DigitalSignature, along with the corresponding v3 key viz. uddiv3tModelKey, as defined in Section 4. A tModel may also contain a uddiHidden to logically delete a tModel.
目录中的tModel由属性uddiTModelKey、uddiAuthorizedName、uddiOperator、uddiName、uddiDescription、uddiOverviewDescription、uddiOverviewURL、uddiIdentifierBag、uddiCategoryBag、uddiIsHidden和uddiv3DigitalSignature以及相应的v3密钥viz表示。uddiv3tModelKey，定义见第4节。tModel还可以包含uddiHidden以逻辑方式删除tModel。
A mandatory attribute, uddiTModelKey, contains the unique identifier for a given instance of a tModel.
强制属性uddiTModelKey包含给定tModel实例的唯一标识符。
tModel's definition is given in Section 5.
第5节给出了tModel的定义。
Many businesses, such as large enterprises or marketplaces, are not effectively represented by a single businessEntity, since their description and discovery are likely to be diverse. As a consequence, several businessEntity instances can be published, representing individual subsidiaries of a large enterprise or individual participants of a marketplace. Nevertheless, they still represent a more or less coupled community and would like to make some of their relationships visible in their UDDI registrations.
Many businesses, such as large enterprises or marketplaces, are not effectively represented by a single businessEntity, since their description and discovery are likely to be diverse. As a consequence, several businessEntity instances can be published, representing individual subsidiaries of a large enterprise or individual participants of a marketplace. Nevertheless, they still represent a more or less coupled community and would like to make some of their relationships visible in their UDDI registrations.translate error, please retry
A publisherAssertion is represented in the directory by the attributes uddiFromKey, uddiToKey, uddiKeyedReference, and uddiUUID, and uddiv3DigitalSignature, as defined in Section 5.
如第5节中所定义的，publisherAssertion在目录中由属性uddiFromKey、uddiToKey、uddiKeyedReference和uddiUUID以及uddiv3DigitalSignature表示。
A mandatory attribute, uddiUUID, contains the unique identifier for a given instance of a publisherAssertion.
强制属性uddiUUID包含publisherAssertion的给定实例的唯一标识符。
publisherAssertion's definition is given in Section 5.
第5节给出了publisherAssertion的定义。
3.6. Operational Information:
3.6. 操作信息：
With UDDIv3, the operational information associated with the core UDDI data structures is maintained in a separate OperationalInfo structure, so that the digital signature specified by the publisher remains valid.
使用UDDIv3，与核心UDDI数据结构相关联的操作信息被维护在一个单独的OperationalInfo结构中，因此发布者指定的数字签名仍然有效。
The operationalInfo structure is used to convey the operational information for the UDDIv3 core data structures, that is, the businessEntity, businessService, bindingTemplate, and tModel
operationalInfo结构用于传递UDDIv3核心数据结构的操作信息，即businessEntity、businessService、bindingTemplate和tModel
structures. UDDIv3 OperationalInfo consists of 5 elements: created, Modified, modifiedIncludingChildren, nodeId, and authorizedName.
结构。UDDIv3 OperationalInfo由5个元素组成：创建、修改、修改（包括子项）、节点ID和授权名称。
Depending on the specific UDDIv3 core data structure, the operationalInformation is represented in the directory as a combination of implicit LDAP Standard Operational attributes: createTimestamp and modifyTimestamp, and the following explicit attributes: uddiAuthorizedName, uddiv3EntityCreationTime, uddiv3EntityModificationTime, and uddiv3NodeId.
根据特定的UDDIv3核心数据结构，操作信息在目录中表示为隐式LDAP标准操作属性的组合：CreateTimstamp和modifyTimestamp，以及以下显式属性：uddiAuthorizedName、uddiv3EntityCreationTime、uddiv3EntityModificationTime和uddiv3NodeId。
The OIDs for the attribute types in this document have been registered by the IANA.
本文档中属性类型的OID已由IANA注册。
This is used in uddiBusinessEntity and uddiBusinessService.
这在uddiBusinessEntity和uddiBusinessService中使用。
The uddiBusinessKey is the unique identifier for a given instance of a uddiBusinessEntity. The attribute is optional for businessService instances contained within a fully expressed parent that already contains a businessKey value.
uddiBusinessKey是uddiBusinessEntity给定实例的唯一标识符。对于包含在已包含businessKey值的完全表达的父级中的businessService实例，该属性是可选的。
If the businessService instance is rendered into the Extensible Markup Language [XML] and has no containing parent that has within its data a businessKey, the value of the businessKey that is the parent of the businessService is required to be provided. This behavior supports the ability to browse through the parent-child relationships given any of the core elements as a starting point. The businessKey may differ from the publishing businessEntity's businessKey to allow service projections.
如果businessService实例被呈现为可扩展标记语言[XML]，并且其数据中没有包含businessKey的父级，则需要提供作为businessService父级的businessKey的值。此行为支持以任何核心元素为起点浏览父-子关系。businessKey可能与publishing businessEntity的businessKey不同，以允许服务预测。
( 1.3.6.1.1.10.4.1 NAME 'uddiBusinessKey' DESC 'businessEntity unique identifier' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.1名称'uddiBusinessKey'描述'businessEntity唯一标识符'EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
The uddiAuthorizedName is the recorded name of the individual who published the uddiBusinessEntity or uddiTModel data. This data is generated by the controlling operator and should not be supplied within save_business operations.
uddiAuthorizedName是发布uddiBusinessEntity或uddiTModel数据的个人的记录名称。此数据由控制操作员生成，不应在save_业务操作中提供。
With UDDIv3, this attribute is part of the "operationalInformation"
对于UDDIv3，此属性是“操作信息”的一部分
metadata associated with core data structures.
与核心数据结构关联的元数据。
( 1.3.6.1.1.10.4.2 NAME 'uddiAuthorizedName' DESC 'businessEntity publisher name' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 SINGLE-VALUE )
（1.3.6.1.1.10.4.2名称“uddiAuthorizedName”描述“businessEntity发布者名称”相等区分名称匹配语法1.3.6.1.4.1.1466.115.121.1.12单值）
The uddiOperator is the certified name of the UDDI registry site operator that manages the master copy of the uddiBusinessEntity or uddiTModel. The controlling operator records this data at the time data is saved. This data is generated and should not be supplied within save_business or save_tModel operations.
UDDI操作员是管理uddiBusinessEntity或uddiTModel主副本的UDDI注册中心站点操作员的认证名称。控制操作员在保存数据时记录此数据。此数据是生成的，不应在save_business或save_tModel操作中提供。
With UDDIv3, this field is no longer used -- it is replaced by the nodeId (uddiv3NodeId) attribute that is part of the "operationalInformation" metadata.
在UDDIv3中，不再使用此字段——它被作为“operationalInformation”元数据一部分的nodeId（uddiv3NodeId）属性所取代。
( 1.3.6.1.1.10.4.3 NAME 'uddiOperator' DESC 'registry site operator of businessEntitys master copy' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.3名称“uddiOperator”DESC“业务实体主副本的注册站点运营商”EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
This is used in uddiBusinessEntity, uddiBusinessService, and uddiTModel.
这在uddiBusinessEntity、uddiBusinessService和uddiTModel中使用。
These are the human-readable names recorded for the uddiBusinessEntity, uddiBusinessService, or uddiTModel, adorned with a unique xml:lang value to signify the language that they are expressed in. Name search is provided via find_business, find_service, or find_tModel calls.
这些是为uddiBusinessEntity、uddiBusinessService或uddiTModel记录的人类可读名称，用唯一的xml:lang值修饰，以表示它们所用的语言。名称搜索通过find_business、find_service或find_tModel调用提供。
The publishing of several names, e.g., for romanization purposes, is supported. In order to signify the language that the names are expressed in, they carry unique xml:lang values. Not more than one name element may omit specifying its language. Names passed in this way will be assigned the default language code of the registering party. This default language code is established at the time that publishing credentials are established with an individual Operator
支持多个名称的发布，例如出于罗马化目的。为了表示名称所用的语言，它们带有唯一的xml:lang值。不能有多个name元素忽略指定其语言。以这种方式传递的姓名将被指定为注册方的默认语言代码。此默认语言代码是在与单个操作员建立发布凭据时建立的
Site. If no default language is provisioned at the time a publisher signs up, the operator can adopt an appropriate default language code.
地点如果在发布者注册时未设置默认语言，则运营商可以采用适当的默认语言代码。
With UDDIv3, multiple values with the same language code are permitted.
使用UDDIv3，允许使用相同语言代码的多个值。
( 1.3.6.1.1.10.4.4 NAME 'uddiName' DESC 'human readable name' EQUALITY caseIgnoreMatch ORDERING caseIgnoreOrderingMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.10.4.4名称“uddiName”描述“人类可读名称”相等caseIgnoreMatch排序caseIgnoreOrderingMatch子字符串匹配语法1.3.6.1.4.1.1466.115.121.1.15）
The xml:lang value precedes the name value, with the "#" character used as the separator.
xml:lang值位于name值之前，使用“#”字符作为分隔符。
The uddiDescription is an optional repeating element of one or more descriptions. One description is allowed per national language code supplied. With UDDIv3, there is no restriction on the number of descriptions or on what xml:lang value that they may have.
uddiDescription是一个或多个描述的可选重复元素。每个提供的国家语言代码允许有一个描述。使用UDDIv3，对描述的数量或它们可能具有的xml:lang值没有限制。
( 1.3.6.1.1.10.4.5 NAME 'uddiDescription' DESC 'short description' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.10.4.5名称“uddiDescription”描述“short description”相等大小写匹配语法1.3.6.1.4.1.1466.115.121.1.15）
The xml:lang value precedes the name value, with the "#" character used as the separator.
xml:lang值位于name值之前，使用“#”字符作为分隔符。
This is a list of Uniform Resource Locators (URLs) that point to alternate, file-based service discovery mechanisms. Each recorded uddiBusinessEntity structure is automatically assigned a URL that returns the individual uddiBusinessEntity structure. A URL search is provided via find_business call.
这是指向备用的、基于文件的服务发现机制的统一资源定位器（URL）列表。每个记录的uddiBusinessEntity结构自动分配一个URL，该URL返回单个uddiBusinessEntity结构。通过find_business call提供URL搜索。
The uddiDiscoveryURLs attribute is used to hold pointers to URL-addressable discovery documents. The expected retrieval mechanism for URLs referenced in the data within this structure is via the Hypertext Transfer Protocol [HTTP] HTTP-GET operation. The expected return document is not defined. Rather, a framework for establishing conventions is provided, and two such conventions are defined within
uddiDiscoveryURLs属性用于保存指向URL可寻址发现文档的指针。此结构中数据中引用的URL的预期检索机制是通过超文本传输协议[HTTP]HTTP-GET操作。未定义预期退货单据。相反，它提供了一个建立公约的框架，其中定义了两个这样的公约
UDDI behaviors. It is hoped that other conventions come about and use this structure to accommodate alternate means of discovery. With UDDIv3, a new convention is defined with useType as "homepage". Further, a UDDIv3 server need not generate/add a discoveryURL itself, since this can invalidate the digital signature of signed the Business Entity saved by publishers.
UDDI行为。希望其他的约定也会出现，并使用这种结构来适应其他的发现方式。在UDDIv3中，使用useType将新约定定义为“主页”。此外，UDDIv3服务器本身不需要生成/添加发现URL，因为这会使发布者保存的已签名业务实体的数字签名无效。
( 1.3.6.1.1.10.4.6 NAME 'uddiDiscoveryURLs' DESC 'URL to retrieve a businessEntity instance' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.10.4.6名称“uddiDiscoveryURLs”DESC“用于检索业务实体实例的URL”EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15）
The useType value precedes the URL value, with the "#" character used as the separator.
useType值位于URL值之前，使用“#”字符作为分隔符。
The uddiUseType is used to describe the type of contact or address in freeform text. Suggested examples for contact include "technical questions", "technical contact", "establish account", "sales contact", etc. Suggested examples for address include "headquarters", "sales office", "billing department", etc.
uddiUseType用于以自由格式文本描述联系人或地址的类型。建议的联系人示例包括“技术问题”、“技术联系人”、“建立帐户”、“销售联系人”等。建议的地址示例包括“总部”、“销售办事处”、“计费部门”等。
( 1.3.6.1.1.10.4.7 NAME 'uddiUseType' DESC 'name of convention the referenced document follows' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.7名称'uddiUseType'描述'约定名称参考文件遵循'EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15单值）
The uddiPersonName should list the name of the person or name of the job role that will be available behind the contact. Examples of roles include "administrator" or "webmaster".
uddiPersonName应列出联系人后面可用的人员名称或职务角色名称。角色示例包括“管理员”或“网站管理员”。
( 1.3.6.1.1.10.4.8 NAME 'uddiPersonName' DESC 'name of person or job role available for contact' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.8名称“uddiPersonName”DESC“联系人可用的人员或工作角色的名称”EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
With UDDIv3, uddiPersonName becomes multi-valued and each name can have an xml:lang attribute. The xml:lang value precedes the name value with the "#" character used as the separator.
使用UDDIv3，uddiPersonName变成多值的，每个名称都可以有一个xml:lang属性。xml:lang值位于名称值之前，并使用“#”字符作为分隔符。
This is used to hold telephone numbers for the contact. This element can be adorned with an optional uddiUseType attribute for descriptive purposes. If more than one phone element is saved, uddiUseType attributes are required on each.
这用于保存联系人的电话号码。为了便于描述，可以使用可选的uddiUseType属性修饰此元素。如果保存了多个phone元素，则每个元素上都需要uddiUseType属性。
( 1.3.6.1.1.10.4.9 NAME 'uddiPhone' DESC 'telephone number for contact' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.10.4.9姓名“uddiPhone”DESC“联系人电话号码”EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15）
The useType precedes the telephone number by a separating '#' (e.g., "Work Number#123 456-7890") .
useType在电话号码前加上一个分隔的“#”（例如，“工作号码#123 456-7890”）。
This is used to hold email addresses for the contact. This element can be adorned with an optional uddiUseType attribute for descriptive purposes. If more than one email element is saved, uddiUseType attributes are required on each.
这用于保存联系人的电子邮件地址。为了便于描述，可以使用可选的uddiUseType属性修饰此元素。如果保存了多个电子邮件元素，则每个元素上都需要uddiUseType属性。
( 1.3.6.1.1.10.4.10 NAME 'uddiEMail' DESC 'e-mail address for contact' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.10.4.10姓名“uddiEMail”DESC“联系人的电子邮件地址”EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15）
The useType precedes the email address by a separating '#' (e.g., "President of the United States #president@whitehouse.gov").
useType在电子邮件地址前面加上一个分隔的“#”（例如，“美国总统”）#president@whitehouse.gov").
The uddiSortCode is used to drive the behavior of external display mechanisms that sort addresses. The suggested values for uddiSortCode include numeric ordering values (e.g., 1, 2, 3), alphabetic character ordering values (e.g., a, b, c), or the first n positions of relevant data within the address.
uddiSortCode用于驱动对地址进行排序的外部显示机制的行为。uddiSortCode的建议值包括数字排序值（例如，1、2、3）、字母字符排序值（例如，a、b、c）或地址内相关数据的前n个位置。
( 1.3.6.1.1.10.4.11 NAME 'uddiSortCode' DESC 'specifies an external display mechanism' EQUALITY caseIgnoreMatch ORDERING caseIgnoreOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
( 1.3.6.1.1.10.4.11 NAME 'uddiSortCode' DESC 'specifies an external display mechanism' EQUALITY caseIgnoreMatch ORDERING caseIgnoreOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )translate error, please retry
With UDDIv3, the sortCode attribute is deprecated because of the guarantee of preserving the document Order.
在UDDIv3中，由于保证保存文档顺序，所以不推荐使用sortCode属性。
The uddiTModelKey is the unique identifier for a given instance of an uddiTModel.
uddiTModelKey是uddiTModel的给定实例的唯一标识符。
It is also used in a KeyedReference and in Address structures. When used with a keyed reference, this is the unique key to identify a value set and implies that the keyName keyValue pair in a uddiIdentifier or uddiCategory Bag are to be interpreted by the value set referenced by the tModelKey.
它也用于KeyedReference和地址结构中。当与键控引用一起使用时，这是标识值集的唯一键，并意味着uddiIdentifier或uddiCategory包中的keyName keyValue对将由tModelKey引用的值集进行解释。
When used with Addressline elements, it implies that the keyName keyValue pair given by subsequent uddiAddressLine elements are to be interpreted by the address structure associated with the tModel that is referenced.
当与Addressline元素一起使用时，它意味着后续uddiAddressLine元素给出的keyName-keyValue对将由与所引用的tModel关联的地址结构来解释。
( 1.3.6.1.1.10.4.12 NAME 'uddiTModelKey' DESC 'tModel unique identifier' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.12名称“uddiTModelKey”描述“tModel唯一标识符”相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
The uddiAddressLine contains the actual address in freeform text. If the address element contains a uddiTModelKey, these uddiAddressLine elements are to be adorned, each with an optional keyName keyValue attribute pair. Together with the uddiTModelKey, keyName and keyValue qualify the uddiAddressLine in order to describe its meaning.
uddiAddressLine包含自由格式文本中的实际地址。如果address元素包含uddiTModelKey，则这些uddiAddressLine元素将被修饰，每个元素都有一个可选的keyName keyValue属性对。为了描述uddiAddressLine的含义，keyName和keyValue与uddiTModelKey一起限定了uddiAddressLine。
The uddiAddressLine elements contain string data with a line length limit of 80 character positions. Each uddiAddressLine element can be adorned with two optional descriptive attributes, keyName and keyValue. Both attributes must be present in each address line if a uddiTModelKey is assigned to the address structure. By doing this, the otherwise arbitrary use of address lines becomes structured. Together with the address' uddiTModelKey, keyName and keyValue virtually build a uddiKeyedReference that represents an address line qualifier, given by the referenced uddiTModel.
uddiAddressLine元素包含行长度限制为80个字符位置的字符串数据。每个uddiAddressLine元素都可以用两个可选的描述性属性（keyName和keyValue）修饰。如果将uddiTModelKey分配给地址结构，则这两个属性必须出现在每个地址行中。通过这样做，地址行的任意使用变得结构化。与地址的uddiTModelKey、keyName和keyValue一起，虚拟地构建了一个uddiKeyedReference，该引用表示所引用的uddiTModel给出的地址行限定符。
When no uddiTModelKey is provided for the address structure, the keyName and keyValue attributes can be used without restrictions, for example, to provide descriptive information for each uddiAddressLine
当没有为地址结构提供uddiTModelKey时，可以不受限制地使用keyName和keyValue属性，例如，为每个uddiAddressLine提供描述性信息
by using the keyName attribute. Since both the keyName and the keyValue attributes are optional, address line order is significant and will always be returned by the UDDI-compliant registry in the order originally provided during a call to save_business.
通过使用keyName属性。由于keyName和keyValue属性都是可选的，因此地址行顺序非常重要，并且将始终由符合UDDI的注册中心按照最初在调用save_business时提供的顺序返回。
( 1.3.6.1.1.10.4.13 NAME 'uddiAddressLine' DESC 'address' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.10.4.13名称“uddiAddressLine”描述“address”相等大小写匹配语法1.3.6.1.4.1.1466.115.121.1.15）
The keyName, keyValue, and addressData of this attribute are separated by "#" (e.g., "#"<keyName>"#"<keyValue>"#"<addressData>). The addressData is the only required portion of the attribute.
此属性的keyName、keyValue和addressData由“#”分隔（例如“#”<keyName>“#”<keyValue>“#”<addressData>）。addressData是该属性唯一必需的部分。
The uddiIdentifierBag element allows uddiBusinessEntity or uddiTModel structures to include information about common forms of identification such as D-U-N-S_ numbers, tax identifiers, etc. This data can be used to signify the identity of the uddiBusinessEntity or can be used to signify the identity of the publishing party. Including data of this sort is optional, but when used greatly enhances the search behaviors exposed via the find_xx messages defined in the UDDI Version 2.0 API Specification [UDDIapi]. For a full description of the structures involved in establishing an identity, see UDDI Version 2.0 Data Structure Specification - Appendix A: Using Identifiers [UDDIdsr].
uddiIdentifierBag元素允许uddiBusinessEntity或uddiTModel结构包含有关常用标识形式的信息，如D-U-N-S_U号码、税务标识符等。该数据可用于表示uddiBusinessEntity的身份，也可用于表示发布方的身份。包含这种类型的数据是可选的，但如果使用，将大大增强通过UDDI 2.0版API规范[UDDIapi]中定义的find_xx消息公开的搜索行为。有关建立标识所涉及的结构的完整描述，请参见UDDI 2.0版数据结构规范-附录a：使用标识符[UDDISR]。
( 1.3.6.1.1.10.4.14 NAME 'uddiIdentifierBag' DESC 'identification information' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.10.4.14名称“uddiIdentifierBag”描述“标识信息”相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15）
The tModel, keyName, and keyValue of this attribute are separated by "#" (e.g., <tModel>"#"<keyName>"#"<keyValue>). The keyValue is the only required portion of the attribute.
<keytmodel>，35tmodel>的<keytmodel>和35tmodel>的值用35tmodel>分隔。keyValue是属性的唯一必需部分。
The uddiCategoryBag element allows uddiBusinessEntity, uddiBusinessService, and uddiTModel structures to be categorized according to any of several available taxonomy-based classification schemes. Operator Sites automatically provide validated categorization support for three taxonomies that cover industry codes (via NAICS), product and service classifications (via UNSPC), and geography (via ISO 3166). Including data of this sort is optional,
uddiCategoryBag元素允许uddiBusinessEntity、uddiBusinessService和uddiTModel结构根据几种可用的基于分类法的分类方案中的任何一种进行分类。运营商站点自动为三种分类法提供经过验证的分类支持，包括行业代码（通过NAICS）、产品和服务分类（通过UNSC）和地理（通过ISO 3166）。包含此类数据是可选的，
but when used, it greatly enhances the search behaviors exposed by the find_xx messages defined in the UDDI Version 2.0 API Specification [UDDIapi]. For a full description of structures involved in establishing categorization information, see UDDI Version 2.03 Data Structure Specification--Appendix B: Using Categorization [UDDIdsr].
但是当使用时，它极大地增强了UDDI版本2.0 API规范[UDDIapi]中定义的find_xx消息所公开的搜索行为。有关建立分类信息所涉及的结构的完整描述，请参见UDDI 2.03版数据结构规范——附录B：使用分类[UDDISR]。
( 1.3.6.1.1.10.4.15 NAME 'uddiCategoryBag' DESC 'categorization information' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.10.4.15名称“uddiCategoryBag”描述“分类信息”相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15）
The tModel, keyName, and keyValue of this attribute are separated by "#" (e.g., <tModel>"#"<keyName>"#"<keyValue>). The keyValue is the only required portion of the attribute.
<keytmodel>，35tmodel>的<keytmodel>和35tmodel>的值用35tmodel>分隔。keyValue是属性的唯一必需部分。
With UDDIv3, uddiBindingTemplates also supports the uddiCategoryBag element and they can also be categorized according to any of several available taxonomy-based classification schemes.
使用UDDIv3，uddiBindingTemplates还支持uddiCategoryBag元素，并且它们还可以根据几种可用的基于分类法的分类方案中的任何一种进行分类。
The uddiKeyedReference is a general-purpose attribute for a name-value pair, with an additional reference to a tModel.
uddiKeyedReference是名称-值对的通用属性，另外还有对tModel的引用。
( 1.3.6.1.1.10.4.16 NAME 'uddiKeyedReference' DESC 'categorization information' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.10.4.16名称“uddiKeyedReference”描述“分类信息”相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15）
The tModel, keyName, and keyValue of this attribute are separated by "#" (e.g., <tModel>"#"<keyName>"#"<keyValue>). The keyValue is the only required portion of the attribute. With UDDIv3, the tModelKey also becomes a mandatory part of the attribute.
<keytmodel>，35tmodel>的<keytmodel>和35tmodel>的值用35tmodel>分隔。keyValue是属性的唯一必需部分。使用UDDIv3，tModelKey也成为属性的一个必需部分。
Also, UDDIv3 defines KeyedReferenceGroups for CategoryBags. A keyedReferenceGroup contains a tModelKey and a simple list of KeyedReference structures. The uddiKeyedReference attribute will support KeyedReferenceGroups by suffixing the tModelKey for KeyedReferenceGroup to each of the keyedReference values associated with the group.
而且，UDDIv3为CategoryBag定义了KeyedReferenceGroup。keyedReferenceGroup包含一个tModelKey和一个KeyedReference结构的简单列表。uddiKeyedReference属性将通过将KeyedReferenceGroup的tModelKey后缀为与组关联的每个keyedReference值来支持KeyedReferenceGroup。
For example, to represent a keyedReference group containing a list of 2 keyed references, the attribute will hold the following 2 strings as its values:
例如，要表示包含2个键控引用列表的keyedReference组，该属性将包含以下2个字符串作为其值：
tModelKey1#KeyName1#KeyValue1#KeyedReferenceGroup1_tModelKey
tModelKey2#KeyName2#KeyValue2#KeyedReferenceGroup1_tModelKey
tModelKey1#KeyName1#KeyValue1#KeyedReferenceGroup1_tModelKey
tModelKey2#KeyName2#KeyValue2#KeyedReferenceGroup1_tModelKey
This is the unique key for a given uddiBusinessService. When saving a new uddiBusinessService structure, pass an empty uddiServiceKey value. This signifies that a UUID value is to be generated. To update an existing uddiBusinessService structure, pass the UUID value that corresponds to the existing service. If a uddiServiceKey is received via an inquiry operation, the key values may not be blank. When saving a new or updated service projection, pass the uddiServiceKey of the referenced uddiBusinessService structure.
这是给定uddiBusinessService的唯一密钥。保存新的uddiBusinessService结构时，传递一个空的uddiServiceKey值。这表示要生成UUID值。要更新现有uddiBusinessService结构，请传递与现有服务对应的UUID值。如果通过查询操作接收uddiServiceKey，则键值不能为空。保存新的或更新的服务投影时，传递引用的uddiBusinessService结构的uddiServiceKey。
This attribute is optional when the uddiBindingTemplate data is contained within a fully expressed parent that already contains a uddiServiceKey value. If the uddiBindingTemplate data is rendered into XML and has no containing parent that has within its data a uddiServiceKey, the value of the uddiServiceKey that is the ultimate containing parent of the uddiBindingTemplate is required to be provided. This behavior supports the ability to browse through the parent-child relationships given any of the core elements as a starting point.
当uddiBindingTemplate数据包含在已包含uddiServiceKey值的完全表达的父级中时，此属性是可选的。如果uddiBindingTemplate数据被呈现为XML，并且其数据中没有包含uddiServiceKey的父级，则需要提供uddiBindingTemplate的最终包含父级的uddiServiceKey的值。此行为支持以任何核心元素为起点浏览父-子关系。
( 1.3.6.1.1.10.4.17 NAME 'uddiServiceKey' DESC 'businessService unique identifier' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.17名称'uddiServiceKey'描述'businessService唯一标识符'EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
This is the unique key for a given uddiBindingTemplate. When saving a new uddiBindingTemplate structure, pass an empty uddiBindingKey value. This signifies that a UUID value is to be generated. To update an existing uddiBindingTemplate, pass the UUID value that corresponds to the existing uddiBindingTemplate instance. If a uddiBindingKey is received via an inquiry operation, the key values may not be blank.
这是给定uddiBindingTemplate的唯一键。保存新的uddiBindingTemplate结构时，传递一个空的uddiBindingKey值。这表示要生成UUID值。要更新现有uddiBindingTemplate，请传递与现有uddiBindingTemplate实例对应的UUID值。如果通过查询操作接收uddiBindingKey，则键值不能为空。
( 1.3.6.1.1.10.4.18 NAME 'uddiBindingKey' DESC 'bindingTemplate unique identifier' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.18名称'uddiBindingKey'描述'bindingTemplate唯一标识符'EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
The uddiAccessPoint element is an attribute-qualified pointer to a service entry point. The notion of service at the metadata level seen here is fairly abstract and many types of entry points are accommodated. A single attribute is provided named URLType.
uddiAccessPoint元素是指向服务入口点的属性限定指针。这里看到的元数据级别的服务概念相当抽象，并且包含了许多类型的入口点。提供了一个名为URLType的属性。
Required attribute-qualified element8: This element is a text field that is used to convey the entry point address suitable for calling a particular Web service. This may be a URL, an electronic mail address, or even a telephone number. No assumptions about the type of data in this field can be made without first understanding the technical requirements associated with the Web service.
Required attribute qualified element8：此元素是一个文本字段，用于传递适合调用特定Web服务的入口点地址。这可能是URL、电子邮件地址，甚至是电话号码。如果不首先了解与Web服务相关的技术要求，就不能对该领域中的数据类型进行任何假设。
( 1.3.6.1.1.10.4.19 NAME 'uddiAccessPoint' DESC 'entry point address to call a web service' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.19名称“uddiAccessPoint”DESC“用于调用web服务的入口点地址”EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
The URLType value precedes the accessPoint value by a separating '#'.
URLType值在accessPoint值之前加上一个分隔的“#”。
With UDDIv3, the "URLType" attribute is replaced by a "UseType" attribute. Using this UseType attribute, the accessPoint attribute can model a hostingRedirector or support indirection to indicate that the accesspoint is specified within a remotely hosted WSDL document.
在UDDIv3中，“URLType”属性被“UseType”属性替换。使用此UseType属性，accessPoint属性可以建模hostingRedirector或支持间接寻址，以指示accessPoint是在远程托管的WSDL文档中指定的。
For a UDDIv3 registry that needs to support UDDIv2 clients, the attribute must allow the representation of URLType and UseType values independently.
对于需要支持UDDIv2客户端的UDDIv3注册中心，该属性必须允许分别表示URLType和UseType值。
The UDDIv3 spec specifies the following logic for mapping values between URLType and UseType: If an entity is saved with the v3 namespace and a v2 inquiry is made, the URLType will be returned as "other". In the case when a v3 inquiry is made on an entity published with the v2 namespace, the v3 useType attribute will be returned as "endPoint".
UDDIv3规范为URLType和UseType之间的值映射指定了以下逻辑：如果使用v3命名空间保存实体并进行v2查询，则URLType将作为“其他”返回。在对使用v2命名空间发布的实体进行v3查询的情况下，v3 useType属性将作为“端点”返回。
For implementations that need to explicitly model both forms, the recommended format is as follows: v2URLType#v3UseType#Address
对于需要显式建模这两种表单的实现，建议的格式如下：v2URLType#v3UseType#Address
The uddiHostingRedirector element is used to designate that a uddiBindingTemplate entry is a pointer to a different uddiBindingTemplate entry. The value in providing this facility is seen when a business or entity wants to expose a service description
uddiHostingRedirector元素用于指定uddiBindingTemplate条目是指向其他uddiBindingTemplate条目的指针。当企业或实体想要公开服务描述时，可以看到提供此功能的价值
(e.g., advertise that it has a service available that suits a specific purpose) that is actually a service described in a separate uddiBindingTemplate record. This might occur when a service is remotely hosted (hence the name of this element), or when many service descriptions could benefit from a single service description.
（例如，公布其具有适合特定用途的可用服务），该服务实际上是在单独的uddiBindingTemplate记录中描述的服务。当服务被远程托管时（因此该元素的名称），或者当多个服务描述可以从单个服务描述中受益时，可能会发生这种情况。
The uddiHostingRedirector element has a single attribute and no element content. The attribute is a uddiBindingKey value that is suitable within the same UDDI registry instance for querying and obtaining the uddiBindingDetail data that is to be used.
uddiHostingRedirector元素只有一个属性，没有元素内容。该属性是一个uddiBindingKey值，适用于在同一UDDI注册中心实例中查询和获取要使用的uddiBindingDetail数据。
More on the uddiHostingRedirector can be found in the appendices for the UDDI Version 2.0 API Specification [UDDIapi].
有关uddiHostingRedirector的更多信息，请参见UDDI 2.0版API规范[UDDIapi]的附录。
Required element if uddiAccessPoint is not provided: This element is adorned with a uddiBindingKey attribute, giving the redirected reference to a different uddiBindingTemplate. If you query a uddiBindingTemplate and find a uddiHostingRedirector value, you should retrieve that uddiBindingTemplate and use it in place of the one containing the uddiHostingRedirector data.
如果未提供uddiAccessPoint，则为必需元素：此元素用uddiBindingKey属性修饰，提供对不同uddiBindingTemplate的重定向引用。如果查询uddiBindingTemplate并找到uddiHostingRedirector值，则应检索该uddiBindingTemplate并使用它代替包含uddiHostingRedirector数据的模板。
( 1.3.6.1.1.10.4.20 NAME 'uddiHostingRedirector' DESC 'designates a pointer to another bindingTemplate' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.20名称“uddiHostingRedirector”DESC指定指向另一个bindingTemplate“EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15单值”的指针）
With UDDIv3, the hostingRedirector is a deprecated element, since its functionality is now covered by the accessPoint. For backward-compatibility, it can still be used, but it is not recommended.
对于UDDIv3，hostingRedirector是一个不推荐使用的元素，因为它的功能现在由accessPoint覆盖。对于向后兼容性，仍然可以使用它，但不建议使用它。
This is an optional repeating element. This is one or more language-qualified text descriptions that designate what role a uddiTModel reference plays in the overall service description.
这是一个可选的重复元素。这是一个或多个语言限定的文本描述，指定uddiTModel引用在整个服务描述中扮演的角色。
( 1.3.6.1.1.10.4.21 NAME 'uddiInstanceDescription' DESC 'instance details description' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.10.4.21名称'uddiInstanceDescription'DESC'实例详细信息说明'EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15）
The xml:lang value precedes the name value, with the "#" character used as the separator.
xml:lang值位于name值之前，使用“#”字符作为分隔符。
The uddiInstanceParms is an optional element of the uddiInstance. It is used to contain settings parameters or a URL reference to a file that contains settings or parameters required to use a specific facet of a uddiBindingTemplate description. If used to house the parameters themselves, the suggested content is a namespace-qualified XML string using a namespace outside of the UDDI schema. If used to house a URL pointer to a file, the suggested format is a URL that is suitable for retrieving the settings or parameters via HTTP-GET.
UDDIInstanceArms是uddiInstance的可选元素。它用于包含设置参数或对文件的URL引用，该文件包含使用uddiBindingTemplate描述的特定方面所需的设置或参数。如果用于存放参数本身，则建议的内容是使用UDDI模式之外的名称空间的名称空间限定的XML字符串。如果用于存放指向文件的URL指针，建议的格式是适合通过HTTP-GET检索设置或参数的URL。
( 1.3.6.1.1.10.4.22 NAME 'uddiInstanceParms' DESC 'URL reference to required settings' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.22名称“UDDIInstanceParts”描述“URL对所需设置的引用”相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
This is an optional repeating element. This language-qualified string is intended to hold a short descriptive overview of how a particular uddiTModel is to be used.
这是一个可选的重复元素。此语言限定字符串旨在对如何使用特定uddiTModel进行简短的描述性概述。
( 1.3.6.1.1.10.4.23 NAME 'uddiOverviewDescription' DESC 'outlines tModel usage' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.10.4.23名称“uddiOverviewDescription”描述“DESC”概述tModel用法“EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15）
The xml:lang value precedes the name value, with the "#" character used as the separator.
xml:lang值位于name值之前，使用“#”字符作为分隔符。
This is an optional element. This string data element is to be used to hold a URL reference to a long form of an overview document that covers the way a particular uddiTModel specific reference is used as a component of an overall Web service description. The recommended format for the overviewURL is a URI that is suitable for retrieving the actual overview document with an HTTP-GET operation, for example, via a Web browser.
这是一个可选元素。此字符串数据元素用于保存对概述文档长格式的URL引用，该文档涵盖了特定uddiTModel特定引用作为整体Web服务描述的组件的使用方式。overviewURL的推荐格式是一个URI，它适用于通过HTTP-GET操作（例如，通过Web浏览器）检索实际的概览文档。
( 1.3.6.1.1.10.4.24 NAME 'uddiOverviewURL' DESC 'URL reference to overview document' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.24名称“uddiOverviewURL”DESC“URL参考概述文件”EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
With UDDIv3, uddiOverviewURL becomes multi-valued to allow the representation of multiple OverviewDocs within a single InstanceDetail element.
使用UDDIv3，uddiOverviewURL变为多值，以允许在单个InstanceDetail元素中表示多个概览文档。
Modeling multiple OverviewDocs within an InstanceDetail element:
在InstanceDetail元素中建模多个概览文档：
In UDDIv3, the InstanceDetails element in TmodelInstanceInfo can have multiple OverviewDoc's. In UDDIv2, we could have only 1 OverviewDoc. To retain the grouping between a set of overviewDescriptions and overviewURL, we can make both OverviewDoc and OverviewURL multi-valued, and have a "group ID" Prefix to each value (to group OverviewDescriptions and OverviewURL).
在UDDIv3中，TmodelInstanceInfo中的InstanceDetails元素可以有多个OverviewDoc。在UDDIv2中，我们只能有一个概览文档。为了保留一组overviewDescriptions和overviewURL之间的分组，我们可以将OverviewDoc和overviewURL都设置为多值，并且每个值都有一个“组ID”前缀（用于对overviewDescriptions和overviewURL进行分组）。
An example is shown below:
示例如下所示：
Overview Description OverviewURL
1#xml:lang#overviewDescription1 1#UseType#overviewURL
1#xml:lang#overviewDescription2 2#UseType#overviewURL
1#xml:lang#overviewDescription3 4#UseType#overviewURL
3#xml:lang#overviewDescription1
3#xml:lang#overviewDescription2
4#xml:lang#overviewDescription1
Overview Description OverviewURL
1#xml:lang#overviewDescription1 1#UseType#overviewURL
1#xml:lang#overviewDescription2 2#UseType#overviewURL
1#xml:lang#overviewDescription3 4#UseType#overviewURL
3#xml:lang#overviewDescription1
3#xml:lang#overviewDescription2
4#xml:lang#overviewDescription1
This implies that OverviewDoc1 has 3 overview descriptions and an overviewURL. OverviewDoc2 has only an overviewURL. OverviewDoc3 has only 2 overviewDescriptions. OverviewDoc4 also has 1 overview description and an overviewURL.
这意味着OverviewDoc1有3个概述描述和一个overviewURL。OverviewDoc2只有一个overviewURL。OverviewDoc3只有2个概览说明。OverviewDoc4还有1个概述说明和一个overviewURL。
The uddiFromKey is a required element. This is the unique key reference to the first uddiBusinessEntity for which the assertion is made.
uddiFromKey是必需的元素。这是对进行断言的第一个uddiBusinessEntity的唯一键引用。
( 1.3.6.1.1.10.4.25 NAME 'uddiFromKey' DESC 'unique businessEntity key reference' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.25名称'uddiFromKey'DESC'唯一业务实体密钥引用'EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
The uddiToKey is a required element. This is the unique key reference to the second uddiBusinessEntity for which the assertion is made.
uddiToKey是必需的元素。这是对进行断言的第二个uddiBusinessEntity的唯一键引用。
( 1.3.6.1.1.10.4.26 NAME 'uddiToKey' DESC 'unique businessEntity key reference' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.26名称'uddiToKey'描述'unique businessEntity key reference'相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
The uddiUUID is a required element. This is to ensure unique identification of uddiContact, uddiAddress, and uddiPublisherAssertion objects.
uddiUUID是必需的元素。这是为了确保uddiContact、uddiAddress和uddiPublisherAssertion对象的唯一标识。
( 1.3.6.1.1.10.4.27 NAME 'uddiUUID' DESC 'unique attribute' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.27名称“uddiUUID”描述“唯一属性”相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
With UDDIv3, this attribute will also be used for unique identification of Subscription-feature-related entities.
对于UDDIv3，此属性还将用于订阅功能相关实体的唯一标识。
This is used to provide functionality for the delete_tModel operation. Logical deletion hides the deleted tModels from find_tModel result sets but does not physically delete it.
这用于为delete_tModel操作提供功能。逻辑删除会从find_tModel结果集中隐藏已删除的tModel，但不会实际删除它。
( 1.3.6.1.1.10.4.28 NAME 'uddiIsHidden' DESC 'isHidden attribute' EQUALITY booleanMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 SINGLE-VALUE )
（1.3.6.1.1.10.4.28名称“uddiIsHidden”描述“isHidden属性”相等布尔匹配语法1.3.6.1.4.1.1466.115.121.1.7单值）
In case of UDDIv3, this attribute will represent the "deleted" attribute value.
对于UDDIv3，此属性将表示“已删除”属性值。
This is used to identify a Business Service that has a Service Projection.
这用于标识具有服务投影的业务服务。
( 1.3.6.1.1.10.4.29 NAME 'uddiIsProjection' DESC 'isServiceProjection attribute' EQUALITY booleanMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 SINGLE-VALUE )
（1.3.6.1.1.10.4.29名称'uddisprojection'DESC'isServiceProjection属性'EQUALITY booleanMatch语法1.3.6.1.4.1.1466.115.121.1.7单值）
This is used to model the xml:lang value for the Address structure in UDDIv3.
这用于为UDDIv3中的地址结构的xml:lang值建模。
( 1.3.6.1.1.10.4.30 NAME 'uddiLang' DESC 'xml:lang value in v3 Address structure' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.30名称'uddiLang'DESC'xml:v3地址结构中的lang值'EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
The following are attribute definitions to model new elements/fields in UDDIv3 information model. These attribute definitions have the "uddiv3" prefix to indicate that these attributes represent UDDI information model elements unique to UDDIv3.
以下是在UDDIv3信息模型中为新元素/字段建模的属性定义。这些属性定义具有“uddiv3”前缀，表示这些属性表示uddiv3特有的UDDI信息模型元素。
This is the unique UDDIv3 identifier for a given instance of uddiBusinessEntity. It is used in uddiBusinessEntity and uddiBusinessService.
这是给定uddiBusinessEntity实例的唯一UDDIv3标识符。它用于uddiBusinessEntity和uddiBusinessService。
A uddiBusinessEntity will include the uddiBusinessKey (the v2 form) for unique identification by UDDIv2 clients. The uddiBusinessKey (36-char) will also be the LDAP naming attribute for the uddiBusinessEntity. The uddiBusinessEntity entry MAY also include the uddiv3BusinessKey, the explicit v3 form key, which can be 255 characters long.
uddiBusinessEntity将包含uddiBusinessKey（v2表单），以便UDDIv2客户端进行唯一标识。uddiBusinessKey（36字符）也是uddiBusinessEntity的LDAP命名属性。uddiBusinessEntity条目还可以包括uddiv3BusinessKey，即显式v3表单密钥，其长度可以是255个字符。
( 1.3.6.1.1.10.4.31 NAME 'uddiv3BusinessKey' DESC 'UDDIv3 businessEntity unique identifier' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.31名称'uddiv3BusinessKey'描述'UDDIv3 businessEntity唯一标识符'EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
This is the unique UDDIv3 identifier for a given instance of uddiBusinessService. It is used in uddiBusinessService and uddiBindingTemplate.
这是给定uddiBusinessService实例的唯一UDDIv3标识符。它用于uddiBusinessService和uddiBindingTemplate。
A uddiBusinessService will include the uddiServiceKey (the v2 form) for unique identification by UDDIv2 clients. The uddiServiceKey (36-char) will also be the LDAP naming attribute for the uddiBusinessService entry. The uddiBusinessService entry MAY also include the uddiv3ServiceKey, the explicit v3 form key, which can be 255 characters long.
uddiBusinessService将包含uddiServiceKey（v2格式），以便UDDIv2客户端进行唯一标识。uddiServiceKey（36字符）也是uddiBusinessService条目的LDAP命名属性。uddiBusinessService条目还可以包括uddiv3ServiceKey，即显式v3表单密钥，长度可以为255个字符。
( 1.3.6.1.1.10.4.32 NAME 'uddiv3ServiceKey' DESC 'UDDIv3 businessService unique identifier' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.32名称“uddiv3ServiceKey”描述“UDDIv3业务服务唯一标识符”相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
This is the unique UDDIv3 identifier for a given instance of uddiBindingTemplate.
这是给定uddiBindingTemplate实例的唯一UDDIv3标识符。
A uddiBindingTemplate will include the uddiBindingKey (the v2 form) for unique identification by UDDIv2 clients. The uddiBindingKey (36-char) will also be the LDAP naming attribute for the
uddiBindingTemplate将包含uddiBindingKey（v2格式），以便UDDIv2客户端进行唯一标识。uddiBindingKey（36字符）也将是
uddiBindingTemplate entry. The uddiBindingTemplate entry MAY also include the uddiv3BindingKey, the explicit v3 form key, which can be 255 characters long.
uddiBindingTemplate条目。UDDIVbindingTemplate条目还可以包括uddiv3BindingKey，即显式v3表单键，长度可以为255个字符。
( 1.3.6.1.1.10.4.33 NAME 'uddiv3BindingKey' DESC 'UDDIv3 BindingTemplate unique identifier' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.33名称'uddiv3BindingKey'描述'UDDIv3 BindingTemplate唯一标识符'EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
This is the unique UDDIv3 identifier for a given instance of a uddiTModel.
这是uddiTModel的给定实例的唯一UDDIv3标识符。
A uddiTModel will include the uddiTModelKey (the v2 form) for unique identification by UDDIv2 clients. The uddiTModelKey (41-char) will also be the LDAP naming attribute for the uddiTModel entry. The uddiTModel entry MAY also include the uddiv3TModelKey, the explicit v3 form key, which can be 255 characters long.
uddiTModel将包括uddiTModelKey（v2表单），以便UDDIv2客户端进行唯一标识。uddiTModelKey（41个字符）也是uddiTModel条目的LDAP命名属性。uddiTModel条目还可以包括uddiv3TModelKey，即显式v3表单键，其长度可以是255个字符。
( 1.3.6.1.1.10.4.34 NAME 'uddiv3TModelKey' DESC 'UDDIv3 TModel unique identifier' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.34名称“uddiv3TModelKey”描述“UDDIv3 TModel唯一标识符”相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
The tModelKey is also used in a KeyedReference and in Address structures. In all instances where a tModelKey is used as a reference to tModel, the v3 form of the tModel key (viz. uddiv3TModelKey) will be the form used, since using the v2 form key will require translating it to the v3 key by the UDDI Server, which may invalidate the digital signature of the entity.
tModelKey还用于KeyedReference和地址结构中。在所有使用tModelKey作为tModel引用的情况下，tModel密钥的v3形式（即uddiv3TModelKey）将是使用的形式，因为使用v2形式密钥需要UDDI服务器将其转换为v3密钥，这可能会使实体的数字签名无效。
The UDDIv3 v3 schema supports the signing of the following UDDI elements using "XML-Signature Syntax and Processing" (see http://www.w3.org/TR/xmldsig-core/).
UDDIv3模式支持使用“XML签名语法和处理”对以下UDDI元素进行签名（请参阅http://www.w3.org/TR/xmldsig-core/).
..businessEntity ..businessService ..bindingTemplate ..tModel ..publisherAssertion
..businessEntity..businessService..bindingTemplate..tModel..publisherAssertion
This uddiv3DigitalSignature attribute holds the digital signature for the corresponding UDDI entity.
此uddiv3DigitalSignature属性保存相应UDDI实体的数字签名。
( 1.3.6.1.1.10.4.35 NAME 'uddiv3DigitalSignature' DESC 'UDDIv3 entity digital signature' EQUALITY caseExactMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.10.4.35名称'UDDIv3数字签名'DESC'UDDIv3实体数字签名'ExactMatch语法1.3.6.1.4.1.1466.115.121.1.15）
A Signature element SHOULD be generated according to the required steps of "Core Generation" in XML-Signature Syntax and Processing. The signature should be calculated on the top-level element that will be stored by the registry as a result of the Publication API call. This element, referred to as the data object in the XML-Signature and Syntax specification, is the businessEntity element for save_business API calls, the businessService element for save_service API calls, the bindingTemplate for save_binding API calls, the tModel for save_tModel API calls, and the publisherAssertion for set_publisherAssertions and add_publisherAssertion API calls.
应根据XML签名语法和处理中“核心生成”所需的步骤生成签名元素。签名应在顶级元素上计算，该元素将作为发布API调用的结果由注册表存储。此元素在XML签名和语法规范中称为数据对象，是用于save_业务API调用的businessEntity元素、用于save_服务API调用的businessService元素、用于save_绑定API调用的bindingTemplate、用于save_tModel API调用的tModel，以及用于set_publisherAssertions和add_publisherAssertion API调用的publisherAssertion。
The signature should be generated on the elements before they are added to the body of an API call. Also, according to the signature generation, all children of the element being signed are included in the generation of the signature unless first excluded by application of a transform. Due to the containment of service projections as businessService elements within a businessEntity element, this also means that changes to the projected service will render a signature of the businessEntity containing the projection invalid, unless a businessService element representing a service projection is excluded using a transform.
在将元素添加到API调用主体之前，应该在元素上生成签名。此外，根据签名生成，除非首先通过应用转换排除，否则被签名元素的所有子元素都包括在签名生成中。由于服务投影包含为businessEntity元素中的businessService元素，这也意味着对投影服务的更改将导致包含投影的businessEntity的签名无效，除非使用转换排除表示服务投影的businessService元素。
Due to the location of the sequence of Signature elements within an element that is to be signed, the signature is "enveloped". As a result of the enveloping of the signature, it is necessary to apply at least one transformation on the signed entity to exclude the signature or signature(s). The transformation selected by a publisher or the XML-Signature tool is specified in a Transform element inside the Signature element.
由于签名元素序列在待签名元素中的位置，签名被“封装”。作为签名封装的结果，有必要对签名实体应用至少一个转换以排除签名。发布者或XML签名工具选择的转换在签名元素内的Transform元素中指定。
This attribute contains the Node Identity for a UDDIv3 node.
此属性包含UDDIv3节点的节点标识。
( 1.3.6.1.1.10.4.36 NAME 'uddiv3NodeId' DESC 'UDDIv3 Node Identifier' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.36名称“uddiv3NodeId”描述“UDDIv3节点标识符”相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
This attribute is used to maintain the last modification time for a UDDI entity. It is needed in the context of maintaining the modifiedIncludingChildren element. When a child entity (e.g., uddiBindingTemplate) is updated, the parent entity (e.g., uddiBusinessService) LDAP timestamp also gets updated. The uddiv3EntityModificationTime attribute saves the last modification time of the parent entity (uddiBusinessService in this case).
此属性用于维护UDDI实体的上次修改时间。在维护modifiedIncludingChildren元素的上下文中需要它。更新子实体（例如uddiBindingTemplate）时，父实体（例如uddiBusinessService）LDAP时间戳也会更新。uddiv3EntityModificationTime属性保存父实体（本例中为uddiBusinessService）的上次修改时间。
( 1.3.6.1.1.10.4.37 NAME 'uddiv3EntityModificationTime' DESC 'UDDIv3 Last Modified Time for Entity' EQUALITY generalizedTimeMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 SINGLE-VALUE )
（1.3.6.1.1.10.4.37名称“uddiv3EntityModificationTime”DESC“UDDIv3实体的上次修改时间”相等通用时间匹配语法1.3.6.1.4.1.1466.115.121.1.24单值）
The following attribute definitions define attributes related to the modeling of UDDIv3 subscription-related entities in the LDAP directory.
以下属性定义定义了与LDAP目录中UDDIv3订阅相关实体的建模相关的属性。
Subscription provides clients, known as subscribers, with the ability to register their interest in receiving information concerning changes made in a UDDI registry. These changes can be scoped based on preferences provided with the request. The uddiv3Subscription object class is used to model registered UDDIv3 subscriptions.
订阅为称为订阅者的客户机提供了注册他们对接收有关UDDI注册中心中所做更改的信息感兴趣的能力。可以根据请求提供的首选项确定这些更改的范围。uddiv3Subscription对象类用于对已注册的UDDIv3订阅进行建模。
This is the unique UDDIv3 identifier for a given instance of a uddiv3Subscription entity.
这是UDDIv3订阅实体的给定实例的唯一UDDIv3标识符。
( 1.3.6.1.1.10.4.38 NAME 'uddiv3SubscriptionKey' DESC 'UDDIv3 Subscription unique identifier' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.38名称“uddiv3SubscriptionKey”描述“UDDIv3订阅唯一标识符”相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
This attribute contains the UDDIv3 Subscription Filter, specified as part of the save_subscription API, i.e., the Inquiry API specified as filtering criteria with a registered subscription. The filtering criteria limits the scope of a subscription to a subset of registry records. The get_xx and find_xx APIs are all valid choices for use as a subscriptionFilter. Only one of these can be chosen for each subscription.
此属性包含UDDIv3订阅筛选器，该筛选器指定为save_订阅API的一部分，即指定为具有已注册订阅的筛选条件的查询API。筛选条件将订阅的范围限制为注册表记录的子集。get_xx和find_xx API都是可用作subscriptionFilter的有效选项。每个订阅只能选择其中一个。
( 1.3.6.1.1.10.4.39 NAME 'uddiv3SubscriptionFilter' DESC 'UDDIv3 Subscription Filter' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.39名称'uddiv3SubscriptionFilter'说明'UDDIv3 SubscriptionFilter'相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
This attribute contains the Notification Interval string. It is of the type xsd:duration and specifies how often Asynchronous change notifications are to be provided to a subscriber.
此属性包含通知间隔字符串。它的类型为xsd:duration，并指定向订阅服务器提供异步更改通知的频率。
( 1.3.6.1.1.10.4.40 NAME 'uddiv3NotificationInterval' DESC 'UDDIv3 Notification Interval' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.40名称“UDDIv3通知间隔”描述“UDDIv3通知间隔”相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
This attribute contains the maximum number of entities to be returned as part of a subscription notification. It is an integer and specifies the maximum number of entities in a notification returned to a subscription listener.
此属性包含作为订阅通知的一部分返回的最大实体数。它是一个整数，指定返回给订阅侦听器的通知中的最大实体数。
( 1.3.6.1.1.10.4.41 NAME 'uddiv3MaxEntities' DESC 'UDDIv3 Subscription maxEntities field' EQUALITY integerMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE )
（1.3.6.1.1.10.4.41名称“uddiv3MaxEntities”描述“UDDIv3订阅maxEntities字段”相等整数匹配语法1.3.6.1.4.1.1466.115.121.1.27单值）
This attribute specifies the Expiry Time associated with a subscription. It is of the XML Schema type xsd:dateTime.
此属性指定与订阅关联的到期时间。它是XML模式类型xsd:dateTime。
( 1.3.6.1.1.10.4.42 NAME 'uddiv3ExpiresAfter' DESC 'UDDIv3 Subscription ExpiresAfter field' EQUALITY generalizedTimeMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 SINGLE-VALUE )
（1.3.6.1.1.10.4.42名称“uddiv3ExpiresAfter”DESC“UDDIv3订阅过期After字段”相等通用时间匹配语法1.3.6.1.4.1.1466.115.121.1.24单值）
This attribute is a Boolean flag for Brief Response associated with a subscription entity. It controls the level of detail returned to a subscription listener. The default is "false" when omitted. When set to "true", it indicates that the subscription results are to be returned to the subscriber in the form of a keyBag, listing all of the entities that matched the subscriptionFilter.
此属性是与订阅实体关联的简短响应的布尔标志。它控制返回给订阅侦听器的详细程度。省略时，默认值为“false”。当设置为“true”时，它表示订阅结果将以密钥包的形式返回给订阅方，列出与subscriptionFilter匹配的所有实体。
( 1.3.6.1.1.10.4.43 NAME 'uddiv3BriefResponse' DESC 'UDDIv3 Subscription ExpiresAfter field' EQUALITY booleanMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 SINGLE-VALUE )
（1.3.6.1.1.10.4.43名称“uddiv3BriefResponse”描述“UDDIv3订阅到期后字段”相等布尔匹配语法1.3.6.1.4.1.1466.115.121.1.7单值）
This is the unique UDDIv3 identifier for a given instance of a core UDDI data structure that is to be logged as an Obituary entry uddiv3EntityObituary. When a core UDDIv3 Entity is deleted and there is an active subscription registered against this UDDI Entity, an Obituary entry is created, in which the v3 key of the deleted entry is logged as part of the uddiv3EntityKey attribute.
这是要记录为讣告条目UDDIV3EntityObitual的核心UDDI数据结构的给定实例的唯一UDDIv3标识符。当删除一个核心UDDIv3实体并且存在针对该UDDI实体注册的活动订阅时，将创建一个讣告条目，其中已删除条目的v3密钥作为uddiv3EntityKey属性的一部分记录。
( 1.3.6.1.1.10.4.44 NAME 'uddiv3EntityKey' DESC 'UDDIv3 Entity unique identifier' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
（1.3.6.1.1.10.4.44名称'uddiv3EntityKey'描述'UDDIv3实体唯一标识符'EQUALITY caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15单值）
This attribute is used to log the original Creation Time for a UDDI Entity that is deleted in the uddiv3EntityObituary entry.
此属性用于记录在UDDIV3EntityObitual条目中删除的UDDI实体的原始创建时间。
It is also used in uddiBusinessService and uddiBindingTemplate. A Move BS operation needs to delete and recreate BT sub-tree due to lack of support for moving a sub-tree in many LDAPv3 servers. This attribute is used to save the original creation time of the BT during a Move BS.
它还用于uddiBusinessService和uddiBindingTemplate。移动BS操作需要删除并重新创建BT子树，因为在许多LDAPv3服务器中不支持移动子树。此属性用于在移动BS期间保存BT的原始创建时间。
( 1.3.6.1.1.10.4.45 NAME 'uddiv3EntityCreationTime' DESC 'UDDIv3 Entity Creation Time' EQUALITY generalizedTimeMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 SINGLE-VALUE )
（1.3.6.1.1.10.4.45名称'uddiv3EntityCreationTime'描述'UDDIv3实体创建时间'EQUALITY GeneratedTimeMatch语法1.3.6.1.4.1.1466.115.121.1.24单值）
This attribute is used to log the entity deletion time for a UDDI Entity that is deleted in the uddiv3EntityObituary entry.
此属性用于记录在UDDIV3EntityObitual条目中删除的UDDI实体的实体删除时间。
( 1.3.6.1.1.10.4.46 NAME 'uddiv3EntityDeletionTime' DESC 'UDDIv3 Entity Deletion Time' EQUALITY generalizedTimeMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 SINGLE-VALUE )
（1.3.6.1.1.10.4.46名称'UDDIv3实体删除时间'DESC'UDDIv3实体删除时间'EQUALITY GeneratedTimeMatch语法1.3.6.1.4.1.1466.115.121.1.24单值）
The OIDs for the object classes in this document have been registered by the IANA.
本文档中对象类的OID已由IANA注册。
This structural object class represents a businessEntity.
此结构对象类表示businessEntity。
( 1.3.6.1.1.10.6.1 NAME 'uddiBusinessEntity' SUP top STRUCTURAL MUST ( uddiBusinessKey $ uddiName) MAY ( uddiAuthorizedName $ uddiOperator $ uddiDiscoveryURLs $ uddiDescription $ uddiIdentifierBag $ uddiCategoryBag $ uddiv3BusinessKey $ uddiv3DigitalSignature $ uddiv3EntityModificationTime $ uddiv3NodeId) )
（1.3.6.1.1.10.6.1名称“uddiBusinessEntity”SUP top STRUCTURAL MUST（uddiBusinessKey$uddiName）MAY（uddiAuthorizedName$uddiOperator$uddiDiscoveryURLs$uddiDescription$uddiIdentifierBag$uddiCategoryBag$uddiv3BusinessKey$UDDIV3数字签名$uddiv3EntityModificationTime$uddiv3NodeId））
This structural object class represents a contact. It is contained by a uddiBusinessEntity.
此结构对象类表示接触。它由uddiBusinessEntity包含。
( 1.3.6.1.1.10.6.2 NAME 'uddiContact' SUP top STRUCTURAL MUST ( uddiPersonName $ uddiUUID ) MAY ( uddiUseType $ uddiDescription $ uddiPhone $ uddiEMail ) )
（1.3.6.1.1.10.6.2名称“uddiContact”SUP top STRUCTURAL MUST（uddiPersonName$uddiUUID）MAY（uddiUseType$uddiDescription$uddiPhone$uddiEMail））
This structural object class represents an address. It is contained by a uddiContact.
此结构对象类表示一个地址。它包含在UDDI联系人中。
( 1.3.6.1.1.10.6.3 NAME 'uddiAddress' SUP top STRUCTURAL MUST ( uddiUUID ) MAY ( uddiUseType $ uddiSortCode $ uddiTModelKey $ uddiv3TmodelKey $ uddiAddressLine $ uddiLang) )
（1.3.6.1.1.10.6.3名称“uddiAddress”SUP top STRUCTURAL MUST（uddiUUID）MAY（uddiUseType$uddiSortCode$uddiTModelKey$uddiv3TmodelKey$uddiAddressLine$uddiLang））
This structural object class represents a businessService.
此结构对象类表示businessService。
( 1.3.6.1.1.10.6.4 NAME 'uddiBusinessService' SUP top STRUCTURAL MUST ( uddiServiceKey ) MAY ( uddiName $ uddiBusinessKey $ uddiDescription $ uddiCategoryBag $ uddiIsProjection $ uddiv3ServiceKey $ uddiv3BusinessKey $ uddiv3DigitalSignature $ uddiv3EntityCreationTime $ uddiv3EntityModificationTime $ uddiv3NodeId) )
（1.3.6.1.1.10.6.4名称“uddiBusinessService”Supp top STRUCTURAL MUST（uddiServiceKey）可以（uddiName$uddiBusinessKey$uddiDescription$uddiCategoryBag$uddiIsProjection$uddiv3ServiceKey$uddiv3BusinessKey$uddiv3DigitalSignature$uddiv3EntityCreationTime$uddiv3EntityModificationTime$uddiv3NodeId））
This structural object class represents a bindingTemplate.
此结构对象类表示bindingTemplate。
( 1.3.6.1.1.10.6.5 NAME 'uddiBindingTemplate' SUP top STRUCTURAL MUST ( uddiBindingKey ) MAY ( uddiServiceKey $ uddiDescription $ uddiAccessPoint $ uddiHostingRedirector uddiCategoryBag $ uddiv3BindingKey $ uddiv3ServiceKey $ uddiv3DigitalSignature $ uddiv3EntityCreationTime $ uddiv3NodeId) )
（1.3.6.1.1.10.6.5名称“uddiBindingTemplate”支持顶级结构必须（uddiBindingKey）可以（uddiServiceKey$uddiDescription$uddiAccessPoint$uddiHostingRedirector uddiCategoryBag$uddiv3BindingKey$uddiv3ServiceKey$uddiv3DigitalSignature$uddiv3EntityCreationTime$uddiv3NodeId））
This structural object class represents a tModelInstanceInfo. It is contained by a uddiBindingTemplate.
此结构对象类表示tModelInstanceInfo。它包含在uddiBindingTemplate中。
( 1.3.6.1.1.10.6.6 NAME 'uddiTModelInstanceInfo' SUP top STRUCTURAL MUST ( uddiTModelKey ) MAY ( uddiDescription $ uddiInstanceDescription $ uddiInstanceParms $ uddiOverviewDescription $ uddiOverviewURL $ uddiv3TmodelKey) )
（1.3.6.1.1.10.6.6名称“uddiTModelInstanceInfo”支持顶级结构必须（uddiTModelKey）可以（uddiDescription$uddiInstanceDescription$UDDIInstancePartners$uddiOverviewDescription$uddiOverviewURL$uddiv3TmodelKey））
This structural object class represents a tModel.
此结构对象类表示一个tModel。
( 1.3.6.1.1.10.6.7 NAME 'uddiTModel' SUP top STRUCTURAL MUST ( uddiTModelKey $ uddiName ) MAY ( uddiAuthorizedName $ uddiOperator $ uddiDescription $ uddiOverviewDescription $ uddiOverviewURL $ uddiIdentifierBag $ uddiCategoryBag $ uddiIsHidden uddiv3TModelKey $ uddiv3DigitalSignature $ uddiv3NodeId) )
（1.3.6.1.1.10.6.7名称“uddiTModel”SUP top STRUCTURAL MUST（uddiTModelKey$uddiName）可以（uddiAuthorizedName$uddiOperator$uddiDescription$uddiOverviewDescription$uddiOverviewURL$uddiIdentifierBag$uddiCategoryBag$uddiIsHidden uddiv3TModelKey$uddiv3DigitalSignature$uddiv3NodeId））
This structural object class represents a publisherAssertion.
此结构对象类表示publisherAssertion。
( 1.3.6.1.1.10.6.8 NAME 'uddiPublisherAssertion' SUP top STRUCTURAL MUST ( uddiFromKey $ uddiToKey $ uddiKeyedReference $ uddiUUID ) MAY ( uddiv3DigitalSignature $ uddiv3NodeId) )
（1.3.6.1.1.10.6.8名称“uddiPublisherAssertion”支持顶级结构必须（uddiFromKey$uddiToKey$uddiKeyedReference$uddiUUID）可以（uddiv3DigitalSignature$uddiv3NodeId））
The following are object class definitions to model new data structures needed to implement the UDDIv3 information model. These object class definitions have the "uddiv3" prefix to indicate that these attributes represent UDDI information model elements unique to UDDIv3.
实现UDDIv3对象模型需要以下数据定义信息。这些对象类定义具有“uddiv3”前缀，表示这些属性表示uddiv3特有的UDDI信息模型元素。
This structural object class represents a Subscription entity.
此结构对象类表示订阅实体。
( 1.3.6.1.1.10.6.9 NAME 'uddiv3Subscription' SUP top STRUCTURAL MUST ( uddiv3SubscriptionFilter $ uddiUUID) MAY ( uddiAuthorizedName $ uddiv3SubscriptionKey $ uddiv3BindingKey $ uddiv3NotificationInterval $ uddiv3MaxEntities $ uddiv3ExpiresAfter $ uddiv3BriefResponse $ uddiv3NodeId) )
（1.3.6.1.1.10.6.9名称“uddiv3Subscription”SUP top STRUCTURAL MUST（uddiv3SubscriptionFilter$uddiUUID）可以（uddiAuthorizedName$uddiv3SubscriptionKey$uddiv3BindingKey$uddiv3NotificationInterval$uddiv3MaxEntities$uddiv3ExpiresAfter$uddiv3BriefResponse$uddiv3NodeId））
This structural object class represents an Obituary entry for and stores obituary information for deleted UDDIv3 entities needed for handling subscriptions.
此结构对象类表示讣告条目，并存储处理订阅所需的已删除UDDIv3实体的讣告信息。
( 1.3.6.1.1.10.6.10 NAME 'uddiv3EntityObituary' SUP top STRUCTURAL MUST ( uddiv3EntityKey $ uddiUUID) MAY ( uddiAuthorizedName $ uddiv3EntityCreationTime $ uddiv3EntityDeletionTime $ uddiv3NodeId) )
（1.3.6.1.1.10.6.10名称“UDDIV3EntityObitual”支持顶级结构必须（uddiv3EntityKey$uddiUUID）可以（uddiAuthorizedName$uddiv3EntityCreationTime$uddiv3EntityDeletionTime$uddiv3NodeId））
This section defines the required hierarchical structure rules and naming attributes for the object classes defined in Section 6.
本节定义了第6节中定义的对象类所需的层次结构规则和命名属性。
The OIDs for the structure rules in this document have been registered by the IANA.
本文件中结构规则的OID已由IANA注册。
This name form defines the naming attribute for a businessEntity.
此名称表单定义businessEntity的命名属性。
( 1.3.6.1.1.10.15.1 NAME 'uddiBusinessEntityNameForm' OC uddiBusinessEntity MUST ( uddiBusinessKey ) )
（1.3.6.1.1.10.15.1名称“uddiBusinessEntityNameForm”OC uddiBusinessEntity必须（uddiBusinessKey））
This name form defines the naming attribute for a contact.
此名称表单定义联系人的命名属性。
( 1.3.6.1.1.10.15.2 NAME 'uddiContactNameForm' OC uddiContact MUST ( uddiUUID ) )
（1.3.6.1.1.10.15.2名称“uddiContactNameForm”OC uddiContact必须（uddiUUID））
This name form defines the naming attribute for an address.
此名称表单定义地址的命名属性。
( 1.3.6.1.1.10.15.3 NAME 'uddiAddressNameForm' OC uddiAddress MUST ( uddiUUID ) )
（1.3.6.1.1.10.15.3名称“uddiAddressNameForm”OC uddiAddress必须（uddiUUID））
This name form defines the naming attribute for a businessService.
此名称表单定义businessService的命名属性。
( 1.3.6.1.1.10.15.4 NAME 'uddiBusinessServiceNameForm' OC uddiBusinessService MUST ( uddiServiceKey ) )
（1.3.6.1.1.10.15.4名称“uddiBusinessServiceNameForm”OC uddiBusinessService必须（uddiServiceKey））
This name form defines the naming attribute for a bindingTemplate.
此名称表单定义bindingTemplate的命名属性。
( 1.3.6.1.1.10.15.5 NAME 'uddiBindingTemplateNameForm' OC uddiBindingTemplate MUST ( uddiBindingKey ) )
（1.3.6.1.1.10.15.5名称“uddiBindingTemplateNameForm”OC uddiBindingTemplate必须（uddiBindingKey））
This name form defines the naming attribute for a tModelInstanceInfo.
此名称表单定义了tModelInstanceInfo的命名属性。
( 1.3.6.1.1.10.15.6 NAME 'uddiTModelInstanceInfoNameForm' OC uddiTModelInstanceInfo MUST ( uddiTModelKey ) )
（1.3.6.1.1.10.15.6名称“uddiTModelInstanceInfo表单”OC uddiTModelInstanceInfo必须（uddiTModelKey））
This name form defines the naming attribute for a tModel.
此名称表单定义tModel的命名属性。
( 1.3.6.1.1.10.15.7 NAME 'uddiTModelNameForm' OC uddiTModel MUST ( uddiTModelKey ) )
（1.3.6.1.1.10.15.7名称“uddiTModelNameForm”OC uddiTModel必须（uddiTModelKey））
This name form defines the naming attribute for a publisherAssertion.
此名称表单定义PublisherSerition的命名属性。
( 1.3.6.1.1.10.15.8 NAME 'uddiPublisherAssertionNameForm' OC uddiPublisherAssertion MUST ( uddiUUID ) )
（1.3.6.1.1.10.15.8名称“UDDIPublisherSertionNameForm”OC UDDIPublisherSertion必须（uddiUUID））
This name form defines the naming attribute for a Subscription.
此名称表单定义订阅的命名属性。
( 1.3.6.1.1.10.15.9 NAME 'uddiv3SubscriptionNameForm' OC uddiv3Subscription MUST ( uddiUUID ) )
（1.3.6.1.1.10.15.9名称“UDDIV3订阅名称表单”OC UDDIV3订阅必须（uddiUUID））
This name form defines the naming attribute for an Entity Obituary.
此名称表单定义实体讣告的命名属性。
( 1.3.6.1.1.10.15.10 NAME 'uddiv3EntityObituaryNameForm' OC uddiv3EntityObituary MUST ( uddiUUID ) )
（1.3.6.1.1.10.15.10名称“UDDIV3EntityObitualNameForm”OC UDDIV3EntityObitual必须（uddiUUID））
This section defines the required hierarchical structure rules for the object classes defined in Section 6.
本节为第6节中定义的对象类定义了所需的层次结构规则。
Note that rule identifiers defined here show the relationship between structure rules. Implementations may use different identifiers but must follow the same hierarchical model.
请注意，此处定义的规则标识符显示了结构规则之间的关系。实现可以使用不同的标识符，但必须遵循相同的层次模型。
( 1 NAME 'uddiBusinessEntityStructureRule' FORM uddiBusinessEntityNameForm )
（1名称“uddiBusinessEntityStructureRule”表格uddiBusinessEntityNameForm）
This structure rule defines the object class containment for a contact.
此结构规则定义联系人的对象类包含。
( 2 NAME 'uddiContactStructureRule' FORM uddiContactNameForm SUP ( 1 ) )
（2名称“uddiContactStructureRule”表格UDDIContactName表格SUP（1））
This structure rule defines the object class containment for an address.
此结构规则定义地址的对象类包含。
( 3 NAME 'uddiAddressStructureRule' FORM uddiAddressNameForm SUP ( 2 ) )
（3名称“uddiAddressStructureRule”表格UDDIAddressName表格SUP（2））
This structure rule defines the object class containment for a businessService.
此结构规则定义businessService的对象类包含。
( 4 NAME 'uddiBusinessServiceStructureRule' FORM uddiBusinessServiceNameForm SUP ( 1 ) )
（4名称“uddiBusinessServiceStructureRule”表格UDDIBusinessServiceName表格SUP（1））
This structure rule defines the object class containment for a bindingTemplate.
此结构规则定义bindingTemplate的对象类包含。
( 5 NAME 'uddiBindingTemplateStructureRule' FORM uddiBindingTemplateNameForm SUP ( 4 ) )
（5名称“uddiBindingTemplateStructureRule”表格uddiBindingTemplateNameForm SUP（4））
This structure rule defines the object class containment for a tModelInstanceInfo.
此结构规则定义了tModelInstanceInfo的对象类包含。
( 6 NAME 'uddiTModelInstanceInfoStructureRule' FORM uddiTModelInstanceInfoNameForm SUP ( 5 ) )
（6名称“UDDITModelinstanceInfo结构规则”表格UDDITModelinstanceInfo表格SUP（5））
( 7 NAME 'uddiTModelStructureRule' FORM uddiTModelNameForm )
（7名称“uddiTModelStructureRule”表格uddiTModelNameForm）
( 8 NAME 'uddiPublisherAssertionStructureRule' FORM uddiPublisherAssertionNameForm )
（8名称“UDDIPublishersCertionStructureRule”表格UDDIPublishersCertionNameForm）
( 9 NAME 'uddiv3SubscriptionStructureRule' FORM uddiv3SubscriptionNameForm )
（9名称“uddiv3SubscriptionStructureRule”表格uddiv3SubscriptionNameForm）
( 10 NAME 'uddiv3EntityObituaryStructureRule' FORM uddiv3EntityObituaryNameForm )
（10名称“UDDIV3EntityObitualStructureRule”表格UDDIV3EntityObitualNameForm）
Storing UDDI data into the directory enables the data to be examined and used outside the environment in which it was originally created. The directory entry containing the UDDI data could be read and modified within the constraints imposed by the access control mechanisms of the directory. With UDDIv3 [UDDIv3], publishers can digitally sign UDDI Entities enabling registry clients to validate the integrity of entries read from the UDDIv3 registry by verifying the digital signature.
将UDDI数据存储到目录中可以在最初创建数据的环境之外检查和使用数据。包含UDDI数据的目录条目可以在目录的访问控制机制施加的约束范围内读取和修改。使用UDDIv3[UDDIv3]，发布者可以对UDDI实体进行数字签名，使注册中心客户端能够通过验证数字签名来验证从UDDIv3注册中心读取的条目的完整性。
Each UDDI Entity has a uddiAuthorizedName attribute that contains an LDAP DN identifying the publisher/owner. The referenced LDAP object can provide the public key of the signer to a registry client for integrity validation of the UDDI Entity.
每个UDDI实体都有一个uddiAuthorizedName属性，该属性包含标识发布者/所有者的LDAP DN。被引用的LDAP对象可以向注册中心客户机提供签名者的公钥，以便对UDDI实体进行完整性验证。
Other general LDAP [LDAPv3] security considerations apply. Some of the UDDI attributes such as AccessPoints for services may contain sensitive information. Use of strong authentication mechanisms and data integrity/confidentiality services [RFC2829][RFC2830] is advised.
其他一般LDAP[LDAPv3]安全注意事项也适用。一些UDDI属性（如服务的访问点）可能包含敏感信息。建议使用强身份验证机制和数据完整性/机密性服务[RFC2829][RFC2830]。
Refer to RFC 3383, "Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)" [RFC3383].
请参阅RFC 3383，“轻量级目录访问协议（LDAP）的Internet分配号码管理局（IANA）注意事项”[RFC3383]。
The IANA has registered an LDAP Object Identifier for use in this technical specification, according to the following template:
IANA已根据以下模板注册了LDAP对象标识符，以用于本技术规范：
Subject: Request for LDAP OID Registration Person & email address to contact for further information: Bruce Bergeson (bruce.bergeson@novell.com) Specification: RFC 4403 Author/Change Controller: IESG Comments: The assigned OID (10) will be used as a base for identifying a number of UDDI schema elements defined in this document.
主题：请求LDAP OID注册人员和电子邮件地址，以获取更多信息：Bruce Bergeson（Bruce。bergeson@novell.com)规范：RFC 4403作者/变更控制者：IESG注释：分配的OID（10）将用作标识本文档中定义的大量UDDI模式元素的基础。
The IANA has registered the LDAP Descriptors used in this technical specification as detailed in the following template:
IANA已注册了本技术规范中使用的LDAP描述符，详情见以下模板：
Subject: Request for LDAP Descriptor Registration Update Descriptor (short name): see table Object Identifier: see table Person & email address to contact for further information: Bruce Bergeson (bruce.bergeson@novell.com) Usage: see table Specification: RFC 4403 Author/Change Controller: IESG Table:
主题：请求LDAP描述符注册更新描述符（简称）：请参阅表对象标识符：请参阅表联系人和电子邮件地址以获取更多信息：Bruce Bergeson（Bruce）。bergeson@novell.com)用法：见表格规范：RFC 4403作者/变更控制器：IESG表格：
The following descriptors have been added:
已添加以下描述符：
NAME Type OID
-------------- ---- ------------
uddiBusinessKey A 1.3.6.1.1.10.4.1
uddiAuthorizedName A 1.3.6.1.1.10.4.2
uddiOperator A 1.3.6.1.1.10.4.3
uddiName A 1.3.6.1.1.10.4.4
uddiDescription A 1.3.6.1.1.10.4.5
uddiDiscoveryURLs A 1.3.6.1.1.10.4.6
uddiUseType A 1.3.6.1.1.10.4.7
uddiPersonName A 1.3.6.1.1.10.4.8
uddiPhone A 1.3.6.1.1.10.4.9
uddiEMail A 1.3.6.1.1.10.4.10
uddiSortCode A 1.3.6.1.1.10.4.11
uddiTModelKey A 1.3.6.1.1.10.4.12
uddiAddressLine A 1.3.6.1.1.10.4.13
NAME Type OID
-------------- ---- ------------
uddiBusinessKey A 1.3.6.1.1.10.4.1
uddiAuthorizedName A 1.3.6.1.1.10.4.2
uddiOperator A 1.3.6.1.1.10.4.3
uddiName A 1.3.6.1.1.10.4.4
uddiDescription A 1.3.6.1.1.10.4.5
uddiDiscoveryURLs A 1.3.6.1.1.10.4.6
uddiUseType A 1.3.6.1.1.10.4.7
uddiPersonName A 1.3.6.1.1.10.4.8
uddiPhone A 1.3.6.1.1.10.4.9
uddiEMail A 1.3.6.1.1.10.4.10
uddiSortCode A 1.3.6.1.1.10.4.11
uddiTModelKey A 1.3.6.1.1.10.4.12
uddiAddressLine A 1.3.6.1.1.10.4.13
NAME Type OID
-------------- ---- ------------
uddiIdentifierBag A 1.3.6.1.1.10.4.14
uddiCategoryBag A 1.3.6.1.1.10.4.15
uddiKeyedReference A 1.3.6.1.1.10.4.16
uddiServiceKey A 1.3.6.1.1.10.4.17
uddiBindingKey A 1.3.6.1.1.10.4.18
uddiAccessPoint A 1.3.6.1.1.10.4.19
uddiHostingRedirector A 1.3.6.1.1.10.4.20
uddiInstanceDescription A 1.3.6.1.1.10.4.21
uddiInstanceParms A 1.3.6.1.1.10.4.22
uddiOverviewDescription A 1.3.6.1.1.10.4.23
uddiOverviewURL A 1.3.6.1.1.10.4.24
uddiFromKey A 1.3.6.1.1.10.4.25
uddiToKey A 1.3.6.1.1.10.4.26
uddiUUID A 1.3.6.1.1.10.4.27
uddiIsHidden A 1.3.6.1.1.10.4.28
uddiIsProjection A 1.3.6.1.1.10.4.29
uddiLang A 1.3.6.1.1.10.4.30
uddiv3BusinessKey A 1.3.6.1.1.10.4.31
uddiv3ServiceKey A 1.3.6.1.1.10.4.32
uddiv3BindingKey A 1.3.6.1.1.10.4.33
uddiv3TmodelKey A 1.3.6.1.1.10.4.34
uddiv3DigitalSignature A 1.3.6.1.1.10.4.35
uddiv3NodeId A 1.3.6.1.1.10.4.36
uddiv3EntityModificationTime A 1.3.6.1.1.10.4.37
uddiv3SubscriptionKey A 1.3.6.1.1.10.4.38
uddiv3SubscriptionFilter A 1.3.6.1.1.10.4.39
uddiv3NotificationInterval A 1.3.6.1.1.10.4.40
uddiv3MaxEntities A 1.3.6.1.1.10.4.41
uddiv3ExpiresAfter A 1.3.6.1.1.10.4.42
uddiv3BriefResponse A 1.3.6.1.1.10.4.43
uddiv3EntityKey A 1.3.6.1.1.10.4.44
uddiv3EntityCreationTime A 1.3.6.1.1.10.4.45
uddiv3EntityDeletionTime A 1.3.6.1.1.10.4.46
uddiBusinessEntity O 1.3.6.1.1.10.6.1
uddiContact O 1.3.6.1.1.10.6.2
uddiAddress O 1.3.6.1.1.10.6.3
uddiBusinessService O 1.3.6.1.1.10.6.4
uddiBindingTemplate O 1.3.6.1.1.10.6.5
uddiTModelInstanceInfo O 1.3.6.1.1.10.6.6
uddiTModel O 1.3.6.1.1.10.6.7
uddiPublisherAssertion O 1.3.6.1.1.10.6.8
uddiv3Subscription O 1.3.6.1.1.10.6.9
uddiv3EntityObituary O 1.3.6.1.1.10.6.10
uddiBusinessEntityNameForm N 1.3.6.1.1.10.15.1
uddiContactNameForm N 1.3.6.1.1.10.15.2
uddiAddressNameForm N 1.3.6.1.1.10.15.3
NAME Type OID
-------------- ---- ------------
uddiIdentifierBag A 1.3.6.1.1.10.4.14
uddiCategoryBag A 1.3.6.1.1.10.4.15
uddiKeyedReference A 1.3.6.1.1.10.4.16
uddiServiceKey A 1.3.6.1.1.10.4.17
uddiBindingKey A 1.3.6.1.1.10.4.18
uddiAccessPoint A 1.3.6.1.1.10.4.19
uddiHostingRedirector A 1.3.6.1.1.10.4.20
uddiInstanceDescription A 1.3.6.1.1.10.4.21
uddiInstanceParms A 1.3.6.1.1.10.4.22
uddiOverviewDescription A 1.3.6.1.1.10.4.23
uddiOverviewURL A 1.3.6.1.1.10.4.24
uddiFromKey A 1.3.6.1.1.10.4.25
uddiToKey A 1.3.6.1.1.10.4.26
uddiUUID A 1.3.6.1.1.10.4.27
uddiIsHidden A 1.3.6.1.1.10.4.28
uddiIsProjection A 1.3.6.1.1.10.4.29
uddiLang A 1.3.6.1.1.10.4.30
uddiv3BusinessKey A 1.3.6.1.1.10.4.31
uddiv3ServiceKey A 1.3.6.1.1.10.4.32
uddiv3BindingKey A 1.3.6.1.1.10.4.33
uddiv3TmodelKey A 1.3.6.1.1.10.4.34
uddiv3DigitalSignature A 1.3.6.1.1.10.4.35
uddiv3NodeId A 1.3.6.1.1.10.4.36
uddiv3EntityModificationTime A 1.3.6.1.1.10.4.37
uddiv3SubscriptionKey A 1.3.6.1.1.10.4.38
uddiv3SubscriptionFilter A 1.3.6.1.1.10.4.39
uddiv3NotificationInterval A 1.3.6.1.1.10.4.40
uddiv3MaxEntities A 1.3.6.1.1.10.4.41
uddiv3ExpiresAfter A 1.3.6.1.1.10.4.42
uddiv3BriefResponse A 1.3.6.1.1.10.4.43
uddiv3EntityKey A 1.3.6.1.1.10.4.44
uddiv3EntityCreationTime A 1.3.6.1.1.10.4.45
uddiv3EntityDeletionTime A 1.3.6.1.1.10.4.46
uddiBusinessEntity O 1.3.6.1.1.10.6.1
uddiContact O 1.3.6.1.1.10.6.2
uddiAddress O 1.3.6.1.1.10.6.3
uddiBusinessService O 1.3.6.1.1.10.6.4
uddiBindingTemplate O 1.3.6.1.1.10.6.5
uddiTModelInstanceInfo O 1.3.6.1.1.10.6.6
uddiTModel O 1.3.6.1.1.10.6.7
uddiPublisherAssertion O 1.3.6.1.1.10.6.8
uddiv3Subscription O 1.3.6.1.1.10.6.9
uddiv3EntityObituary O 1.3.6.1.1.10.6.10
uddiBusinessEntityNameForm N 1.3.6.1.1.10.15.1
uddiContactNameForm N 1.3.6.1.1.10.15.2
uddiAddressNameForm N 1.3.6.1.1.10.15.3
NAME Type OID
-------------- ---- ------------
uddiBusinessServiceNameForm N 1.3.6.1.1.10.15.4
uddiBindingTemplateNameForm N 1.3.6.1.1.10.15.5
uddiTModelInstanceInfoNameForm N 1.3.6.1.1.10.15.6
uddiTModelNameForm N 1.3.6.1.1.10.15.7
uddiPublisherAssertionNameForm N 1.3.6.1.1.10.15.8
uddiv3SubscriptionNameForm N 1.3.6.1.1.10.15.9
uddiv3EntityObituaryNameForm N 1.3.6.1.1.10.15.10
NAME Type OID
-------------- ---- ------------
uddiBusinessServiceNameForm N 1.3.6.1.1.10.15.4
uddiBindingTemplateNameForm N 1.3.6.1.1.10.15.5
uddiTModelInstanceInfoNameForm N 1.3.6.1.1.10.15.6
uddiTModelNameForm N 1.3.6.1.1.10.15.7
uddiPublisherAssertionNameForm N 1.3.6.1.1.10.15.8
uddiv3SubscriptionNameForm N 1.3.6.1.1.10.15.9
uddiv3EntityObituaryNameForm N 1.3.6.1.1.10.15.10
where Type A is Attribute, Type O is ObjectClass, Type N is NameForm
其中类型A是属性，类型O是对象类，类型N是NameForm
These assignments have been recorded in the following registry:
这些分配已记录在以下注册表中：
http://www.iana.org/assignments/ldap-parameters
http://www.iana.org/assignments/ldap-parameters
[LDAPv3] Hodges, J. and R. Morgan, "Lightweight Directory Access Protocol (v3): Technical Specification", RFC 3377, September 2002.
[LDAPv3]Hodges，J.和R.Morgan，“轻量级目录访问协议（v3）：技术规范”，RFC3372002年9月。
[RFC2252] Wahl, M., Coulbeck, A., Howes, T., and S. Kille, "Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions", RFC 2252, December 1997.
[RFC2252]Wahl，M.，Coulbeck，A.，Howes，T.，和S.Kille，“轻量级目录访问协议（v3）：属性语法定义”，RFC2252，1997年12月。
[UDDIdsr] UDDI.ORG, "UDDI version 2.03 Data Structure Reference,"
http://uddi.org/pubs/DataStructure-V2.03-Published-
20020719.htm
[UDDIdsr] UDDI.ORG, "UDDI version 2.03 Data Structure Reference,"
http://uddi.org/pubs/DataStructure-V2.03-Published-
20020719.htm
[UDDIapi] "UDDI Version 2.04 API Specification",
http://uddi.org/pubs/ProgrammersAPI-V2.04-Published-
20020719.htm
[UDDIapi] "UDDI Version 2.04 API Specification",
http://uddi.org/pubs/ProgrammersAPI-V2.04-Published-
20020719.htm
[UDDIv3] UDDI Version 3.0, Published Specification, 19 July 2002
http://uddi.org/pubs/uddi-v3.00-published-20020719.htm
[UDDIv3] UDDI Version 3.0, Published Specification, 19 July 2002
http://uddi.org/pubs/uddi-v3.00-published-20020719.htm
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2829] Wahl, M., Alvestrand, H., Hodges, J., and R. Morgan, "Authentication Methods for LDAP", RFC 2829, May 2000.
[RFC2829]Wahl，M.，Alvestrand，H.，Hodges，J.，和R.Morgan，“LDAP的身份验证方法”，RFC 28292000年5月。
[RFC2830] Hodges, J., Morgan, R., and M. Wahl, "Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security", RFC 2830, May 2000.
[RFC2830]Hodges，J.，Morgan，R.，和M.Wahl，“轻量级目录访问协议（v3）：传输层安全扩展”，RFC 2830，2000年5月。
[RFC3383] Zeilenga, K., "Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)", BCP 64, RFC 3383, September 2002.
[RFC3383]Zeilenga，K.，“轻量级目录访问协议（LDAP）的互联网分配号码管理局（IANA）注意事项”，BCP 64，RFC 3383，2002年9月。
[XML] Extensible Markup Language (XML) 1.0 (Second Edition) W3C
Recommendation 6 October 2000 http://www.w3.org/TR/REC-xml
[XML] Extensible Markup Language (XML) 1.0 (Second Edition) W3C
Recommendation 6 October 2000 http://www.w3.org/TR/REC-xml
[URL] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
[URL]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，2005年1月。
[HTTP] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[HTTP]菲尔丁，R.，盖蒂斯，J.，莫卧儿，J.，弗莱斯蒂克，H.，马斯特，L.，利奇，P.，和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC2616，1999年6月。
Authors' Addresses
作者地址
Bruce Bergeson Novell, Inc. 1800 S Novell Place Provo, UT 84606
Bruce Bergeson Novell，Inc.美国犹他州普罗沃诺维尔广场南1800号，邮编84606
Phone: +1 801 861 3854
EMail: bruce.bergeson@novell.com
Phone: +1 801 861 3854
EMail: bruce.bergeson@novell.com
Kent Boogert Novell, Inc. 1800 S Novell Place Provo, UT 84606
肯特·布格特·诺维尔公司，地址：美国犹他州普罗沃诺维尔广场南1800号，邮编：84606
Phone: +1 801 861 3212
EMail: kent.boogert@novell.com
Phone: +1 801 861 3212
EMail: kent.boogert@novell.com
Vijay Nanjundaswamy Oracle India Pvt. Ltd. Lexington Towers, Prestige St. John's Woods #18, 2nd Cross Road, Chikka Audugodi, Bangalore 560029 India
Vijay Nanjundaswamy甲骨文印度私人有限公司，印度班加罗尔Chikka Audugodi第二十字路口Prestige St.John’s Woods 18号列克星敦大厦，邮编560029
Phone: +11 9180 4108 5000
EMail: vijay.nanjundaswamy@oracle.com
Phone: +11 9180 4108 5000
EMail: vijay.nanjundaswamy@oracle.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。