7
7
- [ Extensions] ( #extensions )
8
8
- [ Structuring Catalog Hierarchies] ( #structuring-catalog-hierarchies )
9
9
10
- - ** OpenAPI specification:** [ openapi.yaml] ( openapi.yaml ) ([ rendered version] ( https://api.stacspec.org/v1.0.0-rc.1 /core ) ),
10
+ - ** OpenAPI specification:** [ openapi.yaml] ( openapi.yaml ) ([ rendered version] ( https://api.stacspec.org/v1.0.0-rc.2 /core ) ),
11
11
- ** Conformance URIs:**
12
- - < https://api.stacspec.org/v1.0.0-rc.1 /core >
13
- - < https://api.stacspec.org/v1.0.0-rc.1 /browseable >
12
+ - < https://api.stacspec.org/v1.0.0-rc.2 /core >
13
+ - < https://api.stacspec.org/v1.0.0-rc.2 /browseable >
14
14
- ** [ Maturity Classification] ( ../README.md#maturity-classification ) :** Candidate
15
15
- ** Dependencies** : None
16
16
and [ commons.yaml] ( commons.yaml ) is the OpenAPI version of the core [ STAC spec] ( ../stac-spec ) JSON Schemas.
17
17
18
18
All STAC API implementations must implement the * STAC API - Core* specification. The conformance class
19
- < https://api.stacspec.org/v1.0.0-rc.1 /core > requires a server to provide a valid
19
+ < https://api.stacspec.org/v1.0.0-rc.2 /core > requires a server to provide a valid
20
20
[ STAC Catalog] ( ../stac-spec/catalog-spec/catalog-spec.md ) that also includes a ` conformsTo `
21
21
attribute with a string array value. Any API implementing this is considered a valid STAC API. Additionally,
22
- a STAC API conforming conformance class (< https://api.stacspec.org/v1.0.0-rc.1 /browseable > ) must be structured
22
+ a STAC API conforming conformance class (< https://api.stacspec.org/v1.0.0-rc.2 /browseable > ) must be structured
23
23
such that all Items in the catalog can be accessed by following ` child ` and ` item ` link relations.
24
24
25
25
Even if a STAC catalog is simply files on a web server or objects in cloud storage, serving these files over HTTP
@@ -31,7 +31,7 @@ this "browse" mode of interaction is complementary to the dynamic search capabil
31
31
Conversely, STAC API implementations may not support browse, even though the root is a Catalog object, if they do not
32
32
have the appropriate ` child ` and ` item ` link relations to traverse over the objects in the catalog. STAC API
33
33
implementations may provide an even greater guarantee of Item reachability with the
34
- browseable conformance class (< https://api.stacspec.org/v1.0.0-rc.1 /browseable > ).
34
+ browseable conformance class (< https://api.stacspec.org/v1.0.0-rc.2 /browseable > ).
35
35
36
36
Providing these two complementary ways of interacting with the catalog allow users to iteratively interrogate the data
37
37
to discover what data is available through browse and filter the data to only what they are interested in
@@ -76,7 +76,7 @@ support the *STAC API - Item Search* conformance class, perhaps because it uses
76
76
but sub-catalogs whose items are all in one database can support search.
77
77
78
78
A STAC API conforming to the * STAC API - Browseable* conformance class
79
- (< https://api.stacspec.org/v1.0.0-rc.1 /browseable > ) must be structured such that
79
+ (< https://api.stacspec.org/v1.0.0-rc.2 /browseable > ) must be structured such that
80
80
all Items in the catalog can be accessed by following ` child ` and ` item ` link relations. This is a more significant
81
81
constraint than a STAC API without this conformance class or a STAC Catalog that is available over HTTP but does not
82
82
implement STAC API, neither of which have any guarantee regarding the reachability of Items. This conformance
@@ -114,7 +114,7 @@ Additionally, `child` relations may exist to child Catalogs and Collections and
114
114
relations form a directed graph that enables traversal from a root catalog or collection to items.
115
115
116
116
If all Items in a Catalog can be accessed by traversing these links, the browseable conformance class
117
- < https://api.stacspec.org/v1.0.0-rc.1 /browseable > should be advertised also.
117
+ < https://api.stacspec.org/v1.0.0-rc.2 /browseable > should be advertised also.
118
118
119
119
| ** rel** | ** href** | ** From** | ** Description** |
120
120
| ------- | -------- | --------- | -------------------------------------- |
@@ -186,7 +186,7 @@ different conformance classes and a different set of links.
186
186
"description" : " This Catalog aims to demonstrate the a simple landing page" ,
187
187
"type" : " Catalog" ,
188
188
"conformsTo" : [
189
- " https://api.stacspec.org/v1.0.0-rc.1 /core"
189
+ " https://api.stacspec.org/v1.0.0-rc.2 /core"
190
190
],
191
191
"links" : [
192
192
{
0 commit comments