Skip to main content

Applications

Applications provide ontological models for specific third-party systems, platforms, and tools that integrate with the ABI ecosystem. These application-level ontologies extend ABI domain concepts for concrete implementations.

note

Application ontologies in this section are not fully vetted and are subject to changes as we refine the modeling approach for third-party integrations.

Application Categories​

Microsoft Office Suite​

  • Microsoft Office - Complete Office suite integration
  • Word - Document processing with text-based schema
  • Excel - Spreadsheet application with cell-based schema
  • PowerPoint - Presentation application with slide-based schema

Google Workspace Suite​

Professional Networks​

  • LinkedIn - Professional networking and career data
  • GitHub - Code repositories and development workflows

AI & ML Platforms​

Communication Platforms​

  • Slack - Team communication and collaboration
  • Discord - Community and voice communication
  • Email - Email systems and protocols

Development Tools​

  • OpenAPI - API specification and documentation
  • Docker - Containerization and deployment
  • Kubernetes - Container orchestration

Data Platforms​

Architecture​

Applications extend the ontological hierarchy:

Integration Patterns​

Data Integration​

Applications typically extend ABI data concepts:

  • Data Sources - Application-specific data access patterns
  • Information Objects - Application document types
  • Message Types - Application communication protocols

Agent Integration​

Applications extend ABI agent concepts:

  • Application Agents - Platform-specific AI agents
  • User Agents - Human users within applications
  • System Agents - Automated application processes

Process Integration​

Applications extend ABI process concepts:

  • Application Workflows - Platform-specific processes
  • Integration Events - Cross-application triggers
  • Synchronization Processes - Data consistency operations

Implementation Guidelines​

Naming Conventions​

  • Use PascalCase for class names (e.g., LinkedInProfilePage)
  • Prefix with application namespace (e.g., linkedin:, office:)
  • Extend appropriate ABI domain classes

Documentation Standards​

  • Include practical examples for each application class
  • Document API integration patterns
  • Provide authentication and authorization guidance
  • Reference official application documentation

See Also​