idnits 2.17.1 draft-bergeson-uddi-ldap-schema-06.txt: -(333): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(775): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(865): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(920): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1536): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1.a on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2086. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2063. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2070. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2076. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 10 instances of lines with non-ascii characters in the document. == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 2698 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 11 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 286 has weird spacing: '...tion of impli...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC2251' is defined on line 1960, but no explicit reference was found in the text == Unused Reference: 'UDDIapi' is defined on line 1972, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3377 (ref. 'LDAPv3') (Obsoleted by RFC 4510) ** Obsolete normative reference: RFC 2251 (Obsoleted by RFC 4510, RFC 4511, RFC 4512, RFC 4513) ** Obsolete normative reference: RFC 2252 (Obsoleted by RFC 4510, RFC 4512, RFC 4517, RFC 4523) ** Obsolete normative reference: RFC 2253 (ref. 'RFC2119') (Obsoleted by RFC 4510, RFC 4514) ** Obsolete normative reference: RFC 2829 (Obsoleted by RFC 4510, RFC 4513) ** Obsolete normative reference: RFC 2830 (Obsoleted by RFC 4510, RFC 4511, RFC 4513) ** Obsolete normative reference: RFC 3383 (Obsoleted by RFC 4520) ** Obsolete normative reference: RFC 2616 (ref. 'HTTP') (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) Summary: 14 errors (**), 0 flaws (~~), 7 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Individual Submission B. Bergeson 3 K. Boogert 4 Vijay K.Nanjundaswamy 5 Internet Draft Novell, Inc. 6 Document: draft-bergeson-uddi-ldap-schema-06.txt February, 2005 7 Intended Category: Informational Expires August, 2005 9 LDAP Schema for UDDIv3 11 Status of this Memo 13 This document is an Internet-Draft and is subject to all provisions 14 of section 3 of RFC 3667. By submitting this Internet-Draft, each 15 author represents that any applicable patent or other IPR claims of 16 which he or she is aware have been or will be disclosed, and any of 17 which he or she become aware will be disclosed, in accordance with 18 RFC 3668. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six 26 months and may be updated, replaced, or obsoleted by other documents 27 at any time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on February 25, 2005. 38 Copyright Notice 40 Copyright (C) The Internet Society (2004). 42 Abstract 44 This document defines the Lightweight Directory Access Protocol 45 (LDAPv3) schema for representing Universal Description, Discovery & 46 Integration (UDDI) data types in an LDAP directory. It defines the 47 LDAP object class & attribute definitions and containment rules to 48 model UDDI entities, defined in the UDDI version 3 information 49 model, in an LDAPv3 compliant directory. 51 Bergeson, Boogert & Nanjundaswamy Internet-Draft 1 53 LDAP Schema for UDDI February 2005 55 Discussion Forum 57 Technical discussion of this document will take place on the IETF 58 LDAP Extensions mailing list . Please send 59 editorial comments directly to the authors. 61 Table of Contents 62 1. Introduction.........................................................2 63 2. Conventions used in this document....................................2 64 3. Representation of UDDI Data Structures...............................2 65 4. Attribute Type Definitions...........................................6 66 5. Object Class Definitions............................................26 67 6. Name Forms..........................................................30 68 7. DIT Structure Rules.................................................32 69 8. Security Considerations.............................................34 70 9. IANA Considerations.................................................34 71 10. Normative References...............................................37 72 11. Author's Addresses.................................................39 74 1. Introduction 76 This document defines "Lightweight Directory Access Protocol" 77 [LDAPv3] schema elements to represent the core data structures 78 identified in "Universal Description Discovery and Integration" 79 version 3 [UDDIv3] information model. This includes: a 80 businessEntity, a businessService, a bindingTemplate, a tModel, a 81 publisherAssertion and a Subscription. Portions of [UDDIv3] are 82 repeated here for clarity. 84 2. Conventions used in this document 86 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 87 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 88 document are to be interpreted as described in RFC 2119 [RFC2119]. 90 All schema definitions are provided using [RFC2252] descriptions, 91 line-wrapped for readability only. 93 3. Representation of UDDI Data Structures 95 The information that makes up a registration in a UDDI registry 96 consists of these data structure types. This division by 97 information type provides simple partitions to assist in the rapid 98 location and understanding of the different information that makes 99 up a registration. 101 Bergeson,Boogert & Nanjundaswamy Internet-Draft 2 103 LDAP Schema for UDDI February 2005 105 The individual instance data managed by a UDDI registry are 106 sensitive to the parent/child relationships found in the schema. A 107 businessEntity object contains one or more unique businessService 108 objects. Similarly, individual businessService objects contain 109 specific instances of bindingTemplate, which in turn contains 110 information that includes pointers to specific instances of tModel 111 objects. 113 It is important to note that no single instance of a core schema 114 type is ever "contained" by more than one parent instance. This 115 means that only one specific businessEntity object (identified by 116 its unique key value) will ever contain or be used to express 117 information about a specific instance of a businessService object 118 (also identified by its own unique key value). 120 3.1 businessEntity 122 The businessEntity object represents all known information about a 123 business or entity that publishes descriptive information about the 124 entity as well as the services that it offers. The businessEntity 125 is the top-level container that accommodates holding descriptive 126 information about a business or entity. Service descriptions and 127 technical information are expressed within a businessEntity by a 128 containment relationship. 130 3.1.1 Representation in the Directory 132 A businessEntity is represented in the directory by the attributes 133 uddiBusinessKey, uddiAuthorizedName, uddiOperator, 134 uddiDiscoveryURLs, uddiName, uddiDescription, uddiIdentifierBag, 135 uddiCategoryBag, and uddiv3DigitalSignature, along with 136 corresponding v3 keys viz. uddiv3BusinessKey, as defined in section 137 4. A businessEntity may contain zero or more instances of 138 uddiContact and uddiBusinessService. 140 A mandatory attribute, uddiBusinessKey, contains the unique 141 identifier for a given instance of a businessEntity. 143 businessEntity's definition is given in Section 5. 145 3.2 businessService 147 The businessService instances represent a logical business service. 148 Each businessService object is the logical child of a single 149 businessEntity object. Each businessService element contains 150 descriptive information in business terms outlining the type of 151 technical services found within each businessService instance. 153 In some cases, businesses would like to share or reuse services, 154 e.g. when a large enterprise publishes separate businessEntity 156 Bergeson,Boogert & Nanjundaswamy Internet-Draft 3 158 LDAP Schema for UDDI February 2005 160 structures. This can be established by using the businessService 161 instance as a projection to an already published businessService. 163 3.2.1 Representation in the Directory 165 A businessService is represented in the directory by the attributes 166 uddiBusinessKey, uddiServiceKey, uddiName, uddiDescription, 167 uddiCategoryBag, uddiIsProjection, and uddiv3DigitalSignature, along 168 with corresponding v3 keys viz. uddiv3BusinessKey & 169 uddiv3ServiceKey, as defined in section 4. A businessService may 170 contain zero or more instances of uddiBindingTemplate. 172 The mandatory attribute, uddiServiceKey, contains the unique 173 identifier for a given instance of a businessService. 175 businessService's definition is given in Section 5. 177 3.3 bindingTemplate 179 Technical descriptions of Web services are accommodated via 180 individual contained instances of bindingTemplate objects. These 181 instances provide support for determining a technical entry point or 182 optionally support remotely hosted services, as well as a 183 lightweight facility for describing unique technical characteristics 184 of a given implementation. Support for technology and application 185 specific parameters and settings files are also supported. 187 Since UDDI's main purpose is to enable description and discovery of 188 Web Service information, it is the bindingTemplate that provides the 189 most interesting technical data. With UDDIv3, bindingTemplates also 190 can have categorization information. 192 Each bindingTemplate instance has a single logical businessService 193 parent, which in turn has a single logical businessEntity parent. 195 3.3.1 Representation in the Directory 197 A bindingTemplate is represented in the directory by the attributes 198 uddiBindingKey, uddiServiceKey, uddiDescription, uddiAccessPoint, 199 uddiHostingRedirector, uddiCategoryBag and uddiv3DigitalSignature, 200 along with corresponding v3 keys viz. uddiv3ServiceKey and 201 uddiv3BindingKey, as defined in section 4. A bindingTemplate may 202 contain zero or more instances of uddiTModelInstanceDetails. 204 The mandatory attribute, uddiBindingKey, contains the unique 205 identifier for a given instance of a bindingTemplate. 207 BindingTemplate's definition is given in Section 5. 209 Bergeson,Boogert & Nanjundaswamy Internet-Draft 4 211 LDAP Schema for UDDI February 2005 213 3.4 tModel 215 The tModel object takes the form of keyed metadata (data about 216 data). In a general sense, the purpose of a tModel within the UDDI 217 registry is to provide a reference system based on abstraction. 218 Thus, the kind of data that a tModel represents is pretty nebulous. 219 In other words, a tModel registration can define just about 220 anything, but in the current revision, two conventions have been 221 applied for using tModels: as sources for determining compatibility 222 and as keyed namespace references. 224 The information that makes up a tModel is quite simple. There's a 225 key, a name, an optional description, and a Uniform Resource Locator 226 [URL] that points somewhere--presumably somewhere where the curious 227 can go to find out more about the actual concept represented by the 228 metadata in the tModel itself. 230 3.4.1 Representation in the Directory 232 A tModel is represented in the directory by the attributes 233 uddiTModelKey, uddiAuthorizedName, uddiOperator, uddiName, 234 uddiDescription, uddiOverviewDescription, uddiOverviewURL, 235 uddiIdentifierBag, uddiCategoryBag, uddiIsHidden, and 236 uddiv3DigitalSignature, along with corresponding v3 key viz. 237 uddiv3tModelKey, as defined in section 4. A tModel may also contain 238 a uddiHidden to logically delete a tModel. 240 A mandatory attribute, uddiTModelKey, contains the unique identifier 241 for a given instance of a tModel. 243 tModel's definition is given in Section 5. 245 3.5 publisherAssertion 247 Many businesses, like large enterprises or marketplaces, are not 248 effectively represented by a single businessEntity, since their 249 description and discovery are likely to be diverse. As a 250 consequence, several businessEntity instances can be published, 251 representing individual subsidiaries of a large enterprise or 252 individual participants of a marketplace. Nevertheless, they still 253 represent a more or less coupled community and would like to make 254 some of their relationships visible in their UDDI registrations. 256 3.5.1 Representation in the Directory 258 A publisherAssertion is represented in the directory by the 259 attributes uddiFromKey, uddiToKey, uddiKeyedReference, and uddiUUID, 260 and uddiv3DigitalSignature, as defined in section 5. 262 Bergeson,Boogert & Nanjundaswamy Internet-Draft 5 264 LDAP Schema for UDDI February 2005 266 A mandatory attribute, uddiUUID, contains the unique identifier for 267 a given instance of a publisherAssertion. 269 publisherAssertion's definition is given in Section 5. 271 3.6 Operational Information: 273 With UDDIv3, the operational information associated with the core 274 UDDI data structures is maintained in a separate OperationalInfo 275 structure, so that the digital signature specified by the publisher 276 remains valid. 278 The operationalInfo structure is used to convey the operational 279 information for the UDDIv3 core data structures, that is, the 280 businessEntity, businessService, bindingTemplate and tModel 281 structures. UDDIv3 OperationalInfo consists of 5 elements: created. 282 Modified, modifiedIncludingChildren, nodeId and authorizedName. 284 Depending on the specific UDDIv3 core data structure, the 285 operationalInformation is represented in the directory as a 286 combination of implicit LDAP Standard Operational attributes: 287 createTimestamp and modifyTimestamp, and the following explicit 288 attributes: uddiAuthorizedName, uddiv3EntityCreationTime, 289 uddiv3EntityModificationTime and uddiv3NodeId. 291 4. Attribute Type Definitions 293 Note that OIDs for the attribute types in this document have not 294 been assigned. All OIDs are in brackets, , as a 295 placeholder until real OIDs are assigned. 297 4.1 uddiBusinessKey 299 Used in uddiBusinessEntity and uddiBusinessService. 301 The uddiBusinessKey is the unique identifier for a given instance of 302 an uddiBusinessEntity. The attribute is optional for businessService 303 instances contained within a fully expressed parent that already 304 contains a businessKey value. 306 If the businessService instance is rendered into Extensible Markup 307 Language [XML] and has no containing parent that has within its data 308 a businessKey, the value of the businessKey that is the parent of 309 the businessService is required to be provided. This behavior 310 supports the ability to browse through the parent-child 311 relationships given any of the core elements as a starting point. 312 The businessKey may differ from the publishing businessEntity's 313 businessKey to allow service projections. 315 Bergeson,Boogert & Nanjundaswamy Internet-Draft 6 317 LDAP Schema for UDDI February 2005 319 ( IANA-ASSIGNED-OID.4.1 NAME 'uddiBusinessKey' 320 DESC 'businessEntity unique identifier' 321 EQUALITY caseIgnoreMatch 322 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 323 SINGLE-VALUE 324 ) 326 4.2 uddiAuthorizedName 328 The uddiAuthorizedName is the recorded name of the individual that 329 published the uddiBusinessEntity or uddiTModel data. This data is 330 generated by the controlling operator and should not be supplied 331 within save_business operations. 333 With UDDIv3, this attribute is part of the �operationalInformation� 334 meta-data associated with core data structures. 336 ( IANA-ASSIGNED-OID.4.2 NAME 'uddiAuthorizedName' 337 DESC 'businessEntity publisher name' 338 EQUALITY distinguishedNameMatch 339 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 340 SINGLE-VALUE 341 ) 343 4.3 uddiOperator 345 The uddiOperator is the certified name of the UDDI registry site 346 operator that manages the master copy of the uddiBusinessEntity or 347 uddiTModel. The controlling operator records this data at the time 348 data is saved. This data is generated and should not be supplied 349 within save_business or save_tModel operations. 351 With UDDIv3, this field is no longer used - it is replaced by the 352 nodeId (uddiv3NodeId) attribute that is part of the 353 �operationalInformation� meta-data. 355 ( IANA-ASSIGNED-OID.4.3 NAME 'uddiOperator' 356 DESC 'registry site operator of businessEntitys master copy' 357 EQUALITY caseIgnoreMatch 358 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 359 SINGLE-VALUE 360 ) 362 4.4 uddiName 364 Used in uddiBusinessEntity, uddiBusinessService and uddiTModel. 366 These are the human readable names recorded for the 367 uddiBusinessEntity, uddiBusinessService, or uddiTModel, adorned with 368 a unique xml:lang value to signify the language that they are 370 Bergeson,Boogert & Nanjundaswamy Internet-Draft 7 372 LDAP Schema for UDDI February 2005 374 expressed in. Name search is provided via find_business, 375 find_service, or find_tModel calls. 377 The publishing of several names, e.g. for romanization purposes, is 378 supported. In order to signify the language that the names are 379 expressed in, they carry unique xml:lang values. Not more than one 380 name element may omit specifying its language. Names passed in this 381 way will be assigned the default language code of the registering 382 party. This default language code is established at the time that 383 publishing credentials are established with an individual Operator 384 Site. If no default language is provisioned at the time a publisher 385 signs up, the operator can adopt an appropriate default language 386 code. 388 With UDDIv3, multiple values with the same language code are 389 permitted. 391 ( IANA-ASSIGNED-OID.4.4 NAME 'uddiName' 392 DESC 'human readable name' 393 EQUALITY caseIgnoreMatch 394 ORDERING caseIgnoreOrderingMatch 395 SUBSTR caseIgnoreSubstringsMatch 396 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 397 ) 399 The xml:lang value precedes the name value with the "#" character 400 used as the separator. 402 4.5 uddiDescription 404 The uddiDescription is an optional repeating element of one or more 405 descriptions. One description is allowed per national language code 406 supplied. With UDDIv3, there is no restriction on the number of 407 descriptions or on what xml:lang value that they may have. 409 ( IANA-ASSIGNED-OID.4.5 NAME 'uddiDescription' 410 DESC 'short description' 411 EQUALITY caseIgnoreMatch 412 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 413 ) 415 The xml:lang value precedes the name value with the "#" character 416 used as the separator. 418 4.6 uddiDiscoveryURLs 420 This is a list of Uniform Resource Locators (URLs) that point to 421 alternate, file based service discovery mechanisms. Each recorded 422 uddiBusinessEntity structure is automatically assigned a URL that 424 Bergeson,Boogert & Nanjundaswamy Internet-Draft 8 426 LDAP Schema for UDDI February 2005 428 returns the individual uddiBusinessEntity structure. URL search is 429 provided via find_business call. 431 The uddiDiscoveryURLs attribute is used to hold pointers to URL 432 addressable discovery documents. The expected retrieval mechanism 433 for URLs referenced in the data within this structure is via 434 Hypertext Transfer Protocol [HTTP] HTTP-GET operation. The expected 435 return document is not defined. Rather, a framework for establishing 436 convention is provided, and two such conventions are defined within 437 UDDI behaviors. It is hoped that other conventions come about and 438 use this structure to accommodate alternate means of discovery. 439 With UDDIv3, a new convention is defined with useType as "homepage". 440 Further, a UDDIv3 server need not generate/add a discoveryURL 441 itself, since this can invalidate the digital signature of signed 442 Business Entity saved by publishers. 444 ( IANA-ASSIGNED-OID.4.6 NAME 'uddiDiscoveryURLs' 445 DESC 'URL to retrieve a businessEntity instance' 446 EQUALITY caseIgnoreMatch 447 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 448 ) 450 The useType value precedes the URL value with the "#" character used 451 as the separator. 453 4.7 uddiUseType 455 The uddiUseType is used to describe the type of contact or address 456 in freeform text. Suggested examples for contact include "technical 457 questions", "technical contact", "establish account", "sales 458 contact", etc. Suggested examples for address include 459 "headquarters", "sales office", "billing department", etc. 461 ( IANA-ASSIGNED-OID.4.7 NAME 'uddiUseType' 462 DESC 'name of convention the referenced document follows' 463 EQUALITY caseIgnoreMatch 464 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 465 SINGLE-VALUE 466 ) 468 4.8 uddiPersonName 470 The uddiPersonName should list the name of the person or name of the 471 job role that will be available behind the contact. Examples of 472 roles include "administrator" or "webmaster". 474 ( IANA-ASSIGNED-OID.4.8 NAME 'uddiPersonName' 475 DESC 'name of person or job role available for contact' 476 EQUALITY caseIgnoreMatch 477 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 479 Bergeson,Boogert & Nanjundaswamy Internet-Draft 9 481 LDAP Schema for UDDI February 2005 483 SINGLE-VALUE 484 ) 486 With UDDIv3, uddiPersonName becomes multi-valued and each name can 487 have an xml:lang attribute. The xml:lang value precedes the name 488 value with the "#" character used as the separator. 490 4.9 uddiPhone 492 Used to hold telephone numbers for the contact. This element can be 493 adorned with an optional uddiUseType attribute for descriptive 494 purposes. If more than one phone element is saved, uddiUseType 495 attributes are required on each. 497 ( IANA-ASSIGNED-OID.4.9 NAME 'uddiPhone' 498 DESC 'telephone number for contact' 499 EQUALITY caseIgnoreMatch 500 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 501 ) 503 The useType precedes the telephone number by a separating '#' (e.g. 504 "Work Number#123 456-7890") 506 4.10 uddiEMail 508 Used to hold email addresses for the contact. This element can be 509 adorned with an optional uddiUseType attribute for descriptive 510 purposes. If more than one email element is saved, uddiUseType 511 attributes are required on each. 513 ( IANA-ASSIGNED-OID.4.10 NAME 'uddiEMail' 514 DESC 'e-mail address for contact' 515 EQUALITY caseIgnoreMatch 516 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 517 ) 519 The useType precedes the email address by a separating '#' (e.g. 520 "President of the United States #president@whitehouse.gov"). 522 4.11 uddiSortCode 524 The uddiSortCode is used to drive the behavior of external display 525 mechanisms that sort addresses. The suggested values for 526 uddiSortCode include numeric ordering values (e.g. 1, 2, 3), 527 alphabetic character ordering values (e.g. a, b, c) or the first n 528 positions of relevant data within the address. 530 ( IANA-ASSIGNED-OID.4.11 NAME 'uddiSortCode' 531 DESC 'specifies an external disply mechanism' 533 Bergeson,Boogert & Nanjundaswamy Internet-Draft 10 535 LDAP Schema for UDDI February 2005 537 EQUALITY caseIgnoreMatch 538 ORDERING caseIgnoreOrderingMatch 539 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 540 SINGLE-VALUE 541 ) 543 With UDDIv3, the sortCode attribute is deprecated because of the 544 guarantee of preserving the document Order. 546 4.12 uddiTModelKey 548 The uddiTModelKey is the unique identifier for a given instance of 549 an uddiTModel. 551 It is also used in a KeyedReference and in Address structures. When 552 used with a keyed reference, this is the unique key to identify a 553 value-set and implies that the keyName keyValue pair in an 554 uddiIdentifier or uddiCategory Bag,are to be interpreted by the 555 value set referenced by the tModelKey. 557 When used with Addressline elements, implies that the keyName 558 keyValue pair given by subsequent uddiAddressLine elements are to be 559 interpreted by the address structure associated with the tModel that 560 is referenced. 562 ( IANA-ASSIGNED-OID.4.12 NAME 'uddiTModelKey' 563 DESC 'tModel unique identifier' 564 EQUALITY caseIgnoreMatch 565 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 566 SINGLE-VALUE 567 ) 569 4.13 uddiAddressLine 571 The uddiAddressLine contains the actual address in freeform text. If 572 the address element contains a uddiTModelKey, these uddiAddressLine 573 elements are to be adorned each with an optional keyName keyValue 574 attribute pair. Together with the uddiTModelKey, keyName and 575 keyValue qualify the uddiAddressLine in order to describe its 576 meaning. 578 The uddiAddressLine elements contain string data with a line length 579 limit of 80 character positions. Each uddiAddressLine element can be 580 adorned with two optional descriptive attributes, keyName and 581 keyValue. Both attributes must be present in each address line if a 582 uddiTModelKey is assigned to the address structure. By doing this, 583 the otherwise arbitrary use of address lines becomes structured. 584 Together with the address' uddiTModelKey, keyName and keyValue 585 virtually build a uddiKeyedReference that represents an address line 586 qualifier, given by the referenced uddiTModel. 588 Bergeson,Boogert & Nanjundaswamy Internet-Draft 11 590 LDAP Schema for UDDI February 2005 592 When no uddiTModelKey is provided for the address structure, the 593 keyName and keyValue attributes can be used without restrictions, 594 for example, to provide descriptive information for each 595 uddiAddressLine by using the keyName attribute. Since both the 596 keyName and the keyValue attributes are optional, address line order 597 is significant and will always be returned by the UDDI compliant 598 registry in the order originally provided during a call to 599 save_business. 601 ( IANA-ASSIGNED-OID.4.13 NAME 'uddiAddressLine' 602 DESC 'address' 603 EQUALITY caseIgnoreMatch 604 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 605 ) 607 The keyName, keyValue, and addressData of this attribute are 608 separated by "#", (e.g. "#""#""#"). 609 The addressData is the only required portion of the attribute. 611 4.14 uddiIdentifierBag 613 The uddiIdentifierBag element allows uddiBusinessEntity or 614 uddiTModel structures to include information about common forms of 615 identification such as D-U-N-S_ numbers, tax identifiers, etc. This 616 data can be used to signify the identity of the uddiBusinessEntity, 617 or can be used to signify the identity of the publishing party. 618 Including data of this sort is optional, but when used greatly 619 enhances the search behaviors exposed via the find_xx messages 620 defined in the UDDI Version 2.0 API Specification [UDDI]. For a full 621 description of the structures involved in establishing an identity, 622 see UDDI Version 2.0 Data Structure Specification - Appendix A: 623 Using Identifiers. 625 ( IANA-ASSIGNED-OID.4.14 NAME 'uddiIdentifierBag' 626 DESC 'identification information' 627 EQUALITY caseIgnoreMatch 628 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 629 ) 631 The tModel, keyName, and keyValue of this attribute are separated by 632 "#", (e.g. "#""#"). The keyValue is the 633 only required portion of the attribute. 635 4.15 uddiCategoryBag 637 The uddiCategoryBag element allows uddiBusinessEntity, 638 uddiBusinessService and uddiTModel structures to be categorized 639 according to any of several available taxonomy based classification 640 schemes. Operator Sites automatically provide validated 642 Bergeson,Boogert & Nanjundaswamy Internet-Draft 12 644 LDAP Schema for UDDI February 2005 646 categorization support for three taxonomies that cover industry 647 codes (via NAICS), product and service classifications (via UNSPC) 648 and geography (via ISO 3166). Including data of this sort is 649 optional, but when used greatly enhances the search behaviors 650 exposed by the find_xx messages defined in the UDDI Version 2.0 API 651 Specification. For a full description of structures involved in 652 establishing categorization information, see UDDI Version 2.0 Data 653 Structure Specification - Appendix B: Using categorization. 655 ( IANA-ASSIGNED-OID.4.15 NAME 'uddiCategoryBag' 656 DESC 'categorization information' 657 EQUALITY caseIgnoreMatch 658 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 659 ) 661 The tModel, keyName, and keyValue of this attribute are separated by 662 "#", (e.g. "#""#"). The keyValue is the 663 only required portion of the attribute. 665 With UDDIv3, uddiBindingTemplates also supports the uddiCategoryBag 666 element and they can also be categorized according to any of several 667 available taxonomy based classification schemes. 669 4.16 uddiKeyedReference 671 The uddiKeyedReference is a general-purpose attribute for a name- 672 value pair, with an additional reference to a tModel. 674 ( IANA-ASSIGNED-OID.4.16 NAME 'uddiKeyedReference' 675 DESC 'categorization information' 676 EQUALITY caseIgnoreMatch 677 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 678 ) 680 The tModel, keyName, and keyValue of this attribute are separated by 681 "#", (e.g. "#""#"). The keyValue is the 682 only required portion of the attribute. With UDDIv3, the tModelKey 683 also becomes mandatory part of the attribute. 685 Also, UDDIv3 defines KeyedReferenceGroups for CategoryBags. A 686 keyedReferenceGroup contains a tModelKey and a simple list of 687 KeyedReference structures. The uddiKeyedReference attribute will 688 support KeyedReferenceGroups by suffixing the tModelKey for 689 KEyedReferenceGroup to each of the keyedReference values associated 690 with the group. 691 e.g. to represent a keyedReference group containing a list of 2 692 keyed references, the attribute will hold the following 2 strings as 693 its values: 694 tModelKey1#KeyName1#KeyValue1#KeyedReferenceGroup1_tModelKey 695 tModelKey2#KeyName2#KeyValue2#KeyedReferenceGroup1_tModelKey 697 Bergeson,Boogert & Nanjundaswamy Internet-Draft 13 699 LDAP Schema for UDDI February 2005 701 4.17 uddiServiceKey 703 This is the unique key for a given uddiBusinessService. When saving 704 a new uddiBusinessService structure, pass an empty uddiServiceKey 705 value. This signifies that a UUID value is to be generated. To 706 update an existing uddiBusinessService structure, pass the UUID 707 value that corresponds to the existing service. If an uddiServiceKey 708 is received via an inquiry operation, the key values may not be 709 blank. When saving a new or updated service projection, pass the 710 uddiServiceKey of the referenced uddiBusinessService structure. 712 This attribute is optional when the uddiBindingTemplate data is 713 contained within a fully expressed parent that already contains a 714 uddiServiceKey value. If the uddiBindingTemplate data is rendered 715 into XML and has no containing parent that has within its data a 716 uddiServiceKey, the value of the uddiServiceKey that is the ultimate 717 containing parent of the uddiBindingTemplate is required to be 718 provided. This behavior supports the ability to browse through the 719 parent-child relationships given any of the core elements as a 720 starting point. 722 ( IANA-ASSIGNED-OID.4.17 NAME 'uddiServiceKey' 723 DESC 'businessService unique identifier' 724 EQUALITY caseIgnoreMatch 725 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 726 SINGLE-VALUE 727 ) 729 4.18 uddiBindingKey 731 This is the unique key for a given uddiBindingTemplate. When saving 732 a new uddiBindingTemplate structure, pass an empty uddiBindingKey 733 value. This signifies that a UUID value is to be generated. To 734 update an existing uddiBindingTemplate, pass the UUID value that 735 corresponds to the existing uddiBindingTemplate instance. If an 736 uddiBindingKey is received via an inquiry operation, the key values 737 may not be blank. 739 ( IANA-ASSIGNED-OID.4.18 NAME 'uddiBindingKey' 740 DESC 'bindingTemplate unique identifier' 741 EQUALITY caseIgnoreMatch 742 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 743 SINGLE-VALUE 744 ) 746 4.19 uddiAccessPoint 748 The uddiAccessPoint element is an attribute-qualified pointer to a 749 service entry point. The notion of service at the metadata level 751 Bergeson,Boogert & Nanjundaswamy Internet-Draft 14 753 LDAP Schema for UDDI February 2005 755 seen here is fairly abstract and many types of entry points are 756 accommodated. A single attribute is provided named URLType. 758 Required attribute qualified element8. This element is a text field 759 that is used to convey the entry point address suitable for calling 760 a particular Web service. This may be a URL, an electronic mail 761 address, or even a telephone number. No assumptions about the type 762 of data in this field can be made without first understanding the 763 technical requirements associated with the Web service. 765 ( IANA-ASSIGNED-OID.4.19 NAME 'uddiAccessPoint' 766 DESC 'entry point address to call a web service' 767 EQUALITY caseIgnoreMatch 768 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 769 SINGLE-VALUE 770 ) 772 The URLType value precedes the accessPoint value by a separating 773 '#'. 775 With UDDIv3,the �URLType� attribute is replaced by a �UseType� 776 attribute. Using this UseType attribute, the accessPoint attribute 777 can model a hostingRedirector or support indirection to indicate the 778 accesspoint is specified within a remotely hosted WSDL document. 780 For a UDDIv3 registry that needs support UDDIv2 clients, the 781 attribute must allow representing the URLType and UseType values 782 independently. 784 The UDDIv3 spec specifies the following logic for mapping values 785 between URLType and UseType: If an entity is saved with the v3 786 namespace and a v2 inquiry is made, the URLType will be returned as 787 "other". In the case when a v3 inquiry is made on an entity 788 published with the v2 namespace, the v3 useType attribute will be 789 returned as "endPoint". 791 For implementations that need to explicitly model both forms, the 792 recommended format is as follows: v2URLType#v3UseType#Address 794 4.20 uddiHostingRedirector 796 The uddiHostingRedirector element is used to designate that a 797 uddiBindingTemplate entry is a pointer to a different 798 uddiBindingTemplate entry. The value in providing this facility is 799 seen when a business or entity wants to expose a service description 800 (e.g. advertise that they have a service available that suits a 801 specific purpose) that is actually a service that is described in a 802 separate uddiBindingTemplate record. This might occur when a service 803 is remotely hosted (hence the name of this element), or when many 805 Bergeson,Boogert & Nanjundaswamy Internet-Draft 15 807 LDAP Schema for UDDI February 2005 809 service descriptions could benefit from a single service 810 description. 812 The uddiHostingRedirector element has a single attribute and no 813 element content. The attribute is a uddiBindingKey value that is 814 suitable within the same UDDI registry instance for querying and 815 obtaining the uddiBindingDetail data that is to be used. 817 More on the uddiHostingRedirector can be found in the appendices for 818 the UDDI Version 2.0 API Specification. 820 Required element if uddiAccessPoint not provided. This element is 821 adorned with a uddiBindingKey attribute, giving the redirected 822 reference to a different uddiBindingTemplate. If you query a 823 uddiBindingTemplate and find a uddiHostingRedirector value, you 824 should retrieve that uddiBindingTemplate and use it in place of the 825 one containing the uddiHostingRedirector data. 827 ( IANA-ASSIGNED-OID.4.20 NAME 'uddiHostingRedirector' 828 DESC 'designates a pointer to another bindingTemplate' 829 EQUALITY caseIgnoreMatch 830 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 831 SINGLE-VALUE 832 ) 834 With UDDIv3, the hostingRedirector is a deprecated element, since 835 its functionality is now covered by the accessPoint. For backward- 836 compatibility, it can still be used, but it is not recommended. 838 4.21 uddiInstanceDescription 840 This is an optional repeating element. This is one or more language 841 qualified text descriptions that designate what role a uddiTModel 842 reference plays in the overall service description. 844 ( IANA-ASSIGNED-OID.4.21 NAME 'uddiInstanceDescription' 845 DESC 'instance details description' 846 EQUALITY caseIgnoreMatch 847 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 848 ) 850 The xml:lang value precedes the name value with the "#" character 851 used as the separator. 853 4.22 uddiInstanceParms 855 The uddiInstance Parms is an Optional element of the uddiInstance. 856 Used to contain settings parameters or a URL reference to a file 857 that contains settings or parameters required to use a specific 858 facet of a uddiBindingTemplate description. If used to house the 860 Bergeson,Boogert & Nanjundaswamy Internet-Draft 16 862 LDAP Schema for UDDI February 2005 864 parameters themselves, the suggested content is a namespace 865 qualified XML string � using a namespace outside of the UDDI schema. 866 If used to house a URL pointer to a file, the suggested format is 867 URL that is suitable for retrieving the settings or parameters via 868 HTTP-GET. 870 ( IANA-ASSIGNED-OID.4.22 NAME 'uddiInstanceParms' 871 DESC 'URL reference to required settings' 872 EQUALITY caseIgnoreMatch 873 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 874 SINGLE-VALUE 875 ) 877 4.23 uddiOverviewDescription 879 This is optional repeating element. This language-qualified string 880 is intended to hold a short descriptive overview of how a particular 881 uddiTModel is to be used. 883 ( IANA-ASSIGNED-OID.4.23 NAME 'uddiOverviewDescription' 884 DESC 'outlines tModel usage' 885 EQUALITY caseIgnoreMatch 886 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 887 ) 889 The xml:lang value precedes the name value with the "#" character 890 used as the separator. 892 4.24 uddiOverviewURL 894 This is an optional element. This string data element is to be used 895 to hold a URL reference to a long form of an overview document that 896 covers the way a particular uddiTModel specific reference is used as 897 a component of an overall web service description. The recommended 898 format for the overviewURL is a URI that is suitable for retrieving 899 the actual overview document with an HTTP GET operation, for 900 example, via a Web browser. 902 ( IANA-ASSIGNED-OID.4.24 NAME 'uddiOverviewURL' 903 DESC 'URL reference to overview document' 904 EQUALITY caseIgnoreMatch 905 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 906 SINGLE-VALUE 907 ) 909 With UDDIv3, uddiOverviewURL becomes multi-valued, to allow 910 representing multiple OverviewDocs within a single InstanceDetail 911 element. 913 Modeling multiple OverviewDocs within an InstanceDetail element: 915 Bergeson,Boogert & Nanjundaswamy Internet-Draft 17 917 LDAP Schema for UDDI February 2005 919 In UDDIv3, InstanceDetails element in TmodelInstanceInfo can have 920 multiple OverviewDoc�s. In UDDIv2, we could have only 1 OverviewDoc. 921 To retain the grouping between a set of overviewDescriptions and 922 overviewURL, we can make both OverviewDoc and OverviewURL multi- 923 valued. And have a �group ID� Prefix to each value (to group 924 OverviewDescriptions and OverviewURL). 926 An example is shown below: 927 Overview Description OverviewURL 928 1#xml:lang#overviewDescription1 1#UseType#overviewURL 929 1#xml:lang#overviewDescription2 2#UseType#overviewURL 930 1#xml:lang#overviewDescription3 4#UseType#overviewURL 931 3#xml:lang#overviewDescription1 932 3#xml:lang#overviewDescription2 933 4#xml:lang#overviewDescription1 935 This implies that OverviewDoc1 has 3 overview descriptions and an 936 overviewURL. OverviewDoc2 has only an overviewURL. OverviewDoc3 has 937 only 2 overviewDescriptions. OverviewDoc4 also has 1 overview 938 description and an overviewURL. 940 4.25 uddiFromKey 942 The uddiFromKey is a required element. This is the unique key 943 reference to the first uddiBusinessEntity the assertion is made for. 945 ( IANA-ASSIGNED-OID.4.25 NAME 'uddiFromKey' 946 DESC 'unique businessEntity key reference' 947 EQUALITY caseIgnoreMatch 948 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 949 SINGLE-VALUE 950 ) 952 4.26 uddiToKey 954 The uddiToKey is a required element. This is the unique key 955 reference to the second uddiBusinessEntity the assertion is made 956 for. 958 ( IANA-ASSIGNED-OID.4.26 NAME 'uddiToKey' 959 DESC 'unique businessEntity key reference' 960 EQUALITY caseIgnoreMatch 961 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 962 SINGLE-VALUE 963 ) 965 4.27 uddiUUID 967 Bergeson,Boogert & Nanjundaswamy Internet-Draft 18 969 LDAP Schema for UDDI February 2005 971 The uddiUUID is a required element. This is to insure unique 972 identification of uddiContact, uddiAddress, and 973 uddiPublisherAssertion objects. 975 ( IANA-ASSIGNED-OID.4.27 NAME 'uddiUUID' 976 DESC 'unique attribute' 977 EQUALITY caseIgnoreMatch 978 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 979 SINGLE-VALUE 980 ) 982 With UDDIv3, this attribute will also be used for unique 983 identification of Subscription feature related entities. 985 4.28 uddiIsHidden 987 Used to provide functionality for the delete_tModel operation. 988 Logical deletion hides the deleted tModels from find_tModel result 989 sets but does not physically delete it. 991 ( IANA-ASSIGNED-OID.4.28 NAME 'uddiIsHidden' 992 DESC 'isHidden attribute' 993 EQUALITY booleanMatch 994 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 995 SINGLE-VALUE 996 ) 998 In case of UDDIv3, this attribute will represent the �deleted� 999 attribute value. 1001 4.29 uddiIsProjection 1003 Used to identify a Business Service that as a Service Projection. 1005 ( IANA-ASSIGNED-OID.4.29 NAME 'uddiIsProjection' 1006 DESC 'isServiceProjection attribute' 1007 EQUALITY booleanMatch 1008 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 1009 SINGLE-VALUE 1010 ) 1012 4.30 uddiLang 1014 Used to model the xml:lang value for the Address structure in 1015 UDDIv3. 1017 ( IANA-ASSIGNED-OID.4.30 NAME 'uddiLang' 1018 DESC 'xml:lang value in v3 Address structure' 1019 EQUALITY caseIgnoreMatch 1020 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1022 Bergeson,Boogert & Nanjundaswamy Internet-Draft 19 1024 LDAP Schema for UDDI February 2005 1026 SINGLE-VALUE 1027 ) 1029 The following are attribute definitions to model new elements/fields 1030 in UDDIv3 information model. These attribute definitions have the 1031 �uddiv3� prefix to indicate that these attributes represent UDDI 1032 information model elements unique to UDDIv3. 1034 4.31 uddiv3BusinessKey 1036 This is the unique UDDIv3 identifier for a given instance of 1037 uddiBusinessEntity. Used in uddiBusinessEntity and 1038 uddiBusinessService. 1040 A uddiBusinessEntity will include the uddiBusinessKey (the v2 form) 1041 for unique identification by UDDIv2 clients. The uddiBusinessKey 1042 (36-char) will also be the LDAP naming attribute for the 1043 uddiBusinessEntity. The uddiBusinessEntity entry MAY also include 1044 the uddiv3BusinessKey, the explicit v3 form key, which can be 255 1045 characters long. 1047 ( IANA-ASSIGNED-OID.4.31 NAME 'uddiv3BusinessKey' 1048 DESC 'UDDIv3 businessEntity unique identifier' 1049 EQUALITY caseIgnoreMatch 1050 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1051 SINGLE-VALUE 1052 ) 1054 4.32 uddiv3ServiceKey 1056 This is the unique UDDIv3 identifier for a given instance of 1057 uddiBusinessService. Used in uddiBusinessService and 1058 uddiBindingTemplate. 1060 A uddiBusinessService will include the uddiServiceKey (the v2 form) 1061 for unique identification by UDDIv2 clients. The uddiServiceKey (36- 1062 char) will also be the LDAP naming attribute for the 1063 uddiBusinessService entry. The uddiBusinessService entry MAY also 1064 include the uddiv3ServiceKey, the explicit v3 form key, which can be 1065 255 characters long. 1067 ( IANA-ASSIGNED-OID.4.32 NAME 'uddiv3ServiceKey' 1068 DESC 'UDDIv3 businessService unique identifier' 1069 EQUALITY caseIgnoreMatch 1070 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1071 SINGLE-VALUE 1072 ) 1074 4.33 uddiv3BindingKey 1076 Bergeson,Boogert & Nanjundaswamy Internet-Draft 20 1078 LDAP Schema for UDDI February 2005 1080 This is the unique UDDIv3 identifier for a given instance of 1081 uddiBindingTemplate. 1083 A uddiBindingTemplate will include the uddiBindingKey (the v2 form) 1084 for unique identification by UDDIv2 clients. The uddiBindingKey (36- 1085 char) will also be the LDAP naming attribute for the 1086 uddiBindingTemplate entry. The uddiBindingTemplate entry MAY also 1087 include the uddiv3BindingKey, the explicit v3 form key, which can be 1088 255 characters long. 1090 ( IANA-ASSIGNED-OID.4.33 NAME 'uddiv3BindingKey' 1091 DESC 'UDDIv3 BindingTemplate unique identifier' 1092 EQUALITY caseIgnoreMatch 1093 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1094 SINGLE-VALUE 1095 ) 1097 4.34 uddiv3TModelKey 1099 This is the unique UDDIv3 identifier for a given instance of an 1100 uddiTModel. 1102 A uddiTModel will include the uddiTModelKey (the v2 form) for unique 1103 identification by UDDIv2 clients. The uddiTModelKey (41-char) will 1104 also be the LDAP naming attribute for the uddiTModel entry. The 1105 uddiTModel entry MAY also include the uddiv3TModelKey, the explicit 1106 v3 form key, which can be 255 characters long. 1108 ( IANA-ASSIGNED-OID.4.34 NAME 'uddiv3TModelKey' 1109 DESC 'UDDIv3 TModel unique identifier' 1110 EQUALITY caseIgnoreMatch 1111 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1112 SINGLE-VALUE 1113 ) 1115 The tModelKey is also used in a KeyedReference and in Address 1116 structures. At all places, where a tModelKey is used as a reference 1117 to tModel, the v3 form of the tModel key (viz. uddiv3TModelKey) will 1118 be the form used, since using the v2 form key will require 1119 translating it to the v3 key by the UDDI Server and this may 1120 invalidate the digital signature of the entity. 1122 4.35 uddiv3DigitalSignature 1124 The UDDIv3 v3 schema supports signing of the following UDDI elements 1125 using �XML-Signature Syntax and Processing� (see 1126 http://www.w3.org/TR/xmldsig-core/). 1127 ..businessEntity 1128 ..businessService 1129 ..bindingTemplate 1131 Bergeson,Boogert & Nanjundaswamy Internet-Draft 21 1133 LDAP Schema for UDDI February 2005 1135 ..tModel 1136 ..publisherAssertion 1138 This uddiv3DigitalSignature attribute holds the digital signature 1139 for the corresponding UDDI entity. 1141 ( IANA-ASSIGNED-OID.4.35 NAME 'uddiv3DigitalSignature' 1142 DESC 'UDDIv3 entity digital signature' 1143 EQUALITY caseExactMatch 1144 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1145 ) 1147 A Signature element SHOULD be generated according to the required 1148 steps of "Core Generation" in XML-Signature Syntax and Processing. 1149 The signature should be calculated on the top level element that 1150 will be stored by the registry as a result of the Publication API 1151 call. This element, referred to as the data object in the 1152 XMLSignature and Syntax specification, is the businessEntity element 1153 for save_business API calls, the businessService element for 1154 save_service API calls, the bindingTemplate for save_binding 1155 API calls, the tModel for save_tModel API calls and the 1156 publisherAssertion for set_publisherAssertions and 1157 add_publisherAssertion API calls. 1159 The signature should be generated on the elements before they are 1160 added to the body of an API call. Also, according to the signature 1161 generation, all children of the element being signed are included in 1162 the generation of the signature unless first excluded by application 1163 of a transform. Due to the containment of service projections as 1164 businessService elements within a businessEntity element, this also 1165 means that changes to the projected service will render a signature 1166 of the businessEntity containing the projection invalid, unless a 1167 businessService element representing a service projection is 1168 excluded using a transform. 1170 Due to the location of the sequence of Signature elements within an 1171 element that is to be signed, the signature is "enveloped". As a 1172 result of the enveloping of the signature, it is necessary to apply 1173 at least one transformation on the signed entity to exclude the 1174 signature or signature(s). The transformation selected by a 1175 publisher or the XML Signature tool is specified in a Transform 1176 element inside the Signature element. 1178 4.36 uddiv3NodeId 1180 This attribute contains the Node Identity for a UDDIv3 node. 1182 ( IANA-ASSIGNED-OID.4.36 NAME 'uddiv3NodeId' 1183 DESC 'UDDIv3 Node Identifier' 1184 EQUALITY caseIgnoreMatch 1186 Bergeson,Boogert & Nanjundaswamy Internet-Draft 22 1188 LDAP Schema for UDDI February 2005 1190 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1191 SINGLE-VALUE 1192 ) 1194 4.37 uddiv3EntityModificationTime 1196 This attribute is used to maintain the last modification time for a 1197 UDDI entity. It is needed in context of maintaining the 1198 modifiedIncludingChildren element. When a child entity (e.g. 1199 uddiBindingTemplate) is updated, the parent entity (e.g. 1200 uddiBusinessService) LDAP timestamp also gets updated. The 1201 uddiv3EntityModificationTime attribute saves the last modification 1202 time of the parent entity (uddiBusinessService in this case). 1204 ( IANA-ASSIGNED-OID.4.37 NAME 'uddiv3EntityModificationTime' 1205 DESC 'UDDIv3 Last Modified Time for Entity' 1206 EQUALITY generalizedTimeMatch 1207 SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 1208 SINGLE-VALUE 1209 ) 1211 The following attribute definitions define attributes related to 1212 modeling of UDDIv3 subscription related entities in LDAP directory. 1214 Subscription provides clients, known as subscribers, with the 1215 ability to register their interest in receiving information 1216 concerning changes made in a UDDI registry. These changes can be 1217 scoped based on preferences provided with the request. The 1218 uddiv3Subscription object class is used to model registered UDDIv3 1219 Subscriptions. 1221 4.38 uddiv3SubscriptionKey 1223 This is the unique UDDIv3 identifier for a given instance of a 1224 uddiv3Subscription entity. 1226 ( IANA-ASSIGNED-OID.4.38 NAME 'uddiv3SubscriptionKey' 1227 DESC 'UDDIv3 Subscription unique identifier' 1228 EQUALITY caseIgnoreMatch 1229 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1230 SINGLE-VALUE 1231 ) 1233 4.39 uddiv3SubscriptionFilter 1235 This attribute contains the UDDIv3 Subscription Filter, specified as 1236 part of the save_subscription API i.e. the Inquiry API specified as 1237 filtering criteria with a registered subscription. The filtering 1238 criteria limits the scope of a subscription to a subset of registry 1240 Bergeson,Boogert & Nanjundaswamy Internet-Draft 23 1242 LDAP Schema for UDDI February 2005 1244 records. The get_xx and find_xx APIs are all valid choices for use 1245 as a subscriptionFilter. Only one of these can be chosen for each 1246 subscription. 1248 ( IANA-ASSIGNED-OID.4.39 NAME 'uddiv3SubscriptionFilter' 1249 DESC 'UDDIv3 Subscription Filter' 1250 EQUALITY caseIgnoreMatch 1251 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1252 SINGLE-VALUE 1253 ) 1255 4.40 uddiv3NotificationInterval 1257 This attribute contains the Notification Interval string. It is of 1258 type xsd:duration and specifies how often Asynchronous change 1259 notifications are to be provided to a subscriber. 1261 ( IANA-ASSIGNED-OID.4.40 NAME 'uddiv3NotificationInterval' 1262 DESC 'UDDIv3 Notification Interval' 1263 EQUALITY caseIgnoreMatch 1264 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1265 SINGLE-VALUE 1266 ) 1268 4.41 uddiv3MaxEntities 1270 This attribute contains the maximum number of entities to be 1271 returned as part of a subscription notification. It is an integer 1272 and specifies the maximum number of entities in a notification 1273 returned to a subscription listener. 1275 ( IANA-ASSIGNED-OID.4.41 NAME 'uddiv3MaxEntities' 1276 DESC 'UDDIv3 Subscription maxEntities field' 1277 EQUALITY integerMatch 1278 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1279 SINGLE-VALUE 1280 ) 1282 4.42 uddiv3ExpiresAfter 1284 This attribute specifies the Expiry Time associated with a 1285 Subscription. It is of the XML Schema type xsd:dateTime. 1287 ( IANA-ASSIGNED-OID.4.42 NAME 'uddiv3ExpiresAfter' 1288 DESC 'UDDIv3 Subscription ExpiresAfter field' 1289 EQUALITY generalizedTimeMatch 1290 SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 1291 SINGLE-VALUE 1292 ) 1294 Bergeson,Boogert & Nanjundaswamy Internet-Draft 24 1296 LDAP Schema for UDDI February 2005 1298 4.43 uddiv3BriefResponse 1300 This attribute is a Boolean flag for Brief Response associated with 1301 a Subscription entity. It controls the level of detail returned to a 1302 subscription listener. The default is "false" when omitted. When set 1303 to "true," it indicates that the subscription results are to be 1304 returned to the subscriber in the form of a keyBag, listing all of 1305 the entities that matched the subscriptionFilter. 1307 ( IANA-ASSIGNED-OID.4.43 NAME 'uddiv3BriefResponse' 1308 DESC 'UDDIv3 Subscription ExpiresAfter field' 1309 EQUALITY booleanMatch 1310 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 1311 SINGLE-VALUE 1312 ) 1314 4.44 uddiv3EntityKey 1316 This is the unique UDDIv3 identifier for a given instance of a core 1317 UDDI data structure that is to be logged as an Obituary Entry 1318 uddiv3EntityObituary. When a core UDDIv3 entity is deleted and there 1319 is an active subscription registered against this UDDI entity, an 1320 Obituary entry is created, in which the v3 key of the deleted entry 1321 is logged as part of the uddiv3EntityKey attribute. 1323 ( IANA-ASSIGNED-OID.4.44 NAME 'uddiv3EntityKey' 1324 DESC 'UDDIv3 Entity unique identifier' 1325 EQUALITY caseIgnoreMatch 1326 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 1327 SINGLE-VALUE 1328 ) 1330 4.45 uddiv3EntityCreationTime 1332 This attribute is used to log the original Creation Time for a UDDI 1333 Entity that is deleted, in the uddiv3EntityObituary entry. 1335 It is also used in uddiBusinessService and uddiBindingTemplate. A 1336 Move BS operation needs to delete and recreate BT sub-tree due to 1337 lack of support for moving a sub-tree in many LDAPv3 servers. This 1338 attribute is used to save the original creation time of the BT 1339 during a Move BS. 1341 ( IANA-ASSIGNED-OID.4.45 NAME 'uddiv3EntityCreationTime' 1342 DESC 'UDDIv3 Entity Creation Time' 1343 EQUALITY generalizedTimeMatch 1344 SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 1345 SINGLE-VALUE 1346 ) 1348 Bergeson,Boogert & Nanjundaswamy Internet-Draft 25 1350 LDAP Schema for UDDI February 2005 1352 4.46 uddiv3EntityDeletionTime 1354 This attribute is used to log the entity deletion time for a UDDI 1355 Entity that is deleted, in the uddiv3EntityObituary entry. 1357 ( IANA-ASSIGNED-OID.4.46 NAME 'uddiv3EntityDeletionTime' 1358 DESC 'UDDIv3 Entity Deletion Time' 1359 EQUALITY generalizedTimeMatch 1360 SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 1361 SINGLE-VALUE 1362 ) 1364 5. Object Class Definitions 1366 Note that OIDs for the object classes in this document have not been 1367 assigned. All OIDs are in brackets, , as a placeholder 1368 until real OIDs are assigned. 1370 5.1 uddiBusinessEntity 1372 This structural object class represents a businessEntity. 1374 ( IANA-ASSIGNED-OID.6.1 NAME 'uddiBusinessEntity' 1375 SUP top 1376 STRUCTURAL 1377 MUST ( uddiBusinessKey $ 1378 uddiName) 1379 MAY ( uddiAuthorizedName $ 1380 uddiOperator $ 1381 uddiDiscoveryURLs $ 1382 uddiDescription $ 1383 uddiIdentifierBag $ 1384 uddiCategoryBag $ 1385 uddiv3BusinessKey $ 1386 uddiv3DigitalSignature $ 1387 uddiv3EntityModificationTime $ 1388 uddiv3NodeId) 1389 ) 1391 5.2 uddiContact 1393 This structural object class represents a contact. It is contained 1394 by an uddiBusinessEntity. 1396 ( IANA-ASSIGNED-OID.6.2 NAME 'uddiContact' 1397 SUP top 1398 STRUCTURAL 1399 MUST ( uddiPersonName $ 1400 uddiUUID ) 1402 Bergeson,Boogert & Nanjundaswamy Internet-Draft 26 1404 LDAP Schema for UDDI February 2005 1406 MAY ( uddiUseType $ 1407 uddiDescription $ 1408 uddiPhone $ 1409 uddiEMail ) 1410 ) 1412 5.3 uddiAddress 1414 This structural object class represents an address. It is contained 1415 by an uddiContact. 1417 ( IANA-ASSIGNED-OID.6.3 NAME 'uddiAddress' 1418 SUP top 1419 STRUCTURAL 1420 MUST ( uddiUUID ) 1421 MAY ( uddiUseType $ 1422 uddiSortCode $ 1423 uddiTModelKey $ 1424 uddiv3TmodelKey $ 1425 uddiAddressLine $ 1426 uddiLang) 1427 ) 1429 5.4 uddiBusinessService 1431 This structural object class represents a businessService. 1433 ( IANA-ASSIGNED-OID.6.4 NAME 'uddiBusinessService' 1434 SUP top 1435 STRUCTURAL 1436 MUST ( uddiServiceKey ) 1437 MAY ( uddiName $ 1438 uddiBusinessKey $ 1439 uddiDescription $ 1440 uddiCategoryBag $ 1441 uddiIsProjection $ 1442 uddiv3ServiceKey $ 1443 uddiv3BusinessKey $ 1444 uddiv3DigitalSignature $ 1445 uddiv3EntityCreationTime $ 1446 uddiv3EntityModificationTime $ 1447 uddiv3NodeId) 1448 ) 1450 5.5 uddiBindingTemplate 1452 This structural object class represents a bindingTemplate. 1454 ( IANA-ASSIGNED-OID.6.5 NAME 'uddiBindingTemplate' 1455 SUP top 1457 Bergeson,Boogert & Nanjundaswamy Internet-Draft 27 1459 LDAP Schema for UDDI February 2005 1461 STRUCTURAL 1462 MUST ( uddiBindingKey ) 1463 MAY ( uddiServiceKey $ 1464 uddiDescription $ 1465 uddiAccessPoint $ 1466 uddiHostingRedirector 1467 uddiCategoryBag $ 1468 uddiv3BindingKey $ 1469 uddiv3ServiceKey $ 1470 uddiv3DigitalSignature $ 1471 uddiv3EntityCreationTime $ 1472 uddiv3NodeId) 1473 ) 1475 5.6 uddiTModelInstanceInfo 1477 This structural object class represents a tModelInstanceInfo. It is 1478 contained by an uddiBindingTemplate. 1480 ( IANA-ASSIGNED-OID.6.6 NAME 'uddiTModelInstanceInfo' 1481 SUP top 1482 STRUCTURAL 1483 MUST ( uddiTModelKey ) 1484 MAY ( uddiDescription $ 1485 uddiInstanceDescription $ 1486 uddiInstanceParms $ 1487 uddiOverviewDescription $ 1488 uddiOverviewURL $ 1489 uddiv3TmodelKey) 1490 ) 1492 5.7 uddiTModel 1494 This structural object class represents a tModel. 1496 ( IANA-ASSIGNED-OID.6.7 NAME 'uddiTModel' 1497 SUP top 1498 STRUCTURAL 1499 MUST ( uddiTModelKey $ 1500 uddiName ) 1501 MAY ( uddiAuthorizedName $ 1502 uddiOperator $ 1503 uddiDescription $ 1504 uddiOverviewDescription $ 1505 uddiOverviewURL $ 1506 uddiIdentifierBag $ 1507 uddiCategoryBag $ 1508 uddiIsHidden 1509 uddiv3TModelKey $ 1511 Bergeson,Boogert & Nanjundaswamy Internet-Draft 28 1513 LDAP Schema for UDDI February 2005 1515 uddiv3DigitalSignature $ 1516 uddiv3NodeId) 1517 ) 1519 5.8 uddiPublisherAssertion 1521 This structural object class represents a publisherAssertion. 1523 ( IANA-ASSIGNED-OID.6.8 NAME 'uddiPublisherAssertion' 1524 SUP top 1525 STRUCTURAL 1526 MUST ( uddiFromKey $ 1527 uddiToKey $ 1528 uddiKeyedReference $ 1529 uddiUUID ) 1530 MAY ( uddiv3DigitalSignature $ 1531 uddiv3NodeId) 1532 ) 1534 The following are object class definitions to model new data 1535 structures needed to implement UDDIv3 information model. These 1536 object class definitions have the �uddiv3� prefix to indicate that 1537 these attributes represent UDDI information model elements unique to 1538 UDDIv3. 1540 5.9 uddiv3Subscription 1542 This structural object class represents a Subscription entity. 1544 ( IANA-ASSIGNED-OID.6.9 NAME 'uddiv3Subscription' 1545 SUP top 1546 STRUCTURAL 1547 MUST ( uddiv3SubscriptionFilter $ 1548 uddiUUID) 1549 MAY ( uddiAuthorizedName $ 1550 uddiv3SubscriptionKey $ 1551 uddiv3BindingKey $ 1552 uddiv3NotificationInterval $ 1553 uddiv3MaxEntities $ 1554 uddiv3ExpiresAfter $ 1555 uddiv3BriefResponse $ 1556 uddiv3NodeId) 1557 ) 1559 5.10 uddiv3EntityObituary 1561 This structural object class represents an Obituary entry for and 1562 stores obituary information for deleted UDDIv3 entities needed for 1563 handling Subscriptions. 1565 Bergeson,Boogert & Nanjundaswamy Internet-Draft 29 1567 LDAP Schema for UDDI February 2005 1569 ( IANA-ASSIGNED-OID.6.10 NAME 'uddiv3EntityObituary' 1570 SUP top 1571 STRUCTURAL 1572 MUST ( uddiv3EntityKey $ 1573 uddiUUID) 1574 MAY ( uddiAuthorizedName $ 1575 uddiv3EntityCreationTime $ 1576 uddiv3EntityDeletionTime $ 1577 uddiv3NodeId) 1578 ) 1580 6. Name Forms 1582 This section defines the required hierarchical structure rules and 1583 naming attributes for the object classes defined in section 6. 1585 Note that OIDs for the structure rules in this document have not 1586 been assigned. All OIDs are in brackets, , as a 1587 placeholder until real OIDs are assigned. 1589 6.1 uddiBusinessEntityNameForm 1591 This name form defines the naming attribute for a businessEntity. 1593 ( IANA-ASSIGNED-OID.15.1 NAME 'uddiBusinessEntityNameForm' 1594 OC uddiBusinessEntity 1595 MUST ( uddiBusinessKey ) 1596 ) 1598 6.2 uddiContactNameForm 1600 This name form defines the naming attribute for a contact. 1602 ( IANA-ASSIGNED-OID.15.2 NAME 'uddiContactNameForm' 1603 OC uddiContact 1604 MUST ( uddiUUID ) 1605 ) 1607 6.3 uddiAddressNameForm 1609 This name form defines the naming attribute for an address. 1611 ( IANA-ASSIGNED-OID.15.3 NAME 'uddiAddressNameForm' 1612 OC uddiAddress 1613 MUST ( uddiUUID ) 1614 ) 1616 6.4 uddiBusinessServiceNameForm 1618 Bergeson,Boogert & Nanjundaswamy Internet-Draft 30 1620 LDAP Schema for UDDI February 2005 1622 This name form defines the naming attribute for a businessService. 1624 ( IANA-ASSIGNED-OID.15.4 NAME 'uddiBusinessServiceNameForm' 1625 OC uddiBusinessService 1626 MUST ( uddiServiceKey ) 1627 ) 1629 6.5 uddiBindingTemplateNameForm 1631 This name form defines the naming attribute for a bindingTemplate. 1633 ( IANA-ASSIGNED-OID.15.5 NAME 'uddiBindingTemplateNameForm' 1634 OC uddiBindingTemplate 1635 MUST ( uddiBindingKey ) 1636 ) 1638 6.6 uddiTModelInstanceInfoNameForm 1640 This name form defines the naming attribute for a 1641 tModelInstanceInfo. 1643 ( IANA-ASSIGNED-OID.15.6 NAME 'uddiTModelInstanceInfoNameForm' 1644 OC uddiTModelInstanceInfo 1645 MUST ( uddiTModelKey ) 1646 ) 1648 6.7 uddiTModelNameForm 1650 This name form defines the naming attribute for a tModel. 1652 ( IANA-ASSIGNED-OID.15.7 NAME 'uddiTModelNameForm' 1653 OC uddiTModel 1654 MUST ( uddiTModelKey ) 1655 ) 1657 6.8 uddiPublisherAssertionNameForm 1659 This name form defines the naming attribute for a 1660 publisherAssertion. 1662 ( IANA-ASSIGNED-OID.15.8 NAME 'uddiPublisherAssertionNameForm' 1663 OC uddiPublisherAssertion 1664 MUST ( uddiUUID ) 1665 ) 1667 6.9 uddiv3SubscriptionNameForm 1669 This name form defines the naming attribute for a Subscription. 1671 ( IANA-ASSIGNED-OID.15.9 NAME 'uddiv3SubscriptionNameForm' 1673 Bergeson,Boogert & Nanjundaswamy Internet-Draft 31 1675 LDAP Schema for UDDI February 2005 1677 OC uddiv3Subscription 1678 MUST ( uddiUUID ) 1679 ) 1681 6.10 uddiv3EntityObituaryNameForm 1683 This name form defines the naming attribute for an Entity Obituary. 1685 ( IANA-ASSIGNED-OID.15.10 NAME 'uddiv3EntityObituary' 1686 OC uddiv3EntityObituary 1687 MUST ( uddiUUID ) 1688 ) 1690 7. DIT Structure Rules 1692 This section defines the required hierarchical structure rules for 1693 the object classes defined in section 6. 1695 Note that rule identifiers defined here show the relationship 1696 between structure rules. Implementations may use different 1697 identifiers but must follow the same hierarchical model. 1699 7.1 uddiBusinessEntityStructureRule 1701 ( 1 1702 NAME 'uddiBusinessEntityStructureRule' 1703 FORM uddiBusinessEntityNameForm 1704 ) 1706 7.2 uddiContactStructureRule 1708 This structure rule defines the object class containment for a 1709 contact. 1711 ( 2 1712 NAME 'uddiContactStructureRule' 1713 FORM uddiContactNameForm 1714 SUP ( 1 ) 1715 ) 1717 7.3 uddiAddressStructureRule 1719 This structure rule defines the object class containment for a 1720 address. 1722 ( 3 1723 NAME 'uddiAddressStructureRule' 1724 FORM uddiAddressNameForm 1725 SUP ( 2 ) 1727 Bergeson,Boogert & Nanjundaswamy Internet-Draft 32 1729 LDAP Schema for UDDI February 2005 1731 ) 1733 7.4 uddiBusinessServiceStructureRule 1735 This structure rule defines the object class containment for a 1736 businessService. 1738 ( 4 1739 NAME 'uddiBusinessServiceStructureRule' 1740 FORM uddiBusinessServiceNameForm 1741 SUP ( 1 ) 1742 ) 1744 7.5 uddiBindingTemplateStructureRule 1746 This structure rule defines the object class containment for a 1747 bindingTemplate. 1749 ( 5 1750 NAME 'uddiBindingTemplateStructureRule' 1751 FORM uddiBindingTemplateNameForm 1752 SUP ( 4 ) 1753 ) 1755 7.6 uddiTModelInstanceInfoStructureRule 1757 This structure rule defines the object class containment for a 1758 tModelInstanceInfo. 1760 ( 6 1761 NAME 'uddiTModelInstanceInfoStructureRule' 1762 FORM uddiTModelInstanceInfoNameForm 1763 SUP ( 5 ) 1764 ) 1766 7.7 uddiTModelStructureRule 1768 ( 7 1769 NAME 'uddiTModelStructureRule' 1770 FORM uddiTModelNameForm 1771 ) 1773 7.8 uddiPublisherAssertion 1775 ( 8 1776 NAME 'uddiPublisherAssertionStructureRule' 1777 FORM uddiPublisherAssertionNameForm 1778 ) 1780 7.9 uddiv3SubscriptionStructureRule 1782 Bergeson,Boogert & Nanjundaswamy Internet-Draft 33 1784 LDAP Schema for UDDI February 2005 1786 ( 9 1787 NAME 'uddiv3SubscriptionStructureRule' 1788 FORM uddiv3SubscriptionNameForm 1789 ) 1791 7.10 uddiv3EntityObituaryStructureRule 1793 ( 10 1794 NAME 'uddiv3EntityObituaryStructureRule' 1795 FORM uddiv3EntityObituaryNameForm 1796 ) 1798 8. Security Considerations 1800 Storing UDDI data into the directory enables the data to be examined 1801 and used outside the environment in which it was originally created. 1802 The directory entry containing the UDDI data could be read and 1803 modified within the constraints imposed by the access control 1804 mechanisms of the directory. With UDDIv3 [UDDIv3], publishers can 1805 digitally sign UDDI Entities enabling registry clients to validate 1806 the integrity of entries read from the UDDIv3 registry by verifying 1807 the digital signature. 1809 Each UDDI Entity has an uddiAuthorizedName attribute which contains 1810 an LDAP DN identifying the publisher/owner. The referenced LDAP 1811 object can provide the public key of the signer to a registry client 1812 for integrity validation of the UDDI Entity. 1814 Other general LDAP [LDAPv3] security considerations apply. Some of 1815 the UDDI attributes like AccessPoints for services may contain 1816 sensitive information. Use of strong authentication mechanisms and 1817 data integrity/confidentiality services [RFC2829][RFC2830] is 1818 advised. 1820 9. IANA Considerations 1822 Refer to RFC 3383, "Internet Assigned Numbers Authority (IANA) 1823 Considerations for the Lightweight Directory Access Protocol (LDAP)" 1824 [RFC3383]. 1826 9.1. Object Identifier Registration 1828 It is requested that the IANA register upon Informational Action an 1829 LDAP Object Identifier for use in this technical specification 1830 according to the following template: 1832 Subject: Request for LDAP OID Registration 1834 Bergeson,Boogert & Nanjundaswamy Internet-Draft 34 1836 LDAP Schema for UDDI February 2005 1838 Person & email address to contact for further information: 1839 Bruce Bergeson (bruce.bergeson@novell.com) 1840 Specification: RFC XXXX 1841 Author/Change Controller: IESG 1842 Comments: 1843 The assigned OID will be used as a base for identifying a number 1844 of UDDI schema elements defined in this document. 1846 9.2. Object Identifier Descriptors 1848 It is requested that the IANA register upon Informational Action the 1849 LDAP Descriptors used in this technical specification as detailed in 1850 the following template: 1852 Subject: Request for LDAP Descriptor Registration Update 1853 Descriptor (short name): see table 1854 Object Identifier: see table 1855 Person & email address to contact for further information: 1856 Bruce Bergeson (bruce.bergeson@novell.com) 1857 Usage: see table 1858 Specification: RFC XXXX 1859 Author/Change Controller: IESG 1860 Table: 1862 The following descriptors have been added: 1864 NAME Type OID 1865 -------------- ---- ------------ 1866 uddiBusinessKey A IANA-ASSIGNED-OID.4.1 1867 uddiAuthorizedName A IANA-ASSIGNED-OID.4.2 1868 uddiOperator A IANA-ASSIGNED-OID.4.3 1869 uddiName A IANA-ASSIGNED-OID.4.4 1870 uddiDescription A IANA-ASSIGNED-OID.4.5 1871 uddiDiscoveryURLs A IANA-ASSIGNED-OID.4.6 1872 uddiUseType A IANA-ASSIGNED-OID.4.7 1873 uddiPersonName A IANA-ASSIGNED-OID.4.8 1874 uddiPhone A IANA-ASSIGNED-OID.4.9 1875 uddiEMail A IANA-ASSIGNED-OID.4.10 1876 uddiSortCode A IANA-ASSIGNED-OID.4.11 1877 uddiTModelKey A IANA-ASSIGNED-OID.4.12 1878 uddiAddressLine A IANA-ASSIGNED-OID.4.13 1879 uddiIdentifierBag A IANA-ASSIGNED-OID.4.14 1880 uddiCategoryBag A IANA-ASSIGNED-OID.4.15 1881 uddiKeyedReference A IANA-ASSIGNED-OID.4.16 1882 uddiServiceKey A IANA-ASSIGNED-OID.4.17 1883 uddiBindingKey A IANA-ASSIGNED-OID.4.18 1884 uddiAccessPoint A IANA-ASSIGNED-OID.4.19 1885 uddiHostingRedirector A IANA-ASSIGNED-OID.4.20 1886 uddiInstanceDescription A IANA-ASSIGNED-OID.4.21 1888 Bergeson,Boogert & Nanjundaswamy Internet-Draft 35 1890 LDAP Schema for UDDI February 2005 1892 NAME Type OID 1893 -------------- ---- ------------ 1894 uddiInstanceParms A IANA-ASSIGNED-OID.4.22 1895 uddiOverviewDescription A IANA-ASSIGNED-OID.4.23 1896 uddiOverviewURL A IANA-ASSIGNED-OID.4.24 1897 uddiFromKey A IANA-ASSIGNED-OID.4.25 1898 uddiToKey A IANA-ASSIGNED-OID.4.26 1899 uddiUUID A IANA-ASSIGNED-OID.4.27 1900 uddiIsHidden A IANA-ASSIGNED-OID.4.28 1901 uddiIsProjection A IANA-ASSIGNED-OID.4.29 1902 uddiLang A IANA-ASSIGNED-OID.4.30 1903 uddiv3BusinessKey A IANA-ASSIGNED-OID.4.31 1904 uddiv3ServiceKey A IANA-ASSIGNED-OID.4.32 1905 uddiv3BindingKey A IANA-ASSIGNED-OID.4.33 1906 uddiv3TmodelKey A IANA-ASSIGNED-OID.4.34 1907 uddiv3DigitalSignature A IANA-ASSIGNED-OID.4.35 1908 uddiv3NodeId A IANA-ASSIGNED-OID.4.36 1909 uddiv3EntityModificationTime A IANA-ASSIGNED-OID.4.37 1910 uddiv3SubscriptionKey A IANA-ASSIGNED-OID.4.38 1911 uddiv3SubscriptionFilter A IANA-ASSIGNED-OID.4.39 1912 uddiv3NotificationInterval A IANA-ASSIGNED-OID.4.40 1913 uddiv3MaxEntities A IANA-ASSIGNED-OID.4.41 1914 uddiv3ExpiresAfter A IANA-ASSIGNED-OID.4.42 1915 uddiv3BriefResponse A IANA-ASSIGNED-OID.4.43 1916 uddiv3EntityKey A IANA-ASSIGNED-OID.4.44 1917 uddiv3EntityCreationTime A IANA-ASSIGNED-OID.4.45 1918 uddiv3EntityDeletionTime A IANA-ASSIGNED-OID.4.46 1919 uddiBusinessEntity O IANA-ASSIGNED-OID.6.1 1920 uddiContact O IANA-ASSIGNED-OID.6.2 1921 uddiAddress O IANA-ASSIGNED-OID.6.3 1922 uddiBusinessService O IANA-ASSIGNED-OID.6.4 1923 uddiBindingTemplate O IANA-ASSIGNED-OID.6.5 1924 uddiTModelInstanceInfo O IANA-ASSIGNED-OID.6.6 1925 uddiTModel O IANA-ASSIGNED-OID.6.7 1926 uddiPublisherAssertion O IANA-ASSIGNED-OID.6.8 1927 uddiv3Subscription O IANA-ASSIGNED-OID.6.9 1928 uddiv3EntityObituary O IANA-ASSIGNED-OID.6.10 1929 uddiBusinessEntityNameForm N IANA-ASSIGNED-OID.15.1 1930 uddiContactNameForm N IANA-ASSIGNED-OID.15.2 1931 uddiAddressNameForm N IANA-ASSIGNED-OID.15.3 1932 uddiBusinessServiceNameForm N IANA-ASSIGNED-OID.15.4 1933 uddiBindingTemplateNameForm N IANA-ASSIGNED-OID.15.5 1934 uddiTModelInstanceInfoNameForm N IANA-ASSIGNED-OID.15.6 1935 uddiTModelNameForm N IANA-ASSIGNED-OID.15.7 1936 uddiPublisherAssertionNameForm N IANA-ASSIGNED-OID.15.8 1937 uddiv3SubscriptionNameForm N IANA-ASSIGNED-OID.15.9 1939 Bergeson,Boogert & Nanjundaswamy Internet-Draft 36 1941 LDAP Schema for UDDI February 2005 1943 where Type A is Attribute, Type O is ObjectClass, Type N is NameForm 1945 Upon Informational Action these assignments will be recorded in the 1946 following registry: 1948 http://www.iana.org/assignments/ldap-parameters 1950 Bergeson,Boogert & Nanjundaswamy Internet-Draft 37 1952 LDAP Schema for UDDI February 2005 1954 10. Normative References 1956 [LDAPv3] Hodges, J. and R. Morgan, "Lightweight Directory Access 1957 Protocol (v3):Technical Specification", Internet 1958 Standard, September 2002, Available as RFC 3377 1960 [RFC2251] Wahl, M., Kille, S. and T. Howes, "Lightweight 1961 Directory Access Protocol (v3)", Internet Standard, 1962 December, 1997. 1964 [RFC2252] Wahl, M., Coulbeck, A., Kille, S. and T. Howes, 1965 "Lightweight Directory Access Protocol (v3): Attribute 1966 Syntax Definitions", Internet Standard, December, 1997. 1968 [UDDI] UDDI.ORG, "UDDI version 2.03 Data Structure Reference," 1969 http://uddi.org/pubs/DataStructure-V2.03-Published- 1970 20020719.htm 1972 [UDDIapi] "UDDI Version 2.04 API Specification", 1973 http://uddi.org/pubs/ProgrammersAPI-V2.04-Published- 1974 20020719.htm 1976 [UDDIv3] UDDI Version 3.0, Published Specification, 19 July 2002 1977 http://uddi.org/pubs/uddi-v3.00-published-20020719.htm 1979 [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate 1980 Requirement Levels," Internet Standard, December, 1997. 1981 Available as RFC2253 1983 [RFC2829] Wahl, M., Alvestrand, H., Hodges, J. and R. Morgan, 1984 "Authentication Methods for LDAP," Internet Standard, 1985 May 2000. 1987 [RFC2830] Hodges, J., Morgan, R. and M. Wahl, "Lightweight 1988 Directory Access Protocol (v3): Extension for Transport 1989 Layer Security," Internet Standard, May 2000 1991 [RFC3383] Zeilenga, K., "Internet Assigned Numbers Authority 1992 (IANA) Considerations for the Lightweight Directory 1993 Access Protocol (LDAP)", BCP 64, RFC 3383, September 1994 2002 1996 [uuid] Paul J. Leach, Rich Salz, "UUIDs and GUIDs", Internet 1997 Draft, February 1998 1999 [XML] Extensible Markup Language (XML) 1.0 (Second Edition) 2000 W3C Recommendation 6 October 2000 2001 http://www.w3.org/TR/REC-xml 2003 [URL] Uniform Resource Locators as defined in 2005 Bergeson,Boogert & Nanjundaswamy Internet-Draft 38 2007 LDAP Schema for UDDI February 2005 2009 T. Berners-Lee et al., "Uniform Resource Identifiers 2010 (URI): Generic Syntax", Internet Standard, August 1998. 2011 Available as RFC 2396. 2012 http://www.ietf.org/rfc/rfc2396.txt 2014 [HTTP] R. Fielding et al.,"Hypertext Transfer Protocol -- 2015 HTTP/1.1", Internet Standard, June 1999. 2016 http://www.w3.org/Protocols/rfc2616/rfc2616.txt 2018 Bergeson,Boogert & Nanjundaswamy Internet-Draft 39 2020 LDAP Schema for UDDI February 2005 2022 11. Author's Addresses 2024 Bruce Bergeson 2025 Novell, Inc. 2026 Mail Stop PRV-H411 2027 1800 S Novell Place 2028 Provo, UT 84606 2030 Phone: +1 801 861 3854 2031 Email: bruce.bergeson@novell.com 2033 Kent Boogert 2034 Novell, Inc. 2035 1800 S Novell Place 2036 Provo, UT 84606 2038 Phone: +1 801 861 3212 2039 Email: kent.boogert@novell.com 2041 Vijay Nanjundaswamy 2042 Novell Software Development (I) Pvt Ltd. 2043 7th Mile, Hosur Road, 2044 Bangalore 560068 2045 India 2047 Phone: +11 9180 573 1858 2048 Email: knvijay@novell.com 2050 Bergeson,Boogert & Nanjundaswamy Internet-Draft 40 2052 LDAP Schema for UDDI September 2004 2054 Intellectual Property Rights 2056 The IETF takes no position regarding the validity or scope of any 2057 Intellectual Property Rights or other rights that might be claimed 2058 to pertain to the implementation or use of the technology described 2059 in this document or the extent to which any license under such 2060 rights might or might not be available; nor does it represent that 2061 it has made any independent effort to identify any such rights. 2062 Information on the procedures with respect to rights in RFC 2063 documents can be found in BCP 78 and BCP 79. 2065 Copies of IPR disclosures made to the IETF Secretariat and any 2066 assurances of licenses to be made available, or the result of an 2067 attempt made to obtain a general license or permission for the use 2068 of such proprietary rights by implementers or users of this 2069 specification can be obtained from the IETF on-line IPR repository 2070 at http://www.ietf.org/ipr. 2072 The IETF invites any interested party to bring to its attention any 2073 copyrights, patents or patent applications, or other proprietary 2074 rights that may cover technology that may be required to implement 2075 this standard. Please address the information to the IETF at ietf- 2076 ipr@ietf.org. 2078 Disclaimer of Validity 2080 This document and the information contained herein are provided on 2081 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 2082 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 2083 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 2084 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2085 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2086 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2088 Copyright Statement 2090 Copyright (C) The Internet Society (2004). This document is subject 2091 to the rights, licenses and restrictions contained in BCP 78, and 2092 except as set forth therein, the authors retain all their rights. 2094 Acknowledgment 2096 Funding for the RFC Editor function is currently provided by the 2097 Internet Society. 2099 Bergeson,Boogert & Nanjundaswamy Internet-Draft 41