refactor: terminology and schema consistency pass

Signed-off-by: Jeremy Ho <jujaga@gmail.com>

Author: jujaga

docs/spec/code_system/asset_kind.md

@@ -13,6 +13,7 @@ Official URL: `https://bcgov.github.io/nr-pies/docs/spec/code_system/asset_kind`
 
 This Code System is used or referenced by:
 
+- Element Definition: [Asset](/docs/spec/element/data/asset)
 - Value Set: [TBD](.)
 
 ## Definition

docs/spec/code_system/message_kind.md

@@ -27,10 +27,10 @@ Not Applicable
 
 ### Concepts
 
-| Code      | Display | Description                                                                                                |
-| --------- | ------- | ---------------------------------------------------------------------------------------------------------- |
-| `GROUP`   | Group   | The message represents a grouping or collection of related records.                                        |
-| `LINKAGE` | Linkage | The message represents a linkage between records.                                                          |
-| `RECORD`  | Record  | The message represents a record resource, containing on hold period information and process event history. |
+| Code      | Display | Description                                                        |
+| --------- | ------- | ------------------------------------------------------------------ |
+| `GROUP`   | Group   | The message represents a grouping or collection of related assets. |
+| `LINKAGE` | Linkage | The message represents a linkage between assets.                   |
+| `RECORD`  | Record  | The message represents information pertaining to the asset itself. |
 
 ## Errata

docs/spec/element/data/asset.schema.json

@@ -29,5 +29,6 @@
       "enum": ["Anchor", "Permit"]
     }
   },
+  "anyOf": [{ "required": ["asset_id", "asset_kind"] }, { "required": ["record_id", "record_kind"] }],
   "required": ["system_id"]
 }

docs/spec/element/data/collection.schema.json

@@ -1,5 +1,5 @@
 {
-  "$id": "https://raw.githubusercontent.com/bcgov/nr-pies/refs/heads/main/docs/spec/element/resource/collection.schema.json",
+  "$id": "https://raw.githubusercontent.com/bcgov/nr-pies/refs/heads/main/docs/spec/element/data/collection.schema.json",
   "$schema": "http://json-schema.org/draft-07/schema#",
   "title": "Collection",
   "description": "Represents a collection.",

docs/spec/element/message/record.mdx

@@ -30,9 +30,10 @@ Represents a message envelope for transmitting asset records.
 This message type serves as a transport envelope for transmitting records between systems. A Record message combines
 Header metadata (transaction tracking, asset identification) with a resource payload selected via `asset_kind`.
 
-The Record message can be composed of either an [Anchor](/docs/spec/element/resource/anchor) or
-[Permit](/docs/spec/element/resource/permit) resource type defined in the specification. Refer to the
-[Type Hierarchy](/docs/spec#hierarchy) for how messages, resources and data types compose together.
+The Record message can be composed of either an [Anchor](/docs/spec/element/resource/anchor),
+[Permit](/docs/spec/element/resource/permit), or [Project](/docs/spec/element/resource/project) resource type defined in
+the specification. Refer to the [Type Hierarchy](/docs/spec#hierarchy) for how messages, resources and data types
+compose together.
 
 ## Structure
 
@@ -52,9 +53,9 @@ Records shall declare an `asset_kind` property value as defined in
 
 The `asset_kind` field acts as a type selector, binding and identifying which resource type this message contains:
 
--- **asset_kind: `ANCHOR`** - Message payload conforms to [Anchor](/docs/spec/element/resource/anchor) resource schema
--- **asset_kind: `PERMIT`** - Message payload conforms to [Permit](/docs/spec/element/resource/permit) resource schema
--- **asset_kind: `PROJECT`** - Message payload conforms to [Project](/docs/spec/element/resource/project) resource schema
+- **asset_kind: `ANCHOR`** - Message payload conforms to [Anchor](/docs/spec/element/resource/anchor) resource schema
+- **asset_kind: `PERMIT`** - Message payload conforms to [Permit](/docs/spec/element/resource/permit) resource schema
+- **asset_kind: `PROJECT`** - Message payload conforms to [Project](/docs/spec/element/resource/project) resource schema
 
 This selection is enforced at the schema level via conditional `if/then` logic.
 

docs/spec/element/message/record.schema.json

@@ -8,15 +8,6 @@
     {
       "$ref": "https://raw.githubusercontent.com/bcgov/nr-pies/refs/heads/main/docs/spec/element/data/header.schema.json"
     },
-    {
-      "title": "Anchor",
-      "description": "Represents an anchor via asset_kind.",
-      "type": "object",
-      "if": { "properties": { "asset_kind": { "const": "ANCHOR" } } },
-      "then": {
-        "$ref": "https://raw.githubusercontent.com/bcgov/nr-pies/refs/heads/main/docs/spec/element/resource/anchor.schema.json"
-      }
-    },
     {
       "title": "Permit",
       "description": "Represents a permit via asset_kind.",
@@ -35,6 +26,15 @@
         "$ref": "https://raw.githubusercontent.com/bcgov/nr-pies/refs/heads/main/docs/spec/element/resource/permit.schema.json"
       }
     },
+    {
+      "title": "Anchor",
+      "description": "Represents an anchor via asset_kind.",
+      "type": "object",
+      "if": { "properties": { "asset_kind": { "const": "ANCHOR" } } },
+      "then": {
+        "$ref": "https://raw.githubusercontent.com/bcgov/nr-pies/refs/heads/main/docs/spec/element/resource/anchor.schema.json"
+      }
+    },
     {
       "title": "Project",
       "description": "Represents a project via asset_kind.",

docs/spec/element/resource/project.mdx

@@ -34,7 +34,7 @@ are selected.
 
 ## Structure
 
-A header shall contain every [Collection](/docs/spec/element/data/collection#structure) data property.
+A project shall contain every [Collection](/docs/spec/element/data/collection#structure) data property.
 
 This structure contains no properties and is functionally equivalent to an empty object.