1. 1 The Ken Orr Institute Web 2.0 Wiki Pilot: Tutorial Brand Niemann July 12, 2008 http://kenorrinstitute.wik.is/

2. 22 Introduction Background: Brand Niemann attended Ken Orr's Data Architecture for Business Architects at the Brainstorm DC, June 26, 2008, and suggested using Web 2.0 Wikis and Ken asked for a demonstration of how they could be used and this is the initial result. Brand is a senior Enterprise Architect in the Office of Environmental Information and the Chief Information Officer at the U.S. Environmental Protection Agency and did this work on his own time to honor Ken and the 20th anniversary of The Ken Orr Institute. Purpose: Bring together the following: Traditional data modeling (David Hay); Ontologies (John Sowa and Arun Majumdar); and Semantic Web (Jim Hendler and Dean Allemang) using Web 2.0/3.0 Wikis for bookkeeping and collaboration on all of this that would have the added advantage of attracting younger people to this area. Deki Wiki Technology: This is really a web-services platform with a Wiki interface (see slides 3-4).

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

4. 44 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.

5. 5 Tutorial Overview 1: Decide on Name 2: Register Name 3: Login 4: Set Preferences 5: Control Panel 6: Design Home Page 7: Create Subtopics 8: Repurpose 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

6. 6 1: Decide on Name http://wik.is/

7. 7 2: Register Name http://wik.is/register/?sitename=kenorrinstitute&x=47&y=11

8. 8 3: Login http://wik.is/success/?sitename=kenorrinstitute

9. 9 4: Set Preferences http://kenorrinstitute.wik.is/Welcome

10. 10 4: Set Preferences Private Email

11. 11 4: Set Preferences http://kenorrinstitute.wik.is/Special:Preferences

12. 12 5: Control Panel http://kenorrinstitute.wik.is/Adminhttp://kenorrinstitute.wik.is/Admin:

13. 13 5: Control Panel http://kenorrinstitute.wik.is/Admin:Settings

14. 14 5: Control Panel http://kenorrinstitute.wik.is/Admin:Styles

15. 15 6: Design Home Page http://kenorrinstitute.wik.is/

16. 16 7: Create Subtopics http://kenorrinstitute.wik.is/About_Ken_Orr

17. 17 8: Repurpose Web Content Into Wiki http://kenorrinstitute.wik.is/Publications/Putting_Data_into_SOA

18. 18 9: Attach Files http://kenorrinstitute.wik.is/Wikilog

19. 19 9: Attach Files http://kenorrinstitute.wik.is/Wikilog

20. 20 10: Insert Images and Links http://kenorrinstitute.wik.is/Publications/Putting_Data_into_SOA

21. 21 10: Insert Images and Links http://kenorrinstitute.wik.is/

22. 22 11: Create Wikilog http://kenorrinstitute.wik.is/Wikilog

23. 23 12: Set Security http://kenorrinstitute.wik.is/

24. 24 12: Set Security Public: everybody can view and edit. Semi-Public: everybody can view, but only selected users can edit. Private: only selected users can view and edit this page. Note: Deki Wiki has one of the most advanced permission systems available. Deki Wiki administrators can make wikis public or private, anonymous or not. There is user groups support. Users can permission entire hierarchies to create private or non-editable workspaces or permission single pages.

25. 25 13: Monitor Users http://kenorrinstitute.wik.is/Special:Recentchanges

26. 26 14: Revise/Reorganize To soon for this new Wiki, but for another Web 2.0 Wiki Project I did the following quickly: –Moved content from Wiki to another Wiki. –Implemented a set of topics and subtopics. –Created a new user interface. –Updated the Tutorial slides and uploaded them. Note: This shows how agile and flexible the Web 2.0 Wiki environment is to respond to requests that would be more difficult (or impossible) and time consuming with Web 1.0 collaboration technology.