SOAP, UDDI, Web Services, andthe Semantic Web

Justin R. Erenkrantz

ICS 221

December 3rd, 2002

Web Services

• Identified by URI, HTTP, and XML

• Making websites more than content

• Enabling extensible interactions

• Ideally public, perhaps private– Commercial web services

SOAP

• W3C’s Simple Object Access Protocol

• XML-centric middleware data format

• Origins from simpler XML-RPC

• Nodes, roles, faults

• Typically bound to HTTP– Interesting architectural mismatches

UDDI

• Universal Description Discovery and Integration

• Acts as a naming service for Web Services

• Built on top of SOAP

• Distributed repositories

• Publish/subscribe support– SOAP callbacks

Semantic Web

• “Crown Jewel”

• Meaningful interpretation of web content

• Not just interactions, but understanding

• Each semantic web site agrees on meaning

• Effects of non-participation