Extending `providers` values for remote/decentralized data

[fmigneault]

In the providers roles: https://github.com/radiantearth/stac-spec/blob/master/commons/common-metadata.md#roles

stac-spec/item-spec/json-schema/provider.json

Lines 25 to 37 in ec002bb

	"roles": {
	"title": "Organization roles",
	"type": "array",
	"items": {
	"type": "string",
	"enum": [
	"producer",
	"licensor",
	"processor",
	"host"
	]
	}
	},

Available roles allow representing self-hosting of derived products.
However, given that STAC can point to assets hosted anywhere (including decentralized nodes), a STAC catalog/collection/items that simply indexes existing data from alternate source locations does have a clear way to indicate its own role.

For example, we intend to provide "augmented" STAC metadata of parsed non-STAC data sources to facilitate search and retrieval by users from common location, but we are neither going to duplicate the data (therefore not host or producer of the data), nor modify it (therefore not processor), and are not owner (therefore not licensor). A network of decentralized nodes could all refer to a common data source, while neither of them hosts or duplicates the reference data to ensure that they share the same unique "source of truth".

Could there be an addition to the Enum to include indexer, or other similar roles for remote server references?

Current workarounds include using rel: alternate links and https://github.com/stac-extensions/contacts, but those are not as explicit about the "data provisioning" aspect, and is mixed with other non-data-specific contact details.

[jsignell]

This proposal makes a lot of sense to me. I think you would want to update the descriptive text for Providers in the stac-spec since it really emphasizes processing or altering the data.

[m-mohr]

In STAC Index we don't actually alter the metadata. People will find it through the indexer any way so I didn't see a point in adding it specifically as additional provider. If I'd go for it, I'd honestly just use "host". If you index it, you host the metadata. I don't think host must specifically be about the assets only.

If we add a new role to the enum, is that a breaking change that needs 2.0? A client not expecting it could break, right?

[fmigneault]

The current "host" definition does not allow using it for that purpose:

host: The host is the actual provider offering the data on their storage. There should be no more than one host, specified as the last element of the provider list.

Because:

1. The server is not the actual data storage location
2. Since the actual host storage should still be indicated, another host (or multiple ones in a decentralized network) would be invalid and confusing