You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: extensions/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,8 +56,7 @@ with the template.
56
56
57
57
The logic for when an object should list an extension ID in its `stac_extension` array is as follows:
58
58
59
-
- If the object directly implements the extension (by including at least one of the fields of the extension, plus any
60
-
additional specified requirements), the `stac_extensions` of that object should contain the extension ID.
59
+
- If the object directly implements the extension (by following the specified requirements - usually by including fields, but occasionally implementing alternate behaviors), the `stac_extensions` of that object should contain the extension ID.
61
60
- If an Asset implements fields of the extension, then `stac_extensions` of the Item or Collection which holds that
62
61
Asset should contain the extension ID.
63
62
- If a Collection [summary](../collection-spec/collection-spec.md#summaries) contains Item fields that implement an extension, then
@@ -106,7 +105,7 @@ Best practices for extension proposals are still emerging in this section.
106
105
107
106
### General Conventions
108
107
109
-
Creating a new extension involves defining a set of logically grouped fields, and specifying what the allowed values
108
+
Creating a new extension usually involves defining a set of logically grouped fields, and specifying what the allowed values
110
109
for those fields are. This should be done in the extension text and in JSON Schema, to provide validation. While one
111
110
can theoretically add fields anywhere in JSON there are some conventions as to where to add them in STAC objects.
112
111
@@ -117,6 +116,7 @@ can theoretically add fields anywhere in JSON there are some conventions as to w
117
116
the Item Asset objects contained in the Item, but may also be used in an individual Item Asset to describe only the bands available in that asset.
118
117
3. Additional attributes relating to a [Catalog](../catalog-spec/catalog-spec.md) or
119
118
[Collection](../collection-spec/collection-spec.md) should be added to the root of the object.
119
+
4. Extensions may also extend other extensions, declaring that dependency in the text and JSON Schema.
0 commit comments