Skip to content

Conversation

philvarner
Copy link
Collaborator

rework example landing page, link rel table, and conformsTo for conformance classes to make it more clear which of them go with which conformance classes

Related Issue(s): n/a

Proposed Changes:

  1. add landing page examples to each conformance class, with correct conformsTo and links only for that conformance class
  2. Add a landing page example to overview that uses all conformance classes
  3. Move API diagram to overview

PR Checklist:

  • This PR is made against the dev branch (all proposed changes except releases should be against dev, not master).
  • This PR has no breaking changes.
  • I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.

…rmance classes to make it more clear which of them go with which conformance classes
The base of a STAC API is its landing page. This resource is the starting point to discover what behaviors the API supports via link relations.
This behavior in a RESTful API is known as Hypermedia as the Engine of Application State (HATEOAS). STAC API relies heavily on hypermedia for API endpoint
navigation.
The base of a STAC API is its landing page. This resource is the starting point to discover what behaviors the API supports via the `conformsTo` values and link relations.
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't as large of a change as the diff implies -- I moved a couple sections around.


```json
{
"stac_version": "1.0.0-beta.2",
"id": "example-stac",
"title": "A simple STAC API Example",
"description": "This Catalog aims to demonstrate the a simple landing page",
"conformsTo" : [
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I moved conformsTo to the top of all the examples, since this is pretty critical to how most of the clients and validators are going to interact with the API

@@ -30,11 +84,6 @@ navigation.
"type": "application/json",
"href": "https://stacserver.org"
},
{
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

conformance, data, and search are not part of Core, so removed them from this example.

Copy link
Collaborator

@cholmes cholmes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. The one tweak I'd make is to add links to the other landing page examples from the core one. I get why you have reduced it, but now it's hard to get a sense from it alone what a 'real' landing page would look like. I was going to recommend a fuller example included at the bottom. But I see the other ones now have examples, so I think it can be sufficient to just link to them.

@philvarner philvarner merged commit 14790ff into radiantearth:dev May 19, 2021
@philvarner philvarner deleted the service-doc branch May 19, 2021 00:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants