The document discusses the concept of Web 2.0, defined as a network-driven platform enhancing collaboration and user participation through continuously updated services. It emphasizes the importance of interoperability in Web 2.0, which allows diverse systems and users to connect and exchange information effectively. Furthermore, it outlines various architectural models, tools, and examples that illustrate the transition from traditional web applications to more interactive and collaborative web services.

1. Web 2.0 ExamplesInfluencing the GeowebIntroduction to the GeowebGregory L. GuntherUniversity of Colorado at Denver

3. (Karp 200 7)

4. Tim O’Reilly Definition of Web2.0 I said I'm not fond of definitions, but I woke up this morning with the start of one in my head: Web 2.0 is the network as platform, spanning all connected devices; Web 2.0 applications are those that make the most of the intrinsic advantages of that platform: delivering software as a continually-updated service that gets better the more people use it, consuming and remixing data from multiple sources, including individual users, while providing their own data and services in a form that allows remixing by others, creating network effects through an "architecture of participation," and going beyond the page metaphor of Web 1.0 to deliver rich user experiences. (O’Reilly, 2005)

5. I define Web 2.0 as the design of systems that harness network effects to get better the more people use them, or more colloquially, as “harnessing collective intelligence.” This includes explicit network-enabled collaboration, to be sure, but it should encompass every way that people connected to a network create synergistic effects.(Carpenter 2008)

7. Before We Proceed!InteroperabilityWebservicesInternet as a platform (foundation of web 2.0)Models and Patterns

8. InteroperiblityInteroperability: is connecting people, data and diverse systems. The term can be defined in a technical way or in a broad way, taking into account social, political and organizational factors.System specific: “the ability to exchange and use information across a large, heterogeneous network made up of several local information system nodes.” Semantic Interoperability: is the ability of two or more computer systems to exchange information and have the meaning of that information accurately and automatically interpreted by the receiving system.(Interoperability, 2009)

9. Achieving InteroperabilityWeb 1.0JDBC, CORBA, DCOMWeb 2.0Coarse GrainedXML encoded address vs. individual method calls (CORBA and DCOM)More close alignment with business process, not its partsLoosely CoupledPlug and PlayEnterprise data models can change but won’t break applicationsMessage basedWeb ServicesXML, WMS, WFS

10. WebservicesBased on the broad acceptance of XML for data encoding, transport and messagingMicrosoft Definition“Web services are applications that use standard transports, encodings, and protocols to exchange information. With broad support across vendors and businesses, Web services enable computer systems on any platform to communicate over corporate intranets, extranets, and across the Internet with support for end-to-end security, reliable messaging, distributed transactions”W3C Definition“software system designed to support interoperable Machine to Machine interaction over a network. Web services are frequently just application programming interfaces (API) that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services. “(Webservices, 2009)

11. Why WebservicesServices are reusable units providing business functionality that are:Clearly defined using standard policies, practices, and frameworksClearly described (xml)AutonomousAbstractions of the underlying business logic and functionalityActual overlay process not necessaryEasy to understand: one party delivers a service according to a contract with the other party(King, 2006)

12. Is Everything On the Web A WebserviceNO!The WWW provides mechanism for people and organizations to share information Many web pages provide “services” to the user that are supported by a variety of software, most of this functionality is not currently created with Web ServicesBuilt on the same basic standards

13. The Internet Is The Foundation of Web 2.0

14. Patterns and ModelsTools for building system architectures and future system implementationsAbstract, durable and can be repurposed across domainsPattern FormulationUsers can click on features within an ArcIMS website to obtain attribute DataAn entity obtains information about geographic features online(Govenor et al. 2009)

15. Pattern FormulationPatternContextDerived RequirementsProblemBusiness problem (story)ContextGeneralizedSpecifications, static structure, dynamic behaviorConsequencesReferencesBusiness problem resolvedImplementationsKnown use(Govenor et al. 2009)

16. Reference ModelModelABCDEGFH

17. Models, Patterns, Architectures: Oh My!(OASIS, 2006)

18. Tim O’s List of 1.0 vs. 2.0 ExamplesO’Reilly, 2005)

19. DoubleClick AdSense

20. Ofoto or SnapFish Flickr

21. Personal Websites  BlogsHTML with contentIntended for specific groups (family and friends)1 way communication (no comments)HTML with content but also feed (RSS)Intended for wider communitiesMuch easier to find (search engines, blog crawlers, aggregators) because of feedEncourage community participation (comments)Community affiliation with BlogRoll

22. Screenscaping WebservicesContext of data integration“Crawling” web pages for dataIntegration of webpagesUnstructured Structured and predictableContent is data oriented, not presentationBased on open standardsIntegration is the goal, not a hack

23. Taxonomies  FolksonomiesYahoo DirectoryTag Cloud

24. GeographyNetwork/USGS GeodeArcGIS Online/WeoGeo

25. ArcIMS ArcGIS Server

26. Modeling Web 2.0UsersClient applications/runtimesConnectivity/reachabilityServicesCapabilities(Govenor et al. 2009)

27. Web 2.0 Reference ArchitectureClient application tierStandards protocolsService tierResource tier(Govenor et al. 2009)

28. Client TierControllerState managementSecurityVirtual machineRenderingCommunication(Govenor et al. 2009)

29. Service TierService provider interfaceBusiness logicInvocation layer(Govenor et al. 2009)

30. Resource TierDatabaseFile systemLegacy systems(Govenor et al. 2009)

31. Common Web 2.0 Patterns Influencing the GeowebService Oriented Architecture (SOA)Software as a Service (SaaS)Participation-CollaborationAsynchronous Particle UpdateMashupRich User ExperienceCollaborative TaggingStructured InformationFormulated By Real Examples….

32. References CitedCarpenter, Hutch. Tim O’Reilly Course Corrects the Definition of Web 2.0. Weblog entry. I’m Not Actually A Geek. October 1, 2008. http://bhc3.wordpress.com/2008/10/01/tim-oreilly-course-corrects-the-definition-of-web-20/. Governor, James, Dion Hunchcliffe and Duane Nickull (2009). Web 2.0 Architectures. California: O’Reilly Media Inc.Interoperability. Wikipedia, The Free Encyclopedia. 7 Aug 2009, 10:13 UTC. 7 Aug 2009 http://en.wikipedia.org/w/index.php?title=Interoperability&oldid=306573452.Karp, David. A Web 2.0 Tag Cloud. Weblog entry. A TangieSlice of Web 2.o. September 25, 2007. http://tangyslice.wordpress.com/2007/09/25/a-web-20-tag-cloud/. King, JJ. SOA What? Introduction to Service Oriented Architecture. Rocky Mountain Oracle Users Group. Denver, 2006.

33. References CitedOASIS. (2006). Reference Model for Service Oriented Architecture 1.0.http://www.oasis-open.org/committees/download.php/19679/soa-rm-cs.pdfO'Reilly, Tim. Web 2.o: Compact Definition. Weblog entry. O’Reilly Radar. October 2005. http://radar.oreilly.com/archives/2005/10/web-20-compact-definition.html.Web service. Wikipedia, The Free Encyclopedia. 7 Aug 2009, 18:12 UTC. 7 Aug 2009 http://en.wikipedia.org/w/index.php?title=Web_service&oldid=306643330.