The first part of a tutorial on Web 2.0 compared to Web services and Grid systems

1. Web 2.0 in a Web Services and Grid Context Part I: CTS2007 Web 2.0 Tutorial CTS 2007 Embassy Suites Hotel-Lake Buena Vista Resort, Orlando, FL, USA May 25 2007 Geoffrey Fox and Marlon Pierce Computer Science, Informatics, Physics Pervasive Technology Laboratories Indiana University Bloomington IN 47401 [email_address] http:// www.infomall.org

16. APIs/Mashups per Protocol Distribution Number of Mashups Number of APIs REST SOAP XML-RPC REST, XML-RPC REST, XML-RPC, SOAP REST, SOAP JS Other google maps netvibes live.com virtual earth google search amazon S3 amazon ECS flickr ebay youtube 411sync del.icio.us yahoo! search yahoo! geocoding technorati yahoo! images trynt yahoo! local

18. Mash Planet Web 2.0 Architecture http://www.imagine-it.org/mashplanet Display too large to be a Gadget

19. Searched on Transit/Transportation Searched on Transit/Transportation

20. Browser + Google Map API Cass County Map Server (OGC Web Map Server) Hamilton County Map Server (AutoDesk) Marion County Map Server (ESRI ArcIMS) Browser client fetches image tiles for the bounding box using Google Map API. Tile Server requests map tiles at all zoom levels with all layers. These are converted to uniform projection, indexed, and stored. Overlapping images are combined. Must provide adapters for each Map Server type . The cache server fulfills Google map calls with cached tiles at the requested bounding box that fill the bounding box. Google Maps Server A “Grid” Workflow (built in Java!) Uses Google Maps clients and server and non Google map APIs Tile Server Cache Server Adapter Adapter Adapter

21. Indiana Map Grid Workflow/Mashup GIS Grid of “Indiana Map” and ~10 Indiana counties with accessible Map (Feature) Servers from different vendors. Grids federate different data repositories (cf Astronomy VO federating different observatory collections)

28. The Ten areas covered by the 60 core WS-* Specifications WSRP (Remote Portlets) 10: Portals and User Interfaces WS-Policy, WS-Agreement 9: Policy and Agreements WSDM, WS-Management, WS-Transfer 8: Management WSRF, WS-MetadataExchange, WS-Context 7: System Metadata and State UDDI, WS-Discovery 6: Service Discovery WS-Security, WS-Trust, WS-Federation, SAML, WS-SecureConversation 5: Security BPEL, WS-Choreography, WS-Coordination 4: Workflow and Transactions WS-Notification, WS-Eventing (Publish-Subscribe) 3: Notification WS-Addressing, WS-MessageDelivery; Reliable Messaging WSRM; Efficient Messaging MOTM 2: Service Internet XML, WSDL, SOAP 1: Core Service Model Typical Grid/Web Service Examples WS-* Specification Area

29. WS-* Areas and Web 2.0 Start Pages, AJAX and Widgets(Netvibes) Gadgets 10: Portals and User Interfaces Service dependent. Processed by application 9: Policy and Agreements WS-Transfer style Protocols GET PUT etc. 8: Management==Interaction Processed by application – no system state – Microformats are a universal metadata approach 7: System Metadata and State http://www.programmableweb.com 6: Service Discovery SSL, HTTP Authentication/Authorization, OpenID is Web 2.0 Single Sign on 5: Security Mashups, Google MapReduce Scripting with PHP JavaScript …. 4: Workflow and Transactions (no Transactions in Web 2.0) Hard with HTTP without polling – JMS perhaps? 3: Notification No special QoS. Use JMS or equivalent? 2: Service Internet XML becomes optional but still useful SOAP becomes JSON RSS ATOM WSDL becomes REST with API as GET PUT etc. Axis becomes XmlHttpRequest 1: Core Service Model Web 2.0 Approach WS-* Specification Area