1. LICGF, UW-MadisonGIScience 2008 Design of Web 2.0/3.0 and SOA for Geospatial Science: Mashups for Fun and Profit! Nancy Wiegand Land Information and Computer Graphics Facility University of Wisconsin – Madison Talk given in conjunction with Brand Niemann, EPA With input also from AJ Wortley, Wisconsin State Cartographer’s Office For the Design of Service-Oriented Architecture (SOA) for Geospatial Science Workshop September 23, 2008

2. LICGF, UW-MadisonGIScience 2008 Overview 1. Introduction 2. Web 2.0/3.0 3. SOA and WOA 4. Mashups 5. Demonstration/Screen Shots 6. Other uses of MindTouch Deki Wiki by the EPA

3. LICGF, UW-MadisonGIScience 2008 1. Introduction An example Wiki and SOA platform (MindTouch Deki Wiki) is presented to show state of the art technology and how it can be used. Example content focuses on the GIScience conference and the SOA workshop.

4. LICGF, UW-MadisonGIScience 2008 1. Introduction Composite applications and data mashups have been created in a state-of-the-art Web 2.0/3.0 Wiki and will be demonstrated as part of this presentation.

5. According to Dario de Judicibus, “Web 2.0 is a knowledge-oriented environment where Human interactions generate content that is published, managed and used through Network applications in a service-oriented architecture.”

6. LICGF, UW-MadisonGIScience 2008 2. Web 2.0/3.0 Web 2.0 (Collaboration) and Service Oriented Architecture (SOA) have come together recently. Web 2.0 facilitates collaboration. SOA enables the infrastructure for flexibility. Web 3.0 (Semantic or Data Web) enables mashups to create Web applications, integrated Web experiences, and expanded customer value networks.

7. Web 2.0 Content Services: Blog content, web surveys, photo sharing, video sharing, social networking sites, locations, and maps.

8. 2. Web 2.0/3.0

9. LICGF, UW-MadisonGIScience 2008 2. Web 2.0/3.0 The first stage, Web 1.0, was about connecting information and getting on the net. Web 2.0 is about connecting people — putting the “I” in user interface, and the “we” into a web of social participation. The next stage, Web 3.0, is starting now. It is about representing meanings, connecting knowledge, and putting them to work in ways that make our experience of internet more relevant, useful, and enjoyable. Web 4.0 will come later. It is about connecting intelligences in a ubiquitous web where both people and things can reason and communicate together.

10. LICGF, UW-MadisonGIScience 2008 3.0 SOA Service-oriented architecture (SOA) -- method for systems development and integration where functionality is grouped around business processes and packaged as interoperable services. SOA also describes IT infrastructure which allows different applications to exchange data with one another as they participate in business processes. The aim is a loose coupling of services with operating systems, programming languages and other technologies which underlie applications. Source: WikipediaWikipedia

11. LICGF, UW-MadisonGIScience 2008 3.0 SOA SOA separates functions into distinct units, or services, which are made accessible over a network in order that they can be combined and reused in the production of business applications. These services communicate with each other by passing data from one service to another or by coordinating an activity between two or more services. Source: WikipediaWikipedia

12. LICGF, UW-MadisonGIScience 2008 3.0 WOA Web Oriented Architecture is “an architectural style that is a substyle of SOA based on the architecture of the World Wide Web.” “The only real difference between traditional SOA and the concept of WOA is that WOA advocates REST, an increasingly popular, powerful, and simple method of leveraging HTTP as a Web service in its own right”. ZapThink believes that the term Web-Oriented SOA represents greater clarity than WOA, since it disambiguates the desire to position WOA as an alternative to SOA as well as more accurately positions the concept at a lower level of abstraction than the SOA concept. Source: ZapthinkZapthink

13. LICGF, UW-MadisonGIScience 2008 4. Mashups

14. LICGF, UW-MadisonGIScience 2008 4. Mashups A mashup is a merging of services and content from multiple Web sites in an integrated, coherent way. Mashups are created when different application program interfaces (API) are combined or 'mashed' to create an entirely new application.

15. LICGF, UW-MadisonGIScience 2008 4. Mashups Mashups often combine internal sources, such as enterprise data, with external Web resources such as Google Maps. Mashups typically add value on top of the individual services used.

17. LICGF, UW-MadisonGIScience 2008 4. Mashups Mashups are the fastest growing enterprise ecosystem on the Web. Mashups are social, role-based, and network-centric and used in knowledge-based networks, models, and businesses. They enhance customer experience, drive productivity and innovation, and achieve fundamental advancements in knowledge economy competitiveness. Stakeholders (customers, employees, suppliers and others) gain enormous benefits using enterprise mashups to create new applications and expand customer value networks. –Source: Open Enterprise 2.0 Mashup Summit - Expanding Customer Value Networks http://www.vncluster.com/muny.htm

18. 4. Mashups Source: ProgrammableWeb.comProgrammableWeb.com Mashup Timeline - New mashups in the last 6 months

19. 4. Mashups http://www.programmableweb.com/tag/mapping

20. LICGF, UW-MadisonGIScience 2008 5.0 Demonstration/Screen Shots Here is a example of a Web 2.0 Wiki, based on WOA that gives a practical demonstration.

21. 5.0 GIScience.wik.is http://giscience2008.wik.is/

22. Concept Definition Specific Example Comments Structure and Interface Next Slide

24. SICoP SOCoP Slide after

27. LICGF, UW-MadisonGIScience 2008 Spatial Ontology Community of Practice Agenda for 6th SOA for E-Gov Conference, September 29-30, 2008: –A 10 minute introduction to the session, a brief description and an overview of the geospatial domain and its centrality as an area for IT services. –Following this we will have a major 45 minute presentation speaking on "Spatial Ontologies and Semantics - tools to enable the NSDI and enhance the use and understanding of data services. –The third part is a 30 minute panel discussion (4-5 members) of variety of key topics. A preliminary list of these include Geo- semantics and Interoperability for Spatial Data and Technology, Ontology and Service Repositories, The SOA Value Proposition for Spatial Ontologies and Incorporating Semantics into Geospatial Standards. –Q & A session. http://federalsoa.wik.is/#Spatial_Ontology_Community_of_Practice

28. LICGF, UW-MadisonGIScience 2008 5.0 Demonstration 5.1 Mindtouch Deki Wiki Features 5.2 Mindtouch Deki Wiki Architecture 5.3 Tutorial outline 5.4 Mapping Extensions 5.5 Google Maps

29. LICGF, UW-MadisonGIScience 200829 5.1 MindTouch Deki Wiki Features Content Creation: –An editing experience similar to what you would expect from modern word processor applications. Content Management: –Hierarchical page organization: Organize content in an intuitive hierarchical manner Search: –Advanced search: User can view all results or only specific subsets of the result set Attachments: –Users can attach any file or image to any page. Versioning and Reversion: –Page versioning: Every page retains a complete history of changes.

30. LICGF, UW-MadisonGIScience 200830 5.1 MindTouch Deki Wiki Features Access Control: –Restrict page editing, Restrict page viewing, Restrict hierarchies Alerts and Notifications: –Watch list Feeds: Every user can create a list of pages to watch. Application Administration: –Site administration: Quickly and easily manage multiple users and users' status Miscellaneous: –Adherence to standards: All content is stored in XML.

31. 5.2 MindTouch Deki's Software Architecture http://wiki.mindtouch.com/MindTouch_Deki/Features/Architecture

32. 5.2 MindTouch Deki's Software Architecture http://wiki.mindtouch.com/MindTouch_Deki/Features/Architecture

33. LICGF, UW-MadisonGIScience 2008 5.3 GIScience.wik.is Tutorial Basic Steps in Tutorial:Tutorial –1: Decide on Name –2: Register Name –3: Login –4: Set Preferences –5: Control Panel –6: Design Home Page –7: Create Subtopics –8: Repurpose Word and Web Content Into Wiki –9: Attach Files –10: Insert Images and Links –11: Create Web Log (Blog) –12: Set Security –13: Monitor Users –14: Revise/Reorganize

34. LICGF, UW-MadisonGIScience 2008 5.4 Mapping Extensions Deki supports lots of extensions, features which allow embedding content from other websites, e.g., embed Google Maps, Windows Live Maps, AND Yahoo! Maps, all on the same page.extensionsGoogle MapsWindows Live MapsYahoo! Maps Images can also be dynamically manipulated using the ImageMagick extension.ImageMagick extension There's so much that can be done. Learn about available extensions in a Deki by clicking the "Extensions List" tab (when the editor loads) or by viewing the Extensions page at the MindTouch Developer CenterExtensions page at the MindTouch Developer Center

35. 5.5 Google Maps http://wiki.developer.mindtouch.com/MindTouch_Deki/Extensions/Google

36. 5.5 Google Maps http://wiki.mindtouch.com/MindTouch_Deki/Demo_Galleryhttp://wiki.mindtouch.com/MindTouch_Deki/Demo_Gallery - see last 2- minutes

37. LICGF, UW-MadisonGIScience 2008 6. How the EPA is using MindTouch Deki Wikis EPA Deki Pilot Wikis at http://semanticommunity.net (next slides) http://semanticommunity.net Other EPA uses at http://www.epa.gov/nationaldialogue/ (just starting to use Media Wiki for internal projects)

38. http://semanticommunity.net SICOP

39. Next 4 slides

40. EPA Data Architecture Wiki: Tutorial Brand Niemann Senior Enterprise Architect EPA Enterprise Architecture Team April 1, 2008, Updated April 12, 2008

41. Preface Our Metadata COI expressed a need to stand-up a web- based collaboration tool that would be easily accessible to members outside EPA's firewall. Specifically, there are members of our COI that are contractors working on multiple task orders and/or working on projects of our EPA COI members that we have not been able to access materials posted behind our EPA fire-wall. Interim solutions considered include standing-up (for fee) a series of pages on internet sites on a contractor's web- site to be maintained by others or use CORE.GOV under the Data Architecture Subcommittee internet site. Both of these options were deemed problematic because we would not be able to easily maintain our collab space without going through a third-party system administrator.

42. Preface In a nutshell we needed a site that provides the following functionality: –Requirements: Easily accessible both inside and outside the EPA firewall. Agile enough to post content and track comments posted to content. Secure enough to have an effective gate-keeping aspect whereby we can allow access on an individual or identified group list basis. Be able to administer our own site. –Participants invited/allowed to access our site: EA Team and management chain. EAWG. EPA Metadata COI. Interested individuals invited and granted access. –Accessibility controls: Ability to allow access inside or outside the EPA firewall. Ability to lock-down any part/page of our Wiki.

43. Step 1: Decide on Name, etc. http://wik.is/

44. LICGF, UW-MadisonGIScience 2008 Summary One of the exciting and promising aspects of the technology presented here is to be able to do mashups (i.e., integrate Web Services) directly in a Wiki. That is, the Wiki platform becomes a SOA. Further, just one technology platform enables collaboration of many forms—text, attach files, mashups

45. LICGF, UW-MadisonGIScience 2008 Summary Brand suggests the GIScience community could use this technology, say, for the conference and/or workshops, to post agendas, talks, papers, etc. He suggested I use it for the upcoming Terra Cognita workshop, which brings together the GIScience and Semantic Web communities, at the International Semantic Web Conference (ISWC).

46. LICGF, UW-MadisonGIScience 2008 Summary Again, one of the purposes of this talk is to promote collaboration between: the GIScience Community and those involved in the Federal Geospatial Line of Business and the Federal SOA, Along with those in the Semantic Interoperability and Spatial Ontology Communities of Practice (SICoP & SOCoP) (represented Brand Niemann and Nancy Wiegand, respectively).

47. LICGF, UW-MadisonGIScience 2008 Thank you, The End! Nancy Wiegand wiegand@cs.wisc.edu