Component Definitions: Questions and suggested changes to be triaged.

[leecalcote]

In context of a Component definition:

1. Suggestion: Open a GitHub issue regarding the "format": "JSON" property to ensure that this means that the format of the for describing this component's schema source type component and the format of the component's configuration.

2. Question: Why is the more important kind buried under "component":, while the less important displayName and description are at the top level?

3. Question: Can you export a Kubernetes resource at a particular ResourceVersion?

4. Suggestion: There is no need for model in the component schema given that we only register the component in context of the model.

5. Suggestion: "version": "core.meshery.io/v1alpha1" is self-referential in the case of Meshery core components. This should be optional.

6. Suggestion: Capability $refs need to be downsized to only include the smallest set of properties needed to uniquely identify the resprective capability, therein avoiding repeating ourselves. Systems, like Meshery, that offer these capabilities can then use the $ref to lookup the full capability definition and save API requests by intelligently offering the full capability definition upon GET of a Component.