Improvement
We have a number of types in Franklin that would be useful for things outside of the Franklin monolith. For instance, the types of query parameters are maintained in Franklin, but are also maintained (and sometimes out of sync) in projects that would like to communicate with Franklin instances. We should instead move types upstream to an api-client (or similar) package that both Franklin and Franklin consumers can depend on. That should live either here or in Franklin. An argument could be made that it should live here because "Franklin" doesn't have the same obvious STAC branding that stac4s has. An argument could be made that it belongs in Franklin because that's where its default consumer lives.
Improvement
We have a number of types in Franklin that would be useful for things outside of the Franklin monolith. For instance, the types of query parameters are maintained in Franklin, but are also maintained (and sometimes out of sync) in projects that would like to communicate with Franklin instances. We should instead move types upstream to an
api-client(or similar) package that both Franklin and Franklin consumers can depend on. That should live either here or in Franklin. An argument could be made that it should live here because "Franklin" doesn't have the same obvious STAC branding thatstac4shas. An argument could be made that it belongs in Franklin because that's where its default consumer lives.