Part 3: Types of Collections?

Part 3 offers a generic way to load from OGC API Collections.

A couple of uncertainties:

• As far as I can see it doesn't limit the scope. What Collections can it really load from? Is loading from Tiles, Routes, or Styles really meaningful here?
• Is there any way a Processes API can describe which types of collections it can load from? If the requirement is to support all by default, that's a pretty steep requirement.
• How to load from other data source? Would a STAC API fall under loading from OGC API Collections? As STAC API is based on Features, would this only load the "Features" (i.e. the STAC metadata)?
• Is there a way to load from static STAC or static Records catalogs?
• Is there a way to query for more specific data? Like e.g. a CQL query for a specific property (both GET/Text encoding and POST/JSON encoding)?

Disclaimer: I'm struggline with all these tiny files in the repo so I may just not have found the answers yet.

Start with the linked collection-input requirement file and the Part 3 text referenced in the issue. Trace how collection scope, supported source types, static catalogs, and query requirements are defined, then document or resolve the open questions with an explicit scope and completion criteria.