How do the relation types work for assets?

[gadomski]

This extension defines some relation types, e.g. latest-version, and describes how they should be used in links. This extension also applies to Assets, which do not have a links field defined in the spec. How is this intended to work? Should assets get a links attribute to hold a latest-version link?

[m-mohr]

The relation types were not meant to work for assets, only the fields are scoped as such.

• Either you have a deprecated asset and a "new" version of it in the same STAC resource, then you usually don't really need a link, I think.
• Otherwise, you have a deprecated asset and the "new" version of it is in another STAC resource, then you just link to the other STAC resource (and ask yourself whether your model is really making sense, because it sounds like the whole STAC resource should be deprecated).

By the way, this is not an issue specific to this extension. The same applies in STAC for for the license field, which is allowed in assets but you can't provide a license link in the assets.

[gadomski]

Cool, thanks for the clarification. I bumped up against this issue when working in tooling (pystac), and shouldn't be a problem to implement, just a bit more complex. Cheers.