The OCID of the model's compartment.
The OCID of the user who created the model.
An array of custom metadata details for the model.
An array of defined metadata details for the model.
Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: {@code {"Operations": {"CostCenter": "42"}}}
A short description of the model.
A user-friendly display name for the resource. It does not have to be unique and can be modified. Avoid entering confidential information.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. See Resource Tags. Example: {@code {"Department": "Finance"}}
The OCID of the model.
Input schema file content in String format
The state of the model.
The OCID of the model version set that the model is associated to.
The name of the model version set that the model is associated to.
Output schema file content in String format
The OCID of the project associated with the model.
The date and time the resource was created in the timestamp format defined by RFC3339. Example: 2019-08-25T21:10:29.41Z
Unique identifier assigned to each version of the model. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The version label can add an additional description of the lifecycle state of the model or the application using and training the model.
Models are mathematical representations of the relationships between data. Models are represented by their associated metadata and artifacts.