Back to Explore

almatoai/OGIT

GitHub
12 updates · last 90 days1 watchersOpen source

Last release: 5 days ago

Almato AI’s Open Graph of IT (OGIT) provides an ontology and documentation to model IT entities and their relationships with business processes and people. It is useful if you want a shared “common language” for IT data and can leverage it through implementations like Apache Jena Fuseki, Apache Tinkerpop, or Cayley, with support for managing IT data via the Bardioc REST API.

Project status

  • The repository (almatoai/OGIT) appears actively maintained, with the latest upstream push on 2026-05-27 and multiple versioned updates in May 2026.
  • The update cadence looks fairly steady, roughly every few days to a couple of weeks (for example, 100.0.4 on 2026-05-22, then 100.0.3 on 2026-05-20, and 100.0.2 on 2026-05-08).

AI summary generated 6 days ago

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • 100.0.5

    5 days ago

    Release 100.0.5 contains effectively no release-note information (none provided by the publisher). The code diff shows a single change to a Turtle schema/entity definition.

  • 100.0.4

    1 week ago

    Release 100.0.4 contains no publisher-provided release notes. The code diff shows RDF schema/entity definition changes for Document and DocumentInfoRecord, adding new properties and allowed relationships that could affect consumers relying on the previous entity shape.

  • 100.0.3

    1 week ago

    Release 100.0.3 has no publisher release notes provided. The code changes add a new RDF datatype property, savedTimeSeconds, and then reference/include it in the AutomationIssue schema/state structure.

    Features
  • 100.0.2

    3 weeks ago

    This release (100.0.2) has no publisher-provided release notes. The code change set is limited to a single TTL modification in the Person entity.

  • 100.0.1

    3 weeks ago

    Release 100.0.1 introduces a new ontology datatype property, ogit.Automation:manualProcessingTimeSeconds, and registers it as part of the KnowledgeItem attributes set. No release notes were provided by the publisher, so the changes below are all undocumented.

    Features
  • 100.0.0

    3 weeks ago

    This release (100.0.0) has no publisher release notes. The code diff shows a large, additive update to the RDF/ontology schema, introducing many new OWL object properties (verbs) and extending which predicates are allowed on core entities like Organization, Person, Address, and Position.

    Features
  • 3.1.0

    1 month ago

    Release 3.1.0 introduces new ontology (NTO) elements for OSINT security data, focusing on compliance (sanctions) and financial market (crypto transaction tracing), plus transport-related ontology additions per the release notes. The code diff shows only additive changes to Turtle ontology files, with 0 lines deleted, indicating no removed exports or API surfaces.

    Features
  • 3.0.100

    1 month ago

    No release notes were provided for version 3.0.100. The code diff for this release only changes ontology entity definitions (Turtle files) by expanding which relationships are allowed for Ticket and Rating.

  • 3.0.99

    1 month ago

    Release 3.0.99 has no publisher-provided release notes. The only detected change in the code diff updates the RDF ontology definition for the Form entity.

    Features
  • 3.0.98

    1 month ago

    No release notes were provided for version 3.0.98. The only code change in this release updates an RDF/Turtle ontology file for Email by adding a new Automation-related prefix and a new relationship from ogit:Email to ogit:generates ogit:Automation:AutomationIssue.

  • 3.0.97

    1 month ago

    Release 3.0.97 contains no published release notes (none provided by the publisher). The only observed change in the code diff is a small update to the Ticket ontology definition in a single TTL file.

  • 3.0.96

    1 month ago

    Release 3.0.96 includes a small set of ontology/entity schema changes across four Turtle (TTL) files. No release notes were provided by the publisher, so the documented change set cannot be validated against what actually changed.