Could you use a internal URI scheme as the repository URL, like "turandot:"?
Sure, if I extend my whole URL handling library. :) I actually can do that in my specific case, but I'm sure that many orchestrators cannot, and in any case I think it should be supported by TOSCA grammar rather than requiring orchestrators to implement difficult workarounds.
Â
it really would like to know what type of repository it is and have properties or at least metadata.Â
Metadata is the ultimate workaround! In the case of artifacts -- they are typed, so we can use actually modeled data: TOSCA properties (but because TOSCA is object-oriented you would need all artifact types to import from that base type, which is not always possible). These are all workarounds. I think that because artifact management and import management are so intrinsic to TOSCA it should be well-defined in the grammar itself.
I'm sure we all agree that TOSCA repositories are quite ineffective right now and can use some of our attention.