B2B Integration : A Practical Guide to Collaborative E-commerce

More documents

Recommendations

Info

Appendix B 521 Note: Only parts of the paper have been reproduced verbatim here. The contents have been formatted to be consistent with the book style. Technical Overview The Universal Description, Discovery and Integration (UDDI) specifications consist of an XML schema for SOAP messages, and a description of the UDDI API specification. Together, these form a base information model and interaction framework that provides the ability to publish information about a broad array of Web services. Four Information Types The core information model used by the UDDI registries is defined in an XML schema. XML was chosen because it offers a platform-neutral view of data and allows hierarchical relationships to be described in a natural way. The emerging XML schema standard was chosen because of its support for rich data types as well as its ability to easily describe and validate information based on information models represented in schemas. The UDDI XML schema defines four core types of information that provide the kind of information that a technical person would need to know in order to use a partner's Web services. These are: business information; service information, binding information; and information about specifications for services. The information hierarchy and the key XML element names that are used to describe and discover information about Web services are shown in Figure 1. Business Information: The businessEntity Element Many partners will need to be able to locate information about your services and will have as starting information a small set of facts about your business. Technical staff, programmers or application programs themselves will know either your business name or perhaps your business name and some key identifiers, as well as optional categorization and
522 B2B Integration — A Practical Guide to Collaborative E-commerce BusinessEntity: Information about the party who publishes information about a service businessService: Descriptive information about a particular family of technical services M bindngTempi ate: Technical information about a service entry point and construction ^Dedications Figure 1. — | tModei: Descriptions of specifications ' fo r se rvices o r taxon om i es. Ba sis for techn ica I fi n gerp rints bindingTemplate data contains references totModels, These references designate the interface specifieationsfor a service. contact information. The core XML elements for supporting, publishing and discovering information about a business — the UDDI Business Registration — are contained in a structure named 'businessEntity.' This structure serves as the top-level information manager for all of the information about a particular set of information related to a business unit. The overall businessEntity information includes support for 'yellow pages' taxonomies, so that searches can be performed to locate businesses who service a particular industry or product category, or who are located within a specific geographic region. Service Information: The businessService and bindingTemplate Elements Technical and business descriptions of Web services — the 'green pages' data — live within substructures of the businessEntity information. Two structures are defined: businessService and bindingTemplate. The businessService structure is a descriptive container that is used to group a series of related Web services related to either a business process or category of services. Examples of business processes that would include related Web service information include purchasing services, shipping services, and other high-level business processes.
Page 1 and 2:
nioioimuc;./! 1011 1 1 .«.•.«!
Page 3 and 4:
This page is intentionally left bla
Page 5 and 6:
Published by Imperial College Press
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
xii B2B Integration — A Practical
Page 15 and 16:
xiv B2B Integration — A Practical
Page 17 and 18:
xvi B2B Integration — A Practical
Page 19 and 20:
xviii B2B Integration — A Practic
Page 21 and 22:
xx B2B Integration — A Practical
Page 23 and 24:
xxii B2B Integration — A Practica
Page 25 and 26:
xxiv B2B Integration — A Practica
Page 27 and 28:
xxvi B2B Integration — A Practica
Page 29 and 30:
xxviii B2B Integration — A Practi
Page 31 and 32:
xxx B2B Integration — A Practical
Page 33 and 34:
xxxii B2B Integration — A Practic
Page 35 and 36:
xxxiv B2B Integration — A Practic
Page 37 and 38:
xxxvi B2B Integration — A Practic
Page 39 and 40:
xxxviii B2B Integration — A Pract
Page 41 and 42:
Page 43 and 44:
4 B2B Integration — A Practical G
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
10 B2B Integration — A Practical
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Chapter 2 Components, Benefits, Cha
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Chapter 4 Enterprise Application In
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Chapter Q Extensible Markup Languag
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Chapter Q Integration Brokers The f
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Chapter "] 2 Wireless Technologies
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Company Brience Everypath GadgetSpa
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Page 453 and 454:
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Page 463 and 464:
Page 465 and 466:
Page 467 and 468:
Page 469 and 470:
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Chapter "] 5 E-Marketplaces and Col
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Page 495 and 496:
Page 497 and 498:
Page 499 and 500:
Page 501 and 502:
Page 503 and 504:
Page 505 and 506:
Page 507 and 508:
Page 509 and 510: 470 B2B Integration — A Practical
Page 525 and 526: This page is intentionally left bla
Page 559: 520 B2B Integration — A Practical
Page 589: This comprehensive guide reveals th
show all

B2B Integration : A Practical Guide to Collaborative E-commerce

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?