Skip to content
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

New field in links (method, headers, body) #1253

Merged
merged 19 commits into from
Jul 17, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions item-spec/common-metadata.md
Original file line number Diff line number Diff line change
Expand Up @@ -221,15 +221,15 @@ with the links section, to describe things like the Catalog an Item is in, relat
child Items (modeled in different ways, like an 'acquisition' or derived data).
It is allowed to add additional fields such as a `title` and `type`.
emmanuelmathot marked this conversation as resolved.
Show resolved Hide resolved

| Field Name | Type | Description |
| ---------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| href | string | **REQUIRED.** The actual link in the format of an URL. Relative and absolute links are both allowed. [Trailing slashes are significant.](../best-practices.md#consistent-uris) |
| rel | string | **REQUIRED.** Relationship between the current document and the linked document. See chapter "Relation types" for more information. |
| type | string | [Media type](../catalog-spec/catalog-spec.md#media-types) of the referenced entity. |
| title | string | A human readable title to be used in rendered displays of the link. |
| method | string | The HTTP method required to be supported by the target resource. `GET` by default |
| headers | object | The HTTP headers required to be sent by the target resource. |
| body | object | The HTTP body required to be sent by the target resource. |
| Field Name | Type | Description |
| ---------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| href | string | **REQUIRED.** The actual link in the format of an URL. Relative and absolute links are both allowed. [Trailing slashes are significant.](../best-practices.md#consistent-uris) |
| rel | string | **REQUIRED.** Relationship between the current document and the linked document. See chapter "Relation types" for more information. |
| type | string | [Media type](../catalog-spec/catalog-spec.md#media-types) of the referenced entity. |
m-mohr marked this conversation as resolved.
Show resolved Hide resolved
| title | string | A human readable title to be used in rendered displays of the link. |
| method | string | The HTTP method required to be supported by the target resource. `GET` by default |
| headers | Map<string, *> | The HTTP headers required to be sent by the target resource. |
m-mohr marked this conversation as resolved.
Show resolved Hide resolved
| body | object | The HTTP body required to be sent by the target resource. |
emmanuelmathot marked this conversation as resolved.
Show resolved Hide resolved

For a full discussion of the situations where relative and absolute links are recommended see the
['Use of links'](../best-practices.md#use-of-links) section of the STAC best practices.