Paul Boyd

@rareddy, @dhirajsb, based on our discussion, I made some changes to this: - added catalog artifact endpoints - add `repository` field to `CatalogModel` - moved everything possible to the base...

> I am still of the opinion that we should move all even 3 existing properties of `BaseModel` to `BaseModelVersion` and rename the `BaseModelVersion` to `BaseModel` or simply `Model`. IMO...

@danielezonca, this is a re-attempt at PR #823. Can you take a look?

This PR has been overhauled after some recent discussions and the re-worked base types: - Separate the model catalog from the model registry spec (based on #1012, which can be...

The latest update removes catalog model versions and adds the specific fields back. We can't merge this until the registry code is updated to handle the new fields, but the...

> @pboyd Maybe I'm missing something, but how is common.yaml being used? [`scripts/merge_opernapi.sh`](https://github.com/kubeflow/model-registry/blob/main/scripts/merge_openapi.sh) merges `common.yaml` with either `api/openapi/src/catalog.yaml` or `api/openapi/src/model-registry.yaml`.

Thanks for the review, @tarilabs. > I have one question please. For a Model, "uri" is only available in the several Artifact(s), as the relationship is Model 1:N Artifacts. I'm...

@tarilabs, yes, we could have the same model from multiple sources. I'm not sure what we could do to merge the records though.

@tarilabs, yes, I agree that that is probably the most likely scenario.

The last update removes the `long_description` field. There will now be a single `description` (and a readme/model-card).