AI Model
IRI: https://w3id.org/altium/cdm/software/AIModel
Bounded context: software
AI model artifact in context of a workspace
Platform API
GRID (1)
grid:workspace:{workspace-id}:software:ai-model/{id}
Diagram
---
config:
layout: elk
theme: neutral
class:
hideEmptyMembersBox: true
---
classDiagram
direction LR
class sft_ai_model["AI Model"]
style sft_ai_model fill:#3c78d8
click sft_ai_model href "../../classes/sft_ai_model/"
sft_ai_model --> "*" plt_solution : part of solution
click plt_solution href "../../classes/plt_solution/"
class plt_solution["Solution"]
style plt_solution fill:#cccccc
sft_ai_model : id
class sft_software_project["Software Project"]
style sft_software_project fill:#3c78d8
sft_software_project --> "0..1" sft_ai_model: ai_models
click sft_software_project href "../../classes/sft_software_project/"
class sft_software_release["Software Release"]
style sft_software_release fill:#3c78d8
sft_software_release --> "0..1" sft_ai_model: ai_models
click sft_software_release href "../../classes/sft_software_release/"
Comments
We start with a simple Artifact-like entity without explicit revisions support. The assumption is that if we need revisions going forward, we'll add explicit revision entity, define GRID for it, relations, etc.
TODOs
Data Content Platform would likely define another (but related) AI model entity - the one that is going to be part of Solution Template. The exact name / definition of the entity is TBD.
Inheritance
- Entity
- Artifact
- sft_ai_model [ SolutionItem]
- Artifact
Fields
| Name | Cardinality | Type | Description | Inheritance |
|---|---|---|---|---|
| part of solution | * |
Solution | None | SolutionItem |
| id | 1 |
GRID | Globally unique identifier across the whole platform. | Entity |
Identifier and Mapping Information
Annotations
| property | value |
|---|---|
| grid | grid:workspace:{workspace-id}:software:ai-model/{id} |
| maturity | EXPERIMENTAL |