The document proposes an OpenNASA portal using an open source/social architecture to provide a unified platform for NASA's online resources. It would transition external and internal sites/data to standardized gadgets and applications. This would improve access, efficiency and innovation through crowdsourcing development. The goals are to minimize redundancy, provide services via an enterprise catalog, and leverage new technologies like cloud computing through partnerships with other federal agencies.

1. The OpenNASA v2.0 Portal:
A Conceptual Open Source/Opensocial Architecture for
the Federal Community Cloud
Megan Eskey
Megan.A.Eskey@nasa.gov
NASA Enterprise Architecture, Collaboration and Content
Management Team
Web Manager
NASA Ames Research Center
http://www.arc.nasa.gov
Federal Intranet Content Managers
June 11, 2009

2. Overview
Business Drivers
One Tent for the Community Cloud
The Open Stack
Why Liferay?
Conceptual Architecture
Transition Processes
End Goals
Summary
Appendix
High-level NASA Enterprise “To Be” Architecture – Draft
Portal UI Design Mockups – eTouch Systems
Government Cloud References and Definitions
Web 2.0 References and Definitions
Seven Steps for Next Gen Web

3. Business Drivers
Transparency and Open Government Memo
Push for community engagement/citizen “idea sourcing”
GSA “Terms of Service Agreements” for Social Media
YouTube, Flickr, Blip.tv, Yahoo Video, Vimeo, Facebook,
iTunes, Blist, MySpace, AddThis, Slideshare, Cooliris (video
and picture browsing), Dipity (multimedia timelines),
FriendFeed (social networking aggregator), IdeaScale
(voting and feedback), MixedInk (collaborative writing),
Scribd (social publishing), TubeMogul (video analytics and
distribution), TwitVid (video sharing), Wikispaces
(collaboration) and others TBD
Internet of Services: widespread adoption of “Cloud
Computing” solutions: SaaS, PaaS, IaaS, etc.
Nebula, Google, Salesforce, Amazon EC2, S3, Hadoop, etc.
Internet of Things: iPhones, laptops, blackberries, etc.

4. Business Drivers, Cont.
Data.gov: push to provide our nation’s federal data sets on
open networks: http://www.data.gov
$7 billion Broadband stimulus package
Enterprise 2.0 Evolves Quickly: Federal policies must evolve in
parallel
Enterprise 2.0 is Participatory: end users consume and create
Information is increasingly published at higher fidelity (i.e.,
microformats) or presented via smaller “byte sized” objects
to share, aggregate, syndicate, embed, use on
handheld/mobile devices
Examples: gadgets, widgets, microblogs, RSS feeds, portlets,
podcasts, video spots, etc.

5. Social Networking/Social Media
Challenges for Federal Agencies: Recent
Brainstorming Session at Gov’t 2.0 Camp

7. Federal Cloud Program Status:
To support the Federal Cloud Computing Direction and
Deployment Approach, the ITI Line of Business PMO has
been refocused as the Cloud Computing PMO
Building on ITI LoB Initiative
Infrastructure defined
Consensus model
Metrics
Key Focus Areas
Key Themes: consolidation and virtualization
Cloud Computing Initiative
Continue the migration towards a services-based environment that is
technology and vendor-agnostic
Enable rapid deployment of technology solutions for the Federal
government without developing stove-pipes
Enable scalability for existing and new capabilities
Increase savings through virtualization
Potentially reduce cost of infrastructure, buildings, power, and staffing
Improve the government's ability to create a transparent, open and
participatory government

8. Building Upon the ITILoB Effort
ITILoB Cloud Computing
GOAL: To achieve an optimized, cost-effective, government-wide information
technology infrastructure that supports agency mission, while providing reliability and
security in service delivery.
Established a vision for Government-
wide ITI Optimization Will use the information gathered
through the ITILoB effort to deploy
Created a collaborative governance
“Common Solutions” using a Cloud
framework involving 23 Federal
Computing technology platform
Agencies
This initiative will:
Captured and analyzed critical
information in terms of: Follow a service oriented
approach
Optimization strategies
Be based on agency business
Common Solutions
needs
Performance Metrics
Maintain a collaborative
IT Infrastructure Tools used governance framework
across Government
Benchmarked Federal ITI Data

9. Deployment Model Overview
COMMUNITY CLOUD
PRIVATE CLOUD Shared by several
organizations and
Operated solely for an supports a specific
organization. community that has
shared concerns
HYBRID CLOUD
PUBLIC CLOUD
Composition of two or more
Made available to the clouds (private, community, or
general public or a large public) that remain unique entities
industry group and is but are bound together by
owned by an organization standardized or proprietary
selling cloud services. technology that enables data and
application portability

10. Delivery Model Overview
Model Capability Provided Example Services
Citizen Engagement (Wikis,
Blogs, Data.gov)
To use the provider’s applications running on a cloud Government Productivity (Cloud
infrastructure and accessible from various client based tools)
SaaS Business Enablement
devices through a thin client interface such as a Web
browser (Salesforce.com)
Enterprise Applications (Core
Mission & Business Svcs
To deploy onto the cloud infrastructure consumer- Database and Database
Management Systems
created applications using programming languages
PaaS Developer / Testing Tools
and tools supported by the provider (e.g., java, Virtual Environments
python, .Net)
To provision processing, storage, networks, and
other fundamental computing resources where the • Computing
IaaS consumer is able to deploy and run arbitrary • Storage
software, which can include operating systems and • Application hosting
applications

11. OpenNASA: “One Tent” Portal for
the Community Cloud
Increasingly, Federal/Agency data, content and innovative
“mashups” are moving off of Federal/Agency networks and
servers and onto others’
Social Media Sites: “Free” Online Services: NASA Ames
Facebook site
Microsoft Space Act Agreement: World Wide Telescope
Online News Media: USA Today International Space Station
Flash
Google Moon, Google Mars
Other external sites – partner sites, sites hosted at other
ASPs, ISPs: http://www.opennasa.com
Federal Agencies will need a mechanism for pulling the best of
breed content/data/apps back under “one tent” per
records management and other related policy requirements
We don’t want 100s of social sites, we want a few we can trust

12. Will intranets supercede the
need for a corporate website?
From the Intranet Benchmarking Forum Blog, June 5, 2009:
“The emerging trend is for increasing access to be
given to intranets [and intranet content] for people
outside the firewall; suppliers, contractors,
customers, former staff etc.
Major companies globally are looking to open up to
their marketplaces, customers and consumers. They
are also looking to increase their presence and
engagement with social media and emerging 2.0
technologies.”
If this is the trend, then what are the “bridge points”?
How can we make our public presence more relevant?

13. The Social Cloud: Opensocial Partners

14. The Open Stack
Discovery
Identity
Access Control
People
Apps

15. People, Friends, Actions, Data in Context
•OpenID is the standard that lets you prove to other websites that you own such a URL,
thus letting you link your online identities
•Under the hood, most social networking sites have names, photographs, addresses, phone
numbers, preferences. This model is expressed in the Portable Contacts standard, which is
also used in OpenSocial for people and friends/collaborators
•OAuth lets you grant permission for very specific tasks. You may let another site see all
your profile data or just your name and image. You may let it see all the people you know
or just a subset - your family or colleagues. Additionally, OAuth lets the social site know
that a request is being made on behalf of a specific user, so if the social site reveals
different information to different people, that can be taken into account.
•The last piece of this social web is activities — what you and your collaborators are doing
around the web. This is why OpenSocial allows any application to generate an activity and
provides a way to send those activities from one place to another. The social networking
site can then filter those activities in a way that makes sense for their users.

16. Opensocial Containers
Social Network Sites – Profiles and
Homepages
Personal Dashboards
iGoogle, MyYahoo
http://code.google.com/apis/igoogle/docs/tutorial.
html
Any Web Site
Google Friend Connect enables this for any site
http://google.com/friendconnect

17. Why the Liferay Open Source Horizontal
Portal Software?
Provides the capability for a primary entry point to in-house and
external online resources with a standard and consistent user
experience/user interface
Provides a mechanism for leveraging Web 2.0 as an integrated
solution
Provides an extensible platform for Web Developers to integrate
additional applications and features via open portal standards (WSRP
1/2, JSR 286, JSR 170, JBI, etc.), Liferay open source software
enhancements, and the addition of new Gadgets and Apps via the
Shindig Gadget Container and Opensocial reference implementation
Provides a framework for consolidating disparate and widely
distributed content and data under “one tent”
Provides a model that can keep pace with technology innovation
and change
Enterprise 2.0 – easily scales for extranet/limited public access,
scalability testing in lab for general public use
Provides a framework for standardizing Web IT security models
and processes
Provides a framework for standardizing Web policy compliance and
leveraging “connected governance” models and processes

18. Web 2.0 for Internal Efficiency and Effectiveness:
A recent discussion on the Web Content Managers Listserve
From: Schools Ji-Hyon K [mailto:Ji-Hyon.K.Schools@IRS.GOV]
Sent: Monday, April 06, 2009 8:24 AM
To: CONTENT-MANAGERS-L@hudlist.hud.gov
Subject: Re: Facebook, Facebook, Facebook, ad nauseam ... (U)
I see social media - as stated by others in this thread - as yet another communication tool to
reach out, and I believe we would be remiss if we didn't explore all the opportunities Web 2.0
offers. It is finding the right tool to get the job done that may be the hardest task.
Personally, my primary objective, for now, is to find ways to integrate Web
2.0 functionality into the business lives of federal employees. It seems that this
aspect of the "customer" hasn't really been discussed, or maybe it has and I just
missed it. How can we harness this technology to make running the federal
government more efficient? How can we provide an iGoogle kind of
platform to our employees so they aren't "hunting and pecking" for
information through a myriad of Intranet sites and resources?
Ji-Hyon Schools
IRS, Web Program Manager
Appeals, Communications

20. Concept:
“Gadget/Apps” Collections Tailored to NASA End Users
Portal Front Door
All end users will see a basic subset of predefined gadgets before they login
Out of the Box Gadgets: wiki, blog, forum
Gadgets and Apps extracted from key public NASA site collections
http://astrobiology.nasa.gov/
http://www.nasa.gov
http://nasascience.nasa.gov
External/Social Media Gadgets: Twitter, Facebook, YouTube, etc.
Login Use Cases - Specialized Gadgets/Apps for Personal User-Configurable
Dashboards:
NASA Employees: (full time, part time, students): Shared Federal applications, Agency and
Center specific applications, general information, project applications
Other Federal Gov't Employees: Shared Federal Applications: Training, Recruitment, Payroll,
Travel
Contractor Employees: general purpose employee information
Business Partners: Applications related to partnering with NASA: SBIR, Technology Transfer
Academic Partners: Applications related to partnering with NASA: educational programs,
research grants, university programs
General Public: Pending scalability testing/user acceptance. Public apps.
Developers: Data, tools, guidance, ongoing projects, social site for matching expert in-
house developers with new developers, access to Web application frameworks (Java, perl,
Objective-C, Ruby, Python, .PHP, Azure), access to Gadget/App Registry

21. Concept:
Enterprise Architectural Models combined with
“Crowdsourcing” Web Development
Our in-house developers are no longer able to keep up with the
demand to
Maintain legacy sites and applications
Transition legacy sites and applications to new implementations
Integrate innovative or cross-cutting technology
Develop new applications, roll out new COTS
Keep pace with Web policy changes
We can leverage Enterprise Architecture processes and solutions to
minimize redundancy and maximize ROI
Standardize on specific applications for each functional area in
NASA Enterprise Services Catalog (See Appendix for details)
Integrate Agency applications and/or expose functionality via XML
Web Services
Decommission underutilized, obsolete or redundant legacy sites
and applications
With Open Source/Opensocial, we can “crowdsource” some of our
development, leveraging Citizen “idea sourcing” via outreach efforts
such as this:
http://www.appsfordemocracy.org/

22. Phase 1:
Transition a core subset of external (non-NASA) and in-house
public collections and applications to Gadgets/Apps to provide a
uniform/user-friendly platform for future development
Medium Grey Blinds from http://www.nasa.gov Collections

23. Phase 2:
Provide the platform, tools, data, content, processes and policy to
enable in-house developers to transition remaining high-visibility,
widely used public and extranet Agency applications and in-house
Collections to Gadgets/Apps
Provide Content and Data: Medium Grey
3 Column Video Collection from the NASA
E/PO Portal
Develop/Provide Tools to automate the
process
Provide Online Guidance in OpenNASA
“Developers” area
Provide similar guidance for other high
visibility public sites and applications
http://astrobiology.nasa.gov/
Provide similar guidance to create Gadgets
with SSO to widely used legacy
extranet applications
http://webmail.nasa.gov
http://outsidenasa.nasa.gov
http://webtads.arc.nasa.gov/
Provide similar guidance to transition
selected content and functionality from
other high visibility internal portals
(SSO/SSL pending feasibility studies)
http://insidenasa.nasa.gov
Integrated Collaborative Environment

24. Phase 3:
Use Lessons learned in-house to “crowdsource” dev and
bring external data/content/apps back in under one tent
Provide the Platform, Tools, Data, Content, Policy
and Processes for Online “Citizen Developers”
Apps for Earth, Apps for Air, Apps for Space, Apps for
Humanity, Apps for Life
3-D Models for Game Developers
Links to NASA Channels on Social Media Sites
Links to Photosynths
Planetary Data for virtual telescopes, virtual
planets, virtual moon, etc.
Tools for visualizing/modeling Geo-spatial data
Environmental data for “Going Green”
Tools for mining molecular/astrobiology
databases

25. Use Portal “Social Networking” Capabilities combined
with a Gadget and Application Registry to match In-
house Developers with Citizen Developers
Lessons learned from “Apps for Democracy”,
Google, Yahoo
Provide an Application and Gadget Registry
Apps should be “gold certified”
Apps should be targeted and useful
Apps Lifecycle management is essential
Apps Classification and Search – good baseline metadata
required, good search tools
Apps need different security/access models - extranet,
public access, limited access, etc.
Apps data/information integrity and quality assurance is
required

26. End Goals
NASA’s online resources accessible from a primary entry point at:
http://open.nasa.gov via a standard and consistent interface to the
open platform, tools, data, content, processes, and policy
Multiple Layers of Trust:
Federal eAuthentication (SAML) for in-house applications and two-
factor requirements
oAuth at the API layer to “allow” access to opensocial apps
Continuous improvement/continuous synchronization with ongoing
NASA Enterprise Architecture activities to:
Minimize redundancy of purpose of in-house NASA applications
Provide in-house and government-wide IT services via online
Enterprise Services Catalog
Federal Cloud IT Services Survey – Due COB June 12th
Advantages:
Continuous innovation through a virtual circle of contributions from
developers and end users
Standardize information and application access/processes, move
into the “NASA Social Cloud”
Leverage new Administration’s focus on Federal Broadband and
Cloud Initiatives

27. Summary
Potential First Phase Federal Partnerships:
Provide requirements for a generalized Federal open
source/opensocial architecture
Apps for Earth, Apps for Air, Apps for Humanity, Apps for Life
Environmental Protection Agency: http://open.epa.gov
U.S. Geological Survey: http://open.usgs.gov
Federal Aviation Administration: http://open.faa.gov
National Institutes of Health: http://open.nih.gov
Department of Homeland Security: http://open.dhs.gov
USA: http://open.usa.gov
“OpenFederal/opensocial” Transition Timeline:
Three Years to Transition Three Federal Agencies
Five years to Transition other Federal Agencies
Potential First Phase Funding Mechanisms: MOUs, RFPs, CANs, Space
Act Agreements, etc.
OpenNASA Portal Wiki
To get access please send your email address and display name
(first and last name) to nasa-support@etouch.net

28. Appendix:
NASA Enterprise Architecture High Level Overview

29. NASA’s Future State Web:
Enterprise Collaboration and Content Management Services
Partner
Knowledge
Knowledge Base – Published Information – Enforces Security Bases
Records Management
Document Multimedia
Management Management
Other
(Documentum/Alfresco)
e.g. CAD Drawings Public
Web
Cloud
Conferencing Integration Services
(WebEx –
SaaS)
Wiki 2 Blog 2 Team Workspace Other IT
(wiki.nasa. (blogs.nasa. (SharePoint/MOSS/Liferay) Dynamic Business Services
gov) gov) Content DDM
Wiki 1 Blog 1
e.g. e.g. PLM, PDM
(platform- (platform-
IM Multimedia (Windchill)
based) based)
(Jabber) tools
Community Cloud Private Clouds
Adoption / Facilitation / Consulting
Mission Specific Collaboration
and Content Management Services
---------------
Legend Interface with Other Service Area = Adoption & Facilitation
Manual Integration = (Consulting)
External SLA/Web services = Domain-Unique Services
Enterprise Collaboration Services provided by Mission Support = No Domain-unique services
Content (Information & Data) provided for use by the Enterprise = have been identified, but the
architecture supports it.

30. SharePoint/MOSS Usage at NASA:
MOSS 2007 pilot implementations at ARC, JPL, JSC, KSC
Phase 1 Transition: HQ, MSFC
Team Workspace Implementations / Reported User
Counts
7000 SharePoint 2003
6000
SharePoint 2007
5000
# of Users
4000 eRoom
3000
2000 NX / Docushare
1000 PBMA
0
ARC DFRC GRC GSFC HQ JPL JSC KSC LaRC MSFC NSSC SSC

31. NASA Proposed IDM Community Cloud Architecture
open.nasa.gov
apps.nasa.gov
others TBD
NASA Information
Distribution System

32. Phase 1: Intranet -> Cloud Transition
Focus groups at Agency,
Center, and team level
underway for redesign of
current Vignette-based
InsideNASA intranet
SharePoint/MOSS and
Liferay architectures share
processes and
requirements
Open development
process for both efforts
will allow sharing of
community created
content, templates, Private Cloud: InsideNASA -> MOSS 2007
webparts, gadgets,
workflows, ideas, etc.
Community Cloud: OpenNASA -> Liferay

33. LIFERAY – Next Gen Portal
eTouch Systems Corp.

34. Next Generation Portal – Conceptual Model

35. Next Generation Portal – Social & Integration Aspects

36. Portal – What Users Need?

37. Next Generation Portal – Vision
Google Secured Google
Yahoo Apps Widgets Custom Apps
Gadgets Portlets Gadgets
Secured User- contributed
Applications Applications
Public
Communities
Interest
Groups
Federal Pre-loaded
Agencies Site Pages/Tabs Personal Pages Users
Portal Platform
Federal
Groups

38. Next Generation Portal – Vision
Personal Center Division Interest Group
Pages Pages Pages Pages

39. Next Generation Portal – Vision
Applications

40. Next Generation Portal – Vision
Preloaded
Tabs

41. Integration Case Study - Gadgets
Legacy Application
and Site Registry
• Web Sites
• Web Applications
Gadget Registry
• Gold Certified Gadgets
• In-house Gadgets
• External Gadgets
• Community contributed
Gadgets
• Not quite ready for
prime time Gadgets
Gadget and Legacy
Classification
• Categorized
• Searchable
• Different Reports
• Crowdsourced
• Rating/Polls
• Analytics

42. KONA GOLD:
Metalevel Analysis of Registry Data
Analysis of AWRS (Agency Web Registration System) and NATT
(NASA Application Tracking Tool) data to integrate,
decommission or move sites and applications “to the Cloud” in a
consistent and systematic way
Goal: Minimize redundancy of purpose, features, content, etc.
Decision factors:
Sites/Applications can be migrated in whole to cloud vs. sites must
remain legacy - ie, opensource, .php, java, django, etc. - > cloud
Sites/applications are strategically aligned with NASA programs,
projects, missions, ITI LoB, etc.
Sites/applications have a broad customer base
Have high usage statistics – i.e., web analytics
Can be integrated with key Agency intranet applications (have APIs
for) SAP, SharePoint 2010, Exchange/Outlook, Primavera,
Windchill, MS Project, Active Risk Manager, Cradle, Praca, Irma,
Documentum, others TBD
Workflow for user-generated reviews, approvals, ratings, polls

43. Portal Security
Pulling the data from intranet
applications to an external
facing portal in a secured and
reliable way with “one time
user credentials” is an industry
challenge. We suggest couple
of ways to address this
Enable the internal application
to support OAuth
For SSO enabled internal
applications, work with the
industry to develop OAuth
SAML binding with access
secrets/tokens
Build custom
adaptors/interfaces as needed

44. InsideNASA Redesign: Advisory Board
Technical and Governance
Focus Areas:
Application, Business, Product Portfolio
Management
Application, Business, Product Lifecycle
Management
Application, Business, Product Development
Management
Metrics
Standards
Policy, Guidelines, Best Practices
Service Models, Business Models, Operations
Models

45. Lead Roles for NASA’s Collaboration and
Content Management Architecture
One Tent Domain Manager
Operations
Adoption and Consulting
Knowledge Base Development
Collaboration Services Development
Enterprise Search and Portal Development
Configuration Management

46. InsideNASA Redesign:
Focus Groups @ Ames Research Center
Near Term Next Gen Technologies
MOSS/Liferay Integration
Workgroup Workflows
Federated Semantic
Cloud Computing Standards Search
Multimedia Standards
Virtual Worlds (3-D,
Data Standards
Cloud Security Immersive, etc)

47. FIX: Federal Internet eXchange

48. Government Cloud Computing Framework
Cloud User Tools
Software as a Service (SaaS) / Applications Application User/ Reporting &
Integration Admin Analytics
Citizen Engagement
Citizen Engagement Gov Productivity
Gov Productivity Gov Enterprise Apps
Gov Enterprise Apps
Business Svcs
Portal
Wikis / Blogs Email / IM Customer /
Apps
Account
Social Networking Virtual Desktop Core Mission
Apps Mgmt Analytic
API’s Tools
Core Cloud Services
Agency Website Legacy Apps
Office Automation User Profile
Hosting (Mainframes) Data
Workflow Mgmt
Engine Mgmt
Platform as a Order
Testing Developer Reporting
Service (PaaS) Database Tools Tools EAI Mgmt
Directory Trouble Knowledge
DBMS Services Mobile Device Mgmt Mgmt
Integration
Billing /
Infrastructure as a Virtual Data Migration Invoice
Storage Tracking
Service (IaaS) Machines Tools
Product
CDN Web Servers Server Hosting Catalog
ETL
Service Mgmt &
Cloud Service Delivery
Service Performance DR / Operations
Provisioning SLA Mgmt
Provisioning Monitoring Backup Mgmt
Capabilities
Security &
Data/Network Certification & Authentication & Auditing &
Data Privacy Security
Data Privacy
Compliance Authorization Accounting
Data Center Routers / Internet Hosting
LAN/WAN
Facilities Firewalls Access Centers
DRAFT - GSA OCIO INTERNAL USE ONLY

49. Government Cloud Security
All of these functions are in our data centers today,
so where’s the cloud specific threat?

50. Government Cloud Security
Since we can’t find the threat by looking at
the cloud, let’s look at it from the Security
perspective.
The science of Computer Security is
concerned with three things:
1.Confidentiality
2.Availability
3.Integrity

51. Government Cloud Security: Confidentiality
Security may well improve
1. Shared Services will force cloud providers to
encrypt data. How many are encrypted in our
datacenters today?
2. Lack of access to our files and e-mail is a Denial
of Service (failure scenario)
3. What’s the bigger risk? How much of the risk is
internal? How much are we failing today?

52. Government Cloud Security: Threats
The bigger risk stems
from the lack of cloud
services, such as Storage
as a Service.
The threat stems from the
work‐arounds we have
developed, like when we
send things off‐net in e‐
mails or when we carry
around files on
thumbdrives.

53. Government Cloud Security: Availability
Storage as a Service
Web folders
If we had access to our
Files wherever we were
We wouldn’t need USB
Drives.
Next time there’s a flu
Epidemic you’ll
Wish you had these.

54. Integrity
The worst case scenario for NASA is a loss
of data integrity.
That’s where we should be spending our
resources.
Our security profile should heavily favor
Integrity over Availability over
Confidentiality.

55. Cloud Characteristics
SLA-based multi-tenant business model for users
Safe & Secure, on-demand, self-service
Self-configuring & provisioning, self-healing
Comprehensive, open, standardized APIs for
developers
Fully virtualized and scalable
applications, operating systems, network, storage
Hide the complexity of
Create, start/stop, import/export, snapshot, reboot
Backup/restore, move, destroy

57. Cloud Ownership Models
Use the Cloud
Startup, SMB, Research projects
Leverage the Cloud
Temporary on-demand load
Functional off-load
Build my own internal Cloud
Enterprise Infrastructure Grid
Drive Internal IT economics
Standardize development environment/services
Be the Cloud
Redefine Services
New Business Offerings
Hosting and Operations partners
Software Vendors

58. The Cloud Computing Stack
Clients
Services
Applications
Platform
Storage
Infrastructure

59. Web 2.0: Web of Participation
Web 2.0 is the second stage the web. It is the
social web that connects people. It is a web of
participation. User consumes & creates. Sites
are interactive, for example: blogs–keep a web-
diary; Wikipedia — free encyclopedia,anyone
edits; Del.icio.us — social bookmarking;
mySpace, openBC – cultivate social relations;
Flickr — share photos; and YouTube–broadcast
yourself.
According to Tim O’Reilly, several principles
distinguish web 2.0, for example:
(1) the web as platform
(2) harnessing collective intelligence
(3) data is the next Intel inside
(4) end of the software release cycle
(5) lightweight programming models
(6) software above the level of a single device, and
(7) rich user experiences.
In addition Web 2.0 approaches embrace:
remixing data and services; relation-orientation;
the long tail; and bidirectional interaction. Web
2.0 social computing has both consumer and
enterprise impacts, i.e., Enterprise 2.0.

61. Seven Steps for Next Gen Web
1. Empower people with cloud 5. Simplify linking and sharing public
computing, Web 2.0/Web 3.0 to information across systems, agencies,
connect, collaborate, and communicate and jurisdictions. Expose structure and
across boundaries and at scale. meaning using semantic standards.
Provide APIs, web services, widgets
2. Establish pilot programs that open and gadgets. Enable human and system
up government decision-making and to system access. Use Service Oriented
involve the public in the work of Architectures (SOA) to promote
agencies, not simply by soliciting interoperability between applications.
opinions, but by tapping into the vast and
distributed expertise of the American 6. Improve user experience with Web
citizenry to help government make more 2.0/Web 3.0 semantic technologies.
informed decisions. Upgrade web site UIs with semantic
search and query, natural language
3. Employ technologies, including understanding, visualization, and
blogs, wikis, cross-agency portals reporting, that combines structured data
and social networking tools, to sets, document repositories, and web
modernize internal, cross-agency, pages. Add intelligence to user
and public communication and interfaces.
information sharing, and to improve
collaboration and government decision- 7. Use Web 2.0/3.0 social media channels
making. to converse, communicate, publish, and
interact. Reach out to the public, co-
4. Liberate silo-ed data and information. workers, and partners using a full
Make dynamic mash-ups across spectrum of communication
applications, data. channels, feeds, media, and forums.

62. Technical Presentation, Part 2
Technical Overview
Demo
Q&A
Resources:
Federal Cloud Wiki
Federal CIO Council
Dashboard Guidance and Open Houses

63. Share Your Thoughts
The OpenNASA architecture is a work-in-progress and we need
your input.
For those interested in exchanging information about similar
architectures we have established a "OpenNASA Portal Wiki"
at:
http://wiki.nasa.gov/cm/wiki/OpenNASA%20Portal.wiki/ho
me/home.html
To get access to the wiki, please send your email address and
display name (first and last name) to mailto:nasa-
support@etouch.net
Please send an email to mailto:Megan.A.Eskey@nasa.gov for
any additional questions or to arrange a demo/discussion after
the talk.