@open-resource-discovery/specification 1.13.0 → 1.14.1

package/dist/generated/spec/v1/schemas/Document.schema.json

@@ -3,6 +3,7 @@
     "$schema": "http://json-schema.org/draft-07/schema#",
     "$id": "https://open-resource-discovery.org/spec-v1/interfaces/Document.schema.json#",
     "title": "Ord Document",
+    "x-ums-type": "ignore",
     "type": "object",
     "properties": {
         "$schema": {
@@ -36,10 +37,11 @@
                 "1.10",
                 "1.11",
                 "1.12",
-                "1.13"
+                "1.13",
+                "1.14"
             ],
             "examples": [
-                "1.13"
+                "1.14"
             ]
         },
         "description": {
@@ -177,6 +179,15 @@
                 "$ref": "#/definitions/DataProduct"
             }
         },
+        "agents": {
+            "type": "array",
+            "description": "Array of all AI Agents that are described in this ORD document.",
+            "x-introduced-in-version": "1.14.0",
+            "x-feature-status": "beta",
+            "items": {
+                "$ref": "#/definitions/Agent"
+            }
+        },
         "integrationDependencies": {
             "type": "array",
             "description": "Array of all integration dependencies that are described in this ORD document.",
@@ -248,6 +259,7 @@
         "Package": {
             "type": "object",
             "title": "Package",
+            "x-ums-type": "root",
             "description": "A [**Package**](../concepts/grouping-and-bundling#package) organizes a set of related resources together, by publishing and catalog presentation concerns.\n\nThe Package can also be used to indicate which products or vendors provided the packaged resources.\nFor partner or customer content, the Package can indicate this via the `vendor` and `partOfProducts` assignments.\nIn any case, the Package `ordID` namespace MUST reflect the namespace of the providing application (which hosts the resource), not the resource definition owner, which could be a customer or partner.\n\nA Package SHOULD contain at least one resource. Avoid empty Packages.\n\nThe Package assignment of a resource MAY change, so consumers MUST not rely on this to be stable.\n\nA Package does not have a `visibility` property.\nWhether it is displayed is decided by the fact, whether it contains any visible resources according to the visibility role of the aggregator.\n\nTo learn more about the concept and further guidance, see [Package](../concepts/grouping-and-bundling#package).",
             "properties": {
                 "ordId": {
@@ -660,6 +672,7 @@
         "ConsumptionBundle": {
             "type": "object",
             "title": "Consumption Bundle",
+            "x-ums-type": "root",
             "description": "A [**Consumption Bundle**](../concepts/grouping-and-bundling#consumption-bundle) groups APIs and Events together that can be consumed with the credentials and auth mechanism.\nIdeally it also includes instructions and details how to request access and credentials for resources.\n\nFor more documentation and guidance how to correctly this correctly, see [Consumption Bundle details](../concepts/grouping-and-bundling#consumption-bundle).\n\nA Consumption Bundle SHOULD have at least one association with a resource (0..n). Avoid empty Consumption Bundles.\nA Consumption Bundle MUST NOT contain APIs and Events that are NOT defined in the ORD document(s) returned\nby the system instance that defines the Consumption Bundle.\n\nPlease note that some ORD consumer use cases MAY depend on Consumption Bundle assignments to work with the resources.\n\nTo learn more about the concept, see [Consumption Bundle](../concepts/grouping-and-bundling#consumption-bundle).",
             "properties": {
                 "ordId": {
@@ -742,19 +755,19 @@
                 },
                 "visibility": {
                     "type": "string",
-                    "description": "The visibility states who is allowed to \"see\" the described resource or capability.",
+                    "description": "Defines metadata access control - which categories of consumers are allowed to discover and access the resource and its metadata.\n\nThis controls who can see that the resource exists and retrieve its metadata level information.\nIt does NOT control runtime access to the resource itself - that is managed separately through authentication and authorization mechanisms.\n\nUse this to prevent exposing internal implementation details to inappropriate consumer audiences.",
                     "oneOf": [
                         {
                             "const": "public",
-                            "description": "Publicly visible to customers and 3rd parties.\nUsually this includes an contract on the API stability, e.g. the [SAP API Deprecation Policy](https://help.sap.com/viewer/84b35b9c39b247e3ba2a31f02beee46d/Cloud/en-US/5cbfda5a9efe4e97a3e24ddaf7ec5c16.html)."
+                            "description": "Metadata can be discovered and accessed by anyone, including customers, partners, and unauthenticated external parties.\n\nPublic resources typically come with stability guarantees, expressed via versioning and follow formal API lifecycle management. For more details see [Version and Lifecycle](../index.md#version-and-lifecycle) section.\nand follow formal API lifecycle management and deprecation policies.\n\nExample: A REST API that customers use to integrate with your SaaS product."
                         },
                         {
                             "const": "internal",
-                            "description": "Visible to other applications within the same [vendor](#vendor).\nHowever, they are not officially exposed and communicated to customers and 3rd parties.\nThey might not come with the same guarantees on API stability.\n\nInternal resources MUST NOT be made available to consumers without checking the necessary access permissions, e.g., a public API Catalog.\nInternal resources MAY be published through an internal API Catalog if the access permissions are ensured by it."
+                            "description": "Metadata can only be discovered and accessed by vendor internal consumers (e.g. applications or services of the same vendor).\nMUST NOT be made available to external parties or vendor customers.\n\nInternal resources are intended for integration between a vendors own applications and services.\nAPI stability and maturity are explicitly defined via the `releaseStatus` property, which is a separate concern from visibility.\n\nInternal resources MUST NOT be made available without checking the necessary access permissions.\nInternal resources MAY be published through an internal API Catalog if access permissions are ensured by it."
                         },
                         {
                             "const": "private",
-                            "description": "Visible only to the provider application or service, usually within the same system namespace / system type.\n\nPrivate resources MUST NOT be made available to public consumers or consumers outside of the \"private\" scope of the described application."
+                            "description": "Metadata should not be discoverable outside the application / service's own deployment scope (e.g., outside of the provider application or the same system namespace / system type).\nUsed for metadata completeness when describing implementation details or dependencies.\n\nPrivate resources usually have no stability guarantees and can change or be removed at any time.\nThese are typically implementation details not meant for consumption by other services.\n\nExample: Services only used within a microservice architecture or APIs that are only used for the own UIs, not for general consumption.\n\nPrivate resources MUST NOT be made discoverable or accessible outside the application / service's own deployment scope."
                         }
                     ]
                 },
@@ -808,6 +821,7 @@
         "ConsumptionBundleReference": {
             "type": "object",
             "title": "Consumption Bundle Reference",
+            "x-ums-type": "embedded",
             "description": "Reference to a Consumption Bundle.\n\nThis is a complex object to allow additional properties / selections to be attached.",
             "properties": {
                 "ordId": {
@@ -836,6 +850,7 @@
         "ApiResource": {
             "type": "object",
             "title": "Api Resource",
+            "x-ums-type": "root",
             "description": "The API Resource provides a high-level description of an exposed API.\nYou can find more information, such as the API resource definitions, in the links in the table below.\n\nAn API Resource bundles multiple endpoints and resources together.\nThey share the same API namespace and lifecycle (API major version).\nHowever, the exact granularity of this is up to the implementer of the API.\nAs a consequence, an API resource MUST NOT bundle together endpoints from different API versions or namespaces.\n\nA common practice is to bundle endpoints that are based on the same domain or Business Object.\n\nPlease note that APIs can be described, but still be [`disabled`](#api-resource_disabled).\n\nIf the API is not created or owned by the user of the system or by third parties (like partners), it MUST be assigned to dedicated [Packages](#package) that state this the ownership via the `vendor` property.",
             "properties": {
                 "ordId": {
@@ -981,43 +996,50 @@
                         "2022-12-19T15:47:04+00:00"
                     ]
                 },
+                "abstract": {
+                    "type": "boolean",
+                    "default": false,
+                    "x-introduced-in-version": "1.13.0",
+                    "x-feature-status": "beta",
+                    "description": "Indicates that the resource serves as interface only and cannot be called directly, similar to the abstract keyword in programming languages like Java.\n\nAbstract resources define contracts that other resources can declare compatibility with through the `compatibleWith` property.\n\nMore details can be found on the [Compatibility](../concepts/compatibility) concept page."
+                },
                 "visibility": {
                     "type": "string",
-                    "description": "The visibility states who is allowed to \"see\" the described resource or capability.",
+                    "description": "Defines metadata access control - which categories of consumers are allowed to discover and access the resource and its metadata.\n\nThis controls who can see that the resource exists and retrieve its metadata level information.\nIt does NOT control runtime access to the resource itself - that is managed separately through authentication and authorization mechanisms.\n\nUse this to prevent exposing internal implementation details to inappropriate consumer audiences.",
                     "oneOf": [
                         {
                             "const": "public",
-                            "description": "Publicly visible to customers and 3rd parties.\nUsually this includes an contract on the API stability, e.g. the [SAP API Deprecation Policy](https://help.sap.com/viewer/84b35b9c39b247e3ba2a31f02beee46d/Cloud/en-US/5cbfda5a9efe4e97a3e24ddaf7ec5c16.html)."
+                            "description": "Metadata can be discovered and accessed by anyone, including customers, partners, and unauthenticated external parties.\n\nPublic resources typically come with stability guarantees, expressed via versioning and follow formal API lifecycle management. For more details see [Version and Lifecycle](../index.md#version-and-lifecycle) section.\nand follow formal API lifecycle management and deprecation policies.\n\nExample: A REST API that customers use to integrate with your SaaS product."
                         },
                         {
                             "const": "internal",
-                            "description": "Visible to other applications within the same [vendor](#vendor).\nHowever, they are not officially exposed and communicated to customers and 3rd parties.\nThey might not come with the same guarantees on API stability.\n\nInternal resources MUST NOT be made available to consumers without checking the necessary access permissions, e.g., a public API Catalog.\nInternal resources MAY be published through an internal API Catalog if the access permissions are ensured by it."
+                            "description": "Metadata can only be discovered and accessed by vendor internal consumers (e.g. applications or services of the same vendor).\nMUST NOT be made available to external parties or vendor customers.\n\nInternal resources are intended for integration between a vendors own applications and services.\nAPI stability and maturity are explicitly defined via the `releaseStatus` property, which is a separate concern from visibility.\n\nInternal resources MUST NOT be made available without checking the necessary access permissions.\nInternal resources MAY be published through an internal API Catalog if access permissions are ensured by it."
                         },
                         {
                             "const": "private",
-                            "description": "Visible only to the provider application or service, usually within the same system namespace / system type.\n\nPrivate resources MUST NOT be made available to public consumers or consumers outside of the \"private\" scope of the described application."
+                            "description": "Metadata should not be discoverable outside the application / service's own deployment scope (e.g., outside of the provider application or the same system namespace / system type).\nUsed for metadata completeness when describing implementation details or dependencies.\n\nPrivate resources usually have no stability guarantees and can change or be removed at any time.\nThese are typically implementation details not meant for consumption by other services.\n\nExample: Services only used within a microservice architecture or APIs that are only used for the own UIs, not for general consumption.\n\nPrivate resources MUST NOT be made discoverable or accessible outside the application / service's own deployment scope."
                         }
                     ]
                 },
                 "releaseStatus": {
                     "type": "string",
-                    "description": "The `releaseStatus` specifies the stability of the resource and its external contract.",
+                    "description": "Defines the maturity level and stability commitment for the resource's API contract (interface, behavior, data models).\n\nThis indicates whether the resource may undergo backward-incompatible changes. It helps consumers understand the risk\nof depending on the resource and whether it's suitable for production use.\n\nNote: This is independent of `visibility` and does not imply availability guarantees or SLAs - it concerns only the API contract stability.\n\nSee [Lifecycle](../index.md#lifecycle) and [Compatibility](../concepts/compatibility.md) for more details.",
                     "oneOf": [
                         {
                             "const": "beta",
-                            "description": "The contract for the resource is beta and may not be meant for productive use.\nResources of `beta` status MAY be changed or deleted at the providers discretion."
+                            "description": "The API contract has no stability guarantees. Breaking changes may occur at any time without notice or deprecation period.\n\nNot recommended for production use unless you can tolerate breaking changes. Suitable for experimentation, early adopters,\nand feedback gathering. Resources of `beta` status MAY be changed or removed at the provider's discretion."
                         },
                         {
                             "const": "active",
-                            "description": "Resource is meant for productive use and provides a stable API contract."
+                            "description": "The API contract is stable and recommended for production use.\n\nBreaking changes will only be introduced through proper deprecation cycles or new major versions,\nfollowing versioning and compatibility policies. Consumers can rely on active resources with confidence."
                         },
                         {
                             "const": "deprecated",
-                            "description": "Resource has been deprecated.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (aka. decommissioned / removed) in the future, through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
+                            "description": "The resource is still functional but scheduled for removal. No new development should depend on it.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (decommissioned/removed) in the future through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
                         },
                         {
                             "const": "sunset",
-                            "description": "Resource has been sunset, but is still described.\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
+                            "description": "The resource has been decommissioned and is no longer available at runtime. This entry exists for historical reference only.\n\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
                         }
                     ],
                     "examples": [
@@ -1123,32 +1145,32 @@
                         },
                         {
                             "const": "odata-v2",
-                            "description": "[OData Version 2.0](https://www.odata.org/documentation/odata-version-2-0/) API.\nAn API Resource definition of type `edmx` MUST be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `edmx`, `csdl-json`, `openapi-v2`, `openapi-v3`, `openapi-v3.1+`, `sap-csn-interop-effective-v1` or `custom`."
+                            "description": "[OData Version 2.0](https://www.odata.org/documentation/odata-version-2-0/) API.\nAn API Resource definition of type `edmx` MUST be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `edmx`, `csdl-json`, `openapi-v2`, `openapi-v3`, `openapi-v3.1+`, `sap-csn-interop-effective-v1`, `custom` or any valid [Specification ID](../index.md#specification-id)."
                         },
                         {
                             "const": "odata-v4",
-                            "description": "[OData Version 4](https://www.odata.org/documentation/) API.\nAn OData V4 API MUST be described via a Common Schema Definition Language (CSDL).\nAn API Resource definition of type `edmx` MUST be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `edmx`, `csdl-json`, `openapi-v2`, `openapi-v3`, `openapi-v3.1+`, `sap-csn-interop-effective-v1` or `custom`."
+                            "description": "[OData Version 4](https://www.odata.org/documentation/) API.\nAn OData V4 API MUST be described via a Common Schema Definition Language (CSDL).\nAn API Resource definition of type `edmx` MUST be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `edmx`, `csdl-json`, `openapi-v2`, `openapi-v3`, `openapi-v3.1+`, `sap-csn-interop-effective-v1`, `custom` or any valid [Specification ID](../index.md#specification-id)."
                         },
                         {
                             "const": "rest",
-                            "description": "Generic [REST](https://en.wikipedia.org/wiki/Representational_state_transfer) API.\nPlease not that while OData is also a REST API, the most precise/opinionated `apiProtocol` MUST be chosen.\nAn API Resource definition of type `openapi-v3` (RECOMMENDED) or another appropriate option SHOULD be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `openapi-v2`, `openapi-v3`, `openapi-v3.1+`, `raml-v1`, `sap-csn-interop-effective-v1` or `custom`."
+                            "description": "Generic [REST](https://en.wikipedia.org/wiki/Representational_state_transfer) API.\nPlease not that while OData is also a REST API, the most precise/opinionated `apiProtocol` MUST be chosen.\nAn API Resource definition of type `openapi-v3` (RECOMMENDED) or another appropriate option SHOULD be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `openapi-v2`, `openapi-v3`, `openapi-v3.1+`, `raml-v1`, `sap-csn-interop-effective-v1`, `custom` or any valid [Specification ID](../index.md#specification-id)."
                         },
                         {
                             "const": "graphql",
-                            "description": "[GraphQL](https://graphql.org/) API.\nAn API Resource definition of type `graphql-sdl` SHOULD be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `graphql-sdl`, `sap-csn-interop-effective-v1` or `custom`."
+                            "description": "[GraphQL](https://graphql.org/) API.\nAn API Resource definition of type `graphql-sdl` SHOULD be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `graphql-sdl`, `sap-csn-interop-effective-v1`, `custom` or any valid [Specification ID](../index.md#specification-id)."
                         },
                         {
                             "const": "delta-sharing",
                             "x-introduced-in-version": "1.8.0",
-                            "description": "[Delta Sharing](https://github.com/delta-io/delta-sharing/blob/main/PROTOCOL.md) Protocol, where one API Resource corresponds to a share.\nFor each API Resource definition: `type` MUST ONLY be set to `sap-csn-interop-effective-v1` or to `custom`.\nFor delta-sharing APIs the resource definition MAY be omitted, as the protocol itself allows for metadata discovery at runtime."
+                            "description": "[Delta Sharing](https://github.com/delta-io/delta-sharing/blob/main/PROTOCOL.md) Protocol, where one API Resource corresponds to a share.\nFor each API Resource definition: `type` MUST ONLY be set to `sap-csn-interop-effective-v1`, `custom` or any valid [Specification ID](../index.md#specification-id).\nFor delta-sharing APIs the resource definition MAY be omitted, as the protocol itself allows for metadata discovery at runtime."
                         },
                         {
                             "const": "soap-inbound",
-                            "description": "[SOAP](https://en.wikipedia.org/wiki/SOAP) API that provides inbound interfaces.\nAn API Resource definition of type `wsdl-v2` (RECOMMENDED) or `wsdl-v1` MUST be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `wsdl-v1`, `wsdl-v2` or `custom`."
+                            "description": "[SOAP](https://en.wikipedia.org/wiki/SOAP) API that provides inbound interfaces.\nAn API Resource definition of type `wsdl-v2` (RECOMMENDED) or `wsdl-v1` MUST be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `wsdl-v1`, `wsdl-v2`, `custom` or any valid [Specification ID](../index.md#specification-id)."
                         },
                         {
                             "const": "soap-outbound",
-                            "description": "[SOAP](https://en.wikipedia.org/wiki/SOAP) API that provides/describes outbound interfaces for async communication.\nAn API Resource definition of type `wsdl-v2` (RECOMMENDED) or `wsdl-v1` MUST be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `wsdl-v1`, `wsdl-v2` or `custom`."
+                            "description": "[SOAP](https://en.wikipedia.org/wiki/SOAP) API that provides/describes outbound interfaces for async communication.\nAn API Resource definition of type `wsdl-v2` (RECOMMENDED) or `wsdl-v1` MUST be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `wsdl-v1`, `wsdl-v2`, `custom` or any valid [Specification ID](../index.md#specification-id)."
                         },
                         {
                             "const": "mcp",
@@ -1156,7 +1178,7 @@
                         },
                         {
                             "const": "websocket",
-                            "description": "Generic [WebSocket](https://datatracker.ietf.org/doc/html/rfc6455) Protocol.\nSince WebSocket is very generic, it is important to also define or least describe which semantics are concretely used, e.g. via an `implementationStandard`.\nThe API Resource definitions `type` MUST ONLY be set to `custom`."
+                            "description": "Generic [WebSocket](https://datatracker.ietf.org/doc/html/rfc6455) Protocol.\nSince WebSocket is very generic, it is important to also define or least describe which semantics are concretely used, e.g. via an `implementationStandard`.\nThe API Resource definitions `type` MUST ONLY be set to `custom` or any valid [Specification ID](../index.md#specification-id)."
                         },
                         {
                             "const": "a2a",
@@ -1165,11 +1187,13 @@
                         },
                         {
                             "const": "sap-rfc",
-                            "description": "[SAP RFC](https://help.sap.com/viewer/753088fc00704d0a80e7fbd6803c8adb/202009.000/en-US/4888068ad9134076e10000000a42189d.html) (Remote Function Call)  is the standard SAP interface for communication between SAP systems.\nRFC calls a function to be executed in a remote system.\nAn API Resource definition of type `sap-rfc-metadata-v1` MUST be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `sap-rfc-metadata-v1` or `custom`."
+                            "x-introduced-in-version": "1.5.0",
+                            "description": "[SAP RFC](https://help.sap.com/viewer/753088fc00704d0a80e7fbd6803c8adb/202009.000/en-US/4888068ad9134076e10000000a42189d.html) (Remote Function Call)  is the standard SAP interface for communication between SAP systems.\nRFC calls a function to be executed in a remote system.\nAn API Resource definition of type `sap-rfc-metadata-v1` MUST be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `sap-rfc-metadata-v1`, `custom` or any valid [Specification ID](../index.md#specification-id)."
                         },
                         {
                             "const": "sap-sql-api-v1",
-                            "description": "SAP SQL API that follows the [SQL interface specification for SAP ecosystem](https://github.com/SAP/sql-interface-specification).\nAn API Resource definition of type `sap-sql-api-definition-v1` MUST be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `sap-sql-api-definition-v1`, `sap-csn-interop-effective-v1` or `custom`."
+                            "x-introduced-in-version": "1.9.2",
+                            "description": "SAP SQL API that follows the [SQL interface specification for SAP ecosystem](https://github.com/SAP/sql-interface-specification).\nAn API Resource definition of type `sap-sql-api-definition-v1` SHOULD be provided.\nFor each API Resource definition: `type` MUST ONLY be set to `sap-sql-api-definition-v1`, `sap-csn-interop-effective-v1`, `custom` or any valid [Specification ID](../index.md#specification-id)."
                         },
                         {
                             "const": "sap-ina-api-v1",
@@ -1227,15 +1251,19 @@
                     ]
                 },
                 "compatibleWith": {
+                    "x-introduced-in-version": "1.13.0",
+                    "x-feature-status": "beta",
                     "type": "array",
-                    "description": "A reference to the interface (API contract) that this API implements.\nServes as a declaration of compatible implementation of API contract, effectively functioning as an \"implementationOf\" relationship.\n\nMUST be a valid reference to an (usually external) [API Resource](#api-resource) ORD ID.\n\nAll APIs that share the same `compatibleWith` value MAY be treated the same or similar by a consumer client.",
+                    "description": "A reference to the interface (API contract) and its maximum version that this API implements. Even if the interface contract evolves compatible, this resource will not be compatible with versions beyond the specified one.\n\nServes as a declaration of compatible implementation of API contract, effectively functioning as an \"implementationOf\" relationship. The data that compatible APIs return follow the same schema, but itself can be different.\nThis means that if one API is returning 1 record for a dedicated request, a compatible API could return multiple and different records, as long as they adhere to the same schema.\n\nMUST be a valid reference to an (usually external) [API Resource](#api-resource) ORD ID.\n\nAll APIs that share the same `compatibleWith` value MAY be treated the same or similar by a consumer client.\n\nMore details can be found on the [Compatibility](../concepts/compatibility) concept page.",
                     "items": {
-                        "type": "string",
-                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(apiResource):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$"
+                        "$ref": "#/definitions/ApiCompatibility"
                     },
                     "examples": [
                         [
-                            "sap.s4com:apiResource:SomeSharedContract:v1"
+                            {
+                                "ordId": "sap.s4com:apiResource:SomeSharedContract:v1",
+                                "maxVersion": "1.2"
+                            }
                         ]
                     ]
                 },
@@ -1652,6 +1680,7 @@
         "EventResource": {
             "type": "object",
             "title": "Event Resource",
+            "x-ums-type": "root",
             "description": "The event resource provides a high-level description of a collection of related Events. More detailed information, such as the event resource definitions, are provided in links in the table below.\nWhich events are considered \"related\" is up to the implementer. A common practice is to bundle events that are based on the same resource/Business Object. It is also an option to bundle all available events into a single event resource/event catalog.\nPlease note that event resources can be described, but still be [`disabled`](#event-resource_disabled).\nIf the event resource is not created or owned by the user / customer of the system or by partners / third parties, it MUST be assigned to dedicated [Packages](#package) that state this the ownership via the `vendor` property.",
             "properties": {
                 "ordId": {
@@ -1799,43 +1828,50 @@
                         "2022-12-19T15:47:04+00:00"
                     ]
                 },
+                "abstract": {
+                    "type": "boolean",
+                    "default": false,
+                    "x-introduced-in-version": "1.13.0",
+                    "x-feature-status": "beta",
+                    "description": "Indicates that the resource serves as interface only and cannot be called directly, similar to the abstract keyword in programming languages like Java.\n\nAbstract resources define contracts that other resources can declare compatibility with through the `compatibleWith` property.\n\nMore details can be found on the [Compatibility](../concepts/compatibility) concept page."
+                },
                 "visibility": {
                     "type": "string",
-                    "description": "The visibility states who is allowed to \"see\" the described resource or capability.",
+                    "description": "Defines metadata access control - which categories of consumers are allowed to discover and access the resource and its metadata.\n\nThis controls who can see that the resource exists and retrieve its metadata level information.\nIt does NOT control runtime access to the resource itself - that is managed separately through authentication and authorization mechanisms.\n\nUse this to prevent exposing internal implementation details to inappropriate consumer audiences.",
                     "oneOf": [
                         {
                             "const": "public",
-                            "description": "Publicly visible to customers and 3rd parties.\nUsually this includes an contract on the API stability, e.g. the [SAP API Deprecation Policy](https://help.sap.com/viewer/84b35b9c39b247e3ba2a31f02beee46d/Cloud/en-US/5cbfda5a9efe4e97a3e24ddaf7ec5c16.html)."
+                            "description": "Metadata can be discovered and accessed by anyone, including customers, partners, and unauthenticated external parties.\n\nPublic resources typically come with stability guarantees, expressed via versioning and follow formal API lifecycle management. For more details see [Version and Lifecycle](../index.md#version-and-lifecycle) section.\nand follow formal API lifecycle management and deprecation policies.\n\nExample: A REST API that customers use to integrate with your SaaS product."
                         },
                         {
                             "const": "internal",
-                            "description": "Visible to other applications within the same [vendor](#vendor).\nHowever, they are not officially exposed and communicated to customers and 3rd parties.\nThey might not come with the same guarantees on API stability.\n\nInternal resources MUST NOT be made available to consumers without checking the necessary access permissions, e.g., a public API Catalog.\nInternal resources MAY be published through an internal API Catalog if the access permissions are ensured by it."
+                            "description": "Metadata can only be discovered and accessed by vendor internal consumers (e.g. applications or services of the same vendor).\nMUST NOT be made available to external parties or vendor customers.\n\nInternal resources are intended for integration between a vendors own applications and services.\nAPI stability and maturity are explicitly defined via the `releaseStatus` property, which is a separate concern from visibility.\n\nInternal resources MUST NOT be made available without checking the necessary access permissions.\nInternal resources MAY be published through an internal API Catalog if access permissions are ensured by it."
                         },
                         {
                             "const": "private",
-                            "description": "Visible only to the provider application or service, usually within the same system namespace / system type.\n\nPrivate resources MUST NOT be made available to public consumers or consumers outside of the \"private\" scope of the described application."
+                            "description": "Metadata should not be discoverable outside the application / service's own deployment scope (e.g., outside of the provider application or the same system namespace / system type).\nUsed for metadata completeness when describing implementation details or dependencies.\n\nPrivate resources usually have no stability guarantees and can change or be removed at any time.\nThese are typically implementation details not meant for consumption by other services.\n\nExample: Services only used within a microservice architecture or APIs that are only used for the own UIs, not for general consumption.\n\nPrivate resources MUST NOT be made discoverable or accessible outside the application / service's own deployment scope."
                         }
                     ]
                 },
                 "releaseStatus": {
                     "type": "string",
-                    "description": "The `releaseStatus` specifies the stability of the resource and its external contract.",
+                    "description": "Defines the maturity level and stability commitment for the resource's API contract (interface, behavior, data models).\n\nThis indicates whether the resource may undergo backward-incompatible changes. It helps consumers understand the risk\nof depending on the resource and whether it's suitable for production use.\n\nNote: This is independent of `visibility` and does not imply availability guarantees or SLAs - it concerns only the API contract stability.\n\nSee [Lifecycle](../index.md#lifecycle) and [Compatibility](../concepts/compatibility.md) for more details.",
                     "oneOf": [
                         {
                             "const": "beta",
-                            "description": "The contract for the resource is beta and may not be meant for productive use.\nResources of `beta` status MAY be changed or deleted at the providers discretion."
+                            "description": "The API contract has no stability guarantees. Breaking changes may occur at any time without notice or deprecation period.\n\nNot recommended for production use unless you can tolerate breaking changes. Suitable for experimentation, early adopters,\nand feedback gathering. Resources of `beta` status MAY be changed or removed at the provider's discretion."
                         },
                         {
                             "const": "active",
-                            "description": "Resource is meant for productive use and provides a stable API contract."
+                            "description": "The API contract is stable and recommended for production use.\n\nBreaking changes will only be introduced through proper deprecation cycles or new major versions,\nfollowing versioning and compatibility policies. Consumers can rely on active resources with confidence."
                         },
                         {
                             "const": "deprecated",
-                            "description": "Resource has been deprecated.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (aka. decommissioned / removed) in the future, through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
+                            "description": "The resource is still functional but scheduled for removal. No new development should depend on it.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (decommissioned/removed) in the future through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
                         },
                         {
                             "const": "sunset",
-                            "description": "Resource has been sunset, but is still described.\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
+                            "description": "The resource has been decommissioned and is no longer available at runtime. This entry exists for historical reference only.\n\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
                         }
                     ],
                     "examples": [
@@ -1947,15 +1983,19 @@
                     ]
                 },
                 "compatibleWith": {
+                    "x-introduced-in-version": "1.13.0",
+                    "x-feature-status": "beta",
                     "type": "array",
-                    "description": "Declares this event resource is a compatible implementation of the referenced contract.\nThis is also sometimes known as [Service Provider Interface](https://en.wikipedia.org/wiki/Service_provider_interface).\n\nMUST be a valid reference to an (usually external) [Event Resource](#event-resource) ORD ID.\n\nAll event resources that share the same `compatibleWith` value MAY be treated the same or similar by a consumer client.",
+                    "description": "A reference to the interface (event contract) and its maximum version that this event implements. Even if the interface contract evolves compatible, this resource will not be compatible with versions beyond the specified one.\n\nServes as a declaration of compatible implementation of event contract, effectively functioning as an \"implementationOf\" relationship. The data that compatible events return follow the same schema, but itself can be different.\nThis means that if one event is returning 1 record for a dedicated request, a compatible event could return multiple and different records, as long as they adhere to the same schema.\n\nAll events that share the same `compatibleWith` value MAY be treated the same or similar by a consumer client.\n\nMore details can be found on the [Compatibility](../concepts/compatibility) concept page.",
                     "items": {
-                        "type": "string",
-                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(eventResource):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$"
+                        "$ref": "#/definitions/EventCompatibility"
                     },
                     "examples": [
                         [
-                            "sap.s4com:eventResource:SomeSharedContract:v1"
+                            {
+                                "ordId": "sap.s4:eventResource:BillofMaterialEvents:v1",
+                                "maxVersion": "1.2"
+                            }
                         ]
                     ]
                 },
@@ -2320,6 +2360,7 @@
         "EntityType": {
             "type": "object",
             "title": "Entity Type",
+            "x-ums-type": "root",
             "description": "An [**Entity Type**](../concepts/grouping-and-bundling#entity-type) describes either a business concept / term or an underlying conceptual model.\nThe same entity type can be exposed through one or multiple API and events resources.\n\nTo learn more about the concept, see [Entity Type](../concepts/grouping-and-bundling#entity-type).",
             "x-introduced-in-version": "1.8.0",
             "properties": {
@@ -2458,41 +2499,41 @@
                 },
                 "visibility": {
                     "type": "string",
-                    "description": "The visibility states who is allowed to \"see\" the described resource or capability.",
+                    "description": "Defines metadata access control - which categories of consumers are allowed to discover and access the resource and its metadata.\n\nThis controls who can see that the resource exists and retrieve its metadata level information.\nIt does NOT control runtime access to the resource itself - that is managed separately through authentication and authorization mechanisms.\n\nUse this to prevent exposing internal implementation details to inappropriate consumer audiences.",
                     "oneOf": [
                         {
                             "const": "public",
-                            "description": "Publicly visible to customers and 3rd parties.\nUsually this includes an contract on the API stability, e.g. the [SAP API Deprecation Policy](https://help.sap.com/viewer/84b35b9c39b247e3ba2a31f02beee46d/Cloud/en-US/5cbfda5a9efe4e97a3e24ddaf7ec5c16.html)."
+                            "description": "Metadata can be discovered and accessed by anyone, including customers, partners, and unauthenticated external parties.\n\nPublic resources typically come with stability guarantees, expressed via versioning and follow formal API lifecycle management. For more details see [Version and Lifecycle](../index.md#version-and-lifecycle) section.\nand follow formal API lifecycle management and deprecation policies.\n\nExample: A REST API that customers use to integrate with your SaaS product."
                         },
                         {
                             "const": "internal",
-                            "description": "Visible to other applications within the same [vendor](#vendor).\nHowever, they are not officially exposed and communicated to customers and 3rd parties.\nThey might not come with the same guarantees on API stability.\n\nInternal resources MUST NOT be made available to consumers without checking the necessary access permissions, e.g., a public API Catalog.\nInternal resources MAY be published through an internal API Catalog if the access permissions are ensured by it."
+                            "description": "Metadata can only be discovered and accessed by vendor internal consumers (e.g. applications or services of the same vendor).\nMUST NOT be made available to external parties or vendor customers.\n\nInternal resources are intended for integration between a vendors own applications and services.\nAPI stability and maturity are explicitly defined via the `releaseStatus` property, which is a separate concern from visibility.\n\nInternal resources MUST NOT be made available without checking the necessary access permissions.\nInternal resources MAY be published through an internal API Catalog if access permissions are ensured by it."
                         },
                         {
                             "const": "private",
-                            "description": "Visible only to the provider application or service, usually within the same system namespace / system type.\n\nPrivate resources MUST NOT be made available to public consumers or consumers outside of the \"private\" scope of the described application."
+                            "description": "Metadata should not be discoverable outside the application / service's own deployment scope (e.g., outside of the provider application or the same system namespace / system type).\nUsed for metadata completeness when describing implementation details or dependencies.\n\nPrivate resources usually have no stability guarantees and can change or be removed at any time.\nThese are typically implementation details not meant for consumption by other services.\n\nExample: Services only used within a microservice architecture or APIs that are only used for the own UIs, not for general consumption.\n\nPrivate resources MUST NOT be made discoverable or accessible outside the application / service's own deployment scope."
                         }
                     ]
                 },
                 "releaseStatus": {
                     "type": "string",
-                    "description": "The `releaseStatus` specifies the stability of the resource and its external contract.",
+                    "description": "Defines the maturity level and stability commitment for the resource's API contract (interface, behavior, data models).\n\nThis indicates whether the resource may undergo backward-incompatible changes. It helps consumers understand the risk\nof depending on the resource and whether it's suitable for production use.\n\nNote: This is independent of `visibility` and does not imply availability guarantees or SLAs - it concerns only the API contract stability.\n\nSee [Lifecycle](../index.md#lifecycle) and [Compatibility](../concepts/compatibility.md) for more details.",
                     "oneOf": [
                         {
                             "const": "beta",
-                            "description": "The contract for the resource is beta and may not be meant for productive use.\nResources of `beta` status MAY be changed or deleted at the providers discretion."
+                            "description": "The API contract has no stability guarantees. Breaking changes may occur at any time without notice or deprecation period.\n\nNot recommended for production use unless you can tolerate breaking changes. Suitable for experimentation, early adopters,\nand feedback gathering. Resources of `beta` status MAY be changed or removed at the provider's discretion."
                         },
                         {
                             "const": "active",
-                            "description": "Resource is meant for productive use and provides a stable API contract."
+                            "description": "The API contract is stable and recommended for production use.\n\nBreaking changes will only be introduced through proper deprecation cycles or new major versions,\nfollowing versioning and compatibility policies. Consumers can rely on active resources with confidence."
                         },
                         {
                             "const": "deprecated",
-                            "description": "Resource has been deprecated.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (aka. decommissioned / removed) in the future, through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
+                            "description": "The resource is still functional but scheduled for removal. No new development should depend on it.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (decommissioned/removed) in the future through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
                         },
                         {
                             "const": "sunset",
-                            "description": "Resource has been sunset, but is still described.\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
+                            "description": "The resource has been decommissioned and is no longer available at runtime. This entry exists for historical reference only.\n\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
                         }
                     ],
                     "examples": [
@@ -2686,6 +2727,7 @@
         "DataProduct": {
             "type": "object",
             "title": "Data Product",
+            "x-ums-type": "root",
             "x-introduced-in-version": "1.8.0",
             "description": "A [Data Product](../concepts/data-product) is a data set exposed for consumption outside the boundaries of the producing application via APIs and described by high quality metadata that can be accessed through the [ORD Aggregator](../../spec-v1/#ord-aggregator).\n\nPlease note that this concept is in beta, see [Data Product - Current Status](../concepts/data-product#current-status).",
             "properties": {
@@ -2814,15 +2856,15 @@
                     "oneOf": [
                         {
                             "const": "public",
-                            "description": "Publicly visible to customers and 3rd parties.\nUsually this includes an contract on the API stability, e.g. the [SAP API Deprecation Policy](https://help.sap.com/viewer/84b35b9c39b247e3ba2a31f02beee46d/Cloud/en-US/5cbfda5a9efe4e97a3e24ddaf7ec5c16.html)."
+                            "description": "Metadata can be discovered and accessed by anyone, including customers, partners, and unauthenticated external parties.\n\nPublic resources typically come with stability guarantees, expressed via versioning and follow formal API lifecycle management. For more details see [Version and Lifecycle](../index.md#version-and-lifecycle) section.\nand follow formal API lifecycle management and deprecation policies.\n\nExample: A REST API that customers use to integrate with your SaaS product."
                         },
                         {
                             "const": "internal",
-                            "description": "Visible to other applications within the same [vendor](#vendor).\nHowever, they are not officially exposed and communicated to customers and 3rd parties.\nThey might not come with the same guarantees on API stability.\n\nInternal resources MUST NOT be made available to consumers without checking the necessary access permissions, e.g., a public API Catalog.\nInternal resources MAY be published through an internal API Catalog if the access permissions are ensured by it."
+                            "description": "Metadata can only be discovered and accessed by vendor internal consumers (e.g. applications or services of the same vendor).\nMUST NOT be made available to external parties or vendor customers.\n\nInternal resources are intended for integration between a vendors own applications and services.\nAPI stability and maturity are explicitly defined via the `releaseStatus` property, which is a separate concern from visibility.\n\nInternal resources MUST NOT be made available without checking the necessary access permissions.\nInternal resources MAY be published through an internal API Catalog if access permissions are ensured by it."
                         },
                         {
                             "const": "private",
-                            "description": "Visible only to the provider application or service, usually within the same system namespace / system type.\n\nPrivate resources MUST NOT be made available to public consumers or consumers outside of the \"private\" scope of the described application."
+                            "description": "Metadata should not be discoverable outside the application / service's own deployment scope (e.g., outside of the provider application or the same system namespace / system type).\nUsed for metadata completeness when describing implementation details or dependencies.\n\nPrivate resources usually have no stability guarantees and can change or be removed at any time.\nThese are typically implementation details not meant for consumption by other services.\n\nExample: Services only used within a microservice architecture or APIs that are only used for the own UIs, not for general consumption.\n\nPrivate resources MUST NOT be made discoverable or accessible outside the application / service's own deployment scope."
                         }
                     ]
                 },
@@ -2832,19 +2874,19 @@
                     "oneOf": [
                         {
                             "const": "beta",
-                            "description": "The contract for the resource is beta and may not be meant for productive use.\nResources of `beta` status MAY be changed or deleted at the providers discretion."
+                            "description": "The API contract has no stability guarantees. Breaking changes may occur at any time without notice or deprecation period.\n\nNot recommended for production use unless you can tolerate breaking changes. Suitable for experimentation, early adopters,\nand feedback gathering. Resources of `beta` status MAY be changed or removed at the provider's discretion."
                         },
                         {
                             "const": "active",
-                            "description": "Resource is meant for productive use and provides a stable API contract."
+                            "description": "The API contract is stable and recommended for production use.\n\nBreaking changes will only be introduced through proper deprecation cycles or new major versions,\nfollowing versioning and compatibility policies. Consumers can rely on active resources with confidence."
                         },
                         {
                             "const": "deprecated",
-                            "description": "Resource has been deprecated.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (aka. decommissioned / removed) in the future, through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
+                            "description": "The resource is still functional but scheduled for removal. No new development should depend on it.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (decommissioned/removed) in the future through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
                         },
                         {
                             "const": "sunset",
-                            "description": "Resource has been sunset, but is still described.\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
+                            "description": "The resource has been decommissioned and is no longer available at runtime. This entry exists for historical reference only.\n\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
                         }
                     ],
                     "examples": [
@@ -2857,6 +2899,13 @@
                     "default": false,
                     "description": "Indicates that this resource is currently not available for consumption at runtime, but could be configured to be so.\nThis can happen either because it has not been setup for use or disabled by an admin / user.\n\nIf the resource is not available in principle for a particular system instance, e.g. due to lack of entitlement, it MUST not be described in the system-instance-aware perspective.\n\nThis property can only reflect the knowledge of the described system instance itself.\nOutside factors for availability can't need to be considered (e.g. network connectivity, middlewares).\n\nA disabled resource MAY skip describing its resource definitions.\n"
                 },
+                "abstract": {
+                    "type": "boolean",
+                    "default": false,
+                    "x-introduced-in-version": "1.13.0",
+                    "x-feature-status": "beta",
+                    "description": "Indicates that the data product serves as interface only. All output ports MUST be marked as abstract.\n\nImplementations of this data product MUST declare compatible with on their specific output port resources as consumption of data products happens through the output ports."
+                },
                 "minSystemVersion": {
                     "type": "string",
                     "description": "The resource has been introduced in the given [system version](../index.md#system-version).\nThis implies that the resource is only available if the system instance is of at least that system version.\n\nIt MUST follow the [Semantic Versioning 2.0.0](https://semver.org/) standard.",
@@ -3395,6 +3444,7 @@
         "DataProductInputPort": {
             "type": "object",
             "title": "Data Product Input Port",
+            "x-ums-type": "embedded",
             "description": "An input port of a data product states where it retrieves its data inputs from.\n\nIt is described as via an ORD Integration Dependency.",
             "properties": {
                 "ordId": {
@@ -3418,6 +3468,7 @@
         "DataProductOutputPort": {
             "type": "object",
             "title": "Data Product Output Port",
+            "x-ums-type": "embedded",
             "description": "A data product output port references the APIs or Events that can be used to access the data-set.\nIt MAY provide full access to the complete data set, but can also just expose a subset of it - if other output ports cover the missing parts.\n\nReferenced API or Event ORD resources don't need to be provided within the same ORD document.\nIf a data product is built against a specific API contract of another application or data product, this API resource should be referred to.\nIn this case the other application is responsible for the lifecycle of the API contract and will update its ORD description independently.",
             "properties": {
                 "ordId": {
@@ -3444,6 +3495,7 @@
             "type": "object",
             "title": "Api Resource Definition",
             "description": "Link and categorization of a machine-readable API definition.\nFor example, OpenAPI definition, OData Metadata, etc.",
+            "x-ums-type": "custom",
             "properties": {
                 "type": {
                     "description": "Type of the API Resource Definition\nIf \"custom\" is chosen, a customType MUST be provided",
@@ -3530,27 +3582,11 @@
                 "mediaType": {
                     "description": "The [Media Type](https://www.iana.org/assignments/media-types/media-types.xhtml) of the definition serialization format.\nA consuming application can use this information to know which file format parser it needs to use.\nFor example, for OpenAPI 3, it's valid to express the same definition in both YAML and JSON.\n\nIf no Media Type is registered for the referenced file,\n`text/plain` MAY be used for arbitrary plain-text and `application/octet-stream` for arbitrary binary data.\n",
                     "type": "string",
-                    "oneOf": [
-                        {
-                            "const": "application/json"
-                        },
-                        {
-                            "const": "application/xml"
-                        },
-                        {
-                            "const": "text/yaml"
-                        },
-                        {
-                            "const": "text/plain",
-                            "description": "For a plain-text format where no other serialization Media Type fits"
-                        },
-                        {
-                            "const": "application/octet-stream",
-                            "description": "For a binary format where no other serialization Media Type fits"
-                        }
-                    ],
+                    "pattern": "^(application|text)\\/[a-zA-Z0-9][a-zA-Z0-9.+\\-]*$",
                     "examples": [
-                        "application/json"
+                        "application/json",
+                        "text/plain",
+                        "application/xml"
                     ]
                 },
                 "url": {
@@ -3568,15 +3604,15 @@
                     "oneOf": [
                         {
                             "const": "public",
-                            "description": "Publicly visible to customers and 3rd parties.\nUsually this includes an contract on the API stability, e.g. the [SAP API Deprecation Policy](https://help.sap.com/viewer/84b35b9c39b247e3ba2a31f02beee46d/Cloud/en-US/5cbfda5a9efe4e97a3e24ddaf7ec5c16.html)."
+                            "description": "Metadata can be discovered and accessed by anyone, including customers, partners, and unauthenticated external parties.\n\nPublic resources typically come with stability guarantees, expressed via versioning and follow formal API lifecycle management. For more details see [Version and Lifecycle](../index.md#version-and-lifecycle) section.\nand follow formal API lifecycle management and deprecation policies.\n\nExample: A REST API that customers use to integrate with your SaaS product."
                         },
                         {
                             "const": "internal",
-                            "description": "Visible to other applications within the same [vendor](#vendor).\nHowever, they are not officially exposed and communicated to customers and 3rd parties.\nThey might not come with the same guarantees on API stability.\n\nInternal resources MUST NOT be made available to consumers without checking the necessary access permissions, e.g., a public API Catalog.\nInternal resources MAY be published through an internal API Catalog if the access permissions are ensured by it."
+                            "description": "Metadata can only be discovered and accessed by vendor internal consumers (e.g. applications or services of the same vendor).\nMUST NOT be made available to external parties or vendor customers.\n\nInternal resources are intended for integration between a vendors own applications and services.\nAPI stability and maturity are explicitly defined via the `releaseStatus` property, which is a separate concern from visibility.\n\nInternal resources MUST NOT be made available without checking the necessary access permissions.\nInternal resources MAY be published through an internal API Catalog if access permissions are ensured by it."
                         },
                         {
                             "const": "private",
-                            "description": "Visible only to the provider application or service, usually within the same system namespace / system type.\n\nPrivate resources MUST NOT be made available to public consumers or consumers outside of the \"private\" scope of the described application."
+                            "description": "Metadata should not be discoverable outside the application / service's own deployment scope (e.g., outside of the provider application or the same system namespace / system type).\nUsed for metadata completeness when describing implementation details or dependencies.\n\nPrivate resources usually have no stability guarantees and can change or be removed at any time.\nThese are typically implementation details not meant for consumption by other services.\n\nExample: Services only used within a microservice architecture or APIs that are only used for the own UIs, not for general consumption.\n\nPrivate resources MUST NOT be made discoverable or accessible outside the application / service's own deployment scope."
                         }
                     ]
                 },
@@ -3606,6 +3642,7 @@
         "EventResourceDefinition": {
             "type": "object",
             "title": "Event Resource Definition",
+            "x-ums-type": "custom",
             "description": "Link and categorization of a machine-readable API definition.\nFor example, AsyncAPI or OpenAPI with callbacks, etc.",
             "properties": {
                 "type": {
@@ -3646,27 +3683,11 @@
                 "mediaType": {
                     "description": "The [Media Type](https://www.iana.org/assignments/media-types/media-types.xhtml) of the definition serialization format.\nA consuming application can use this information to know which file format parser it needs to use.\nFor example, for OpenAPI 3, it's valid to express the same definition in both YAML and JSON.\n\nIf no Media Type is registered for the referenced file,\n`text/plain` MAY be used for arbitrary plain-text and `application/octet-stream` for arbitrary binary data.\n",
                     "type": "string",
-                    "oneOf": [
-                        {
-                            "const": "application/json"
-                        },
-                        {
-                            "const": "application/xml"
-                        },
-                        {
-                            "const": "text/yaml"
-                        },
-                        {
-                            "const": "text/plain",
-                            "description": "For a plain-text format where no other serialization Media Type fits"
-                        },
-                        {
-                            "const": "application/octet-stream",
-                            "description": "For a binary format where no other serialization Media Type fits"
-                        }
-                    ],
+                    "pattern": "^(application|text)\\/[a-zA-Z0-9][a-zA-Z0-9.+\\-]*$",
                     "examples": [
-                        "application/json"
+                        "application/json",
+                        "text/plain",
+                        "application/xml"
                     ]
                 },
                 "url": {
@@ -3698,15 +3719,15 @@
                     "oneOf": [
                         {
                             "const": "public",
-                            "description": "Publicly visible to customers and 3rd parties.\nUsually this includes an contract on the API stability, e.g. the [SAP API Deprecation Policy](https://help.sap.com/viewer/84b35b9c39b247e3ba2a31f02beee46d/Cloud/en-US/5cbfda5a9efe4e97a3e24ddaf7ec5c16.html)."
+                            "description": "Metadata can be discovered and accessed by anyone, including customers, partners, and unauthenticated external parties.\n\nPublic resources typically come with stability guarantees, expressed via versioning and follow formal API lifecycle management. For more details see [Version and Lifecycle](../index.md#version-and-lifecycle) section.\nand follow formal API lifecycle management and deprecation policies.\n\nExample: A REST API that customers use to integrate with your SaaS product."
                         },
                         {
                             "const": "internal",
-                            "description": "Visible to other applications within the same [vendor](#vendor).\nHowever, they are not officially exposed and communicated to customers and 3rd parties.\nThey might not come with the same guarantees on API stability.\n\nInternal resources MUST NOT be made available to consumers without checking the necessary access permissions, e.g., a public API Catalog.\nInternal resources MAY be published through an internal API Catalog if the access permissions are ensured by it."
+                            "description": "Metadata can only be discovered and accessed by vendor internal consumers (e.g. applications or services of the same vendor).\nMUST NOT be made available to external parties or vendor customers.\n\nInternal resources are intended for integration between a vendors own applications and services.\nAPI stability and maturity are explicitly defined via the `releaseStatus` property, which is a separate concern from visibility.\n\nInternal resources MUST NOT be made available without checking the necessary access permissions.\nInternal resources MAY be published through an internal API Catalog if access permissions are ensured by it."
                         },
                         {
                             "const": "private",
-                            "description": "Visible only to the provider application or service, usually within the same system namespace / system type.\n\nPrivate resources MUST NOT be made available to public consumers or consumers outside of the \"private\" scope of the described application."
+                            "description": "Metadata should not be discoverable outside the application / service's own deployment scope (e.g., outside of the provider application or the same system namespace / system type).\nUsed for metadata completeness when describing implementation details or dependencies.\n\nPrivate resources usually have no stability guarantees and can change or be removed at any time.\nThese are typically implementation details not meant for consumption by other services.\n\nExample: Services only used within a microservice architecture or APIs that are only used for the own UIs, not for general consumption.\n\nPrivate resources MUST NOT be made discoverable or accessible outside the application / service's own deployment scope."
                         }
                     ]
                 }
@@ -3718,126 +3739,21 @@
                 "url"
             ]
         },
-        "Product": {
-            "type": "object",
-            "title": "Product",
-            "description": "A **product** in ORD is understood as a commercial product or service.\n\nIt is a high-level entity for structuring the software portfolio from a sales / software logistics perspective.\nWhile **system type** is a technical concept, **product** covers the commercial and marketing view.\n\nPlease note that the ORD concept of a product is very simple on purpose.\nThere is no distinction between products and services and concepts like product versions, variants, etc.\n\nORD assumes that this is handled by specialized systems and that ORD only provides the means to correlate to them.",
-            "properties": {
-                "ordId": {
-                    "type": "string",
-                    "description": "The ORD ID is a stable, globally unique ID for ORD resources or taxonomy.\n\nIt MUST be a valid [ORD ID](../index.md#ord-id) of the appropriate ORD type.",
-                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(product):([a-zA-Z0-9._\\-]+):()$",
-                    "maxLength": 255,
-                    "examples": [
-                        "sap:product:S4HANA_OD:"
-                    ]
-                },
-                "correlationIds": {
-                    "type": "array",
-                    "description": "Correlation IDs can be used to create a reference to related data in other repositories (especially to the system of record).\n\nThey express an \"identity\" / \"equals\" / \"mappable\" relationship to the target ID.\n\nIf a \"part of\" relationship needs to be expressed, use the `partOfGroups` assignment instead.\n\nMUST be a valid [Correlation ID](../index.md#correlation-id).",
-                    "items": {
-                        "type": "string",
-                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-\\/]+):([a-zA-Z0-9._\\-\\/]+)$",
-                        "maxLength": 255
-                    },
-                    "examples": [
-                        [
-                            "sap.xref:product:ABC"
-                        ]
-                    ]
-                },
-                "title": {
-                    "type": "string",
-                    "description": "Human-readable title.\n\nMUST NOT exceed 255 chars.\nMUST NOT contain line breaks.",
-                    "minLength": 1,
-                    "maxLength": 255,
-                    "examples": [
-                        "SAP S/4HANA Cloud"
-                    ]
-                },
-                "shortDescription": {
-                    "type": "string",
-                    "description": "Plain text short description.\n\nMUST NOT exceed 255 chars.\nMUST NOT contain line breaks.",
-                    "minLength": 1,
-                    "maxLength": 255,
-                    "examples": [
-                        "The next generation digital core designed to help you run simple in a digital economy."
-                    ]
-                },
-                "description": {
-                    "type": "string",
-                    "minLength": 1,
-                    "description": "Full description, notated in [CommonMark](https://spec.commonmark.org/) (Markdown).\n\nThe description SHOULD not be excessive in length and is not meant to provide full documentation.\nDetailed documentation SHOULD be attached as (typed) links.",
-                    "examples": []
-                },
-                "vendor": {
-                    "type": "string",
-                    "description": "Vendor / organization that is responsible for the Product.\n\nMUST be a valid reference to a [Vendor](#vendor) ORD ID.",
-                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(vendor):([a-zA-Z0-9._\\-]+):()$",
-                    "maxLength": 256,
-                    "x-association-target": [
-                        "#/definitions/Vendor/ordId"
-                    ],
-                    "examples": [
-                        "sap:vendor:SAP:",
-                        "customer:vendor:Customer:",
-                        "microsoft:vendor:Microsoft:"
-                    ]
-                },
-                "parent": {
-                    "type": "string",
-                    "description": "Optional product parent ORD ID, if a hierarchical product structure needs to be expressed.\n\nMUST be a valid reference to a [Product](#product) ORD ID.",
-                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(product):([a-zA-Z0-9._\\-]+):()$",
-                    "x-association-target": [
-                        "#/definitions/Product/ordId"
-                    ],
-                    "examples": [
-                        "sap:product:S4HANA_OD:"
-                    ]
-                },
-                "tags": {
-                    "type": "array",
-                    "items": {
-                        "type": "string",
-                        "pattern": "^[a-zA-Z0-9-_.\\/ ]*$",
-                        "minLength": 1
-                    },
-                    "description": "List of free text style tags.\nNo special characters are allowed except `-`, `_`, `.`, `/` and ` `.\n\nTags that are assigned to a `Package` are inherited to all of the ORD resources it contains.",
-                    "examples": [
-                        [
-                            "storage",
-                            "high-availability"
-                        ]
-                    ]
-                },
-                "labels": {
-                    "$ref": "#/definitions/Labels"
-                },
-                "documentationLabels": {
-                    "$ref": "#/definitions/DocumentationLabels"
-                }
-            },
-            "additionalProperties": false,
-            "required": [
-                "ordId",
-                "title",
-                "shortDescription",
-                "vendor"
-            ]
-        },
-        "Capability": {
+        "Agent": {
             "type": "object",
-            "title": "Capability",
-            "x-introduced-in-version": "1.4.0",
-            "description": "Capabilities can be used to describe use case specific capabilities, most notably supported features or additional information (like configuration) that needs to be understood from outside.\nThis is a generic ORD concept that aims to cover many different capability discovery use cases that would otherwise need be implemented as individual service provider interfaces (SPIs).\n\nIf a capability needs to expose more information than possible with generic capability properties, a custom capability definition can be defined and referenced in ORD.\nThis is the same idea and mechanism as with API resources and their resource definition formats.",
+            "title": "Agent",
+            "x-ums-type": "root",
+            "x-introduced-in-version": "1.14.0",
+            "x-feature-status": "beta",
+            "description": "An **Agent** provides a high-level description of an AI-powered autonomous system that can perform tasks, make decisions, and interact with users or other systems to achieve specific business goals.\n\nAn Agent can relate to specific entity types it works with, declare integration dependencies on external systems it requires, and expose its capabilities through APIs using protocols like A2A (Agent-to-Agent).\n\nAgents enable intelligent automation and decision-making within business processes by providing semantic understanding and context-aware capabilities beyond traditional API-based integrations.\n\nFor more details, see [AI Agents and Protocols](../concepts/ai-agents-and-protocols.md).",
             "properties": {
                 "ordId": {
                     "type": "string",
                     "description": "The ORD ID is a stable, globally unique ID for ORD resources or taxonomy.\n\nIt MUST be a valid [ORD ID](../index.md#ord-id) of the appropriate ORD type.",
-                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(capability):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                    "pattern": "^([a-z0-9-]+(?:[.][a-z0-9-]+)*):(agent):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
                     "maxLength": 255,
                     "examples": [
-                        "sap.foo.bar:capability:fieldExtensibility:v1"
+                        "sap.foo.bar:agent:disputeAgent:v1"
                     ]
                 },
                 "localId": {
@@ -3864,44 +3780,13 @@
                         ]
                     ]
                 },
-                "type": {
-                    "description": "Type of the Capability",
-                    "type": "string",
-                    "anyOf": [
-                        {
-                            "type": "string",
-                            "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
-                            "description": "Any valid [Specification ID](../index.md#specification-id)."
-                        },
-                        {
-                            "const": "sap.mdo:mdi-capability:v1",
-                            "description": "Capability for SAP Master Data Integration (MDI).\n\nFor the capability definitions: `type` MUST ONLY be set to `sap.mdo:mdi-capability-definition:v1`."
-                        },
-                        {
-                            "const": "custom",
-                            "description": "If chosen, `customType` MUST be provided."
-                        }
-                    ],
-                    "examples": [
-                        "custom"
-                    ]
-                },
-                "customType": {
-                    "type": "string",
-                    "description": "If the fixed `type` enum values need to be extended, an arbitrary `customType` can be provided.\n\nMUST be a valid [Specification ID](../index.md#specification-id).\n\nMUST only be provided if `type` is set to `custom`.",
-                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
-                    "maxLength": 255,
-                    "examples": [
-                        "sap:custom-definition-format:v1"
-                    ]
-                },
                 "title": {
                     "type": "string",
                     "description": "Human-readable title.\n\nMUST NOT exceed 255 chars.\nMUST NOT contain line breaks.",
                     "minLength": 1,
                     "maxLength": 255,
                     "examples": [
-                        "MDI Capability"
+                        "Dispute Agent"
                     ]
                 },
                 "shortDescription": {
@@ -3964,41 +3849,41 @@
                 },
                 "visibility": {
                     "type": "string",
-                    "description": "The visibility states who is allowed to \"see\" the described resource or capability.",
+                    "description": "Defines metadata access control - which categories of consumers are allowed to discover and access the resource and its metadata.\n\nThis controls who can see that the resource exists and retrieve its metadata level information.\nIt does NOT control runtime access to the resource itself - that is managed separately through authentication and authorization mechanisms.\n\nUse this to prevent exposing internal implementation details to inappropriate consumer audiences.",
                     "oneOf": [
                         {
                             "const": "public",
-                            "description": "Publicly visible to customers and 3rd parties.\nUsually this includes an contract on the API stability, e.g. the [SAP API Deprecation Policy](https://help.sap.com/viewer/84b35b9c39b247e3ba2a31f02beee46d/Cloud/en-US/5cbfda5a9efe4e97a3e24ddaf7ec5c16.html)."
+                            "description": "Metadata can be discovered and accessed by anyone, including customers, partners, and unauthenticated external parties.\n\nPublic resources typically come with stability guarantees, expressed via versioning and follow formal API lifecycle management. For more details see [Version and Lifecycle](../index.md#version-and-lifecycle) section.\nand follow formal API lifecycle management and deprecation policies.\n\nExample: A REST API that customers use to integrate with your SaaS product."
                         },
                         {
                             "const": "internal",
-                            "description": "Visible to other applications within the same [vendor](#vendor).\nHowever, they are not officially exposed and communicated to customers and 3rd parties.\nThey might not come with the same guarantees on API stability.\n\nInternal resources MUST NOT be made available to consumers without checking the necessary access permissions, e.g., a public API Catalog.\nInternal resources MAY be published through an internal API Catalog if the access permissions are ensured by it."
+                            "description": "Metadata can only be discovered and accessed by vendor internal consumers (e.g. applications or services of the same vendor).\nMUST NOT be made available to external parties or vendor customers.\n\nInternal resources are intended for integration between a vendors own applications and services.\nAPI stability and maturity are explicitly defined via the `releaseStatus` property, which is a separate concern from visibility.\n\nInternal resources MUST NOT be made available without checking the necessary access permissions.\nInternal resources MAY be published through an internal API Catalog if access permissions are ensured by it."
                         },
                         {
                             "const": "private",
-                            "description": "Visible only to the provider application or service, usually within the same system namespace / system type.\n\nPrivate resources MUST NOT be made available to public consumers or consumers outside of the \"private\" scope of the described application."
+                            "description": "Metadata should not be discoverable outside the application / service's own deployment scope (e.g., outside of the provider application or the same system namespace / system type).\nUsed for metadata completeness when describing implementation details or dependencies.\n\nPrivate resources usually have no stability guarantees and can change or be removed at any time.\nThese are typically implementation details not meant for consumption by other services.\n\nExample: Services only used within a microservice architecture or APIs that are only used for the own UIs, not for general consumption.\n\nPrivate resources MUST NOT be made discoverable or accessible outside the application / service's own deployment scope."
                         }
                     ]
                 },
                 "releaseStatus": {
                     "type": "string",
-                    "description": "The `releaseStatus` specifies the stability of the resource and its external contract.",
+                    "description": "Defines the maturity level and stability commitment for the resource's API contract (interface, behavior, data models).\n\nThis indicates whether the resource may undergo backward-incompatible changes. It helps consumers understand the risk\nof depending on the resource and whether it's suitable for production use.\n\nNote: This is independent of `visibility` and does not imply availability guarantees or SLAs - it concerns only the API contract stability.\n\nSee [Lifecycle](../index.md#lifecycle) and [Compatibility](../concepts/compatibility.md) for more details.",
                     "oneOf": [
                         {
                             "const": "beta",
-                            "description": "The contract for the resource is beta and may not be meant for productive use.\nResources of `beta` status MAY be changed or deleted at the providers discretion."
+                            "description": "The API contract has no stability guarantees. Breaking changes may occur at any time without notice or deprecation period.\n\nNot recommended for production use unless you can tolerate breaking changes. Suitable for experimentation, early adopters,\nand feedback gathering. Resources of `beta` status MAY be changed or removed at the provider's discretion."
                         },
                         {
                             "const": "active",
-                            "description": "Resource is meant for productive use and provides a stable API contract."
+                            "description": "The API contract is stable and recommended for production use.\n\nBreaking changes will only be introduced through proper deprecation cycles or new major versions,\nfollowing versioning and compatibility policies. Consumers can rely on active resources with confidence."
                         },
                         {
                             "const": "deprecated",
-                            "description": "Resource has been deprecated.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (aka. decommissioned / removed) in the future, through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
+                            "description": "The resource is still functional but scheduled for removal. No new development should depend on it.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (decommissioned/removed) in the future through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
                         },
                         {
                             "const": "sunset",
-                            "description": "Resource has been sunset, but is still described.\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
+                            "description": "The resource has been decommissioned and is no longer available at runtime. This entry exists for historical reference only.\n\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
                         }
                     ],
                     "examples": [
@@ -4020,44 +3905,720 @@
                         "2024.8.0"
                     ]
                 },
-                "relatedEntityTypes": {
+                "partOfProducts": {
                     "type": "array",
-                    "description": "Optional list of related EntityType Resources.\nMUST be a valid reference to an [EntityType Resource](#entity-type) ORD ID.",
+                    "description": "List of products the resources of the Package are a part of.\n\nMUST be a valid reference to a [Product](#product) ORD ID.\n\n`partOfProducts` that are assigned to a `Package` are inherited to all of the ORD resources it contains.",
                     "items": {
                         "type": "string",
-                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(entityType):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(product):([a-zA-Z0-9._\\-]+):()$",
+                        "maxLength": 255,
                         "x-association-target": [
-                            "#/definitions/EntityType/ordId"
+                            "#/definitions/Product/ordId"
                         ]
                     },
+                    "minItems": 0,
                     "examples": [
                         [
-                            "sap.odm:entityType:WorkforcePerson:v1"
+                            "sap:product:S4HANA_OD:"
                         ]
                     ]
                 },
-                "definitions": {
+                "responsible": {
+                    "type": "string",
+                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-\\/]+):([a-zA-Z0-9._\\-\\/]+)$",
+                    "maxLength": 255,
+                    "x-introduced-in-version": "1.8.0",
+                    "description": "Contains typically the organization that is responsible in the sense of RACI matrix for this ORD resource. This includes support and feature requests. It is maintained as correlation id to for example support components.",
+                    "examples": [
+                        "sap:ach:CIC-DP-CO"
+                    ]
+                },
+                "deprecationDate": {
+                    "type": "string",
+                    "format": "date-time",
+                    "description": "The deprecation date defines when the resource has been set as deprecated.\nThis is not to be confused with the `sunsetDate` which defines when the resource will be actually sunset, aka. decommissioned / removed / archived.\n\nThe date format MUST comply with [RFC 3339, section 5.6](https://tools.ietf.org/html/rfc3339#section-5.6).",
+                    "examples": [
+                        "2020-12-08T15:47:04+00:00"
+                    ]
+                },
+                "sunsetDate": {
+                    "type": "string",
+                    "format": "date-time",
+                    "description": "The sunset date defines when the resource is scheduled to be decommissioned / removed / archived.\n\nIf the `releaseStatus` is set to `deprecated`, the `sunsetDate` SHOULD be provided (if already known).\nOnce the sunset date is known and ready to be communicated externally, it MUST be provided here.\n\nThe date format MUST comply with [RFC 3339, section 5.6](https://tools.ietf.org/html/rfc3339#section-5.6).",
+                    "examples": [
+                        "2022-01-08T15:47:04+00:00"
+                    ]
+                },
+                "successors": {
                     "type": "array",
-                    "description": "List of available machine-readable definitions, which describe the resource or capability in detail.\nSee also [Resource Definitions](../index.md#resource-definitions) for more context.\n\nEach definition is to be understood as an alternative description format, describing the same resource / capability.\nAs a consequence the same definition type MUST NOT be provided more than once.\nThe exception is when the same definition type is provided more than once, but with a different `visibility`.\n\nIt is RECOMMENDED to provide the definitions as they enable machine-readable use cases.\nIf the definitions are added or changed, the `version` MUST be incremented.\nAn ORD aggregator MAY only (re)fetch the definitions again when the `version` was incremented.",
+                    "description": "The successor resource(s).\n\nMUST be a valid reference to an ORD ID.\n\nIf the `releaseStatus` is set to `deprecated`, `successors` MUST be provided if one exists.\nIf `successors` is given, the described resource SHOULD set its `releaseStatus` to `deprecated`.",
                     "items": {
-                        "$ref": "#/definitions/CapabilityDefinition"
+                        "type": "string",
+                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(agent):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                        "x-association-target": [
+                            "#/definitions/Agent/ordId"
+                        ],
+                        "maxLength": 255
                     }
                 },
-                "links": {
+                "changelogEntries": {
                     "type": "array",
-                    "description": "Generic Links with arbitrary meaning and content.",
+                    "description": "Contains changelog entries that summarize changes with special regards to version and releaseStatus",
                     "items": {
-                        "$ref": "#/definitions/Link"
+                        "$ref": "#/definitions/ChangelogEntry"
                     }
                 },
-                "tags": {
+                "policyLevels": {
                     "type": "array",
+                    "description": "A list of [policy levels](../../spec-extensions/policy-levels/) that the described resources need to be compliant with.\nFor each chosen policy level, additional expectations and validations rules will be applied.\n\nPolicy levels can be defined on ORD Document level, but also be overwritten on an individual package or resource level.\n\nA policy level MUST be a valid [Specification ID](../index.md#specification-id).",
+                    "x-introduced-in-version": "1.9.9",
                     "items": {
                         "type": "string",
-                        "pattern": "^[a-zA-Z0-9-_.\\/ ]*$",
-                        "minLength": 1
-                    },
-                    "description": "List of free text style tags.\nNo special characters are allowed except `-`, `_`, `.`, `/` and ` `.\n\nTags that are assigned to a `Package` are inherited to all of the ORD resources it contains.",
+                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                        "maxLength": 255,
+                        "examples": [
+                            "sap:core:v1"
+                        ]
+                    }
+                },
+                "countries": {
+                    "type": "array",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^[A-Z]{2}$"
+                    },
+                    "description": "List of countries that the Package resources are applicable to.\n\nMUST be expressed as an array of country codes according to [IES ISO-3166 ALPHA-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2).\n\n`countries` that are assigned to a `Package` are inherited to all of the ORD resources it contains.",
+                    "examples": [
+                        [
+                            "DE",
+                            "US"
+                        ]
+                    ]
+                },
+                "lineOfBusiness": {
+                    "type": "array",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^[a-zA-Z0-9-_.\\/& ]*$",
+                        "minLength": 1,
+                        "anyOf": [
+                            {
+                                "type": "string"
+                            },
+                            {
+                                "const": "Asset Management"
+                            },
+                            {
+                                "const": "Commerce"
+                            },
+                            {
+                                "const": "Finance"
+                            },
+                            {
+                                "const": "Human Resources"
+                            },
+                            {
+                                "const": "Manufacturing"
+                            },
+                            {
+                                "const": "Marketing"
+                            },
+                            {
+                                "const": "R&D Engineering"
+                            },
+                            {
+                                "const": "Sales"
+                            },
+                            {
+                                "const": "Service"
+                            },
+                            {
+                                "const": "Sourcing and Procurement"
+                            },
+                            {
+                                "const": "Strategy, Compliance, and Governance"
+                            },
+                            {
+                                "const": "Supply Chain"
+                            },
+                            {
+                                "const": "Sustainability"
+                            },
+                            {
+                                "const": "Metering"
+                            },
+                            {
+                                "const": "Grid Operations and Maintenance"
+                            },
+                            {
+                                "const": "Plant Operations and Maintenance"
+                            },
+                            {
+                                "const": "Maintenance and Engineering"
+                            }
+                        ]
+                    },
+                    "description": "List of line of business tags.\nNo special characters are allowed except `-`, `_`, `.`, `/` and ` `.\n\n`lineOfBusiness` that are assigned to a `Package` are inherited to all of the ORD resources it contains.",
+                    "examples": [
+                        [
+                            "Sales"
+                        ]
+                    ]
+                },
+                "industry": {
+                    "type": "array",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^[a-zA-Z0-9-_.\\/& ]*$",
+                        "minLength": 1,
+                        "anyOf": [
+                            {
+                                "type": "string"
+                            },
+                            {
+                                "const": "Aerospace and Defense"
+                            },
+                            {
+                                "const": "Agribusiness"
+                            },
+                            {
+                                "const": "Automotive"
+                            },
+                            {
+                                "const": "Banking"
+                            },
+                            {
+                                "const": "Chemicals"
+                            },
+                            {
+                                "const": "Consumer Industries"
+                            },
+                            {
+                                "const": "Consumer Products"
+                            },
+                            {
+                                "const": "Defense and Security"
+                            },
+                            {
+                                "const": "Discrete Industries"
+                            },
+                            {
+                                "const": "Energy and Natural Resources"
+                            },
+                            {
+                                "const": "Engineering Construction and Operations"
+                            },
+                            {
+                                "const": "Financial Services"
+                            },
+                            {
+                                "const": "Future Cities"
+                            },
+                            {
+                                "const": "Healthcare"
+                            },
+                            {
+                                "const": "High Tech"
+                            },
+                            {
+                                "const": "Higher Education and Research"
+                            },
+                            {
+                                "const": "Industrial Machinery and Components"
+                            },
+                            {
+                                "const": "Insurance"
+                            },
+                            {
+                                "const": "Life Sciences"
+                            },
+                            {
+                                "const": "Media"
+                            },
+                            {
+                                "const": "Mill Products"
+                            },
+                            {
+                                "const": "Mining"
+                            },
+                            {
+                                "const": "Oil and Gas"
+                            },
+                            {
+                                "const": "Professional Services"
+                            },
+                            {
+                                "const": "Public Sector"
+                            },
+                            {
+                                "const": "Public Services"
+                            },
+                            {
+                                "const": "Retail"
+                            },
+                            {
+                                "const": "Service Industries"
+                            },
+                            {
+                                "const": "Sports and Entertainment"
+                            },
+                            {
+                                "const": "Telecommunications"
+                            },
+                            {
+                                "const": "Travel and Transportation"
+                            },
+                            {
+                                "const": "Utilities"
+                            },
+                            {
+                                "const": "Wholesale Distribution"
+                            }
+                        ]
+                    },
+                    "description": "List of industry tags.\nNo special characters are allowed except `-`, `_`, `.`, `/` and ` `.\n\n`industry` that are assigned to a `Package` are inherited to all of the ORD resources it contains.",
+                    "examples": [
+                        [
+                            "Automotive"
+                        ],
+                        [
+                            "Retail",
+                            "Public Sector"
+                        ],
+                        []
+                    ]
+                },
+                "relatedEntityTypes": {
+                    "type": "array",
+                    "description": "Optional list of related EntityType Resources.\n\nMUST be a valid reference to an [EntityType Resource](#entity-type) ORD ID.",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(entityType):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                        "x-association-target": [
+                            "#/definitions/EntityType/ordId"
+                        ]
+                    },
+                    "examples": [
+                        [
+                            "sap.odm:entityType:WorkforcePerson:v1"
+                        ]
+                    ]
+                },
+                "exposedApiResources": {
+                    "type": "array",
+                    "description": "Optional list of API Resources that expose the functionality of the agent. Typically using the A2A protocol, but other protocols are possible as well.\n\nMUST be a valid reference to an [API Resource](#api-resource) ORD ID.",
+                    "items": {
+                        "$ref": "#/definitions/ExposedApiResourcesTarget"
+                    },
+                    "examples": [
+                        [
+                            {
+                                "ordId": "sap.foo:apiResource:DisputeResolutionAgent:v1"
+                            }
+                        ]
+                    ]
+                },
+                "integrationDependencies": {
+                    "type": "array",
+                    "description": "Optional list of integration dependencies that the agent relies on.\n\nMUST be a valid reference to an [Integration Dependency](#integration-dependency) ORD ID.",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^([a-z0-9-]+(?:[.][a-z0-9-]+)*):(integrationDependency):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                        "maxLength": 255,
+                        "x-association-target": [
+                            "#/definitions/IntegrationDependency/ordId"
+                        ]
+                    },
+                    "examples": [
+                        [
+                            "sap.foo.bar:integrationDependency:DisputeCaseManagement:v1"
+                        ]
+                    ]
+                },
+                "links": {
+                    "type": "array",
+                    "description": "Generic Links with arbitrary meaning and content.",
+                    "items": {
+                        "$ref": "#/definitions/Link"
+                    }
+                },
+                "tags": {
+                    "type": "array",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^[a-zA-Z0-9-_.\\/ ]*$",
+                        "minLength": 1
+                    },
+                    "description": "List of free text style tags.\nNo special characters are allowed except `-`, `_`, `.`, `/` and ` `.\n\nTags that are assigned to a `Package` are inherited to all of the ORD resources it contains.",
+                    "examples": [
+                        [
+                            "storage",
+                            "high-availability"
+                        ]
+                    ]
+                },
+                "labels": {
+                    "$ref": "#/definitions/Labels"
+                },
+                "documentationLabels": {
+                    "$ref": "#/definitions/DocumentationLabels"
+                }
+            },
+            "additionalProperties": false,
+            "required": [
+                "ordId",
+                "title",
+                "version",
+                "releaseStatus",
+                "visibility",
+                "partOfPackage"
+            ],
+            "x-recommended": [
+                "lastUpdate"
+            ]
+        },
+        "Product": {
+            "type": "object",
+            "title": "Product",
+            "x-ums-type": "root",
+            "description": "A **product** in ORD is understood as a commercial product or service.\n\nIt is a high-level entity for structuring the software portfolio from a sales / software logistics perspective.\nWhile **system type** is a technical concept, **product** covers the commercial and marketing view.\n\nPlease note that the ORD concept of a product is very simple on purpose.\nThere is no distinction between products and services and concepts like product versions, variants, etc.\n\nORD assumes that this is handled by specialized systems and that ORD only provides the means to correlate to them.",
+            "properties": {
+                "ordId": {
+                    "type": "string",
+                    "description": "The ORD ID is a stable, globally unique ID for ORD resources or taxonomy.\n\nIt MUST be a valid [ORD ID](../index.md#ord-id) of the appropriate ORD type.",
+                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(product):([a-zA-Z0-9._\\-]+):()$",
+                    "maxLength": 255,
+                    "examples": [
+                        "sap:product:S4HANA_OD:"
+                    ]
+                },
+                "correlationIds": {
+                    "type": "array",
+                    "description": "Correlation IDs can be used to create a reference to related data in other repositories (especially to the system of record).\n\nThey express an \"identity\" / \"equals\" / \"mappable\" relationship to the target ID.\n\nIf a \"part of\" relationship needs to be expressed, use the `partOfGroups` assignment instead.\n\nMUST be a valid [Correlation ID](../index.md#correlation-id).",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-\\/]+):([a-zA-Z0-9._\\-\\/]+)$",
+                        "maxLength": 255
+                    },
+                    "examples": [
+                        [
+                            "sap.xref:product:ABC"
+                        ]
+                    ]
+                },
+                "title": {
+                    "type": "string",
+                    "description": "Human-readable title.\n\nMUST NOT exceed 255 chars.\nMUST NOT contain line breaks.",
+                    "minLength": 1,
+                    "maxLength": 255,
+                    "examples": [
+                        "SAP S/4HANA Cloud"
+                    ]
+                },
+                "shortDescription": {
+                    "type": "string",
+                    "description": "Plain text short description.\n\nMUST NOT exceed 255 chars.\nMUST NOT contain line breaks.",
+                    "minLength": 1,
+                    "maxLength": 255,
+                    "examples": [
+                        "The next generation digital core designed to help you run simple in a digital economy."
+                    ]
+                },
+                "description": {
+                    "type": "string",
+                    "minLength": 1,
+                    "description": "Full description, notated in [CommonMark](https://spec.commonmark.org/) (Markdown).\n\nThe description SHOULD not be excessive in length and is not meant to provide full documentation.\nDetailed documentation SHOULD be attached as (typed) links.",
+                    "examples": []
+                },
+                "vendor": {
+                    "type": "string",
+                    "description": "Vendor / organization that is responsible for the Product.\n\nMUST be a valid reference to a [Vendor](#vendor) ORD ID.",
+                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(vendor):([a-zA-Z0-9._\\-]+):()$",
+                    "maxLength": 256,
+                    "x-association-target": [
+                        "#/definitions/Vendor/ordId"
+                    ],
+                    "examples": [
+                        "sap:vendor:SAP:",
+                        "customer:vendor:Customer:",
+                        "microsoft:vendor:Microsoft:"
+                    ]
+                },
+                "parent": {
+                    "type": "string",
+                    "description": "Optional product parent ORD ID, if a hierarchical product structure needs to be expressed.\n\nMUST be a valid reference to a [Product](#product) ORD ID.",
+                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(product):([a-zA-Z0-9._\\-]+):()$",
+                    "x-association-target": [
+                        "#/definitions/Product/ordId"
+                    ],
+                    "examples": [
+                        "sap:product:S4HANA_OD:"
+                    ]
+                },
+                "tags": {
+                    "type": "array",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^[a-zA-Z0-9-_.\\/ ]*$",
+                        "minLength": 1
+                    },
+                    "description": "List of free text style tags.\nNo special characters are allowed except `-`, `_`, `.`, `/` and ` `.\n\nTags that are assigned to a `Package` are inherited to all of the ORD resources it contains.",
+                    "examples": [
+                        [
+                            "storage",
+                            "high-availability"
+                        ]
+                    ]
+                },
+                "labels": {
+                    "$ref": "#/definitions/Labels"
+                },
+                "documentationLabels": {
+                    "$ref": "#/definitions/DocumentationLabels"
+                }
+            },
+            "additionalProperties": false,
+            "required": [
+                "ordId",
+                "title",
+                "shortDescription",
+                "vendor"
+            ]
+        },
+        "Capability": {
+            "type": "object",
+            "title": "Capability",
+            "x-ums-type": "root",
+            "x-introduced-in-version": "1.4.0",
+            "description": "Capabilities can be used to describe use case specific capabilities, most notably supported features or additional information (like configuration) that needs to be understood from outside.\nThis is a generic ORD concept that aims to cover many different capability discovery use cases that would otherwise need be implemented as individual service provider interfaces (SPIs).\n\nIf a capability needs to expose more information than possible with generic capability properties, a custom capability definition can be defined and referenced in ORD.\nThis is the same idea and mechanism as with API resources and their resource definition formats.",
+            "properties": {
+                "ordId": {
+                    "type": "string",
+                    "description": "The ORD ID is a stable, globally unique ID for ORD resources or taxonomy.\n\nIt MUST be a valid [ORD ID](../index.md#ord-id) of the appropriate ORD type.",
+                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(capability):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                    "maxLength": 255,
+                    "examples": [
+                        "sap.foo.bar:capability:fieldExtensibility:v1"
+                    ]
+                },
+                "localId": {
+                    "type": "string",
+                    "x-introduced-in-version": "1.2.1",
+                    "description": "The locally unique ID under which this resource can be looked up / resolved in the described system itself.\nUnlike the ORD ID it's not globally unique, but it may be useful to document the original ID / technical name.\n\nIt MAY also be used as the `<resourceName>` fragment in the ORD ID, IF it can fulfill the charset and length limitations within the ORD ID.\nBut since this is not always possible, no assumptions MUST be made about the local ID being the same as the `<resourceName>` fragment in the ORD ID.",
+                    "maxLength": 255,
+                    "examples": [
+                        "SuccessFactorsRecruiting",
+                        "91cd9972-c05d-4d29-8b6e-dbef2a2d48e9"
+                    ]
+                },
+                "correlationIds": {
+                    "type": "array",
+                    "description": "Correlation IDs can be used to create a reference to related data in other repositories (especially to the system of record).\n\nThey express an \"identity\" / \"equals\" / \"mappable\" relationship to the target ID.\n\nIf a \"part of\" relationship needs to be expressed, use the `partOfGroups` assignment instead.\n\nMUST be a valid [Correlation ID](../index.md#correlation-id).",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-\\/]+):([a-zA-Z0-9._\\-\\/]+)$",
+                        "maxLength": 255
+                    },
+                    "examples": [
+                        [
+                            "sap.s4:communicationScenario:SAP_COM_0008"
+                        ]
+                    ]
+                },
+                "type": {
+                    "description": "Type of the Capability",
+                    "type": "string",
+                    "anyOf": [
+                        {
+                            "type": "string",
+                            "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                            "description": "Any valid [Specification ID](../index.md#specification-id)."
+                        },
+                        {
+                            "const": "sap.mdo:mdi-capability:v1",
+                            "description": "Capability for SAP Master Data Integration (MDI).\n\nFor the capability definitions: `type` MUST ONLY be set to `sap.mdo:mdi-capability-definition:v1`."
+                        },
+                        {
+                            "const": "custom",
+                            "description": "If chosen, `customType` MUST be provided."
+                        }
+                    ],
+                    "examples": [
+                        "custom"
+                    ]
+                },
+                "customType": {
+                    "type": "string",
+                    "description": "If the fixed `type` enum values need to be extended, an arbitrary `customType` can be provided.\n\nMUST be a valid [Specification ID](../index.md#specification-id).\n\nMUST only be provided if `type` is set to `custom`.",
+                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                    "maxLength": 255,
+                    "examples": [
+                        "sap:custom-definition-format:v1"
+                    ]
+                },
+                "title": {
+                    "type": "string",
+                    "description": "Human-readable title.\n\nMUST NOT exceed 255 chars.\nMUST NOT contain line breaks.",
+                    "minLength": 1,
+                    "maxLength": 255,
+                    "examples": [
+                        "MDI Capability"
+                    ]
+                },
+                "shortDescription": {
+                    "type": "string",
+                    "description": "Plain text short description.\n\nMUST NOT exceed 255 chars.\nMUST NOT contain line breaks.",
+                    "minLength": 1,
+                    "maxLength": 255,
+                    "examples": [
+                        "SAP S/4HANA Cloud, our next generation cloud ERP suite designed for in-memory computing."
+                    ]
+                },
+                "description": {
+                    "type": "string",
+                    "minLength": 1,
+                    "description": "Full description, notated in [CommonMark](https://spec.commonmark.org/) (Markdown).\n\nThe description SHOULD not be excessive in length and is not meant to provide full documentation.\nDetailed documentation SHOULD be attached as (typed) links.",
+                    "examples": [
+                        "SAP S/4HANA Cloud, our next generation cloud ERP suite designed for\nin-memory computing, acts as a digital core, connecting your\nenterprise with people, business networks, the Internet of Things,\nBig Data, and more.\n"
+                    ]
+                },
+                "partOfPackage": {
+                    "type": "string",
+                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(package):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                    "x-association-target": [
+                        "#/definitions/Package/ordId"
+                    ],
+                    "maxLength": 255,
+                    "description": "Defines which Package the resource is part of.\n\nMUST be a valid reference to a [Package](#package) ORD ID.\n\nEvery resource MUST be part of one package.",
+                    "examples": [
+                        "sap.xref:package:SomePackage:v1"
+                    ]
+                },
+                "partOfGroups": {
+                    "type": "array",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-\\/]+):([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-\\/]+)$",
+                        "x-association-target": [
+                            "#/definitions/Group/groupId"
+                        ]
+                    },
+                    "description": "Defines which groups the resource is assigned to.\n\nThe property is optional, but if given the value MUST be an array of valid Group IDs.\n\nGroups are a lightweight custom taxonomy concept.\nThey express a \"part of\" relationship to the chosen group concept.\nIf an \"identity / equals\" relationship needs to be expressed, use the `correlationIds` instead.\n\nAll resources that share the same group ID assignment are effectively grouped together."
+                },
+                "version": {
+                    "type": "string",
+                    "description": "The complete [SemVer](https://semver.org/) version string.\n\nIt MUST follow the [Semantic Versioning 2.0.0](https://semver.org/) standard.\nIt SHOULD be changed if the ORD information or referenced resource definitions changed.\nIt SHOULD express minor and patch changes that don't lead to incompatible changes.\n\nWhen the `version` major version changes, the [ORD ID](../index.md#ord-id) `<majorVersion>` fragment MUST be updated to be identical.\nIn case that a resource definition file also contains a version number (e.g. [OpenAPI `info`.`version`](https://spec.openapis.org/oas/v3.1.1.html#info-object)), it MUST be equal with the resource `version` to avoid inconsistencies.\n\nIf the resource has been extended by the user, the change MUST be indicated via `lastUpdate`.\nThe `version` MUST not be bumped for changes in extensions.\n\nThe general [Version and Lifecycle](../index.md#version-and-lifecycle) flow MUST be followed.\n\nNote: A change is only relevant for a version increment, if it affects the ORD resource or ORD taxonomy directly.\nFor example: If a resource within a `Package` changes, but the Package itself did not, the Package version does not need to be incremented.",
+                    "pattern": "^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-((?:0|[1-9]\\d*|\\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\\.(?:0|[1-9]\\d*|\\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\\+([0-9a-zA-Z-]+(?:\\.[0-9a-zA-Z-]+)*))?$",
+                    "examples": [
+                        "1.2.3",
+                        "1.0.0-alpha.1"
+                    ]
+                },
+                "lastUpdate": {
+                    "type": "string",
+                    "format": "date-time",
+                    "x-introduced-in-version": "1.4.0",
+                    "description": "Optional, but RECOMMENDED indicator when (date-time) the last change to the resource (including its definitions) happened.\n\nThe date format MUST comply with [RFC 3339, section 5.6](https://tools.ietf.org/html/rfc3339#section-5.6).\n\nWhen retrieved from an ORD aggregator, `lastUpdate` will be reliable there and reflect either the provider based update time or the aggregator processing time.\nTherefore consumers MAY rely on it to detect changes to the metadata and the attached resource definition files.\n\nIf the resource has attached definitions, either the `version` or `lastUpdate` property MUST be defined and updated to let the ORD aggregator know that they need to be fetched again.\n\nTogether with `perspectives`, this property SHOULD be used to optimize the metadata crawling process of the ORD aggregators.",
+                    "examples": [
+                        "2022-12-19T15:47:04+00:00"
+                    ]
+                },
+                "visibility": {
+                    "type": "string",
+                    "description": "Defines metadata access control - which categories of consumers are allowed to discover and access the resource and its metadata.\n\nThis controls who can see that the resource exists and retrieve its metadata level information.\nIt does NOT control runtime access to the resource itself - that is managed separately through authentication and authorization mechanisms.\n\nUse this to prevent exposing internal implementation details to inappropriate consumer audiences.",
+                    "oneOf": [
+                        {
+                            "const": "public",
+                            "description": "Metadata can be discovered and accessed by anyone, including customers, partners, and unauthenticated external parties.\n\nPublic resources typically come with stability guarantees, expressed via versioning and follow formal API lifecycle management. For more details see [Version and Lifecycle](../index.md#version-and-lifecycle) section.\nand follow formal API lifecycle management and deprecation policies.\n\nExample: A REST API that customers use to integrate with your SaaS product."
+                        },
+                        {
+                            "const": "internal",
+                            "description": "Metadata can only be discovered and accessed by vendor internal consumers (e.g. applications or services of the same vendor).\nMUST NOT be made available to external parties or vendor customers.\n\nInternal resources are intended for integration between a vendors own applications and services.\nAPI stability and maturity are explicitly defined via the `releaseStatus` property, which is a separate concern from visibility.\n\nInternal resources MUST NOT be made available without checking the necessary access permissions.\nInternal resources MAY be published through an internal API Catalog if access permissions are ensured by it."
+                        },
+                        {
+                            "const": "private",
+                            "description": "Metadata should not be discoverable outside the application / service's own deployment scope (e.g., outside of the provider application or the same system namespace / system type).\nUsed for metadata completeness when describing implementation details or dependencies.\n\nPrivate resources usually have no stability guarantees and can change or be removed at any time.\nThese are typically implementation details not meant for consumption by other services.\n\nExample: Services only used within a microservice architecture or APIs that are only used for the own UIs, not for general consumption.\n\nPrivate resources MUST NOT be made discoverable or accessible outside the application / service's own deployment scope."
+                        }
+                    ]
+                },
+                "releaseStatus": {
+                    "type": "string",
+                    "description": "Defines the maturity level and stability commitment for the resource's API contract (interface, behavior, data models).\n\nThis indicates whether the resource may undergo backward-incompatible changes. It helps consumers understand the risk\nof depending on the resource and whether it's suitable for production use.\n\nNote: This is independent of `visibility` and does not imply availability guarantees or SLAs - it concerns only the API contract stability.\n\nSee [Lifecycle](../index.md#lifecycle) and [Compatibility](../concepts/compatibility.md) for more details.",
+                    "oneOf": [
+                        {
+                            "const": "beta",
+                            "description": "The API contract has no stability guarantees. Breaking changes may occur at any time without notice or deprecation period.\n\nNot recommended for production use unless you can tolerate breaking changes. Suitable for experimentation, early adopters,\nand feedback gathering. Resources of `beta` status MAY be changed or removed at the provider's discretion."
+                        },
+                        {
+                            "const": "active",
+                            "description": "The API contract is stable and recommended for production use.\n\nBreaking changes will only be introduced through proper deprecation cycles or new major versions,\nfollowing versioning and compatibility policies. Consumers can rely on active resources with confidence."
+                        },
+                        {
+                            "const": "deprecated",
+                            "description": "The resource is still functional but scheduled for removal. No new development should depend on it.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (decommissioned/removed) in the future through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
+                        },
+                        {
+                            "const": "sunset",
+                            "description": "The resource has been decommissioned and is no longer available at runtime. This entry exists for historical reference only.\n\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
+                        }
+                    ],
+                    "examples": [
+                        "active"
+                    ]
+                },
+                "disabled": {
+                    "type": "boolean",
+                    "default": false,
+                    "description": "Indicates that this resource is currently not available for consumption at runtime, but could be configured to be so.\nThis can happen either because it has not been setup for use or disabled by an admin / user.\n\nIf the resource is not available in principle for a particular system instance, e.g. due to lack of entitlement, it MUST not be described in the system-instance-aware perspective.\n\nThis property can only reflect the knowledge of the described system instance itself.\nOutside factors for availability can't need to be considered (e.g. network connectivity, middlewares).\n\nA disabled resource MAY skip describing its resource definitions.\n"
+                },
+                "minSystemVersion": {
+                    "type": "string",
+                    "description": "The resource has been introduced in the given [system version](../index.md#system-version).\nThis implies that the resource is only available if the system instance is of at least that system version.\n\nIt MUST follow the [Semantic Versioning 2.0.0](https://semver.org/) standard.",
+                    "x-introduced-in-version": "1.10.0",
+                    "pattern": "^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-((?:0|[1-9]\\d*|\\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\\.(?:0|[1-9]\\d*|\\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\\+([0-9a-zA-Z-]+(?:\\.[0-9a-zA-Z-]+)*))?$",
+                    "examples": [
+                        "1.2.3",
+                        "2024.8.0"
+                    ]
+                },
+                "relatedEntityTypes": {
+                    "type": "array",
+                    "description": "Optional list of related EntityType Resources.\nMUST be a valid reference to an [EntityType Resource](#entity-type) ORD ID.",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(entityType):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                        "x-association-target": [
+                            "#/definitions/EntityType/ordId"
+                        ]
+                    },
+                    "examples": [
+                        [
+                            "sap.odm:entityType:WorkforcePerson:v1"
+                        ]
+                    ]
+                },
+                "definitions": {
+                    "type": "array",
+                    "description": "List of available machine-readable definitions, which describe the resource or capability in detail.\nSee also [Resource Definitions](../index.md#resource-definitions) for more context.\n\nEach definition is to be understood as an alternative description format, describing the same resource / capability.\nAs a consequence the same definition type MUST NOT be provided more than once.\nThe exception is when the same definition type is provided more than once, but with a different `visibility`.\n\nIt is RECOMMENDED to provide the definitions as they enable machine-readable use cases.\nIf the definitions are added or changed, the `version` MUST be incremented.\nAn ORD aggregator MAY only (re)fetch the definitions again when the `version` was incremented.",
+                    "items": {
+                        "$ref": "#/definitions/CapabilityDefinition"
+                    }
+                },
+                "links": {
+                    "type": "array",
+                    "description": "Generic Links with arbitrary meaning and content.",
+                    "items": {
+                        "$ref": "#/definitions/Link"
+                    }
+                },
+                "tags": {
+                    "type": "array",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^[a-zA-Z0-9-_.\\/ ]*$",
+                        "minLength": 1
+                    },
+                    "description": "List of free text style tags.\nNo special characters are allowed except `-`, `_`, `.`, `/` and ` `.\n\nTags that are assigned to a `Package` are inherited to all of the ORD resources it contains.",
                     "examples": [
                         [
                             "storage",
@@ -4098,6 +4659,7 @@
             "type": "object",
             "title": "Capability Definition",
             "x-introduced-in-version": "1.4.0",
+            "x-ums-type": "custom",
             "description": "Link and categorization of a machine-readable capability definition.",
             "properties": {
                 "type": {
@@ -4134,27 +4696,11 @@
                 "mediaType": {
                     "description": "The [Media Type](https://www.iana.org/assignments/media-types/media-types.xhtml) of the definition serialization format.\nA consuming application can use this information to know which file format parser it needs to use.\nFor example, for OpenAPI 3, it's valid to express the same definition in both YAML and JSON.\n\nIf no Media Type is registered for the referenced file,\n`text/plain` MAY be used for arbitrary plain-text and `application/octet-stream` for arbitrary binary data.\n",
                     "type": "string",
-                    "oneOf": [
-                        {
-                            "const": "application/json"
-                        },
-                        {
-                            "const": "application/xml"
-                        },
-                        {
-                            "const": "text/yaml"
-                        },
-                        {
-                            "const": "text/plain",
-                            "description": "For a plain-text format where no other serialization Media Type fits"
-                        },
-                        {
-                            "const": "application/octet-stream",
-                            "description": "For a binary format where no other serialization Media Type fits"
-                        }
-                    ],
+                    "pattern": "^(application|text)\\/[a-zA-Z0-9][a-zA-Z0-9.+\\-]*$",
                     "examples": [
-                        "application/json"
+                        "application/json",
+                        "text/plain",
+                        "application/xml"
                     ]
                 },
                 "url": {
@@ -4186,15 +4732,15 @@
                     "oneOf": [
                         {
                             "const": "public",
-                            "description": "Publicly visible to customers and 3rd parties.\nUsually this includes an contract on the API stability, e.g. the [SAP API Deprecation Policy](https://help.sap.com/viewer/84b35b9c39b247e3ba2a31f02beee46d/Cloud/en-US/5cbfda5a9efe4e97a3e24ddaf7ec5c16.html)."
+                            "description": "Metadata can be discovered and accessed by anyone, including customers, partners, and unauthenticated external parties.\n\nPublic resources typically come with stability guarantees, expressed via versioning and follow formal API lifecycle management. For more details see [Version and Lifecycle](../index.md#version-and-lifecycle) section.\nand follow formal API lifecycle management and deprecation policies.\n\nExample: A REST API that customers use to integrate with your SaaS product."
                         },
                         {
                             "const": "internal",
-                            "description": "Visible to other applications within the same [vendor](#vendor).\nHowever, they are not officially exposed and communicated to customers and 3rd parties.\nThey might not come with the same guarantees on API stability.\n\nInternal resources MUST NOT be made available to consumers without checking the necessary access permissions, e.g., a public API Catalog.\nInternal resources MAY be published through an internal API Catalog if the access permissions are ensured by it."
+                            "description": "Metadata can only be discovered and accessed by vendor internal consumers (e.g. applications or services of the same vendor).\nMUST NOT be made available to external parties or vendor customers.\n\nInternal resources are intended for integration between a vendors own applications and services.\nAPI stability and maturity are explicitly defined via the `releaseStatus` property, which is a separate concern from visibility.\n\nInternal resources MUST NOT be made available without checking the necessary access permissions.\nInternal resources MAY be published through an internal API Catalog if access permissions are ensured by it."
                         },
                         {
                             "const": "private",
-                            "description": "Visible only to the provider application or service, usually within the same system namespace / system type.\n\nPrivate resources MUST NOT be made available to public consumers or consumers outside of the \"private\" scope of the described application."
+                            "description": "Metadata should not be discoverable outside the application / service's own deployment scope (e.g., outside of the provider application or the same system namespace / system type).\nUsed for metadata completeness when describing implementation details or dependencies.\n\nPrivate resources usually have no stability guarantees and can change or be removed at any time.\nThese are typically implementation details not meant for consumption by other services.\n\nExample: Services only used within a microservice architecture or APIs that are only used for the own UIs, not for general consumption.\n\nPrivate resources MUST NOT be made discoverable or accessible outside the application / service's own deployment scope."
                         }
                     ]
                 }
@@ -4209,6 +4755,7 @@
         "IntegrationDependency": {
             "type": "object",
             "title": "Integration Dependency",
+            "x-ums-type": "root",
             "x-introduced-in-version": "1.7.0",
             "description": "An [Integration Dependency](../concepts/integration-dependency) states that the described system (self) can integrate with external systems (integration target) to achieve an integration purpose.\nThe purpose could be to enable a certain feature or integration scenario, but it could also be a mandatory prerequisite for the described system to work.\n\nThe integration dependency includes a list of individual **aspects** that the integration consists of.\nAspects are an \"ingredient\" for the integration scenario (and are logically combined with AND condition).\nEach aspect can express alternatives (OR condition) on what API and event resources can be used to achieve the same outcome.\n\nThe direction of connection establishment, data flow is not directly implied and needs to be inferred from the referenced resources.\n\nIt is not in scope for the Integration Dependency to describe scenarios that external consumers have with the own exposed resources.\nThis would overstep the boundary of self-description.\n\nIf an integration scenario consists of two sides integration with each other, each need to describe its own part in it as an Integration Dependency.\nTherefore, if an integration with multiple types of systems need to be setup, this SHOULD be separated into distinct Integration Dependencies.\n\nAn integration dependency is also not meant to describe a bigger process.\nInstead it focuses on the technical necessaries to create an integration for one particular purpose.\n\nTo learn more about the concept, see [Integration Dependency](../concepts/integration-dependency).",
             "properties": {
@@ -4314,41 +4861,41 @@
                 },
                 "visibility": {
                     "type": "string",
-                    "description": "The visibility states who is allowed to \"see\" the described resource or capability.",
+                    "description": "Defines metadata access control - which categories of consumers are allowed to discover and access the resource and its metadata.\n\nThis controls who can see that the resource exists and retrieve its metadata level information.\nIt does NOT control runtime access to the resource itself - that is managed separately through authentication and authorization mechanisms.\n\nUse this to prevent exposing internal implementation details to inappropriate consumer audiences.",
                     "oneOf": [
                         {
                             "const": "public",
-                            "description": "Publicly visible to customers and 3rd parties.\nUsually this includes an contract on the API stability, e.g. the [SAP API Deprecation Policy](https://help.sap.com/viewer/84b35b9c39b247e3ba2a31f02beee46d/Cloud/en-US/5cbfda5a9efe4e97a3e24ddaf7ec5c16.html)."
+                            "description": "Metadata can be discovered and accessed by anyone, including customers, partners, and unauthenticated external parties.\n\nPublic resources typically come with stability guarantees, expressed via versioning and follow formal API lifecycle management. For more details see [Version and Lifecycle](../index.md#version-and-lifecycle) section.\nand follow formal API lifecycle management and deprecation policies.\n\nExample: A REST API that customers use to integrate with your SaaS product."
                         },
                         {
                             "const": "internal",
-                            "description": "Visible to other applications within the same [vendor](#vendor).\nHowever, they are not officially exposed and communicated to customers and 3rd parties.\nThey might not come with the same guarantees on API stability.\n\nInternal resources MUST NOT be made available to consumers without checking the necessary access permissions, e.g., a public API Catalog.\nInternal resources MAY be published through an internal API Catalog if the access permissions are ensured by it."
+                            "description": "Metadata can only be discovered and accessed by vendor internal consumers (e.g. applications or services of the same vendor).\nMUST NOT be made available to external parties or vendor customers.\n\nInternal resources are intended for integration between a vendors own applications and services.\nAPI stability and maturity are explicitly defined via the `releaseStatus` property, which is a separate concern from visibility.\n\nInternal resources MUST NOT be made available without checking the necessary access permissions.\nInternal resources MAY be published through an internal API Catalog if access permissions are ensured by it."
                         },
                         {
                             "const": "private",
-                            "description": "Visible only to the provider application or service, usually within the same system namespace / system type.\n\nPrivate resources MUST NOT be made available to public consumers or consumers outside of the \"private\" scope of the described application."
+                            "description": "Metadata should not be discoverable outside the application / service's own deployment scope (e.g., outside of the provider application or the same system namespace / system type).\nUsed for metadata completeness when describing implementation details or dependencies.\n\nPrivate resources usually have no stability guarantees and can change or be removed at any time.\nThese are typically implementation details not meant for consumption by other services.\n\nExample: Services only used within a microservice architecture or APIs that are only used for the own UIs, not for general consumption.\n\nPrivate resources MUST NOT be made discoverable or accessible outside the application / service's own deployment scope."
                         }
                     ]
                 },
                 "releaseStatus": {
                     "type": "string",
-                    "description": "The `releaseStatus` specifies the stability of the resource and its external contract.",
+                    "description": "Defines the maturity level and stability commitment for the resource's API contract (interface, behavior, data models).\n\nThis indicates whether the resource may undergo backward-incompatible changes. It helps consumers understand the risk\nof depending on the resource and whether it's suitable for production use.\n\nNote: This is independent of `visibility` and does not imply availability guarantees or SLAs - it concerns only the API contract stability.\n\nSee [Lifecycle](../index.md#lifecycle) and [Compatibility](../concepts/compatibility.md) for more details.",
                     "oneOf": [
                         {
                             "const": "beta",
-                            "description": "The contract for the resource is beta and may not be meant for productive use.\nResources of `beta` status MAY be changed or deleted at the providers discretion."
+                            "description": "The API contract has no stability guarantees. Breaking changes may occur at any time without notice or deprecation period.\n\nNot recommended for production use unless you can tolerate breaking changes. Suitable for experimentation, early adopters,\nand feedback gathering. Resources of `beta` status MAY be changed or removed at the provider's discretion."
                         },
                         {
                             "const": "active",
-                            "description": "Resource is meant for productive use and provides a stable API contract."
+                            "description": "The API contract is stable and recommended for production use.\n\nBreaking changes will only be introduced through proper deprecation cycles or new major versions,\nfollowing versioning and compatibility policies. Consumers can rely on active resources with confidence."
                         },
                         {
                             "const": "deprecated",
-                            "description": "Resource has been deprecated.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (aka. decommissioned / removed) in the future, through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
+                            "description": "The resource is still functional but scheduled for removal. No new development should depend on it.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (decommissioned/removed) in the future through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
                         },
                         {
                             "const": "sunset",
-                            "description": "Resource has been sunset, but is still described.\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
+                            "description": "The resource has been decommissioned and is no longer available at runtime. This entry exists for historical reference only.\n\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
                         }
                     ],
                     "examples": [
@@ -4451,6 +4998,7 @@
             "type": "object",
             "title": "Aspect",
             "x-introduced-in-version": "1.7.0",
+            "x-ums-type": "custom",
             "description": "An (integration) aspect is the constituent part that makes up an Integration Dependency.\n\nEach aspect can list references to resources, which could be owned and defined by the integration target or by the described system itself.\nIn case the reference links to own resources, it is implied that they are to be used by the integration target to fulfill the Integration Dependency.\n\nIf multiple resources are given within an aspect, they are considered alternatives to each other (OR condition).\nIn case an AND condition is needed, multiple aspects need to be added to the Integration Dependency.",
             "properties": {
                 "title": {
@@ -4503,6 +5051,7 @@
             "type": "object",
             "title": "Api Resource Integration Aspect",
             "x-introduced-in-version": "1.7.0",
+            "x-ums-type": "custom",
             "description": "API resource related integration aspect",
             "properties": {
                 "ordId": {
@@ -4522,6 +5071,13 @@
                         "1.2.3",
                         "1.0.0-alpha.1"
                     ]
+                },
+                "subset": {
+                    "type": "array",
+                    "description": "List of individual API operations that are sufficient to achieve the aspect.",
+                    "items": {
+                        "$ref": "#/definitions/ApiResourceIntegrationAspectSubset"
+                    }
                 }
             },
             "additionalProperties": false,
@@ -4533,6 +5089,7 @@
             "type": "object",
             "title": "Event Resource Integration Aspect",
             "x-introduced-in-version": "1.7.0",
+            "x-ums-type": "custom",
             "description": "Event resource related integration aspect",
             "properties": {
                 "ordId": {
@@ -4585,6 +5142,7 @@
             "type": "object",
             "title": "Event Resource Integration Aspect Subset",
             "x-introduced-in-version": "1.7.0",
+            "x-ums-type": "custom",
             "description": "Defines that Event Resource Integration Aspect only requires a subset of the referenced contract.\n\nFor events, this could be a list of the events that need to be subscribed in order to make the integration work.\nThis information helps to narrow down what is really necessary and can help optimize the integration, e.g. by only publishing the events that are really needed.",
             "properties": {
                 "eventType": {
@@ -4600,9 +5158,31 @@
                 "eventType"
             ]
         },
+        "ApiResourceIntegrationAspectSubset": {
+            "type": "object",
+            "title": "API Resource Integration Aspect Subset",
+            "x-introduced-in-version": "1.10.0",
+            "x-ums-type": "custom",
+            "description": "Defines that API Resource Integration Aspect only requires a subset of the referenced contract.\n\nFor APIs, this is a list of the operations or tools that need to be available in order to make the integration work.\nThis information helps to narrow down what is really necessary and can help optimize the integration.",
+            "properties": {
+                "operationId": {
+                    "type": "string",
+                    "description": "The ID of the individual API operation or tool.\n\nThis MUST be an ID that is understood by the used protocol and resource definition format.\nE.g. for OpenAPI this is the `operationId`, for MCP this is the tool `name`.",
+                    "examples": [
+                        "getOrderById",
+                        "createCustomer"
+                    ]
+                }
+            },
+            "additionalProperties": false,
+            "required": [
+                "operationId"
+            ]
+        },
         "Vendor": {
             "type": "object",
             "title": "Vendor",
+            "x-ums-type": "root",
             "description": "The vendor of a product or a package, usually a corporation or a customer / user.\n\nThe vendor of a `Package` is the owner or creator of the content of the package.\nThe vendor of a `Product` is the owner of the product.\n\nIf the resources are created by the customer / user of the described system, `customer:vendor:Customer:` MUST be used as vendor.\n\nBoth have already a [vendor namespace](../index.md#vendor-namespace) within their ORD ID.\nThe `Vendor` entity is giving more details on the vendor namespace.\nFor one vendor namespace there MUST only be exactly one `Vendor` ORD entity describing it.\n\nFor example: The only correct value for a SAP vendor reference is `sap:vendor:SAP:`.",
             "properties": {
                 "ordId": {
@@ -4673,6 +5253,7 @@
             "type": "object",
             "title": "Changelog Entry",
             "description": "A changelog entry can be used to indicate changes.\nUsually they lead to a change of the version number or the release status.",
+            "x-ums-type": "custom",
             "properties": {
                 "version": {
                     "type": "string",
@@ -4684,23 +5265,23 @@
                 },
                 "releaseStatus": {
                     "type": "string",
-                    "description": "The `releaseStatus` specifies the stability of the resource and its external contract.",
+                    "description": "Defines the maturity level and stability commitment for the resource's API contract (interface, behavior, data models).\n\nThis indicates whether the resource may undergo backward-incompatible changes. It helps consumers understand the risk\nof depending on the resource and whether it's suitable for production use.\n\nNote: This is independent of `visibility` and does not imply availability guarantees or SLAs - it concerns only the API contract stability.\n\nSee [Lifecycle](../index.md#lifecycle) and [Compatibility](../concepts/compatibility.md) for more details.",
                     "oneOf": [
                         {
                             "const": "beta",
-                            "description": "The contract for the resource is beta and may not be meant for productive use.\nResources of `beta` status MAY be changed or deleted at the providers discretion."
+                            "description": "The API contract has no stability guarantees. Breaking changes may occur at any time without notice or deprecation period.\n\nNot recommended for production use unless you can tolerate breaking changes. Suitable for experimentation, early adopters,\nand feedback gathering. Resources of `beta` status MAY be changed or removed at the provider's discretion."
                         },
                         {
                             "const": "active",
-                            "description": "Resource is meant for productive use and provides a stable API contract."
+                            "description": "The API contract is stable and recommended for production use.\n\nBreaking changes will only be introduced through proper deprecation cycles or new major versions,\nfollowing versioning and compatibility policies. Consumers can rely on active resources with confidence."
                         },
                         {
                             "const": "deprecated",
-                            "description": "Resource has been deprecated.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (aka. decommissioned / removed) in the future, through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
+                            "description": "The resource is still functional but scheduled for removal. No new development should depend on it.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (decommissioned/removed) in the future through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
                         },
                         {
                             "const": "sunset",
-                            "description": "Resource has been sunset, but is still described.\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
+                            "description": "The resource has been decommissioned and is no longer available at runtime. This entry exists for historical reference only.\n\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
                         }
                     ],
                     "examples": [
@@ -4740,6 +5321,7 @@
             "type": "object",
             "title": "Link",
             "description": "Link that can be attached to packages or Open Resource Discovery resources.\n",
+            "x-ums-type": "custom",
             "properties": {
                 "title": {
                     "type": "string",
@@ -4781,6 +5363,7 @@
         "PackageLink": {
             "type": "object",
             "title": "Package Link",
+            "x-ums-type": "custom",
             "description": "Links with specific semantic meaning that are related to `Package`.\n\nIf a generic [Link](#link) can also be expressed via a Package Link, the latter MUST be chosen.",
             "properties": {
                 "type": {
@@ -4860,6 +5443,7 @@
         "APIEventResourceLink": {
             "type": "object",
             "title": "Api and Event Resource Link",
+            "x-ums-type": "custom",
             "description": "Links with specific semantic meaning that are related to API or event resources.\n\nIf a generic [Link](#link) can also be expressed via an API / Event Resource Link, the latter MUST be chosen.",
             "properties": {
                 "type": {
@@ -4942,6 +5526,7 @@
         "DataProductLink": {
             "type": "object",
             "title": "Data Product Link",
+            "x-ums-type": "custom",
             "description": "Links with specific semantic meaning that are related to Data Product resources.\nIf a generic [Link](#link) can also be expressed via Data Product Link, the latter MUST be chosen.",
             "properties": {
                 "type": {
@@ -5010,6 +5595,7 @@
         "SystemInstance": {
             "type": "object",
             "title": "System Instance",
+            "x-ums-type": "ignore",
             "description": "A [system instance](../index.md#system-instance) is a concrete, running instance of a system type.\nIn a multi-tenant system, it corresponds to a tenant.\nIn a single-tenant system, it corresponds to the [system installation](../index.md#system-deployment) itself.",
             "properties": {
                 "baseUrl": {
@@ -5074,6 +5660,7 @@
             "type": "object",
             "title": "System Type",
             "description": "A [system type](../index.md#system-type) is the abstract type of an application or service, from operational perspective.",
+            "x-ums-type": "ignore",
             "properties": {
                 "systemNamespace": {
                     "type": "string",
@@ -5128,6 +5715,7 @@
             "type": "object",
             "title": "System Version",
             "description": "A [system version](../index.md#system-version) states the design-time version / release of a [system instance](../index.md#system-instance).\nIt provides versioning for operational purposes for the [system type](../index.md#system-type).",
+            "x-ums-type": "ignore",
             "properties": {
                 "version": {
                     "type": "string",
@@ -5185,6 +5773,7 @@
             "type": "object",
             "title": "Metadata Definition Access Strategy",
             "description": "Defines the [access strategy](../../spec-extensions/access-strategies/) for accessing the resource definitions.",
+            "x-ums-type": "custom",
             "properties": {
                 "type": {
                     "type": "string",
@@ -5250,6 +5839,7 @@
             "type": "object",
             "title": "Credential Exchange Strategy",
             "x-feature-status": "alpha",
+            "x-ums-type": "custom",
             "description": "The credential exchange strategy specifies how a set of credentials for a particular usage\nof the APIs in the Consumption Bundle can be obtained.\nUntil a SAP-wide strategy for obtaining such credentials exists and is agreed upon,\nboth LoBs and aggregators (namely Unified Customer Landscape) can define their own strategy specifications.\n\nWhile the actual flow in term of API calls can differ between the different strategies,\nthe end goal would always be the possibility for automatically obtaining credentials for each client\nthat would like to use the APIs from a particular bundle.",
             "properties": {
                 "type": {
@@ -5300,6 +5890,7 @@
             "title": "Labels",
             "type": "object",
             "description": "Generic labels that can be applied to most ORD information.\nThey are defined as an object that may have arbitrary keys.\nThe value of a key is an array of strings.\n\nLabels can be used to attach technical information that cannot be expressed natively in ORD.\nAn ORD aggregator should allow to categorize and query information based on the labels provided.\n\nIf multiple parties rely on the existence of certain label information,\nstandardization through ORD SHOULD be preferred.\n\nAll labels attached to a `Package` will be inherited to the resources they contain.\nDuplicate labels will be merged by the ORD aggregator according to the following rules:\n* Values of the same label key will be merged.\n* Duplicate values of the same label key will be removed.",
+            "x-ums-type": "custom",
             "patternProperties": {
                 "^[a-zA-Z0-9-_.]*$": {
                     "type": "array",
@@ -5321,6 +5912,7 @@
         "GroupType": {
             "title": "Group Type",
             "type": "object",
+            "x-ums-type": "root",
             "description": "A Group Type defines the semantics of [group assignments](#group).\nWhat the Group Type means and how it is to be used correctly SHOULD be described in the `description` (which may include markdown links).\n\nGroup Types can be defined centrally (ownership by authority namespace) or decentrally (defined by application / service itself).\n\nTo learn more about the concept, see [Group Concept Documentation](../concepts/grouping-and-bundling#groups).",
             "x-introduced-in-version": "1.9.0",
             "properties": {
@@ -5350,6 +5942,23 @@
                         "SAP S/4HANA Cloud, our next generation cloud ERP suite designed for\nin-memory computing, acts as a digital core, connecting your\nenterprise with people, business networks, the Internet of Things,\nBig Data, and more.\n"
                     ]
                 },
+                "labels": {
+                    "$ref": "#/definitions/Labels"
+                },
+                "correlationIds": {
+                    "type": "array",
+                    "description": "Correlation IDs can be used to create a reference to related data in other repositories (especially to the system of record).\n\nThey express an \"identity\" / \"equals\" / \"mappable\" relationship to the target ID.\n\nIf a \"part of\" relationship needs to be expressed, use the `partOfGroups` assignment instead.\n\nMUST be a valid [Correlation ID](../index.md#correlation-id).",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-\\/]+):([a-zA-Z0-9._\\-\\/]+)$",
+                        "maxLength": 255
+                    },
+                    "examples": [
+                        [
+                            "sap.s4:communicationScenario:SAP_COM_0008"
+                        ]
+                    ]
+                },
                 "partOfGroupTypes": {
                     "type": "array",
                     "items": {
@@ -5377,6 +5986,7 @@
         "Group": {
             "title": "Group",
             "type": "object",
+            "x-ums-type": "root",
             "description": "Group (instance) that resources can be assigned to.\n\nGroups are a lightweight custom taxonomy concept.\nThey express a \"part of\" relationship to the chosen group concept.\nIf an \"identity / equals\" relationship needs to be expressed, use the `correlationIds` instead.\n\nTo learn more about the concept, see [Group Concept Documentation](../concepts/grouping-and-bundling#groups).",
             "x-introduced-in-version": "1.9.0",
             "properties": {
@@ -5417,6 +6027,23 @@
                         "SAP S/4HANA Cloud, our next generation cloud ERP suite designed for\nin-memory computing, acts as a digital core, connecting your\nenterprise with people, business networks, the Internet of Things,\nBig Data, and more.\n"
                     ]
                 },
+                "labels": {
+                    "$ref": "#/definitions/Labels"
+                },
+                "correlationIds": {
+                    "type": "array",
+                    "description": "Correlation IDs can be used to create a reference to related data in other repositories (especially to the system of record).\n\nThey express an \"identity\" / \"equals\" / \"mappable\" relationship to the target ID.\n\nIf a \"part of\" relationship needs to be expressed, use the `partOfGroups` assignment instead.\n\nMUST be a valid [Correlation ID](../index.md#correlation-id).",
+                    "items": {
+                        "type": "string",
+                        "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):([a-zA-Z0-9._\\-\\/]+):([a-zA-Z0-9._\\-\\/]+)$",
+                        "maxLength": 255
+                    },
+                    "examples": [
+                        [
+                            "sap.s4:communicationScenario:SAP_COM_0008"
+                        ]
+                    ]
+                },
                 "partOfGroups": {
                     "type": "array",
                     "items": {
@@ -5449,6 +6076,7 @@
             "type": "object",
             "description": "Generic documentation labels that can be applied to most ORD information.\nThey are defined as an object that may have arbitrary keys.\nThe value of a key is an array of [CommonMark](https://spec.commonmark.org/) (Markdown) text.\n\nDocumentation Labels can be used to attach human readable documentation that cannot be expressed natively in ORD.\nA documentation tool (like an API Catalog) can use the documentation labels to provide generic documentation \"snippets\".\nDue to the given structure they can be displayed e.g. as tables.\n\nThe key of the documentation Label is plain-text (MUST not contain line breaks) and denotes the subject matter that is described.\nThe values (multiple can be provided for the same key) are [CommonMark](https://spec.commonmark.org/) (Markdown) text\nwhich describes the subject matter or lists options for the key.\n\nIn contrast to regular labels, documentation labels are not meant to be used to categorize or query information.",
             "x-introduced-in-version": "1.1.0",
+            "x-ums-type": "custom",
             "patternProperties": {
                 "^.*$": {
                     "type": "array",
@@ -5469,6 +6097,7 @@
         "Extensible": {
             "title": "Extensible",
             "type": "object",
+            "x-ums-type": "embedded",
             "description": "Contains information about the extensibility of this resource.\n\nIf applicable, a description and further resources about extending this resource are provided.",
             "properties": {
                 "supported": {
@@ -5504,6 +6133,7 @@
             "title": "Entity Type Mapping",
             "type": "object",
             "x-introduced-in-version": "1.6.0",
+            "x-ums-type": "custom",
             "description": "An API or Event resource may optionally define its `entityTypeMappings`.\nThis is used to map and correlate the API models to the underlying, conceptual **entity types**.\n\nIf the mapping from API resource to entity types is not defined,\ncertain use-cases that rely on this explicit connection will not be possible.\n\nThis mapping is meant to be rather fine granular.\nTherefore, the mapping needs to be done on basis of one of the referenced resource definitions,\nas only there we know the details and the actual contents of the API Model of the API resource.\n\nFor the various resource definition formats the selection of API models may need to be expressed differently.\nAs a consequence, there are different types of selectors that are specialized toward certain resource definition formats.\n\nThe target of the mapping is a correlation to an entity type via a [Correlation ID](../index.md#correlation-id)\nor to an [ORD ID](../index.md#ord-id) of an entity type.\nIt is assumed that the entity types are described in more detail or on a different abstraction level via metadata.\nWhen the correlation ID is used, an ORD consumer may need to know how to access the entity type metadata through conventions.\nThis can be determined either by the namespace of the correlation ID,\nor through a defined and known `implementationStandard` that can resolve the `localId` fragment of the correlation ID .\n\nAt SAP, the metadata about entity types could be retrieved via the CSN_EXPOSURE service.\nTo indicate this, the service needs to be implemented and described in ORD with `implementationStandard` set to `sap:csn-exposure:v1`).\n\nODM 2.0 relies on the entity type mappings and uses the the mapping to express the relationship of an API to the\ncorresponding ODM entity. ORD consumers like SAP Business Accelerator Hub consume the mapping to make the relationships navigate-able for customers.",
             "properties": {
                 "apiModelSelectors": {
@@ -5541,9 +6171,74 @@
                 "entityTypeTargets"
             ]
         },
+        "ApiCompatibility": {
+            "title": "API Compatibility",
+            "x-introduced-in-version": "1.13.0",
+            "x-ums-type": "embedded",
+            "type": "object",
+            "description": "Describes the compatibility of the API with other APIs. This can be used to express that an API is compatible with another API version.",
+            "properties": {
+                "ordId": {
+                    "type": "string",
+                    "description": "ORD ID of the APIResource that serves as contract that this resource is compatible with.\n\nMUST be a valid reference to an (usually external) [API Resource](#api-resource) ORD ID.",
+                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(apiResource):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                    "maxLength": 255,
+                    "examples": [
+                        "sap.s4:apiResource:API_BILL_OF_MATERIAL_SRV:v1"
+                    ]
+                },
+                "maxVersion": {
+                    "type": "string",
+                    "description": "Specifies the maximum version of the interface contract that this resource is compatible with. This is the version, that the resource fully implements and supports.\n\nEven if the interface contract evolves compatible, this resource will not be compatible with versions beyond the specified one. It is important to consider, given the example of an API version 1.0, that has the fields A and B.\nBeing compatible with version 1.0 means to have exactly the fields A and B and potential tenant specific extensions in a dedicated namespace.\nIf an API contract changes to version 1.1 compatible by adding field C, the API declaring compatibility towards 1.0, will miss field C. Only if adopting the contract of 1.1 with having fields A, B, and C, such an API is also\ncompatible with version 1.1 of the contract. However, a client relying on version 1.0 of the contract, can still work with the API being compatible with version 1.1 of the contract.\n\nFollowing the [Semantic Versioning 2.0.0](https://semver.org/) standard, patch versions (x.y.Z) must not have impact on the schema/contract. Therefore, the maxVersion are only the major.minor parts of a semantic version.",
+                    "pattern": "^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)$",
+                    "examples": [
+                        "1.2",
+                        "2.0"
+                    ]
+                }
+            },
+            "additionalProperties": false,
+            "required": [
+                "ordId",
+                "maxVersion"
+            ]
+        },
+        "EventCompatibility": {
+            "title": "Event Compatibility",
+            "x-introduced-in-version": "1.13.0",
+            "x-ums-type": "embedded",
+            "type": "object",
+            "description": "Describes the compatibility of the Event with other Events. This can be used to express that an Event is compatible with another Event version.",
+            "properties": {
+                "ordId": {
+                    "type": "string",
+                    "description": "ORD ID of the EventResource that serves as contract that this resource is compatible with.\n\nMUST be a valid reference to an (usually external) [Event Resource](#event-resource) ORD ID.",
+                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(eventResource):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                    "maxLength": 255,
+                    "examples": [
+                        "sap.s4:eventResource:BillofMaterialEvents:v1"
+                    ]
+                },
+                "maxVersion": {
+                    "type": "string",
+                    "description": "Specifies the maximum version of the interface contract that this resource is compatible with. This is the version, that the resource fully implements and supports.\n\nEven if the interface contract evolves compatible, this resource will not be compatible with versions beyond the specified one. It is important to consider, given the example of an event version 1.0, that has the fields A and B. Being compatible with version 1.0 means to have exactly the fields A and B and potential tenant specific extensions in a dedicated namespace.\nIf an event contract changes to version 1.1 compatible by adding field C, the event declaring compatibility towards 1.0, will miss field C. Only if adopting the contract of 1.1 with having fields A, B, and C, such an event is also\ncompatible with version 1.1 of the contract. However, a client relying on version 1.0 of the contract, can still work with the event being compatible with version 1.1 of the contract.\n\nFollowing the [Semantic Versioning 2.0.0](https://semver.org/) standard, patch versions (x.y.Z) must not have impact on the schema/contract. Therefore, the maxVersion are only the major.minor parts of a semantic version.",
+                    "pattern": "^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)$",
+                    "examples": [
+                        "1.2",
+                        "2.0"
+                    ]
+                }
+            },
+            "additionalProperties": false,
+            "required": [
+                "ordId",
+                "maxVersion"
+            ]
+        },
         "ApiModelSelectorOData": {
             "title": "Api Model Selector (Odata)",
             "x-introduced-in-version": "1.6.0",
+            "x-ums-type": "custom",
             "type": "object",
             "description": "API Model Selector for OData, using entity set names for the selection.\n\nMUST only be used if the API Resource provides an API Resource Definition of type `edmx`.",
             "properties": {
@@ -5578,6 +6273,7 @@
         "ApiModelSelectorJsonPointer": {
             "title": "Api Model Selector (Json Pointer)",
             "x-introduced-in-version": "1.6.0",
+            "x-ums-type": "custom",
             "type": "object",
             "description": "Generic API Model Selector for JSON / YAML based resource definitions.\nIt uses a [JSON Pointer](https://datatracker.ietf.org/doc/html/rfc6901) that points to the\nentity type description within the resource definition.\n\nThe JSON Pointer always to refer to the structure of the document as originally provided, before further post-processing like resolving $ref properties.\n\nMUST only be used if the API Resource provides an API Resource Definition of media type `application/json` or `text/yaml`.",
             "properties": {
@@ -5611,9 +6307,35 @@
                 }
             ]
         },
+        "ExposedApiResourcesTarget": {
+            "title": "Exposed API Resource",
+            "x-introduced-in-version": "1.14.0",
+            "x-ums-type": "embedded",
+            "type": "object",
+            "description": "Reference to an API Resource that exposes the functionality of an agent.\n\nThis is a complex object to allow additional properties / selections to be attached in the future.",
+            "properties": {
+                "ordId": {
+                    "type": "string",
+                    "description": "The API Resource ORD ID that this reference points to.\n\nMUST be a valid reference to an [API Resource](#api-resource) ORD ID.",
+                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(apiResource):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*)$",
+                    "maxLength": 255,
+                    "examples": [
+                        "sap.foo:apiResource:DisputeResolutionAgent:v1"
+                    ],
+                    "x-association-target": [
+                        "#/definitions/ApiResource/ordId"
+                    ]
+                }
+            },
+            "required": [
+                "ordId"
+            ],
+            "additionalProperties": false
+        },
         "EntityTypeOrdIdTarget": {
-            "title": "Entity Type Target (Ord Id)",
+            "title": "Entity Type Target (ORD ID)",
             "x-introduced-in-version": "1.6.0",
+            "x-ums-type": "custom",
             "type": "object",
             "description": "Define which entity type is the target of an entity type mapping\n\nEntity types can be referenced using a [ORD ID](../index.md#ord-id) of an entity type.",
             "properties": {
@@ -5640,6 +6362,7 @@
             "type": "object",
             "description": "Define which entity type is the target of an entity type mapping\n\nEntity types can be referenced using a [Correlation ID](../index.md#correlation-id).",
             "x-introduced-in-version": "1.6.0",
+            "x-ums-type": "custom",
             "properties": {
                 "correlationId": {
                     "type": "string",
@@ -5658,6 +6381,7 @@
         "RelatedEntityType": {
             "title": "Related Entity Type",
             "x-introduced-in-version": "1.9.0",
+            "x-ums-type": "embedded",
             "type": "object",
             "description": "Defines the relation between Entity Types (via its ORD ID).",
             "properties": {
@@ -5703,6 +6427,7 @@
             "type": "object",
             "description": "Defines which Entity Type is exposed through  (via its ORD ID).",
             "x-introduced-in-version": "1.11.0",
+            "x-ums-type": "embedded",
             "properties": {
                 "ordId": {
                     "type": "string",
@@ -5725,12 +6450,13 @@
         "Tombstone": {
             "type": "object",
             "title": "Tombstone",
+            "x-ums-type": "ignore",
             "description": "A tombstone indicates that a previously published ORD resource or taxonomy has been removed / decommissioned / archived.\nThis MUST be indicated explicitly, so ORD aggregators and consumers can learn about the removal.\n\nExactly one of the IDs MUST be provided to state which ORD resource or taxonomy item the Tombstone addresses.\n\nThe tombstone MUST be kept sufficiently long (at least 31 days) so that all ORD aggregators can learn about the tombstone.",
             "properties": {
                 "ordId": {
                     "type": "string",
                     "description": "[ORD ID](../index.md#ord-id) of the ORD resource/taxonomy that has been removed.",
-                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(package|consumptionBundle|product|vendor|apiResource|eventResource|capability|entityType|integrationDependency|dataProduct):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*|)?$",
+                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(package|consumptionBundle|product|vendor|apiResource|eventResource|capability|entityType|integrationDependency|dataProduct|agent):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*|)?$",
                     "maxLength": 255,
                     "examples": [
                         "sap.xref:package:SomePackage:v1"
@@ -5745,7 +6471,8 @@
                         "#/definitions/Capability/ordId",
                         "#/definitions/EntityType/ordId",
                         "#/definitions/IntegrationDependency/ordId",
-                        "#/definitions/DataProduct/ordId"
+                        "#/definitions/DataProduct/ordId",
+                        "#/definitions/Agent/ordId"
                     ]
                 },
                 "groupId": {
@@ -5805,12 +6532,13 @@
         "OrdResource": {
             "type": "object",
             "title": "Ord Resource (abstract)",
+            "x-ums-type": "root",
             "description": "Abstract definition of shared properties across ORD Resources.",
             "properties": {
                 "ordId": {
                     "type": "string",
                     "description": "The ORD ID is a stable, globally unique ID for ORD resources or taxonomy.\n\nIt MUST be a valid [ORD ID](../index.md#ord-id) of the appropriate ORD type.",
-                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(apiResource|eventResource|capability|dataProduct):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*|)$",
+                    "pattern": "^([a-z0-9]+(?:[.][a-z0-9]+)*):(apiResource|eventResource|capability|dataProduct|agent):([a-zA-Z0-9._\\-]+):(v0|v[1-9][0-9]*|)$",
                     "maxLength": 255,
                     "examples": []
                 },
@@ -5893,41 +6621,41 @@
                 },
                 "visibility": {
                     "type": "string",
-                    "description": "The visibility states who is allowed to \"see\" the described resource or capability.",
+                    "description": "Defines metadata access control - which categories of consumers are allowed to discover and access the resource and its metadata.\n\nThis controls who can see that the resource exists and retrieve its metadata level information.\nIt does NOT control runtime access to the resource itself - that is managed separately through authentication and authorization mechanisms.\n\nUse this to prevent exposing internal implementation details to inappropriate consumer audiences.",
                     "oneOf": [
                         {
                             "const": "public",
-                            "description": "Publicly visible to customers and 3rd parties.\nUsually this includes an contract on the API stability, e.g. the [SAP API Deprecation Policy](https://help.sap.com/viewer/84b35b9c39b247e3ba2a31f02beee46d/Cloud/en-US/5cbfda5a9efe4e97a3e24ddaf7ec5c16.html)."
+                            "description": "Metadata can be discovered and accessed by anyone, including customers, partners, and unauthenticated external parties.\n\nPublic resources typically come with stability guarantees, expressed via versioning and follow formal API lifecycle management. For more details see [Version and Lifecycle](../index.md#version-and-lifecycle) section.\nand follow formal API lifecycle management and deprecation policies.\n\nExample: A REST API that customers use to integrate with your SaaS product."
                         },
                         {
                             "const": "internal",
-                            "description": "Visible to other applications within the same [vendor](#vendor).\nHowever, they are not officially exposed and communicated to customers and 3rd parties.\nThey might not come with the same guarantees on API stability.\n\nInternal resources MUST NOT be made available to consumers without checking the necessary access permissions, e.g., a public API Catalog.\nInternal resources MAY be published through an internal API Catalog if the access permissions are ensured by it."
+                            "description": "Metadata can only be discovered and accessed by vendor internal consumers (e.g. applications or services of the same vendor).\nMUST NOT be made available to external parties or vendor customers.\n\nInternal resources are intended for integration between a vendors own applications and services.\nAPI stability and maturity are explicitly defined via the `releaseStatus` property, which is a separate concern from visibility.\n\nInternal resources MUST NOT be made available without checking the necessary access permissions.\nInternal resources MAY be published through an internal API Catalog if access permissions are ensured by it."
                         },
                         {
                             "const": "private",
-                            "description": "Visible only to the provider application or service, usually within the same system namespace / system type.\n\nPrivate resources MUST NOT be made available to public consumers or consumers outside of the \"private\" scope of the described application."
+                            "description": "Metadata should not be discoverable outside the application / service's own deployment scope (e.g., outside of the provider application or the same system namespace / system type).\nUsed for metadata completeness when describing implementation details or dependencies.\n\nPrivate resources usually have no stability guarantees and can change or be removed at any time.\nThese are typically implementation details not meant for consumption by other services.\n\nExample: Services only used within a microservice architecture or APIs that are only used for the own UIs, not for general consumption.\n\nPrivate resources MUST NOT be made discoverable or accessible outside the application / service's own deployment scope."
                         }
                     ]
                 },
                 "releaseStatus": {
                     "type": "string",
-                    "description": "The `releaseStatus` specifies the stability of the resource and its external contract.",
+                    "description": "Defines the maturity level and stability commitment for the resource's API contract (interface, behavior, data models).\n\nThis indicates whether the resource may undergo backward-incompatible changes. It helps consumers understand the risk\nof depending on the resource and whether it's suitable for production use.\n\nNote: This is independent of `visibility` and does not imply availability guarantees or SLAs - it concerns only the API contract stability.\n\nSee [Lifecycle](../index.md#lifecycle) and [Compatibility](../concepts/compatibility.md) for more details.",
                     "oneOf": [
                         {
                             "const": "beta",
-                            "description": "The contract for the resource is beta and may not be meant for productive use.\nResources of `beta` status MAY be changed or deleted at the providers discretion."
+                            "description": "The API contract has no stability guarantees. Breaking changes may occur at any time without notice or deprecation period.\n\nNot recommended for production use unless you can tolerate breaking changes. Suitable for experimentation, early adopters,\nand feedback gathering. Resources of `beta` status MAY be changed or removed at the provider's discretion."
                         },
                         {
                             "const": "active",
-                            "description": "Resource is meant for productive use and provides a stable API contract."
+                            "description": "The API contract is stable and recommended for production use.\n\nBreaking changes will only be introduced through proper deprecation cycles or new major versions,\nfollowing versioning and compatibility policies. Consumers can rely on active resources with confidence."
                         },
                         {
                             "const": "deprecated",
-                            "description": "Resource has been deprecated.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (aka. decommissioned / removed) in the future, through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
+                            "description": "The resource is still functional but scheduled for removal. No new development should depend on it.\n\nIf the `releaseStatus` is set to `deprecated`, the `deprecationDate` SHOULD be provided.\n\nIf successor resources exist, they MUST be referenced through `successors`.\n\nA deprecated resource MAY be sunset (decommissioned/removed) in the future through setting a `Tombstone`.\nOnce the resource is sunset, its description MAY be removed from ORD, but could also be kept with `releaseStatus` set to `sunset`."
                         },
                         {
                             "const": "sunset",
-                            "description": "Resource has been sunset, but is still described.\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
+                            "description": "The resource has been decommissioned and is no longer available at runtime. This entry exists for historical reference only.\n\nIf the status is set to `sunset`, a `Tombstone` MUST be set as well and a `sunsetDate` MUST be provided."
                         }
                     ],
                     "examples": [