fixed schema to reflect intent, update language

radiantearth · May 3, 2021 · 34a7c0e · 34a7c0e
1 parent 2f81fcc
commit 34a7c0e
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 17 deletions.
diff --git a/catalog-spec/catalog-spec.md b/catalog-spec/catalog-spec.md
@@ -94,7 +94,8 @@ The following types are commonly used as `rel` types in the Link Object of a STA
 | child   | URL to a child STAC entity (Catalog or Collection). |
 | item    | URL to a STAC Item. |
 
-**Note:** Empty catalogs are allowed (i.e. without no `item` or `child` link).
+**Note:** A link to at least one `item` or `child` (Catalog or Collection) is **RECOMMENDED**, but empty catalogs are
+allowed if there is an intent to populate it or its children were removed.
 
 There are additional `rel` types in the [Using Relation Types](../best-practices.md#using-relation-types) best practice, but as 
 they are more typically used in Collections, as Catalogs tend to just be used to structure STAC organization, so tend to just use

diff --git a/catalog-spec/json-schema/catalog.json b/catalog-spec/json-schema/catalog.json
@@ -22,22 +22,6 @@
         "type": {
           "title": "Type of STAC entity",
           "const": "Catalog"
-        },
-        "links": {
-          "title": "Links",
-          "type": "array",
-          "contains": {
-            "description": "A link `item` or `child`.",
-            "type": "object",
-            "properties": {
-              "rel": {
-                "enum": [
-                  "child",
-                  "item"
-                ]
-              }
-            }
-          }
         }
       }
     }