Gov 2.0:The Government’s Web 2.0 Platform

Ramesh RamakrishnanDivision DirectorCitizantPh: (703) 667-9420 x165E-mail: ramesh@citizant.com

slide 2

Web 2.0 for the Government

What is Web 2.0? Advantages of Web 2.0 Web 2.0 Challenges Unique Approach to Gov 2.0 A Gov 2.0 Success Story: NHLS

slide 3

What is Web 2.0? Blogging

Allows easy content publishing and syndicating Many standards-based tools (e.g. Wordpress.org) facilitate the process

Podcast Audio and video publishing to the masses Simple syndication and repurposing via RSS

Wikis Online content that multiple, authorized users can freely edit and

modify together Social Networking

Enables people to rendezvous, connect or collaborate through communities

Most popular (e.g. Myspace, Youtube, Facebook etc.) Enterprise Mashups

Use content from more than one source to create a completely new service

Deliver significantly more value to the citizen with little incremental cost Use APIs (e.g. Google Maps)

Rich Internet Application Technology such as AJAX with a very rich user interface Rapid Application Development

slide 4

Advantages of Web 2.0

slide 5

Web 2.0 Challenges Within the Government Blogging

Federal publication rules and regulations apply (esp. if put on a government site) Podcast

Probably the most commonly used since it comes out of earlier transmission or distribution of information.

Integrate with Core content distribution/knowledge management Wikis

Can be one of the most useful tools in the Web 2.0 arsenal - Collaboration is key Identifying the authoritative source and being a moderator will be the greatest

return Social Networking

Potential to create a very robust community of interest (COI) – especially surrounding the official government agency function

Creates the highest challenge in terms of privacy/reach-out Enterprise Mashups

Most effective way of delivering services Re-use of existing resources, infra-structure and data

Rich Internet Application Technical Reference Model might not have the relevant tools Systems Development Methodology (SDM) and Enterprise Architecture Blueprints

might not align closely with Agile Development and/or Rapid Application Development

slide 6

A Gov 2.0 Platform

• Controlled Publications• Defined guidelines • Strategy focused distribution• Interactive features

ex: HHS Secretary Weblog

• Industry standard toolsavailable

• Portal implementation to create personalized access

ex: Nat’l Housing Locator

• Repository of services/data• Information/data sharing• Common XML data exchanges

ex: National Housing Locator

• Portal implementation• Communities of interest• Scalable structure/environment

ex: USAID Portal

• Create knowledge repository w/ moderators

• Collective Intelligence• Unified message – esp.

with lessons learned

ex: USA Services

• Most prevalent media distribution• Integrate with core content and

knowledge distribution • Best practices content distribution

ex: SBA Podcast

Web Logs (Blogging)

Podcast

WikisRich Internet Application

Enterprise Mashup

Social Networking

Gov 2.0 Core

slide 7

Gov 2.0 Platform Design

Based on industry standards for data indexing, syndication and mashups Optimized for search engines Single search across all platform nodes

Intelligence in the Core for authentication, security, branding, and publishing control

Architecture based on FEA and agencySOA strategies

slide 8

Find housing availableanywhere in the U.S.

Locate housing in any area,browse via interactive maps

A Gov 2.0 Success Story: NHLS

slide 9

A Gov 2.0 Success Story: NHLS

Rich User Experience• User friendly• Utilizes AJAX for fluid user navigation

• Commenting & Mapping system• Desktop application look-and-feel under a

distributed Web environment

Rapid Application Development (RAD)• Short iterative development cycles• Developed using the RAD methodology

•Utilized an Integrated Development Environment (IDE) to reduce development time

• Quick and flexible development

Perpetual Beta• Constantly accepting requirements• Soliciting requirements direct from Users• Adaptive/Corrective Maintenance

Long-Tail Approach to Data Collection• Accept data from a large number of sources• No data set is too small• Ability to collect data from numerous sources

to increase the total number of units available

Data Mashups• Utilizing APIs (e.g., Google Maps) as a

data mashup platform• Overlays

• Potential to display other overlays• Displaying grouped data enhances overall

user experience

Web Service/REST• Means of data exchange between systems• Direct access to property data to outside

organizations• Transfer of data using a simple form of Web

service• Adhere to a standard transportation method