@open-resource-discovery/specification 1.10.0 → 1.10.1

package/static/spec-v1/interfaces/Document.annotated.schema.json

@@ -2,6 +2,7 @@
   "description": "The [ORD Document](../index.md#ord-document) object serves as a wrapper for the **ORD resources** and **ORD taxonomy** and adds further top-level information\nthat are specific to the document/the service it describes.\n\nThe constraints and considerations on [ORD Documents](../index.md#ord-document) MUST be followed.",
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://open-resource-discovery.github.io/specification/spec-v1/interfaces/Document.schema.json#",
+  "title": "ORD Document",
   "x-property-order": [
     "Document",
     "ApiResource",
@@ -22,6 +23,7 @@
     "Package": {
       "type": "object",
       "title": "Package",
+      "x-ums-type": "root",
       "description": "A [**Package**](../../details/articles/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](../../details/articles/grouping-and-bundling#package).",
       "properties": {
         "ordId": {
@@ -36,7 +38,7 @@
         "localId": {
           "type": "string",
           "x-introduced-in-version": "1.2.1",
-          "description": "Local ID, as known by the described system.\n\nThis can be the `<resourceName>` fragment in the ORD ID. In this case, make sure it fits the length limits of the ORD ID. It might also be different if e.g. localIds have incompatible charset restrictions.",
+          "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",
@@ -177,7 +179,7 @@
         },
         "partOfProducts": {
           "type": "array",
-          "description": "List of products this resource is 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.",
+          "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]+)*):(product):([a-zA-Z0-9._\\-]+):()$",
@@ -420,6 +422,7 @@
     "ConsumptionBundle": {
       "type": "object",
       "title": "Consumption Bundle",
+      "x-ums-type": "root",
       "description": "A [**Consumption Bundle**](../../details/articles/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](../../details/articles/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](../../details/articles/grouping-and-bundling#consumption-bundle).",
       "properties": {
         "ordId": {
@@ -434,7 +437,7 @@
         "localId": {
           "type": "string",
           "x-introduced-in-version": "1.2.1",
-          "description": "Local ID, as known by the described system.\n\nThis can be the `<resourceName>` fragment in the ORD ID. In this case, make sure it fits the length limits of the ORD ID. It might also be different if e.g. localIds have incompatible charset restrictions.",
+          "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",
@@ -570,6 +573,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": {
@@ -598,6 +602,8 @@
     "ApiResource": {
       "type": "object",
       "title": "API Resource",
+      "x-ums-type": "root",
+      "x-implements": "#/definitions/OrdResource",
       "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": {
@@ -612,7 +618,7 @@
         "localId": {
           "type": "string",
           "x-introduced-in-version": "1.2.1",
-          "description": "Local ID, as known by the described system.\n\nThis can be the `<resourceName>` fragment in the ORD ID. In this case, make sure it fits the length limits of the ORD ID. It might also be different if e.g. localIds have incompatible charset restrictions.",
+          "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": [
             "API_BILL_OF_MATERIAL_SRV"
@@ -664,6 +670,12 @@
           "x-association-target": [
             "#/definitions/Package/ordId"
           ],
+          "x-reverse-relationship": {
+            "propertyName": "apiResources",
+            "description": "The API resources that are part the given Package.",
+            "min": 0,
+            "max": "*"
+          },
           "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": [
@@ -679,6 +691,12 @@
               "#/definitions/Group/groupId"
             ]
           },
+          "x-reverse-relationship": {
+            "propertyName": "apiResourceMembers",
+            "description": "The API resources that are part the given Group.",
+            "min": 0,
+            "max": "*"
+          },
           "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."
         },
         "partOfConsumptionBundles": {
@@ -709,7 +727,7 @@
         },
         "partOfProducts": {
           "type": "array",
-          "description": "List of products this resource is 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.",
+          "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]+)*):(product):([a-zA-Z0-9._\\-]+):()$",
@@ -932,7 +950,7 @@
           "oneOf": [
             {
               "const": "sap:ord-document-api:v1",
-              "description": "API follows the Open Resource Discovery v1 [Document API](../index.md#ord-document-api) contract."
+              "description": "API follows the Open Resource Discovery v1 [Document API](../index.md#ord-provider-api) contract."
             },
             {
               "const": "cff:open-service-broker:v2",
@@ -1375,6 +1393,8 @@
     "EventResource": {
       "type": "object",
       "title": "Event Resource",
+      "x-ums-type": "root",
+      "x-implements": "#/definitions/OrdResource",
       "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": {
@@ -1390,7 +1410,7 @@
         "localId": {
           "type": "string",
           "x-introduced-in-version": "1.2.1",
-          "description": "Local ID, as known by the described system.\n\nThis can be the `<resourceName>` fragment in the ORD ID. In this case, make sure it fits the length limits of the ORD ID. It might also be different if e.g. localIds have incompatible charset restrictions.",
+          "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": [
             "BusinessEvents_SubscriptionEvents"
@@ -1443,6 +1463,12 @@
           "x-association-target": [
             "#/definitions/Package/ordId"
           ],
+          "x-reverse-relationship": {
+            "propertyName": "eventResources",
+            "description": "The event resources that are part the given Package.",
+            "min": 0,
+            "max": "*"
+          },
           "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": [
@@ -1458,6 +1484,10 @@
               "#/definitions/Group/groupId"
             ]
           },
+          "x-reverse-relationship": {
+            "propertyName": "eventResourceMembers",
+            "description": "The event resources that are part the given Group."
+          },
           "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."
         },
         "partOfConsumptionBundles": {
@@ -1488,7 +1518,7 @@
         },
         "partOfProducts": {
           "type": "array",
-          "description": "List of products this resource is 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.",
+          "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]+)*):(product):([a-zA-Z0-9._\\-]+):()$",
@@ -1984,6 +2014,7 @@
     "EntityType": {
       "type": "object",
       "title": "Entity Type",
+      "x-ums-type": "root",
       "description": "An [**Entity Type**](../../details/articles/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](../../details/articles/grouping-and-bundling#entity-type).",
       "x-introduced-in-version": "1.8.0",
       "properties": {
@@ -2001,7 +2032,7 @@
         "localId": {
           "type": "string",
           "x-introduced-in-version": "1.2.1",
-          "description": "Local ID, as known by the described system.\n\nThis can be the `<resourceName>` fragment in the ORD ID. In this case, make sure it fits the length limits of the ORD ID. It might also be different if e.g. localIds have incompatible charset restrictions.",
+          "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": [
             "BusinessPartner",
@@ -2067,6 +2098,12 @@
           "x-association-target": [
             "#/definitions/Package/ordId"
           ],
+          "x-reverse-relationship": {
+            "propertyName": "entityTypes",
+            "description": "The entity types that are part the given Package.",
+            "min": 0,
+            "max": "*"
+          },
           "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": [
@@ -2082,11 +2119,15 @@
               "#/definitions/Group/groupId"
             ]
           },
+          "x-reverse-relationship": {
+            "propertyName": "entityTypeMembers",
+            "description": "The entity types that are part the given Group."
+          },
           "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."
         },
         "partOfProducts": {
           "type": "array",
-          "description": "List of products this resource is 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.",
+          "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]+)*):(product):([a-zA-Z0-9._\\-]+):()$",
@@ -2353,7 +2394,9 @@
     "DataProduct": {
       "type": "object",
       "title": "Data Product",
+      "x-ums-type": "root",
       "x-introduced-in-version": "1.8.0",
+      "x-implements": "#/definitions/OrdResource",
       "description": "A [Data Product](../../details/articles/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 - Beta Status](../../details/articles/data-product#beta-status).",
       "properties": {
         "ordId": {
@@ -2368,7 +2411,7 @@
         "localId": {
           "type": "string",
           "x-introduced-in-version": "1.2.1",
-          "description": "Local ID, as known by the described system.\n\nThis can be the `<resourceName>` fragment in the ORD ID. In this case, make sure it fits the length limits of the ORD ID. It might also be different if e.g. localIds have incompatible charset restrictions.",
+          "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": [
             "CustomerOrder"
@@ -2421,6 +2464,12 @@
           "x-association-target": [
             "#/definitions/Package/ordId"
           ],
+          "x-reverse-relationship": {
+            "propertyName": "dataProducts",
+            "description": "The data products that are part the given Package.",
+            "min": 0,
+            "max": "*"
+          },
           "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": [
@@ -2428,7 +2477,6 @@
           ]
         },
         "partOfGroups": {
-          "x-feature-status": "beta",
           "type": "array",
           "items": {
             "type": "string",
@@ -2437,7 +2485,30 @@
               "#/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."
+          "x-reverse-relationship": {
+            "propertyName": "dataProductMembers",
+            "description": "The data products that are part the given Group."
+          },
+          "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.",
+          "x-feature-status": "beta"
+        },
+        "partOfProducts": {
+          "type": "array",
+          "description": "List of products this Data Product is a part of or is related to, its e.g. data source systems.\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]+)*):(product):([a-zA-Z0-9._\\-]+):()$",
+            "maxLength": 255,
+            "x-association-target": [
+              "#/definitions/Product/ordId"
+            ]
+          },
+          "minItems": 0,
+          "examples": [
+            [
+              "sap:product:S4HANA_OD:"
+            ]
+          ]
         },
         "version": {
           "type": "string",
@@ -2638,6 +2709,12 @@
               "#/definitions/EntityType/ordId"
             ]
           },
+          "x-reverse-relationship": {
+            "propertyName": "dataProducts",
+            "description": "Data Products associated to the Entity Type.",
+            "min": 0,
+            "max": "*"
+          },
           "examples": [
             [
               "sap.odm:entityType:CustomerOrder:v1",
@@ -3006,6 +3083,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": {
@@ -3029,6 +3107,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": {
@@ -3055,6 +3134,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",
@@ -3185,6 +3265,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": {
@@ -3277,6 +3358,7 @@
     "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": {
@@ -3386,7 +3468,9 @@
     "Capability": {
       "type": "object",
       "title": "Capability",
+      "x-ums-type": "root",
       "x-introduced-in-version": "1.4.0",
+      "x-implements": "#/definitions/OrdResource",
       "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": {
@@ -3401,7 +3485,7 @@
         "localId": {
           "type": "string",
           "x-introduced-in-version": "1.2.1",
-          "description": "Local ID, as known by the described system.\n\nThis can be the `<resourceName>` fragment in the ORD ID. In this case, make sure it fits the length limits of the ORD ID. It might also be different if e.g. localIds have incompatible charset restrictions.",
+          "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",
@@ -3480,6 +3564,12 @@
           "x-association-target": [
             "#/definitions/Package/ordId"
           ],
+          "x-reverse-relationship": {
+            "propertyName": "capabilities",
+            "description": "The capabilities that are part the given Package.",
+            "min": 0,
+            "max": "*"
+          },
           "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": [
@@ -3495,6 +3585,10 @@
               "#/definitions/Group/groupId"
             ]
           },
+          "x-reverse-relationship": {
+            "propertyName": "capabilityMembers",
+            "description": "The Capabilities that are part the given Group."
+          },
           "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": {
@@ -3573,6 +3667,12 @@
               "#/definitions/EntityType/ordId"
             ]
           },
+          "x-reverse-relationship": {
+            "propertyName": "capabilities",
+            "description": "Capabilities associated to the Entity Type.",
+            "min": 0,
+            "max": "*"
+          },
           "examples": [
             [
               "sap.odm:entityType:WorkforcePerson:v1"
@@ -3643,6 +3743,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": {
@@ -3731,6 +3832,7 @@
     "IntegrationDependency": {
       "type": "object",
       "title": "Integration Dependency",
+      "x-ums-type": "root",
       "x-introduced-in-version": "1.7.0",
       "description": "An [Integration Dependency](../../details/articles/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](../../details/articles/integration-dependency).",
       "properties": {
@@ -3746,7 +3848,7 @@
         "localId": {
           "type": "string",
           "x-introduced-in-version": "1.2.1",
-          "description": "Local ID, as known by the described system.\n\nThis can be the `<resourceName>` fragment in the ORD ID. In this case, make sure it fits the length limits of the ORD ID. It might also be different if e.g. localIds have incompatible charset restrictions.",
+          "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",
@@ -3799,6 +3901,12 @@
           "x-association-target": [
             "#/definitions/Package/ordId"
           ],
+          "x-reverse-relationship": {
+            "propertyName": "integrationDependencies",
+            "description": "The integration dependencies that are part the given Package.",
+            "min": 0,
+            "max": "*"
+          },
           "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": [
@@ -3814,6 +3922,10 @@
               "#/definitions/Group/groupId"
             ]
           },
+          "x-reverse-relationship": {
+            "propertyName": "integrationDependencyMembers",
+            "description": "The Integration Dependencies that are part the given Group."
+          },
           "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": {
@@ -3971,6 +4083,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": {
@@ -4023,6 +4136,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": {
@@ -4053,6 +4167,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": {
@@ -4105,6 +4220,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": {
@@ -4123,6 +4239,7 @@
     "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": {
@@ -4195,6 +4312,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",
@@ -4258,6 +4376,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",
@@ -4299,6 +4418,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": {
@@ -4373,6 +4493,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": {
@@ -4450,6 +4571,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": {
@@ -4513,6 +4635,7 @@
     "SystemInstance": {
       "type": "object",
       "title": "System Instance",
+      "x-ums-type": "ignore",
       "description": "A [system instance](../index.md#def-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#def-system-deployment) itself.",
       "properties": {
         "baseUrl": {
@@ -4579,6 +4702,7 @@
       "type": "object",
       "title": "System Type",
       "description": "A [system type](../index.md#def-system-type) is the abstract type of an application or service, from operational perspective.",
+      "x-ums-type": "ignore",
       "properties": {
         "systemNamespace": {
           "type": "string",
@@ -4634,6 +4758,7 @@
       "type": "object",
       "title": "System Version",
       "description": "A [system version](../index.md#def-system-version) states the design-time version / release of a [system instance](../index.md#def-system-instance).\nIt provides versioning for operational purposes for the [system type](../index.md#def-system-type).",
+      "x-ums-type": "ignore",
       "properties": {
         "version": {
           "type": "string",
@@ -4693,6 +4818,7 @@
       "type": "object",
       "title": "Access Strategy",
       "description": "Defines the [access strategy](../../spec-extensions/access-strategies/) for accessing the resource definitions.",
+      "x-ums-type": "custom",
       "properties": {
         "type": {
           "type": "string",
@@ -4760,6 +4886,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": {
@@ -4805,6 +4932,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",
@@ -4826,6 +4954,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](../../details/articles/grouping-and-bundling#Groups).",
       "x-introduced-in-version": "1.9.0",
       "properties": {
@@ -4871,6 +5000,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](../../details/articles/grouping-and-bundling#Groups).",
       "x-introduced-in-version": "1.9.0",
       "properties": {
@@ -4892,7 +5022,13 @@
           ],
           "x-association-target": [
             "#/definitions/GroupType/groupTypeId"
-          ]
+          ],
+          "x-reverse-relationship": {
+            "propertyName": "groups",
+            "description": "Group instances of the group type.",
+            "min": 0,
+            "max": "*"
+          }
         },
         "title": {
           "type": "string",
@@ -4930,6 +5066,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",
@@ -4950,6 +5087,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": {
@@ -4984,8 +5122,9 @@
     "EntityTypeMapping": {
       "title": "Entity Type Mapping",
       "x-introduced-in-version": "1.6.0",
+      "x-ums-type": "custom",
       "type": "object",
-      "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](../../#/v1/README?id=correlation-id)\nor to an [ORD ID](../../spec-v1/#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 navigatable for customers.",
+      "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](../../#/v1/README?id=correlation-id)\nor to an [ORD ID](../../spec-v1/#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": {
           "type": "array",
@@ -5025,6 +5164,7 @@
     "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": {
@@ -5059,6 +5199,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": {
@@ -5095,6 +5236,7 @@
     "RelatedEntityType": {
       "title": "Related Entity Type",
       "x-introduced-in-version": "1.9.0",
+      "x-ums-type": "embedded",
       "type": "object",
       "description": "Defines which Entity Type is related (via its ORD ID).\nIn the future, this could include stating the relationship type, too.",
       "properties": {
@@ -5119,6 +5261,7 @@
     "EntityTypeOrdIdTarget": {
       "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](../../spec-v1/#ord-id) of an entity type.",
       "properties": {
@@ -5143,6 +5286,7 @@
     "EntityTypeCorrelationIdTarget": {
       "title": "Entity Type Target (Correlation 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 [Correlation ID](../../spec-v1/#correlation-id).",
       "properties": {
@@ -5163,6 +5307,7 @@
     "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.\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\nIt MUST be kept sufficiently long so that all ORD aggregators can learn about the tombstone.\nAfter that it MAY be removed.",
       "properties": {
         "ordId": {
@@ -5239,10 +5384,189 @@
           "removalDate": "2020-12-02T14:12:59Z"
         }
       ]
+    },
+    "OrdResource": {
+      "type": "object",
+      "title": "ORD Resource (abstract)",
+      "x-abstract": true,
+      "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]*|)$",
+          "maxLength": 255,
+          "examples": []
+        },
+        "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": []
+        },
+        "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": []
+        },
+        "title": {
+          "type": "string",
+          "description": "Human-readable title.\n\nMUST NOT exceed 255 chars.\nMUST NOT contain line breaks.",
+          "minLength": 1,
+          "maxLength": 255,
+          "examples": []
+        },
+        "shortDescription": {
+          "type": "string",
+          "description": "Plain text short description.\n\nMUST NOT exceed 255 chars.\nMUST NOT contain line breaks.",
+          "minLength": 1,
+          "maxLength": 255,
+          "examples": []
+        },
+        "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": []
+        },
+        "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"
+          ],
+          "x-reverse-relationship": null,
+          "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": []
+        },
+        "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"
+            ]
+          },
+          "x-reverse-relationship": {
+            "propertyName": "ordResourceMembers",
+            "description": "The ORD resources that are part the given Group.",
+            "min": 0,
+            "max": "*"
+          },
+          "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.",
+          "examples": []
+        },
+        "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://swagger.io/specification/#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 `systemInstanceAware`, 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": "The visibility states who is allowed to \"see\" the described resource or capability.",
+          "oneOf": [
+            {
+              "const": "public",
+              "description": "Resources are 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)."
+            },
+            {
+              "const": "internal",
+              "description": "Resources are 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."
+            },
+            {
+              "const": "private",
+              "description": "Resources that are exclusive within an application or service.\nThis includes resources that may be called from outside but serve purely private purposes and are not supposed to be known by other outside parties.\nE.g., webhooks for provisioning callbacks or backing services.\n\nPrivate resources MUST NOT be made available to public consumers or consumers outside of the \"private\" scope or without the necessary access permissions."
+            }
+          ]
+        },
+        "releaseStatus": {
+          "type": "string",
+          "description": "The `releaseStatus` specifies the stability of the resource and its external contract.",
+          "oneOf": [
+            {
+              "const": "active",
+              "description": "Resource is meant for productive use and provides a stable API contract."
+            },
+            {
+              "const": "beta",
+              "description": "The contract for the resource is beta and MAY not be meant for productive use.\nIn the SAP context, `beta` APIs may be changed or deleted at SAPs discretion."
+            },
+            {
+              "const": "deprecated",
+              "description": "Resource has been deprecated.\n\nIf successor resources exist, they MUST be referenced through `successors`.\nIf it is deprecated without defining its `successors`, a `sunsetDate` SHOULD be provided.\n\nA deprecated resource MAY be decommissioned (removed) in the future, through setting a `Tombstone`.\nOnce the resource is decommissioned, it MUST be removed from ORD (which is why there is no release status for decommissioned)."
+            }
+          ],
+          "examples": [
+            "active"
+          ]
+        },
+        "links": {
+          "type": "array",
+          "description": "Generic links with arbitrary meaning and content.\n\n`packageLinks` MUST be preferred if applicable.",
+          "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",
+          "description": "Generic labels that can be applied to most ORD information."
+        },
+        "documentationLabels": {
+          "$ref": "#/definitions/DocumentationLabels",
+          "description": "Generic documentation labels that can be applied to most ORD information."
+        }
+      },
+      "required": [
+        "ordId",
+        "title",
+        "description",
+        "version",
+        "visibility",
+        "releaseStatus",
+        "partOfPackage"
+      ],
+      "additionalProperties": true
     }
   },
-  "title": "ORD Document",
   "type": "object",
+  "x-ums-type": "ignore",
   "properties": {
     "$schema": {
       "type": "string",
@@ -5433,6 +5757,7 @@
     "groups": {
       "type": "array",
       "description": "Array of all Groups that are described in this ORD document.",
+      "x-introduced-in-version": "1.9.0",
       "items": {
         "$ref": "#/definitions/Group"
       }
@@ -5440,6 +5765,7 @@
     "groupTypes": {
       "type": "array",
       "description": "Array of all Group Types that are described in this ORD document.",
+      "x-introduced-in-version": "1.9.0",
       "items": {
         "$ref": "#/definitions/GroupType"
       }