Giter Site home page Giter Site logo

project-interoperability / project-interoperability.github.io Goto Github PK

View Code? Open in Web Editor NEW
28.0 25.0 30.0 3.8 MB

Project Interoperability: A Start-Up Guide to Info Sharing

Home Page: http://project-interoperability.github.io

License: Creative Commons Zero v1.0 Universal

Ruby 3.65% HTML 15.56% CSS 79.96% JavaScript 0.15% Shell 0.68%

project-interoperability.github.io's Introduction

Project Interoperability

IMPORTANT: This is a collaborative draft project. If you have questions or concerns, please create an issue.

Problem this Solves

Government needs to share information better, faster, and smarter. Our mission is to improve the government's ability to share the right information, with the right people, at the right time.

How this Project Solves this Problem

The goal of Project Interoperability is to help government and non-government organizations identify a baseline of terms, tools, and techniques to connect networks and systems. We aim to be architecture-agnostic, and we are trying to normalize the way information sharing technology is developed. We want to achieve a connected government.

This project is based on Project Open Data. Imitation is the sincerest form of flattery.

Who Are We?

We are the Office of the Program Manager for the Information Sharing Environment (ISE). We were created in 2004 in response to the 9/11 Commission report. We are the national office charged with advancing responsible information sharing in support of counterterrorism and homeland security. We work with federal, state, local, and tribal government partners, and with the private sector and internationally. You can read more about us here.

The Standards Coordinating Council (SCC) is an advisory group made up of standards organizations and industry associations (such as IJIS and OMG). The SCC is leading the operationalization of Project Interoperability, via two different types of communities:

  • Communities of Interest will drive mission-centric information sharing and safeguarding. Examples of communities of interest are “statewide and regional ISEs” or “cyber information sharing.”
  • Communities of Practice will collaborate with the communities of interest to achieve mission-focused goals of the ISE. Communities of practice will be oriented around functions and capabilities, such as FICAM or open standards.

Where You Come In

Project Interoperability can be used to access, improve, and use information sharing tools and resources. It uses some of the existing, well known enterprise architecture frameworks (TOGAF, DoDAF, FEAF, etc.), and the principles of service-oriented architecture (such as reuse and intrinsic interoperability) to suggest standards, tools, and methodologies to link existing systems. It also specifies the development of common documents and products that will enable disparate departments’ and agencies’ architectures to make the full framework operational.
Project Interoperability can be utilized differently depending on the role you have in your organization. Some examples include:

  • Program manager or procurement officer: Project Interoperability provides suggestions on what you need to have an interoperable system. It gives a program manager the language they need to describe what they want to aid in more cost-effective and smoother procurement.
  • Private industry: Project Interoperability provides a common language to help industry respond to RFIs and hold conversations with federal customers about their needs.
  • Architect: When setting up models, schemas, and deciding what standards to apply, Project Interoperability guides decision making around architecture details.

How to Contribute

We are making this content available on GitHub so that you can share feedback and suggestions for improving these tools and resources. If you are new to GitHub, you should check out our guide to contributing. Any other questions? Reach out to us by creating an issue or sending us a message.

This project constitutes a collaborative work ("open source"). Federal employees and members of the public are encouraged to improve the project by contributing.

License

The project is a public domain work and is not subject to domestic or international copyright protection. See the license file for additional information.

Members of the public and US government employees who wish to contribute are encourage to do so, but by contributing, dedicate their work to the public domain and waive all rights to their contribution under the terms of the CC0 Public Domain Dedication.

Privacy

Comments, pull requests, and any other messages received through this repository may be subject to archiving requirements. Learn more about our privacy policies at http://ISE.gov/site-policies.

project-interoperability.github.io's People

Contributors

allalala avatar beuchelt avatar cathrynmarcuse avatar dsofranac avatar dwvisser avatar leahbannon avatar mekennedy79 avatar mhaselkorn avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

project-interoperability.github.io's Issues

National Strategy

The National Strategy for Information Sharing and Safeguarding has three principles. We list the first - Information as a National Asset - in the header. should we list the other two?

Getting mixed content loading errors in Firefox

Due to attempting to load the following resources via HTTP instead of HTTPS.

  • assets/css/bootstrap.css
  • assets/css/site.css
  • assets/js/bootstrap.min.js
  • github-btn.html

Also, seeing a 404 response error code when page tries to load javascripts/scale.fix.js

site.css attempts to load nonexistent seal.jpg for page background

I see an error like "/assets/img/seal.jpg not found" in my local server log when trying to run this site locally. A little sleuthing determines that assets/css/site.css line 676 is where this reference gets made. Perhaps the decision was made to pull the seal from the site's look? I suggest removing the line from the style file.

Discussion pages for WIS3 topics

Should we add pages or link to existing online forums being used, for communities of interest and communities of practices that are coming together at WIS3?

For example, for the NJ ISE or link to the existing cyber threat modeling online community?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.