-
Notifications
You must be signed in to change notification settings - Fork 47
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
Finish splitting API from main stac-spec #1
Comments
Didn't see this before I started linking. But I linked to master branch. I think it'd be ok to link from dev to master - the idea is that these specs now move semi-independently and cut releases at different times. Thinking about it that could get annoying if all 'released' versions in stac-api-spec are referring to master, as things change. I'd say the ideal would be that a released version of stac-api-spec should depend on a specific version of stac-spec, and ideally we'd update the links to point at those. That sounds like it could be annoying, though maybe that should just spur us to limit the number of links. |
Anything else we need to do for this issue in the API repo? Edit: Re-open or comment if anything is missing. |
This repo contains the contents of the api-spec folder from stac-spec (0.9.0), but there are numerous links and references that need to be updated.
Additional text should be added that this is the API spec and point to stac-spec.
One question is how do we reference individual pages in the main stac-spec? Do we reference master from master branch and dev from dev (really annoying), or tag a specific version?
The text was updated successfully, but these errors were encountered: