4 August 2007
By Paul Davis pdavis39@csc.com 703 645 -5012

02/09/08 09:52 PM 5864_ER_HEALTH 1


• Introduction • CSCwiki a Semantic Wiki Pilot at CSC (sipping the Champagne of Social software) • An Architectural Vision for Knowledge Management • Screen shots from CSCwiki • Status and Next steps

02/09/08 09:52 PM 5864_ER_HEALTH 2

Champagne sipping the Social Web Phenomenon
• Pilot started February 2007 • Functional Requirements that drove pilot
– Follows Web 2.0 Principles
• • • • • • • • • • • Web-based Any user can both read and write content Can be deployed via the Web in countries all over the world Developed and is maintained by a small team Has fast, lightweight and inexpensive development cycles Uses Open Source LAMP technologies (Linux, Apache, MySQL and PHP) - meaning it is very cheap to run The content has no copyright and is freely licensed under some GNU Free Documentation License 1.2 Can and will hook into other Web systems, e.g. Google Maps. Indeed if it introduces its own APIs, then it will be able to be remixed by other developers. Relies on word-of-mouth and other 'viral' marketing. Requires network effects to kick in order to be successful that means at scale it disrupts legacy applications Web 2.0 applications will get better the more people use it.
02/09/08 09:52 PM 5864_ER_HEALTH 3

Champagne sipping the Social Web Phenomenon continued

– Allow expressions from leadership about what is important implemented via topics and forum – Allow users to author insights and allow user to review other insights – implemented with wiki – Support to “bump up against” other users – implemented with semantics – Connect to other sources of data via web services the Knowledge Base – future capability – Support expression of level of confidence in insights, from untested to confirmed – future capability – Find groups and users working problems, create new ones, close old ones – implemented with semantic wiki

02/09/08 09:52 PM 5864_ER_HEALTH 4

Conceptual Architecture
Baked in is Security & ITIL Service Management

Reference Data

Semantic Wiki

Source a

Source b

Source n

Data Sources must comply to • Resource Meta Data • Deep Content Meta Data • Controlled Vocabularies

Other apps Search UI KB Alert
Dynamic Presentation • Web based, but not a monolithic application • Leverages •ajax •mashups •ontology and folksonomy views of data

Core Ontology Supporting • Resource Meta Data • Deep Content Meta Data • Controlled Vocabularies



02/09/08 09:52 PM 5864_ER_HEALTH 5

Sample Pages

RSS feed

TagCloud Navigation

02/09/08 09:52 PM 5864_ER_HEALTH 6

Sample Pages continued
Allows for SPARQL query capabilities - find me all Organizations

Page creation is template driven

All Topics/Subjects have an ontology

02/09/08 09:52 PM 5864_ER_HEALTH 7

Sample Pages continued

Rdf is transparent in Templates

02/09/08 09:52 PM 5864_ER_HEALTH 8

Sample Pages continued

Usage of task extension

rdf is associated with wiki page

02/09/08 09:52 PM 5864_ER_HEALTH 9

Sample Pages continued
Dynamic wiki page generation based on in-line query of rdf relations and attributes

02/09/08 09:52 PM 5864_ER_HEALTH 10

Sample Pages continued

Googlemaps and wiki mashup of Airport Status

02/09/08 09:52 PM 5864_ER_HEALTH 11

Sample Pages continued
Enhanced search with dynamic ontology generation

02/09/08 09:52 PM 5864_ER_HEALTH 12

Sample Pages continued

Multimedia enabled for pod cast Multi-media enabled integration

02/09/08 09:52 PM 5864_ER_HEALTH 13

Sneak Preview to Future Capabilities

Tree view navigation for complex subject taxonomies

02/09/08 09:52 PM 5864_ER_HEALTH 14

Status and next steps
• Pilot is successful • Globally used • Evolves based on user needs • Very stable • Semantic wiki provides value in business environment • Users are adding meta data • Road map of features in process • Add a more sophisticated subject taxonomy to support larger user base • Integration of private social book marking software • Integration with corporate LDAP registry • New skin that integrates search and better supports user created mashups • Export rdf into knowledge base • Scale hardware as needed • Continue to partner with Users/Organizations to develop ontologies that support their needs • Continue to follow Web 2.0 design principles

02/09/08 09:52 PM 5864_ER_HEALTH 15