Part 2 of a 4 part series exploring Web 2.0 and the Geoweb. This short series of lectures is part of the "Introduction to Geoweb" course offered at the University of Colorado at Denver. Previous experience with generic web architectures and http is assumed. Full context is available at http://blog.gishacks.com/2009/08/web-20-and-geoweb-part-2-web-20.html.

1. Web 2.0 PatternsShaping the Geoweb Introduction to the Geoweb Gregory L. Gunther University of Colorado at Denver

2. Common Web 2.0 Patterns Influencing the Geoweb Service Oriented Architecture (SOA) Software as a Service (SaaS) Participation-Collaboration Asynchronous Particle Update Mashup Rich User Experience Collaborative Tagging Structured Information Formulated By Real Examples….

3. Pattern Formulation Pattern Context Derived Requirements Problem Business problem (story) Context Generalized Specifications, static structure, dynamic behavior Consequences References Business problem resolved Implementations Known use (Govenor et al. 2009)

4. Service Oriented Architecture “is an architectural paradigm, a way of architecting a framework for matching needs and capabilities. A key feature of SOA is support for integrating services that are owned and managed independently” (OASIS 2006) No single definition (ubiquitous, depends on context) Standardized framework or software architecture which implements interoperable software components (web services) SOA brings a new way to look at applications Separates messages from processing Provides consistent platform for interoperability (Govenor et al. 2009)

6. Reusable, modular

7. Facilitates integration, eliminates stovepipe barriers

8. Not just technology(King, 2006, ESRI 2007)

10. Classic SOA Reference Model SOAP and WSDL (King, 2006)

11. SOA Dynamic Behaviors Refined Request/Response Via Registry Subscribe/ Push Probe/Match (Govenor et al. 2009)

12. Quick Word On SOAP “is a protocol for exchanging XML-based messages over computer networks, normally using HTTP. SOAP forms the foundation layer of the Web services stack, providing a basic messaging framework that more abstract layers can build on” Envelope Format: A way of putting data into an envelope “Big Web Services”

13. SOA Implementation (SOA Tag Cloud, 2009)

14. REST (Richardson, 2007. Govenor et al. 2009) HTTP XML/JSON/GeoRSS Resource Oriented Architectures Mashups Asynchronous Particle Update

15. Software as a Service (SaaS) Rules Collector Client Spam Filtering Software Client Email Client (Govenor et al. 2009)

16. Web GIS and the Cloud http://www.esri.com/events/uc/images/workshops/cloud.html The web IS the platform (Morehouse et al. 2009)

17. Participation-Collaboration

18. (Govenor et al. 2009)

19. Asynchronous Particle Update (AJAX) Length of time Blocked from further Input Time Network Latency Problem (Crane et al. 2006)

20. Concepts related to software usability Based on usability expert Alan Cooper Transient: used everyday but only in short burst and often as a secondary activity Delays are tolerated Examples File System manager Amazon Search Engines Sovereign: requires users full attention Used more intensely Desktop applications Delays become intolerable (2 second delay each time you type a letter in a Word Processor Sovereign and Transient Usage Patterns (Crane et al. 2006)

21. Web Application LifeCycle Just Views Of the User and Application Data Model Traditional Initial Data And Application Download (Crane et al. 2006)

22. (Crane et al. 2006)

23. (Crane et al. 2006)

24. Mashup

25. Web Browser www.google.com CSS Styling (If Applicable) Web Server (www.gishacks.com) DOM JavaScript Logic Map Data XML Data GXmlHttp XML HTTP Request (AJAX) Mashup

26. User gishacks server google server Request Page API Map Data XML Data Return Page Page Loaded Request and Get XML Request and Get Map

27. Rich Internet Application ADOBE FLEX JavaFX MS Silverlight Flex 3 Component Explorer: http://tinyurl.com/2o78vd

28. Collaborative Tagging “users add metadata in the form of keywords to shared content “

29. Structured Information POSH Semantic XHTML vCard MICROFORMATS hCard GEO hCalendar (Microformat. 2009)

30. Additional Patterns Constant Beta The Synchronized Web Declarative Living and Tag Garderning Semantic Web Grounding Persistent Rights Management

31. Conclusions Bottom-up prevails while top down does not. REST vs SOAP Folksonomyvs Taxonomy Crowdsourced vs. traditional media Time Magazine person of theYear 2006— You! Systems get better the more people use them The web is the system platform Persistence of Web 2.0 Architectures and platforms where people can participate beat websites Plug-in business models Simplicity and scalability Agility Ease of use Security and privacy

32. Web 2.0 and the Geoweb Web as platform Continuous improvement Lightweight programming models and techn0logies Immersive (social, RIA) YOU Geoweb GIS 2.0 Law 2.0 Gov 2.0 Library 2.0 Media 2.0 (Govenor et al. 2009)

33. References Cited Crane, Dave, Eric Pascarello and Darren James (2006). AJAX in Action. Connecticut: Manning Publishing. ESRI. (2007). Geospatial Service Oriented Architectures. ESRI Whitepaper. http://www.esri.com/library/whitepapers/pdfs/geospatial-soa.pdf Governor, James, Dion Hunchcliffe and Duane Nickull (2009). Web 2.0 Architectures. California: O’Reilly Media Inc. King, JJ. SOA What? Introduction to Service Oriented Architecture. Rocky Mountain Oracle Users Group. Denver, 2006.

34. References Cited Microformat. (2009, August 13). In Wikipedia, The Free Encyclopedia. Retrieved 07:50, August 13, 2009, from http://en.wikipedia.org/w/index.php?title=Microformat&oldid=307705991 Morehouse, Scott, Gorter, Dirk and Brenda Wolfe. 2009, Taking Advantage of The Cloud, ESRI 2009 International Users Conference, San Diego, CA, San Diego Convention Center. OASIS. (2006). Reference Model for Service Oriented Architecture 1.0.http://www.oasis-open.org/committees/download.php/19679/soa-rm-cs.pdf Richardson, Leonard, Ruby,Sam (2007). RESTful Web Services California: O’Reilly Media Inc. SOA Tag Cloud. Swik.com. 09 August 2009 http://swik.net/SOA?tagCloud.