One action item determined by the online team from the February 17th Open Government Directive Workshop was to make the feature set for a next gen collaborative platform (for citizen contributed apps) available to the OGD community to add to, comment on, etc.  For consistency with the OGD, we will call this platform Open[AGENCY] 2.0, with the assumption that there will be one at each of the Federal, State and Local Government Agencies.

 

Here is a first draft, please add whatever you would ideally like to see in a .gov or .mil social platform (user profiles, social apps, activity streams/status updates, blogs, wikis, etc.).  Please edit freely - if this format is hard to understand, please modify to make it more transparent:

 

 

4.   Collaborative Platform - Policy Compliance

4.1. All systems and services should be in compliance with federal laws and regulations and [AGENCY] policy, including but not limited to:

4.1.1.              [AGENCY] Policy Directive and [AGENCY] Procedural Requirements for “Records Management”

4.1.2.              Work with the [AGENCY] Records Officer to identify and address the appropriate management of records resulting from Web services provided under this contract;  Such activity may include participation in developing records retention schedules and proposed approaches for compliance with Federal records requirements

4.1.3.              A plan for managing government-owned records

4.1.4.              An inventory of contractor-held, government-owned records

4.1.5.              [AGENCY] Policy Directive and [AGENCY] Procedural Requirement for “Information Technology Security”

4.1.6.              Section 508 of the Rehabilitation Act of 1973 for Electronic and Information Technology, per Subpart B - Technical Standards, Web-based Intranet and Internet Information and Applications (1194.22) parameters and guidelines

4.1.7.              Compliance with [AGENCY] policy, as required in this section, as [AGENCY] policies are updated

4.2. Agency authentication and authorization requirements and integrate with authentication and authorization infrastructure

4.3. Group, role, and/or user-based management and display of data and a simple way for [AGENCY] personnel to assign people to new groups and roles

4.3.1.              Personal User Configurable Dashboards/User Profiles

4.3.2.              A portal-based product for end user personalization of www.[AGENCY].gov content

4.3.2.1.    A mechanism to store and remember a users customizations/profiles

4.3.2.2.    Allow a user to bookmark any feature, image or video from www.[AGENCY].gov

4.3.2.3.    Content Personalization

4.3.2.3.1.   Allow a user to view the content from any topical channel in www.[AGENCY].gov;

4.3.2.3.2.   Allow a user to view any www.[AGENCY].gov RSS feed

4.3.2.3.3.   Allow a user to add any www.[AGENCY].gov widgets to their customized pages. For example, the [AGENCY] calendar, or individual calendars

4.3.2.3.4.   Allow a user to create a custom image gallery from individual image pages in www.[AGENCY].gov

4.3.2.3.5.   Allow a user to create and view a custom RSS feed based on metadata

4.3.2.4.    Behavior Personalization

4.3.2.4.1.   Show in a single interface “User Participation” consisting of any blog or feature comments, ratings, and forum posts submitted by the user

4.3.2.4.2.   Allow a user to share their customizations with other users

4.3.2.4.3.   Allow a user to save searches performed on www.[AGENCY].gov

4.3.3.              Provide a portal-based product to host applications

4.3.3.1.    Support hosting of JSR-168 based applications

4.3.3.2.    Provide a role based authentication capability for end users

4.3.3.3.    Role based authentication capability for administrative users

 

4.3.3.4 Activity Streams (Status updates)

   

4.4.        Open[AGENCY] 2.0 Functionality

4.4.1.              Develop and maintain Open[AGENCY] 2.0 (http://open.[AGENCY].gov), a public/open platform for Agency personnel (employees and contractors), Federal, State, Local Government, Academic and Industry partners, and limited (up to XXX) public citizen access to communicate, comment, collaborate, share knowledge, contribute content and apps, and quickly find information they need to get their jobs done;

 

Open[AGENCY] 2.0:

4.4.1.1.    shall integrate distributed information, as well as hosts content when appropriate and needed

4.4.1.2.    shall provide for distributed content providers and developers who will provide content and local championship

4.4.1.3.    shall be integrated with other social platforms (Facebook, Twitter, YouTube, LinkedIn, myYahoo, iGoogle, GovLoop (Ning), MySpace, etc.) as required by application owners and end users

4.4.1.4.    shall be accessible from all networks

4.4.2.              Design and manage Open[AGENCY] 2.0 as one of the principal avenues for single sign on and application integration

4.4.3.              Provide content creators and editors with content-management capabilities such as the high-volume news publication

4.4.4.              Provide web designers and developers with a social site for matching experienced developers with new/citizen developers

4.4.5.              Provide an integrated web site for web designers and developers to provide support for:

4.4.5.1.    creating/modifying OpenSocial apps

4.4.5.2.    integrating new/existing web applications

4.4.5.3.    integrating core Agency COTS legacy applications

4.4.5.4.    enhancing open source components

4.4.5.5.    creating/ modifying Open[AGENCY] 2.0 portlets and gadgets

4.4.5.6.     accessing core in-house web application frameworks (python, ruby, .net, .php/mySQL, objective-C, Java, Perl, Ajax, others as required)

4.4.5.7.    accessing gadget/app/widget registries

4.4.5.8.    accessing in-house web sites for displaying, commenting on and rating new and ongoing work

4.4.5.9.    accessing web policy

4.4.5.10. accessing web data, content, APIs, data connectors, tools

4.4.5.11. accessing best practices, processes and guidance

4.4.6.              A central, efficiently-organized Web location for authorized [AGENCY]-wide information and applications

4.4.7.              Personalization capability

4.4.8.              Flexibility, scalability and reliability specifically for up to XXX registered users

4.4.9.              Web hosting of static and dynamic content

4.4.10.           Cross [AGENCY] Center connectivity

4.4.10.1. Shall integrate with [AGENCY] WAN connections

4.4.10.2. Shall provide VPN connection between [AGENCY] centers and Internal [AGENCY] datacenters

4.4.10.3. Shall provide LAN connectivity at each of the centers to the WAN and the Internal [AGENCY] datacenters

4.4.11.            Efficient access to mandatory Agency Web resources and trusted external resources

4.4.12.           A Central Web location for [AGENCY]-wide internal and external communications including Emergency Operations Center (EOC)

4.4.13.           Evolvable external Web environment for application integration

4.4.14.           Integrate with Agency authentication and directory integration

4.4.15.           Integrate login with oAuth and open ID

4.4.16.           Support the following standards: PortableContacts, shindig gadget containers, the OpenSocial reference implementation, and XRDS-Simple

4.4.17.           Use open source software components when available

4.4.18.           Provide mobile device versions of the web pages, apps and gadgets

4.4.19.           Provide international or multi-lingual support for at least 22 languages for ingest and display.

4.4.20.           Meet [AGENCY] workforce needs for access to [AGENCY] resources under any circumstances, planned or emergencies

4.4.21.          Integrate with collaboration tools to facilitate two-way communications between [AGENCY] management and employees

4.4.22.           Emergency Operations Center (EOC): Provide internal and external access to internal disaster communications during natural and man-made disasters

4.4.23.           Role-based access. Provide users secure access to resources and tools based on these roles and the user’s credentials:

4.4.23.1. Federal employee

4.4.23.2. [AGENCY] employee

4.4.23.3. Employee, contractor or partner of a [AGENCY] Center or Field installation

4.4.23.4. Employee, contractor or partner of a [AGENCY] Special purpose installation

4.4.23.5. Member of a project or program team

4.4.23.6. Member of the general public (i.e., citizen developers, general users)

 

4.4.23.7 State or Local Government Employee

 

4.4.23.8 Academic Partner

 

4.4.23.9 Industry Partner

4.4.24.           Allow approved [AGENCY] external affiliates to see and contribute content in a secure manner

4.4.25.           Provide authenticated remote access capabilities at the centers to their individual networks

4.4.26.           Document Management

4.4.26.1. Provide a means for users to upload documents and share with other users and/or groups of users

4.4.26.2. Import of multiple documents, web pages, indexed content, etc.

4.4.26.3. Automatic feeds of images, documents, etc.

4.4.27.           Hosting & Operations

4.4.27.1. Provide hosting for Open[AGENCY] 2.0 and the [AGENCY] Team Collaboration systems

4.4.27.2. Provide operations support for Open[AGENCY] 2.0 and the [AGENCY] Team Collaboration systems

4.4.27.3. Provide technical support to Open[AGENCY] 2.0 content publishers

4.4.27.4. Provide technical support for Open[AGENCY] 2.0 application, gadget, widgets, apps and portlet developers

4.4.27.5. Provide technical support for the [AGENCY] Team Collaboration system and users

4.5.        User Interface and Site Design

4.5.1.              Navigation and Information Architecture

4.5.1.1.    Provide the ability for users designated by [AGENCY] to create or edit navigation in defined areas

4.5.1.2.    Provide, upon authorization by [AGENCY], site maps or content maps for logical content collections

4.5.1.3.    Support naming conventions and elements within the [AGENCY] taxonomy by using a taxonomy for categorical organization of content or by mapping content categories to the taxonomy.

 

4.5.1.4.    Generate automatic bread crumb trails that are live links to the labeled content

4.5.2.              Redesigns: Manage and execute redesigns as directed by [AGENCY];

 

4.5.3.              Usability

4.5.3.1.    Perform usability testing quarterly, according to standards and best practices, such as those outlined on usability.gov

4.5.3.1.1.   Plan usability tests to meet requirements specified by [AGENCY];

 

4.5.3.1.2.   Conduct the tests and analyze and report the results and make recommendations

4.5.3.1.3.   As directed by [AGENCY], implement recommendations

4.5.3.1.4.   During the phase-in period, but after the training, conduct with [AGENCY] users an end-to-end usability test that will cover content creation, publication, syndication, all other features (such as polling, comment, content rating, etc.) and incorporate feedback and improvements into the overall system design and individual components before the contract start date

4.5.3.1.5.   Conduct usability tests for all new features and implement results before they go into production

4.5.4.              Presentation

4.5.4.1.    Provide an integrated media player that can incorporate video from [AGENCY] and non-[AGENCY] sources together

4.5.4.2.    Support plug-ins and display documents

4.5.4.3.    Support STEP-compliant CAD files

4.5.4.4.    Design new features to be fully functional for all appropriate user agents and operating systems in common use;  Negotiate specific user agents and operating systems

4.5.4.4.1.   Follow industry best practices for “graceful degradation” of content for user agents not covered by 42.4.4, so that those users receive the basic information on the site, presented effectively, e.g., without having to scroll through expanded navigation menus before getting to content