Title here
Summary here
The command line client supports a special notation scheme for specifying references to OCM components and repositories. This allows for specifying references to any registry supported by the OCM toolset that can host OCM components:
[+][<type>::][./][<file path>//<component id>[:<version>]or
[+][<type>::]<domain>[:<port>][/<repository prefix>]//<component id>[:<version]or
[<type>::][<json repo spec>//]<component id>[:<version>]
Besides dedicated components it is also possible to denote repositories as a whole:
[+][<type>::][<scheme>:://]<domain>[:<port>][/<repository prefix>]or
[+][<type>::]<json repo spec>or
[+][<type>::][./]<file path>
The optional + is used for file based implementations
(Common Transport Format) to indicate the creation of a not yet existing
file.
The type may contain a file format qualifier separated by a +
character. The following formats are supported: directory, tar, tgz
ghcr.io/mandelsoft/cnudie//github.com/mandelsoft/pause:1.0.0
ctf+tgz::./ctf