Recommend HTTP(S) for thumbnails etc.

Author: m-mohr

CHANGELOG.md

@@ -8,6 +8,10 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unreleased]
 
+### Changed
+
+- Recommend that thumbnails and similar assets use HTTP(S) as access mechanism
+
 ## [v1.1.0] - 2024-09-10
 
 ### Added

best-practices.md

@@ -39,6 +39,7 @@
     - [Keep catalogs in sync with cloud notification and queue services](#keep-catalogs-in-sync-with-cloud-notification-and-queue-services)
   - [How to Differentiate STAC Files](#how-to-differentiate-stac-files)
 
+
 This document makes a number of recommendations for creating real world SpatioTemporal Asset Catalogs. None of them 
 are required to meet the core specification, but following these practices will make life easier for client tooling
 and for users. They come about from practical experience of implementors and introduce a bit more 'constraint' for
@@ -426,6 +427,10 @@ If your data for the Item does not come with a thumbnail already we do recommend
 | Spatial extent                 | Limited                                             | Full                                                               | Full                                                                                         |
 | Use case                       | Quick overview, often in lists of items/collections | Display for a single Item/Collection, sometimes shown on a web map | Display for a single Item/Collection, often shown on a map, may be displayed in GIS software |
 
+The files offered for the roles `thumbnail`, `overview` and `visual` should be accessible via HTTP(S).
+If the [Alternate Asset Extension](https://github.com/stac-extensions/alternate-assets) is used,
+the default access mechanism for should be HTTP(S).
+
 ### Bands
 
 As of STAC 1.1, the `bands` array can be used in combination with property inheritance to provide users with more flexibility.