Welcome to the Open Graph of IT Ontology

Overview

Open Graph of IT (OGIT) aims to build a semantic representation of all IT and its interaction with business processes and people. Such an endeavour requires a sound data space as a foundation for computational evaluation of this enterprise space. OGIT aims to become the 'IT version' of Google's Knowledge Graph or Facebook's Social Graph. Hence we need a common language for IT entities and relationships between them.

OGIT aims to provide a such common language by defining an ontology for the Graph of IT.

The OGIT project is not only a hosting place for a specification. It also provides a platform for domain experts to contribute to the ontology. One of the basic principles is: evolution over standardization.

Conventions for contributed namespaces

These apply to every namespace contributed to OGIT, not to any one contributor:

• Creator. Objects contributed by an organisation carry dcterms:creator set to that organisation (e.g. "Almato AG"), never an individual's name or email.
• Fixed value sets. Boolean and closed-enum attributes carry ogit:validation-type "fixed" plus ogit:validation-parameter "<csv>" (for booleans, "true,false"). Attributes whose description is open-ended ("... etc.") omit the fixed parameter.
• Edge targets are concrete. ogit:allowed always names concrete vertex types. OGIT has no edge inheritance and no any-vertex edge target -- ogit:Node and ogit:Entity are never edge targets. To reference an entity of arbitrary type, use a soft *VertexXid attribute (e.g. lockedVertexXid) instead of an edge.
• Additive only. A contributed namespace adds entities, attributes and verbs; it does not alter existing OGIT objects.

Namespace README discipline

• A short README.md in every new namespace subdirectory: what the namespace is and any namespace-specific rule, developer-focused, no marketing prose.
• Do not reference documents outside this repository (internal concept or phase docs, PR backtraces). If more detail is needed it belongs in the published OGIT documentation, not in a backtrace a repo user cannot follow.

OGIT Documentation

Find out more about OGIT using the following links.

• Basic Concepts
• OGIT ontology details
• Maintaining the ontology
• Get started with an implementation:
  • Using OGIT in Apache Jena Fuseki
  • Using OGIT with Apache Tinkerpop
  • Using OGIT in Cayley
• High level use cases
• Contributing to the ontology

Bardioc Documentation

There is an application called Bardioc that allows you to manage IT data through a RESTful API ensuring compliance to the OGIT ontology.

The following links provide more information on OGIT and Bardioc.

(Pages updated on daily basis)

• OGIT documentation for all elements of the OGIT ontology
• OGIT namespace documentation- documentation as PDF and Diagram for each namespace of the OGIT ontology

namespace specific Documentation

• Requirements

  • install pdflatex (on macOS run: brew cask install mactex)
  • install graphviz (on macOS run: brew install graphviz)
  • install doxygen (on macOS run: brew install doxygen)

• Run the following script to generate the documentation. Replace the namespacename with the name of the namespace(for ex. MRP, Accouting, Auth etc.) you want to create the documentation.

sh namespace.sh namespacename

• It will generate the pdf and png files which can be found under folder with namespacename (for ex. MRP, Accounting etc).
• For Example, sh namespace.sh mrp will generate the documentation for MRP namepsace under MRP folder.

Getting Support

If you have general questions or need support please contact us at info@almato.com.

License

Please see LICENSE.md for information about the licensing of OGIT and its components.