Design of Web 2.0/3.0 and SOA for Geospatial Science: Mashups for Fun and Profit!

1. 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. 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 • 7. Spatial Ontology Community of Practice (SOCoP)

3. 1. Introduction • An example Web 2.0/3.0 Wiki that is also a SOA platform (MindTouch Deki Wiki) is presented to show state of the art technology and how it can be used. • Composite applications and data mashups have been created and will be demonstrated. • Brand set up example Wiki content for the SOA workshop as a way to demonstrate its use.

4. Example Geospatial Data

5. Geographic Information Systems

6. Internet Mapping Site

7. Example of a Mashup Using Google Maps

8. Google Earth

9. 2. Web 2.0/3.0

10. 2. Web 2.0 • Web 2.0 facilitates collaboration. • Web 2.0 and Service Oriented Architecture (SOA) have come together recently. • SOA enables the infrastructure for flexibility.

11. http://web2.wsj2.com

12. 2. Web 2.0/3.0

13. 2. Web 2.0/3.0 • Web 1.0 -- connecting information and getting on the net. • Web 2.0 -- connecting people — putting the “I” in user interface, and the “we” into a web of social participation. • Web 3.0, starting now -- representing meanings, connecting knowledge, and putting them to work to make the Internet more relevant, useful, and enjoyable. • Web 4.0, will come later -- connecting intelligences in a ubiquitous web where both people and things can reason and communicate together.

14. 3.0 SOA • Service-oriented architecture (SOA) -- method for systems development and IT infrastructure • Functionality is grouped around business processes and packaged as interoperable services. • Allows different applications to exchange data with one another • The aim is a loose coupling of services with operating systems, programming languages and other technologies which underlie applications. Source: Wikipedia

15. 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: Zapthink

16. 4. Mashups • Web 2.0/3.0 (Semantic or Data Web) enables mashups to create Web applications, integrated Web experiences, and expanded customer value networks.

17. 4. Mashups Low Barrier, High Velocity Integration: Using the Strengths of the Web to Remix and Connect our Content and Functionality from Anywhere to Anywhere Else.

18. 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.

19. 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. • Typically created by “the community” and not by original software developers

21. 4. MashupsOpen Enterprise 2.0 Mashup Summit – Expanding Customer Value Networks (Feb. 1, 2008)http://www.vncluster.com/muny.htm • Mashups are the fastest growing enterprise ecosystem on the Web. • Social, role-based, and network-centric. • 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 • Create new applications • Expand customer value networks

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

23. 5.0 Demonstration/Screen Shots • Here is a example of a Web 2.0/3.0 Wiki, based on WOA that gives a practical demonstration. • Uses MindTouch Deki Wiki • Free and open source

24. 5.0 giscience2008.wik.is http://giscience2008.wik.is/

25. Structure and Interface Concept Definition Specific Example Comments Next Slide http://giscience2008.wik.is/

27. Next Slide SICoP SOCoP Slide after http://giscience2008.wik.is/

30. 8: Repurpose PDF Document Into Wiki http://giscience2008.wik.is/GIScience_2008_Meeting%2c_September_23-26%2c_2008

31. 5.0 MindTouch Information • 5.1 Mindtouch Deki Wiki Features • 5.2 Mindtouch Deki Wiki Architecture • 5.3 Tutorial outline • 5.4 Mapping Extensions • 5.5 Google Maps

32. 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. 32

33. 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. 33

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

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

36. 5.3 GIScience.wik.is Tutorial • Basic Steps in 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

37. 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. • Images can also be dynamically manipulated using the 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 Center

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

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

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

42. From Brand Niemann April 2008 Tutorial 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.

43. From Brand Niemann April 2008 Tutorial 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.

44. giscience2008.wik.is http://giscience2008.wik.is/

45. Additional Purpose of the Talk • 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).

46. 7. Spatial Ontology Community of Practice (SOCoP) • SOCoP was developed because of: • Recognition of the semantic interoperability component of geospatial data • Realization of the potential of ontologies and formal representations to help solve semantic heterogeneity in geospatial data • SOCoP officially began in Oct. 2006 after a June meeting at the National Science Foundation

47. 7. Spatial Ontology Community of Practice (SOCoP) Purpose: “Tofoster collaborationamong researchers, technologists, & users ofspatial knowledge representations and reasoning,towards thedevelopment of spatial ontologiesfor use by all in theSemantic Web” • Co-Chairs: • Kevin Backe, Topographic Engineering Center, US Army Corps of Engineers • John Moeller, Northrop Grumman Information Technology • Executive Secretariat: • Gary Berg-Cross, Engineering, Management and Integration (EM&I) • Membership in SOCoP is open to anyone

48. 7. Spatial Ontology Community of Practice (SOCoP)--Activities • Service-Oriented Architecture (SOA) e-Gov Conference • 6th Semi-Annual, MITRE, McLean VA, Sept. 29 • Workshop on Spatial Semantics and Ontologies • MITRE, McLean VA, Oct. 17th, 2008 • Terra Cognita 2008 Workshop at ISWC (International Semantic Web Conference) • Karlsruhe, Germany, October 26, 2008

49. 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. • Just one technology platform enables collaboration of many forms—text, attach files, mashups, video

50. Summary • The EPA is excited about this technology. • They are using it more and more • Saves IT costs