You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Classical" SemApps instances have the possibility to deploy a VOID endpoint, which is used then by the data provider to find the containers based on the type of resources being requested.
On a Pod provider config, we cannot use a VOID endpoint because it would depend on each Pod. VOID endpoints use /.well-known URLs, and so we can have only one per domain name. As a consequence, we need to hard-code on the data provider config the containers that are available.
However, as soon as Pods supports TypeIndexes, we can use them instead of VOID to find the available containers.
Of course VOID should still be used when available.
The text was updated successfully, but these errors were encountered:
"Classical" SemApps instances have the possibility to deploy a VOID endpoint, which is used then by the data provider to find the containers based on the type of resources being requested.
On a Pod provider config, we cannot use a VOID endpoint because it would depend on each Pod. VOID endpoints use
/.well-known
URLs, and so we can have only one per domain name. As a consequence, we need to hard-code on the data provider config the containers that are available.However, as soon as Pods supports TypeIndexes, we can use them instead of VOID to find the available containers.
Of course VOID should still be used when available.
The text was updated successfully, but these errors were encountered: