Consider to allow an implementer to publish a manifest instead of committing the manifest in the directory

[filip26]

It would be nice to give an implementer more freedom to operationally change [test]manifest. This way, it could evolve in a general manifest [services discovery], and also, it would be a great demonstration of using linked data, by starting just with one endpoint pointing to the manifest that an implementer has provided.

[filip26]

if you would be in a playful mood then the manifest could be signed and wrapped as VC ;) to support possible future direction focusing on a discovery.

It could have an impact on wallets, etc. e.g. a wallet could download "trusted" verifier configuration, the manifest.

[BigBlueHat]

I definitely like where this could head and what doors it would open. Sadly, "for now" (however endless that may be...), I think we'll have to stay the course on committing/storing them here to keep the focus on building the actual test suites.

Definitely open to discussing the idea, though!

[filip26]

Well, sometimes you have to open the door just to see what's behind ;) I see no risk as long as an implementer is interested to pass a test suite, i.e. to provide correct, processable, manifest.