The OpenNASA v2.0 Portal: A Conceptual Open Source/Opensocial Architecture for the Federal Community Cloud

Megan EskeyMegan.A.Eskey@nasa.gov

NASA Enterprise Architecture, Collaboration and Content Management Team

Web ManagerNASA Ames Research Center

http://www.arc.nasa.gov

Federal Intranet Content Managers June 11, 2009

OverviewBusiness DriversOne Tent for the Community Cloud The Open StackWhy Liferay?Conceptual ArchitectureTransition ProcessesEnd GoalsSummaryAppendix

High-level NASA Enterprise “To Be” Architecture – DraftPortal UI Design Mockups – eTouch SystemsGovernment Cloud References and DefinitionsWeb 2.0 References and DefinitionsSeven Steps for Next Gen Web

Business DriversTransparency and Open Government MemoPush 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.

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 packageEnterprise 2.0 Evolves Quickly: Federal policies must evolve in parallelEnterprise 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 devicesExamples: gadgets, widgets, microblogs, RSS feeds, portlets, podcasts, video spots, etc.

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

Federal Cloud Program Status:Federal Cloud Program Status:

ToTo support the Federal Cloudsupport the Federal Cloud Computing Direction andComputing Direction andDeployment Approach, the ITI Line of Business PMO has Deployment Approach, the ITI Line of Business PMO has been refocused as the Cloud Computing PMObeen refocused as the Cloud Computing PMOBuilding on ITI LoB Initiative

Infrastructure defined Consensus modelMetricsKey Focus Areas

Key Themes: consolidation and virtualization

Cloud Computing InitiativeContinue 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

Building Upon the ITILoB EffortBuilding Upon the ITILoB Effort

Established a vision for Government-wide ITI OptimizationCreated a collaborative governance framework involving 23 Federal AgenciesCaptured and analyzed critical information in terms of:

Optimization strategiesCommon SolutionsPerformance MetricsIT Infrastructure Tools used across Government

Benchmarked Federal ITI Data

Will use the information gathered through the ITILoB effort to deploy “Common Solutions” using a Cloud Computing technology platformThis initiative will:

Follow a service oriented approachBe based on agency business needsMaintain a collaborative governance framework

GOAL: To achieve an optimized, cost-effective, government-wide information technology infrastructure that supports agency mission, while providing reliability and

security in service delivery.

ITILoB Cloud Computing

Deployment Model OverviewDeployment Model Overview

PRIVATE CLOUD

Operated solely for an organization.

COMMUNITY CLOUD

Shared by several organizations and supports a specific community that has

shared concerns

PUBLIC CLOUD

Made available to the general public or a large

industry group and is owned by an organization

selling cloud services.

HYBRID CLOUD

Composition of two or more clouds (private, community, or

public) that remain unique entities but are bound together by standardized or proprietary

technology that enables data and application portability

Delivery Model OverviewDelivery Model Overview

SaaS

To use the provider’s applications running on a cloud infrastructure and accessible from various client devices through a thin client interface such as a Web browser

Citizen Engagement (Wikis, Blogs, Data.gov)Government Productivity (Cloud based tools)Business Enablement (Salesforce.com)Enterprise Applications (Core Mission & Business Svcs

PaaS

To deploy onto the cloud infrastructure consumer-created applications using programming languages and tools supported by the provider (e.g., java, python, .Net)

Database and Database Management SystemsDeveloper / Testing ToolsVirtual Environments

IaaS

To provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications

• Computing• Storage• Application hosting

Model Capability Provided Example Services

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 siteMicrosoft Space Act Agreement: World Wide TelescopeOnline News Media: USA Today International Space Station FlashGoogle Moon, Google MarsOther 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

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?

The Social Cloud: Opensocial Partners

The Open Stack

DiscoveryIdentityAccess ControlPeopleApps

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.

Opensocial Containers

Social Network Sites – Profiles and HomepagesPersonal Dashboards

iGoogle, MyYahoohttp://code.google.com/apis/igoogle/docs/tutorial.html

Any Web SiteGoogle Friend Connect enables this for any site http://google.com/friendconnect

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 interfaceProvides a mechanism for leveraging Web 2.0 as an integrated solutionProvides 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 implementationProvides a framework for consolidating disparate and widely distributed content and data under “one tent”Provides a model that can keep pace with technology innovationand changeEnterprise 2.0 – easily scales for extranet/limited public access, scalability testing in lab for general public useProvides a framework for standardizing Web IT security models and processesProvides a framework for standardizing Web policy compliance andleveraging “connected governance” models and processes

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 AMTo: CONTENT-MANAGERS-L@hudlist.hud.govSubject: 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 SchoolsIRS, Web Program ManagerAppeals, Communications

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, forumGadgets and Apps extracted from key public NASA site collections

http://astrobiology.nasa.gov/http://www.nasa.govhttp://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 applicationsOther Federal Gov't Employees: Shared Federal Applications: Training, Recruitment, Payroll,

Travel Contractor Employees: general purpose employee informationBusiness Partners: Applications related to partnering with NASA: SBIR, Technology Transfer Academic Partners: Applications related to partnering with NASA: educational programs,

research grants, university programsGeneral 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

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 implementationsIntegrate innovative or cross-cutting technologyDevelop new applications, roll out new COTSKeep 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 inNASA Enterprise Services Catalog (See Appendix for details)Integrate Agency applications and/or expose functionality via XML Web ServicesDecommission 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/

Phase 1: Transition a core subset of external (non-NASA) and in-house public collections and applications to Gadgets/Apps to provide auniform/user-friendly platform for future development

Medium Grey Blinds from http://www.nasa.gov Collections

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 PortalDevelop/Provide Tools to automate the processProvide 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.govhttp://outsidenasa.nasa.govhttp://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.govIntegrated Collaborative Environment

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 DevelopersLinks to NASA Channels on Social Media SitesLinks to PhotosynthsPlanetary 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

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 RegistryApps should be “gold certified”Apps should be targeted and usefulApps Lifecycle management is essentialApps Classification and Search – good baseline metadata required, good search toolsApps need different security/access models - extranet, public access, limited access, etc.Apps data/information integrity and quality assurance is required

End GoalsNASA’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 policyMultiple Layers of Trust:

Federal eAuthentication (SAML) for in-house applications and two-factor requirementsoAuth 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 applicationsProvide in-house and government-wide IT services via online Enterprise Services Catalog

Federal Cloud IT Services Survey – Due COB June 12thAdvantages:

Continuous innovation through a virtual circle of contributions from developers and end usersStandardize information and application access/processes, move into the “NASA Social Cloud”Leverage new Administration’s focus on Federal Broadband and Cloud Initiatives

SummaryPotential First Phase Federal Partnerships:

Provide requirements for a generalized Federal open source/opensocial architectureApps for Earth, Apps for Air, Apps for Humanity, Apps for Life

Environmental Protection Agency: http://open.epa.govU.S. Geological Survey: http://open.usgs.govFederal Aviation Administration: http://open.faa.govNational Institutes of Health: http://open.nih.govDepartment of Homeland Security: http://open.dhs.govUSA: 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

Appendix: NASA Enterprise Architecture High Level Overview

NASA’s Future State Web: Enterprise Collaboration and Content Management Services

Document Management

(Documentum/Alfresco)

Team Workspace (SharePoint/MOSS/Liferay)

Wiki 1(platform-

based)

Blog 1(platform-

based)

Records Management

Knowledge Base – Published Information – Enforces Security

Web Conferencing

(WebEx –SaaS)

Multimedia Management

IM(Jabber)

Blog 2(blogs.nasa.

gov)

Adoption / Facilitation / Consulting

DDMe.g. PLM, PDM

(Windchill)

IT Business Services

Othere.g. CAD Drawings

Integration Services

Wiki 2 (wiki.nasa.

gov)

Other Dynamic Content

e.g. Multimedia

tools

Partner Knowledge

Bases

Mission Specific Collaboration and Content Management Services

---------------

Domain-Unique Services

Adoption & Facilitation (Consulting)

Legend Interface with Other Service Area =Manual Integration =

External SLA/Web services =Enterprise Collaboration Services provided by Mission Support =Content (Information & Data) provided for use by the Enterprise =

No Domain-unique serviceshave been identified, but the architecture supports it.

Public Cloud

Private CloudsCommunity Cloud

SharePoint/MOSS Usage at NASA: MOSS 2007 pilot implementations at ARC, JPL, JSC, KSC

0

1000

2000

3000

4000

5000

6000

7000

# of Users

ARC DFRC GRC GSFC HQ JPL JSC KSC LaRCMSFCNSSC SSC

Team Workspace Implementations / Reported User Counts

SharePoint 2003

SharePoint 2007

eRoom

NX / Docushare

PBMA

Phase 1 Transition: HQ, MSFC

NASA Proposed IDM Community Cloud Architecture

NASA Information Distribution System

open.nasa.govapps.nasa.govothers TBD

Phase 1: Intranet -> Cloud Transition

Focus groups at Agency, Center, and team level underway for redesign of current Vignette-based InsideNASA intranetSharePoint/MOSS and Liferay architectures share processes and requirementsOpen development process for both efforts will allow sharing of community created content, templates, webparts, gadgets, workflows, ideas, etc.

Private Cloud: InsideNASA -> MOSS 2007 Community Cloud: OpenNASA -> Liferay

LIFERAY – Next Gen PortaleTouch Systems Corp.

Next Generation Portal – Conceptual Model

Next Generation Portal – Social & Integration Aspects

Portal – What Users Need?

Portal Platform

Pre-loaded Site Pages/Tabs Personal Pages

Interest Groups

Federal Agencies

Federal Groups

SecuredApplications

User- contributed Applications

Users

Google Gadgets

SecuredPortlets

Google Gadgets

Yahoo Apps Widgets Custom Apps

Public Communities

Next Generation Portal – Vision

Personal Pages

Center Pages

Division Pages

Interest GroupPages

Next Generation Portal – Vision

Applications

Next Generation Portal – Vision

Next Generation Portal – Vision

Preloaded Tabs

Legacy Application and Site Registry• Web Sites • Web Applications

Integration Case Study - Gadgets

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

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. - > cloudSites/applications are strategically aligned with NASA programs,projects, missions, ITI LoB, etc.Sites/applications have a broad customer baseHave high usage statistics – i.e., web analyticsCan 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

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 thisEnable the internal application to support OAuthFor SSO enabled internal applications, work with the industry to develop OAuthSAML binding with access secrets/tokensBuild custom adaptors/interfaces as needed

InsideNASA Redesign: Advisory BoardTechnical and GovernanceFocus Areas:

Application, Business, Product Portfolio ManagementApplication, Business, Product Lifecycle ManagementApplication, Business, Product Development ManagementMetricsStandardsPolicy, Guidelines, Best PracticesService Models, Business Models, Operations Models

Lead Roles for NASA’s Collaboration and Content Management Architecture

One Tent Domain ManagerOperationsAdoption and ConsultingKnowledge Base DevelopmentCollaboration Services DevelopmentEnterprise Search and Portal DevelopmentConfiguration Management

InsideNASA Redesign: Focus Groups @ Ames Research Center

Near Term MOSS/Liferay IntegrationWorkgroup WorkflowsCloud Computing Standards

Multimedia StandardsData Standards

Cloud Security

Next Gen TechnologiesFederated Semantic SearchVirtual Worlds (3-D, Immersive, etc)

FIX: Federal Internet eXchange

Government Cloud Computing Framework

Infrastructure as a Service (IaaS)

Platform as a Service (PaaS)

Software as a Service (SaaS) / Applications User/ Admin Portal

Reporting & Analytics

Service Mgmt & Provisioning

Analytic Tools

Analytic Tools

Data MgmtData Mgmt

ReportingReporting

Knowledge Mgmt

Knowledge Mgmt

Citizen EngagementCitizen Engagement

Application Integration

API’sAPI’s

Workflow Engine

Workflow Engine

EAIEAI

Mobile Device Integration

Mobile Device Integration

Data Migration Tools

Data Migration Tools

ETLETL

Wikis / BlogsWikis / Blogs

Social NetworkingSocial Networking

Agency Website Hosting

Agency Website Hosting

Email / IM Email / IM

Virtual DesktopVirtual Desktop

Office AutomationOffice Automation

Business Svcs Apps

Business Svcs Apps

Core Mission Apps

Core Mission Apps

Legacy Apps (Mainframes)Legacy Apps (Mainframes)

Gov ProductivityGov Productivity Gov Enterprise AppsGov Enterprise Apps

DatabaseDatabase Testing Tools

Testing Tools

Developer Tools

Developer Tools

DBMSDBMS Directory ServicesDirectory Services

Security & Data Privacy Data/Network

SecurityData/Network

Security Data PrivacyData Privacy Certification & Compliance

Certification & Compliance

Authentication & Authorization

Authentication & Authorization

Auditing & AccountingAuditing & Accounting

Service Provisioning

Service Provisioning SLA MgmtSLA Mgmt Performance

MonitoringPerformance Monitoring

DR / Backup

DR / Backup

Operations Mgmt

Operations Mgmt

StorageStorage Virtual Machines

Virtual Machines

Web ServersWeb Servers Server HostingServer HostingCDNCDN

Data Center Facilities

Routers / FirewallsRouters / Firewalls LAN/WANLAN/WAN Internet

AccessInternet Access

Hosting CentersHosting Centers

User Profile Mgmt

User Profile Mgmt

Trouble Mgmt

Trouble Mgmt

Product CatalogProduct Catalog

Order MgmtOrder Mgmt

Billing / Invoice

Tracking

Billing / Invoice

Tracking

Customer / Account

Mgmt

Customer / Account

Mgmt

Clo

ud S

ervi

ce D

eliv

ery

Cap

abili

ties

Cloud User Tools

Cor

e C

loud

Ser

vice

s

DRAFT - GSA OCIO INTERNAL USE ONLY

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

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.Confidentiality2.Availability3.Integrity

Government Cloud Security

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?

Government Cloud Security: Confidentiality

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.

Government Cloud Security: Threats

Storage as a ServiceWeb folders

If we had access to ourFiles wherever we wereWe wouldn’t need USBDrives.

Next time there’s a fluEpidemic you’llWish you had these.

Government Cloud Security: Availability

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.

Integrity

Cloud CharacteristicsSLA-based multi-tenant business model for usersSafe & Secure, on-demand, self-serviceSelf-configuring & provisioning, self-healingComprehensive, open, standardized APIs for

developersFully virtualized and scalable

applications, operating systems, network, storageHide the complexity of

Create, start/stop, import/export, snapshot, rebootBackup/restore, move, destroy

Cloud Ownership ModelsUse the Cloud

Startup, SMB, Research projectsLeverage the Cloud

Temporary on-demand loadFunctional off-load

Build my own internal CloudEnterprise Infrastructure GridDrive Internal IT economicsStandardize development environment/services

Be the CloudRedefine ServicesNew Business OfferingsHosting and Operations partnersSoftware Vendors

The Cloud Computing Stack

Clients

Services

Applications

Platform

Storage

Infrastructure

Web 2.0: Web of ParticipationWeb 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,anyoneedits; 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.

Seven Steps for Next Gen Web1. Empower people with cloud

computing, Web 2.0/Web 3.0 to connect, collaborate, and communicate across boundaries and at scale.

2. Establish pilot programs that open up government decision-making and involve the public in the work of agencies, not simply by soliciting opinions, but by tapping into the vast and distributed expertise of the American citizenry to help government make more informed decisions.

3. Employ technologies, including blogs, wikis, cross-agency portals and social networking tools, to modernize internal, cross-agency, and public communication and information sharing, and to improve collaboration and government decision-making.

4. Liberate silo-ed data and information. Make dynamic mash-ups across applications, data.

5. Simplify linking and sharing public information across systems, agencies, and jurisdictions. Expose structure and meaning using semantic standards. Provide APIs, web services, widgets and gadgets. Enable human and system to system access. Use Service Oriented Architectures (SOA) to promote interoperability between applications.

6. Improve user experience with Web 2.0/Web 3.0 semantic technologies. Upgrade web site UIs with semantic search and query, natural language understanding, visualization, and reporting, that combines structured data sets, document repositories, and web pages. Add intelligence to user interfaces.

7. Use Web 2.0/3.0 social media channels to converse, communicate, publish, and interact. Reach out to the public, co-workers, and partners using a full spectrum of communication channels, feeds, media, and forums.

Technical Presentation, Part 2

Technical OverviewDemoQ & AResources:

Federal Cloud WikiFederal CIO CouncilDashboard Guidance and Open Houses

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/home/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.

Share Your Thoughts