-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backport attribution from OGC APIs to a STAC extension #1126
Comments
This seems like it has the potential to overlap with the scope of the Scientific Extension, at least at the Collection level...
If this becomes its own extensions, should there be either a restriction or a best practice that |
Scientific citations (usually in scientific publications) and attributions (usually in maps) are pretty different. For example, the OSM attribution in Leaflet is simply
On the other hand, the scientific citation would be more like
This example is taken directly from OSM, see https://wiki.openstreetmap.org/wiki/Legal_FAQ#I_would_like_to_use_OpenStreetMap_maps._How_should_I_credit_you.3F and https://wiki.openstreetmap.org/wiki/Researcher_Information We can probably give such an example in both extensions to make the difference clear. |
To discuss and potentially close at the Sprint. |
Discussed and agreed to be put in the core. |
We discussed it again due to discussions in #1278. The mixture of CommonMark and HTML is an issue. We should test and evolve this in an extension. |
OGC API has a field "attribution" in the landing page and in collections. While it may not be very useful for us in the landing page, it feels useful to have it in Collections somehow. As I don't want to merge it into core, I think we could make this an extension.
The issue in OGC API - Common: opengeospatial/ogcapi-common#174
The text was updated successfully, but these errors were encountered: