@twin.org/standards-dataspace-protocol 0.0.3-next.67 → 0.0.3-next.68

package/dist/es/models/transferProcess/types/dataspaceProtocolEndpointType.js

@@ -3,86 +3,32 @@
 /**
  * TWIN Data Space Protocol Profile endpoint type identifiers.
  *
- * This module defines endpoint types according to the TWIN Foundation's
- * Data Space Protocol Profile (RFC 006), which extends the Eclipse Dataspace
- * Protocol specification with TWIN-specific vocabulary.
- *
- * The TWIN vocabulary uses persistent identifiers under the
- * https://schema.twindev.org namespace to provide stable, semantic
- * identifiers for data space endpoint types.
- *
- * References:
- * - TWIN RFC 006: https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md
- * - TWIN DS Protocol Context: https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-protocol/twin-ds-protocol-profile.jsonld
- * - Eclipse DSP Specification: https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/
- * - RFC 001 (Query Interface): https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-connector/001-data-space-connector-query.md
+ * @see https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md
  */
 // eslint-disable-next-line @typescript-eslint/naming-convention
 export const DataspaceProtocolEndpointType = {
-    // ========================================
-    // TWIN Data Space Protocol Profile (RFC 006)
-    // Namespace: https://schema.twindev.org/dspace/v1/
-    // ========================================
     /**
-     * HTTPS Query Endpoint (TWIN DS Profile).
-     *
-     * Used for PULL transfers via the TWIN Data Space Connector Query interface.
-     * The consumer retrieves data by querying this endpoint using the data access token.
-     * Endpoint must implement the interface specified in RFC 001.
-     *
-     * Transfer Flow:
-     * 1. Consumer initiates transfer request
-     * 2. Provider returns this endpoint type with data access token
-     * 3. Consumer queries the endpoint with the token to retrieve data
+     * HTTPS query endpoint for PULL transfers via the TWIN Data Space Connector Query interface.
      *
      * @see https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md#data-transfer-profile-vocabulary
-     * @see https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-connector/001-data-space-connector-query.md
      */
     HttpsQueryEndpoint: "https://schema.twindev.org/dspace/v1/Https-Query-Endpoint",
     /**
-     * HTTPS Activity Stream Endpoint (TWIN DS Profile).
-     *
-     * Used for PUSH transfers via Activity Streams 2.0 protocol.
-     * The provider actively sends data to the consumer's Activity Stream inbox endpoint.
-     * Based on W3C Activity Streams 2.0 specification.
-     *
-     * Transfer Flow:
-     * 1. Consumer initiates transfer request with this endpoint type
-     * 2. Consumer provides their Activity Stream inbox URL
-     * 3. Provider pushes data to the consumer's inbox as Activity Stream objects
+     * HTTPS Activity Stream endpoint for PUSH transfers via the Activity Streams 2.0 protocol.
      *
      * @see https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md#data-transfer-profile-vocabulary
-     * @see https://www.w3.org/TR/activitystreams-core/
-     * @see https://www.w3.org/TR/activitypub/
      */
     HttpsActivityStreamEndpoint: "https://schema.twindev.org/dspace/v1/Https-Activity-Stream-Endpoint",
-    // ========================================
-    // IDSA W3ID Namespace (Interoperability)
-    // ========================================
     /**
-     * HTTP endpoint (IDSA W3ID v4.1).
-     *
-     * Persistent identifier for HTTP-based data access endpoints.
-     * This W3ID URL is used as a semantic identifier in JSON-LD contexts.
-     *
-     * Note: For TWIN-specific implementations, prefer using `HttpsQueryEndpoint`.
-     * This constant is provided for interoperability with IDSA-based systems.
+     * HTTP endpoint identifier from the IDSA W3ID v4.1 namespace.
      *
      * @see https://w3id.org/idsa/v4.1/HTTP
-     * @see https://github.com/International-Data-Spaces-Association/InformationModel
      */
     HTTP: "https://w3id.org/idsa/v4.1/HTTP",
     /**
-     * HTTPS endpoint (IDSA W3ID v4.1).
-     *
-     * Persistent identifier for HTTPS-based secure data access endpoints.
-     * This W3ID URL is used as a semantic identifier in JSON-LD contexts.
-     *
-     * Note: For TWIN-specific implementations, prefer using `HttpsQueryEndpoint`.
-     * This constant is provided for interoperability with IDSA-based systems.
+     * HTTPS endpoint identifier from the IDSA W3ID v4.1 namespace.
      *
      * @see https://w3id.org/idsa/v4.1/HTTPS
-     * @see https://github.com/International-Data-Spaces-Association/InformationModel
      */
     HTTPS: "https://w3id.org/idsa/v4.1/HTTPS"
 };

package/dist/es/models/transferProcess/types/dataspaceProtocolEndpointType.js.map

@@ -1 +1 @@
-{"version":3,"file":"dataspaceProtocolEndpointType.js","sourceRoot":"","sources":["../../../../../src/models/transferProcess/types/dataspaceProtocolEndpointType.ts"],"names":[],"mappings":"AAAA,gCAAgC;AAChC,uCAAuC;AAEvC;;;;;;;;;;;;;;;;GAgBG;AACH,gEAAgE;AAChE,MAAM,CAAC,MAAM,6BAA6B,GAAG;IAC5C,2CAA2C;IAC3C,6CAA6C;IAC7C,mDAAmD;IACnD,2CAA2C;IAE3C;;;;;;;;;;;;;;OAcG;IACH,kBAAkB,EAAE,2DAA2D;IAE/E;;;;;;;;;;;;;;;OAeG;IACH,2BAA2B,EAC1B,qEAAqE;IAEtE,2CAA2C;IAC3C,yCAAyC;IACzC,2CAA2C;IAE3C;;;;;;;;;;;OAWG;IACH,IAAI,EAAE,iCAAiC;IAEvC;;;;;;;;;;;OAWG;IACH,KAAK,EAAE,kCAAkC;CAChC,CAAC","sourcesContent":["// Copyright 2025 IOTA Stiftung.\n// SPDX-License-Identifier: Apache-2.0.\n\n/**\n * TWIN Data Space Protocol Profile endpoint type identifiers.\n *\n * This module defines endpoint types according to the TWIN Foundation's\n * Data Space Protocol Profile (RFC 006), which extends the Eclipse Dataspace\n * Protocol specification with TWIN-specific vocabulary.\n *\n * The TWIN vocabulary uses persistent identifiers under the\n * https://schema.twindev.org namespace to provide stable, semantic\n * identifiers for data space endpoint types.\n *\n * References:\n * - TWIN RFC 006: https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md\n * - TWIN DS Protocol Context: https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-protocol/twin-ds-protocol-profile.jsonld\n * - Eclipse DSP Specification: https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/\n * - RFC 001 (Query Interface): https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-connector/001-data-space-connector-query.md\n */\n// eslint-disable-next-line @typescript-eslint/naming-convention\nexport const DataspaceProtocolEndpointType = {\n\t// ========================================\n\t// TWIN Data Space Protocol Profile (RFC 006)\n\t// Namespace: https://schema.twindev.org/dspace/v1/\n\t// ========================================\n\n\t/**\n\t * HTTPS Query Endpoint (TWIN DS Profile).\n\t *\n\t * Used for PULL transfers via the TWIN Data Space Connector Query interface.\n\t * The consumer retrieves data by querying this endpoint using the data access token.\n\t * Endpoint must implement the interface specified in RFC 001.\n\t *\n\t * Transfer Flow:\n\t * 1. Consumer initiates transfer request\n\t * 2. Provider returns this endpoint type with data access token\n\t * 3. Consumer queries the endpoint with the token to retrieve data\n\t *\n\t * @see https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md#data-transfer-profile-vocabulary\n\t * @see https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-connector/001-data-space-connector-query.md\n\t */\n\tHttpsQueryEndpoint: \"https://schema.twindev.org/dspace/v1/Https-Query-Endpoint\",\n\n\t/**\n\t * HTTPS Activity Stream Endpoint (TWIN DS Profile).\n\t *\n\t * Used for PUSH transfers via Activity Streams 2.0 protocol.\n\t * The provider actively sends data to the consumer's Activity Stream inbox endpoint.\n\t * Based on W3C Activity Streams 2.0 specification.\n\t *\n\t * Transfer Flow:\n\t * 1. Consumer initiates transfer request with this endpoint type\n\t * 2. Consumer provides their Activity Stream inbox URL\n\t * 3. Provider pushes data to the consumer's inbox as Activity Stream objects\n\t *\n\t * @see https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md#data-transfer-profile-vocabulary\n\t * @see https://www.w3.org/TR/activitystreams-core/\n\t * @see https://www.w3.org/TR/activitypub/\n\t */\n\tHttpsActivityStreamEndpoint:\n\t\t\"https://schema.twindev.org/dspace/v1/Https-Activity-Stream-Endpoint\",\n\n\t// ========================================\n\t// IDSA W3ID Namespace (Interoperability)\n\t// ========================================\n\n\t/**\n\t * HTTP endpoint (IDSA W3ID v4.1).\n\t *\n\t * Persistent identifier for HTTP-based data access endpoints.\n\t * This W3ID URL is used as a semantic identifier in JSON-LD contexts.\n\t *\n\t * Note: For TWIN-specific implementations, prefer using `HttpsQueryEndpoint`.\n\t * This constant is provided for interoperability with IDSA-based systems.\n\t *\n\t * @see https://w3id.org/idsa/v4.1/HTTP\n\t * @see https://github.com/International-Data-Spaces-Association/InformationModel\n\t */\n\tHTTP: \"https://w3id.org/idsa/v4.1/HTTP\",\n\n\t/**\n\t * HTTPS endpoint (IDSA W3ID v4.1).\n\t *\n\t * Persistent identifier for HTTPS-based secure data access endpoints.\n\t * This W3ID URL is used as a semantic identifier in JSON-LD contexts.\n\t *\n\t * Note: For TWIN-specific implementations, prefer using `HttpsQueryEndpoint`.\n\t * This constant is provided for interoperability with IDSA-based systems.\n\t *\n\t * @see https://w3id.org/idsa/v4.1/HTTPS\n\t * @see https://github.com/International-Data-Spaces-Association/InformationModel\n\t */\n\tHTTPS: \"https://w3id.org/idsa/v4.1/HTTPS\"\n} as const;\n\n/**\n * Type representing all valid Dataspace Protocol endpoint types.\n *\n * All values are valid URIs as required by the DS Protocol JSON-LD context\n * which defines endpointType as @type:@vocab.\n *\n * Includes:\n * - TWIN RFC 006 types: HttpsQueryEndpoint, HttpsActivityStreamEndpoint\n * - IDSA W3ID types: HTTP, HTTPS\n */\nexport type DataspaceProtocolEndpointType =\n\t(typeof DataspaceProtocolEndpointType)[keyof typeof DataspaceProtocolEndpointType];\n"]}
+{"version":3,"file":"dataspaceProtocolEndpointType.js","sourceRoot":"","sources":["../../../../../src/models/transferProcess/types/dataspaceProtocolEndpointType.ts"],"names":[],"mappings":"AAAA,gCAAgC;AAChC,uCAAuC;AAEvC;;;;GAIG;AACH,gEAAgE;AAChE,MAAM,CAAC,MAAM,6BAA6B,GAAG;IAC5C;;;;OAIG;IACH,kBAAkB,EAAE,2DAA2D;IAE/E;;;;OAIG;IACH,2BAA2B,EAC1B,qEAAqE;IAEtE;;;;OAIG;IACH,IAAI,EAAE,iCAAiC;IAEvC;;;;OAIG;IACH,KAAK,EAAE,kCAAkC;CAChC,CAAC","sourcesContent":["// Copyright 2025 IOTA Stiftung.\n// SPDX-License-Identifier: Apache-2.0.\n\n/**\n * TWIN Data Space Protocol Profile endpoint type identifiers.\n *\n * @see https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md\n */\n// eslint-disable-next-line @typescript-eslint/naming-convention\nexport const DataspaceProtocolEndpointType = {\n\t/**\n\t * HTTPS query endpoint for PULL transfers via the TWIN Data Space Connector Query interface.\n\t *\n\t * @see https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md#data-transfer-profile-vocabulary\n\t */\n\tHttpsQueryEndpoint: \"https://schema.twindev.org/dspace/v1/Https-Query-Endpoint\",\n\n\t/**\n\t * HTTPS Activity Stream endpoint for PUSH transfers via the Activity Streams 2.0 protocol.\n\t *\n\t * @see https://github.com/iotaledger/twin-rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md#data-transfer-profile-vocabulary\n\t */\n\tHttpsActivityStreamEndpoint:\n\t\t\"https://schema.twindev.org/dspace/v1/Https-Activity-Stream-Endpoint\",\n\n\t/**\n\t * HTTP endpoint identifier from the IDSA W3ID v4.1 namespace.\n\t *\n\t * @see https://w3id.org/idsa/v4.1/HTTP\n\t */\n\tHTTP: \"https://w3id.org/idsa/v4.1/HTTP\",\n\n\t/**\n\t * HTTPS endpoint identifier from the IDSA W3ID v4.1 namespace.\n\t *\n\t * @see https://w3id.org/idsa/v4.1/HTTPS\n\t */\n\tHTTPS: \"https://w3id.org/idsa/v4.1/HTTPS\"\n} as const;\n\n/**\n * All valid Dataspace Protocol endpoint type URI values.\n */\nexport type DataspaceProtocolEndpointType =\n\t(typeof DataspaceProtocolEndpointType)[keyof typeof DataspaceProtocolEndpointType];\n"]}

package/dist/es/models/transferProcess/types/dataspaceProtocolTransferProcessStateType.js

@@ -1,8 +1,8 @@
 // Copyright 2025 IOTA Stiftung.
 // SPDX-License-Identifier: Apache-2.0.
 /**
- * The states for Dataspace Protocol Transfer Process.
- * https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1-err1/#ack-transfer-process
+ * State type identifiers for the Dataspace Protocol Transfer Process.
+ * @see https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1-err1/#ack-transfer-process
  */
 // eslint-disable-next-line @typescript-eslint/naming-convention
 export const DataspaceProtocolTransferProcessStateType = {

package/dist/es/models/transferProcess/types/dataspaceProtocolTransferProcessStateType.js.map

@@ -1 +1 @@
-{"version":3,"file":"dataspaceProtocolTransferProcessStateType.js","sourceRoot":"","sources":["../../../../../src/models/transferProcess/types/dataspaceProtocolTransferProcessStateType.ts"],"names":[],"mappings":"AAAA,gCAAgC;AAChC,uCAAuC;AAEvC;;;GAGG;AACH,gEAAgE;AAChE,MAAM,CAAC,MAAM,yCAAyC,GAAG;IACxD;;OAEG;IACH,SAAS,EAAE,WAAW;IAEtB;;OAEG;IACH,SAAS,EAAE,WAAW;IAEtB;;OAEG;IACH,OAAO,EAAE,SAAS;IAElB;;OAEG;IACH,SAAS,EAAE,WAAW;IAEtB;;OAEG;IACH,UAAU,EAAE,YAAY;CACf,CAAC","sourcesContent":["// Copyright 2025 IOTA Stiftung.\n// SPDX-License-Identifier: Apache-2.0.\n\n/**\n * The states for Dataspace Protocol Transfer Process.\n * https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1-err1/#ack-transfer-process\n */\n// eslint-disable-next-line @typescript-eslint/naming-convention\nexport const DataspaceProtocolTransferProcessStateType = {\n\t/**\n\t * Completed\n\t */\n\tCOMPLETED: \"COMPLETED\",\n\n\t/**\n\t * Requested\n\t */\n\tREQUESTED: \"REQUESTED\",\n\n\t/**\n\t * Started\n\t */\n\tSTARTED: \"STARTED\",\n\n\t/**\n\t * Suspended\n\t */\n\tSUSPENDED: \"SUSPENDED\",\n\n\t/**\n\t * Terminated\n\t */\n\tTERMINATED: \"TERMINATED\"\n} as const;\n\n/**\n * The types for Dataspace Protocol Transfer.\n */\nexport type DataspaceProtocolTransferProcessStateType =\n\t(typeof DataspaceProtocolTransferProcessStateType)[keyof typeof DataspaceProtocolTransferProcessStateType];\n"]}
+{"version":3,"file":"dataspaceProtocolTransferProcessStateType.js","sourceRoot":"","sources":["../../../../../src/models/transferProcess/types/dataspaceProtocolTransferProcessStateType.ts"],"names":[],"mappings":"AAAA,gCAAgC;AAChC,uCAAuC;AAEvC;;;GAGG;AACH,gEAAgE;AAChE,MAAM,CAAC,MAAM,yCAAyC,GAAG;IACxD;;OAEG;IACH,SAAS,EAAE,WAAW;IAEtB;;OAEG;IACH,SAAS,EAAE,WAAW;IAEtB;;OAEG;IACH,OAAO,EAAE,SAAS;IAElB;;OAEG;IACH,SAAS,EAAE,WAAW;IAEtB;;OAEG;IACH,UAAU,EAAE,YAAY;CACf,CAAC","sourcesContent":["// Copyright 2025 IOTA Stiftung.\n// SPDX-License-Identifier: Apache-2.0.\n\n/**\n * State type identifiers for the Dataspace Protocol Transfer Process.\n * @see https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1-err1/#ack-transfer-process\n */\n// eslint-disable-next-line @typescript-eslint/naming-convention\nexport const DataspaceProtocolTransferProcessStateType = {\n\t/**\n\t * Completed\n\t */\n\tCOMPLETED: \"COMPLETED\",\n\n\t/**\n\t * Requested\n\t */\n\tREQUESTED: \"REQUESTED\",\n\n\t/**\n\t * Started\n\t */\n\tSTARTED: \"STARTED\",\n\n\t/**\n\t * Suspended\n\t */\n\tSUSPENDED: \"SUSPENDED\",\n\n\t/**\n\t * Terminated\n\t */\n\tTERMINATED: \"TERMINATED\"\n} as const;\n\n/**\n * The types for Dataspace Protocol Transfer.\n */\nexport type DataspaceProtocolTransferProcessStateType =\n\t(typeof DataspaceProtocolTransferProcessStateType)[keyof typeof DataspaceProtocolTransferProcessStateType];\n"]}

package/dist/es/schemas/DataspaceProtocolAgreement.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolAgreement",
     "title": "DataspaceProtocolAgreement",
-    "description": "Agreement interface compliant with Eclipse Data Space Protocol.\n\nExtends IOdrlAgreement with DS Protocol-specific constraints:\n- `@id` is REQUIRED (used as the primary agreement identifier in DS Protocol)\n- `@context` is omitted (inherited from the parent Dataset/Distribution)",
+    "description": "Agreement interface compliant with Eclipse Data Space Protocol, requiring an id and omitting context.",
     "type": "object",
     "properties": {
         "@id": {

package/dist/es/schemas/DataspaceProtocolCatalog.json

@@ -2,12 +2,12 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolCatalog",
     "title": "DataspaceProtocolCatalog",
-    "description": "Catalog interface compliant with Eclipse Data Space Protocol.\n\nThis interface extends ICatalog and enforces DS Protocol-specific requirements\nby overriding properties with more specific types and constraints.\n\n**Requirements per DS Protocol:**\n- `@id` MUST be present for dataset identification (REQUIRED)\n- participantId MUST be present (REQUIRED)\n\n**Type System Design:**\n- Interface extension allows TypeScript to override inherited property types\n- Standards packages (@twin.org/standards-w3c-*) follow W3C specs exactly\n- DS Protocol-specific constraints are defined here",
+    "description": "Catalog compliant with Eclipse Data Space Protocol, requiring a context, id, and participantId.",
     "type": "object",
     "properties": {
         "@context": {
             "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContextType",
-            "description": "LD Context. Required per Eclipse Data Space Protocol."
+            "description": "The JSON-LD context."
         }
     },
     "required": [

package/dist/es/schemas/DataspaceProtocolCatalogBase.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolCatalogBase",
     "title": "DataspaceProtocolCatalogBase",
-    "description": "Catalog interface compliant with Eclipse Data Space Protocol.\n\nThis interface extends ICatalog and enforces DS Protocol-specific requirements\nby overriding properties with more specific types and constraints.\n\n**Requirements per DS Protocol:**\n- `@id` MUST be present for dataset identification (REQUIRED)\n- participantId MUST be present (REQUIRED)\n\n**Type System Design:**\n- Interface extension allows TypeScript to override inherited property types\n- Standards packages (@twin.org/standards-w3c-*) follow W3C specs exactly\n- DS Protocol-specific constraints are defined here",
+    "description": "Base catalog interface compliant with Eclipse Data Space Protocol, requiring an id and participantId.",
     "type": "object",
     "properties": {
         "@type": {
@@ -15,35 +15,35 @@
         },
         "participantId": {
             "type": "string",
-            "description": "Participant Id"
+            "description": "The participant identifier."
         },
         "catalog": {
             "type": "array",
             "items": {
                 "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolCatalogBase"
             },
-            "description": "Other concerned catalogs"
+            "description": "Nested catalogs."
         },
         "dataset": {
             "type": "array",
             "items": {
                 "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDatasetBase"
             },
-            "description": "Datasets registered"
+            "description": "Datasets registered in this catalog."
         },
         "distribution": {
             "type": "array",
             "items": {
                 "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDistributionBase"
             },
-            "description": "Catalog's distributions"
+            "description": "Distributions for this catalog."
         },
         "service": {
             "type": "array",
             "items": {
                 "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDataServiceBase"
             },
-            "description": "Data services registered-"
+            "description": "Data services registered in this catalog."
         }
     },
     "required": [

package/dist/es/schemas/DataspaceProtocolCatalogError.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolCatalogError",
     "title": "DataspaceProtocolCatalogError",
-    "description": "Interface for Dataspace Protocol Catalog Error.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/#error-catalog-error",
+    "description": "Interface for the Dataspace Protocol catalog error response.",
     "type": "object",
     "properties": {
         "@context": {

package/dist/es/schemas/DataspaceProtocolCatalogRequestMessage.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolCatalogRequestMessage",
     "title": "DataspaceProtocolCatalogRequestMessage",
-    "description": "Interface for Dataspace Protocol Catalog Request Messages.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/#catalog-request-message",
+    "description": "Interface for the Dataspace Protocol catalog request message.",
     "type": "object",
     "properties": {
         "@context": {

package/dist/es/schemas/DataspaceProtocolContractAgreementMessage.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContractAgreementMessage",
     "title": "DataspaceProtocolContractAgreementMessage",
-    "description": "Interface for Dataspace Protocol Contract Agreement Messages.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/#contract-agreement-message",
+    "description": "Interface for the Dataspace Protocol contract agreement message.",
     "type": "object",
     "properties": {
         "@context": {

package/dist/es/schemas/DataspaceProtocolContractAgreementVerificationMessage.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContractAgreementVerificationMessage",
     "title": "DataspaceProtocolContractAgreementVerificationMessage",
-    "description": "Interface for Dataspace Protocol Contract Agreement Verification Messages.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/#contract-agreement-verification-message",
+    "description": "Interface for the Dataspace Protocol contract agreement verification message.",
     "type": "object",
     "properties": {
         "@context": {

package/dist/es/schemas/DataspaceProtocolContractNegotiation.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContractNegotiation",
     "title": "DataspaceProtocolContractNegotiation",
-    "description": "Interface for Dataspace Protocol Contract Agreement Messages.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/#ack-contract-negotiation",
+    "description": "Interface for the Dataspace Protocol contract negotiation acknowledgment.",
     "type": "object",
     "properties": {
         "@context": {
@@ -23,7 +23,7 @@
         },
         "state": {
             "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContractNegotiationStateType",
-            "description": "The offer being requested."
+            "description": "The current state of the contract negotiation."
         }
     },
     "required": [

package/dist/es/schemas/DataspaceProtocolContractNegotiationError.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContractNegotiationError",
     "title": "DataspaceProtocolContractNegotiationError",
-    "description": "Interface for Dataspace Protocol Contract Negotiation Error Messages.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/#error-contract-negotiation-error",
+    "description": "Interface for the Dataspace Protocol contract negotiation error response.",
     "type": "object",
     "properties": {
         "@context": {

package/dist/es/schemas/DataspaceProtocolContractNegotiationEventMessage.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContractNegotiationEventMessage",
     "title": "DataspaceProtocolContractNegotiationEventMessage",
-    "description": "Interface for Dataspace Protocol Contract Negotiation Event Messages.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/#contract-negotiation-event-message",
+    "description": "Interface for the Dataspace Protocol contract negotiation event message.",
     "type": "object",
     "properties": {
         "@context": {

package/dist/es/schemas/DataspaceProtocolContractNegotiationTerminationMessage.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContractNegotiationTerminationMessage",
     "title": "DataspaceProtocolContractNegotiationTerminationMessage",
-    "description": "Interface for Dataspace Protocol Contract Negotiation Termination Messages.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/#contract-negotiation-termination-message",
+    "description": "Interface for the Dataspace Protocol contract negotiation termination message.",
     "type": "object",
     "properties": {
         "@context": {

package/dist/es/schemas/DataspaceProtocolContractOfferMessage.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContractOfferMessage",
     "title": "DataspaceProtocolContractOfferMessage",
-    "description": "Interface for Dataspace Protocol Contract Offer Messages.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/#contract-offer-message",
+    "description": "Interface for the Dataspace Protocol contract offer message.",
     "type": "object",
     "properties": {
         "@context": {

package/dist/es/schemas/DataspaceProtocolContractRequestMessage.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContractRequestMessage",
     "title": "DataspaceProtocolContractRequestMessage",
-    "description": "Interface for Dataspace Protocol Contract Request Messages.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/#contract-request-message",
+    "description": "Interface for the Dataspace Protocol contract request message.",
     "type": "object",
     "properties": {
         "@context": {

package/dist/es/schemas/DataspaceProtocolDataAddress.json

@@ -2,27 +2,27 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDataAddress",
     "title": "DataspaceProtocolDataAddress",
-    "description": "Interface for Dataspace Protocol Transfer Messages.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/#lower-level-types",
+    "description": "Interface for a Dataspace Protocol data address.",
     "type": "object",
     "properties": {
         "@type": {
             "const": "DataAddress",
-            "description": "LD Type"
+            "description": "The JSON-LD type."
         },
         "endpointType": {
             "type": "string",
-            "description": "The type of endpoint of this data address."
+            "description": "The endpoint type identifier."
         },
         "endpoint": {
             "type": "string",
-            "description": "The endpoint of the data address"
+            "description": "The endpoint URL or address."
         },
         "endpointProperties": {
             "type": "array",
             "items": {
                 "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolEndpointProperty"
             },
-            "description": "Properties associated to the endpoint which might depend on the endpoint type."
+            "description": "Transport-specific endpoint properties."
         }
     },
     "required": [

package/dist/es/schemas/DataspaceProtocolDataService.json

@@ -2,12 +2,12 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDataService",
     "title": "DataspaceProtocolDataService",
-    "description": "Data Service interface compliant with Eclipse Data Space Protocol.\n\nThis interface extends IDataService and enforces DS Protocol-specific requirements\nby overriding properties with more specific types and constraints.\n\n**Requirements per DS Protocol:**\n- `@id` MUST be present for dataset identification (REQUIRED)\n- endpointURL MUST be present (REQUIRED)\n\n**Type System Design:**\n- Interface extension allows TypeScript to override inherited property types\n- Standards packages (@twin.org/standards-w3c-*) follow W3C specs exactly\n- DS Protocol-specific constraints are defined here",
+    "description": "Data service compliant with Eclipse Data Space Protocol, requiring an id and endpointURL.",
     "type": "object",
     "properties": {
         "@context": {
             "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContextType",
-            "description": "LD Context. Required per Eclipse Data Space Protocol."
+            "description": "The JSON-LD context."
         }
     },
     "required": [

package/dist/es/schemas/DataspaceProtocolDataServiceBase.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDataServiceBase",
     "title": "DataspaceProtocolDataServiceBase",
-    "description": "Data Service interface compliant with Eclipse Data Space Protocol.\n\nThis interface extends IDataService and enforces DS Protocol-specific requirements\nby overriding properties with more specific types and constraints.\n\n**Requirements per DS Protocol:**\n- `@id` MUST be present for dataset identification (REQUIRED)\n- endpointURL MUST be present (REQUIRED)\n\n**Type System Design:**\n- Interface extension allows TypeScript to override inherited property types\n- Standards packages (@twin.org/standards-w3c-*) follow W3C specs exactly\n- DS Protocol-specific constraints are defined here",
+    "description": "Base data service interface compliant with Eclipse Data Space Protocol, requiring an id and endpointURL.",
     "type": "object",
     "properties": {
         "@type": {

package/dist/es/schemas/DataspaceProtocolDataset.json

@@ -2,12 +2,12 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDataset",
     "title": "DataspaceProtocolDataset",
-    "description": "Dataset interface compliant with Eclipse Data Space Protocol.\n\nThis interface extends IDataset and enforces DS Protocol-specific requirements\nby overriding properties with more specific types and constraints.\n\n**Requirements per DS Protocol:**\n- `@id` MUST be present for dataset identification (REQUIRED)\n- `odrl:hasPolicy` MUST be present as an array of ODRL Offers (REQUIRED)\n- Array MUST contain at least one IOdrlOffer\n- Each Offer MUST have `@type`: \"Offer\"\n- Each Offer MUST have `@id`\n- `dcat:distribution` MUST be present (REQUIRED)\n\n**Type System Design:**\n- W3C DCAT spec defines `odrl:hasPolicy` as optional singular `IOdrlPolicy`\n- DS Protocol requires it as a REQUIRED array of `IOdrlOffer`\n- Interface extension allows TypeScript to override inherited property types\n- Standards packages (@twin.org/standards-w3c-*) follow W3C specs exactly\n- DS Protocol-specific constraints are defined here\n\n**Future Compatibility:**\n- Currently only one Offer per dataset is supported\n- Array structure allows future support for multiple offers",
+    "description": "Dataset compliant with Eclipse Data Space Protocol, requiring an id, hasPolicy, and distribution.",
     "type": "object",
     "properties": {
         "@context": {
             "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContextType",
-            "description": "LD Context. Required per Eclipse Data Space Protocol."
+            "description": "The JSON-LD context."
         }
     },
     "required": [

package/dist/es/schemas/DataspaceProtocolDatasetBase.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDatasetBase",
     "title": "DataspaceProtocolDatasetBase",
-    "description": "Dataset interface compliant with Eclipse Data Space Protocol.\n\nThis interface extends IDataset and enforces DS Protocol-specific requirements\nby overriding properties with more specific types and constraints.\n\n**Requirements per DS Protocol:**\n- `@id` MUST be present for dataset identification (REQUIRED)\n- `odrl:hasPolicy` MUST be present as an array of ODRL Offers (REQUIRED)\n- Array MUST contain at least one IOdrlOffer\n- Each Offer MUST have `@type`: \"Offer\"\n- Each Offer MUST have `@id`\n- `dcat:distribution` MUST be present (REQUIRED)\n\n**Type System Design:**\n- W3C DCAT spec defines `odrl:hasPolicy` as optional singular `IOdrlPolicy`\n- DS Protocol requires it as a REQUIRED array of `IOdrlOffer`\n- Interface extension allows TypeScript to override inherited property types\n- Standards packages (@twin.org/standards-w3c-*) follow W3C specs exactly\n- DS Protocol-specific constraints are defined here\n\n**Future Compatibility:**\n- Currently only one Offer per dataset is supported\n- Array structure allows future support for multiple offers",
+    "description": "Base dataset interface compliant with Eclipse Data Space Protocol, requiring an id, hasPolicy, and distribution.",
     "type": "object",
     "properties": {
         "@type": {
@@ -18,7 +18,7 @@
             "items": {
                 "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolOfferBase"
             },
-            "description": "Array of ODRL policies (Offers) as required by DS Protocol.\n\nREQUIRED per Eclipse Data Space Protocol spec.\nMust contain at least one IOdrlOffer.\nCurrently only single offer is supported, but array structure\nallows for future multi-offer support.",
+            "description": "Array of ODRL offers; must contain at least one entry.",
             "minItems": 1
         },
         "distribution": {
@@ -26,7 +26,7 @@
             "items": {
                 "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDistributionBase"
             },
-            "description": "Distribution of the dataset.\nREQUIRED per Eclipse Data Space Protocol.",
+            "description": "Distributions of this dataset; must contain at least one entry.",
             "minItems": 1
         }
     },

package/dist/es/schemas/DataspaceProtocolDatasetRequestMessage.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDatasetRequestMessage",
     "title": "DataspaceProtocolDatasetRequestMessage",
-    "description": "Interface for Dataspace Protocol Dataset Request Messages.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/#dataset-request-message",
+    "description": "Interface for the Dataspace Protocol dataset request message.",
     "type": "object",
     "properties": {
         "@context": {

package/dist/es/schemas/DataspaceProtocolDistribution.json

@@ -2,16 +2,16 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDistribution",
     "title": "DataspaceProtocolDistribution",
-    "description": "Distribution interface compliant with Eclipse Data Space Protocol.\n\nThis interface extends IDistribution and enforces DS Protocol-specific requirements\nby overriding properties with more specific types and constraints.\n\n**Requirements per DS Protocol:**\n- `@id` MUST be present for dataset identification (REQUIRED)\n- `odrl:hasPolicy` MIGHT be present as an array of ODRL Offers (OPTIONAL)\n- Array MUST contain at least one IOdrlOffer\n- Each Offer MUST have `@type`: \"Offer\"\n- `format` is REQUIRED.\n\n**Type System Design:**\n- W3C DCAT spec defines `odrl:hasPolicy` as optional singular `IOdrlPolicy`\n- DS Protocol requires it as a REQUIRED array of `IOdrlOffer`\n- Interface extension allows TypeScript to override inherited property types\n- Standards packages (@twin.org/standards-w3c-*) follow W3C specs exactly\n- DS Protocol-specific constraints are defined here\n\n**Future Compatibility:**\n- Currently only one Offer per dataset is supported\n- Array structure allows future support for multiple offers",
+    "description": "Distribution compliant with Eclipse Data Space Protocol, requiring an id and format.",
     "type": "object",
     "properties": {
         "@context": {
             "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolContextType",
-            "description": "LD Context. Required per Eclipse Data Space Protocol."
+            "description": "The JSON-LD context."
         },
         "@id": {
             "type": "string",
-            "description": "Unique identifier for the distribution.\nREQUIRED on standalone Distribution objects per Eclipse Data Space Protocol."
+            "description": "Unique identifier for the distribution; required on standalone distribution objects."
         }
     },
     "required": [

package/dist/es/schemas/DataspaceProtocolDistributionBase.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDistributionBase",
     "title": "DataspaceProtocolDistributionBase",
-    "description": "Distribution interface compliant with Eclipse Data Space Protocol.\n\nThis interface extends IDistribution and enforces DS Protocol-specific requirements\nby overriding properties with more specific types and constraints.\n\n**Requirements per DS Protocol:**\n- `@id` MUST be present for dataset identification (REQUIRED)\n- `odrl:hasPolicy` MIGHT be present as an array of ODRL Offers (OPTIONAL)\n- Array MUST contain at least one IOdrlOffer\n- Each Offer MUST have `@type`: \"Offer\"\n- `format` is REQUIRED.\n\n**Type System Design:**\n- W3C DCAT spec defines `odrl:hasPolicy` as optional singular `IOdrlPolicy`\n- DS Protocol requires it as a REQUIRED array of `IOdrlOffer`\n- Interface extension allows TypeScript to override inherited property types\n- Standards packages (@twin.org/standards-w3c-*) follow W3C specs exactly\n- DS Protocol-specific constraints are defined here\n\n**Future Compatibility:**\n- Currently only one Offer per dataset is supported\n- Array structure allows future support for multiple offers",
+    "description": "Base distribution interface compliant with Eclipse Data Space Protocol, requiring a format and accessService.",
     "type": "object",
     "properties": {
         "@type": {
@@ -11,14 +11,14 @@
         },
         "@id": {
             "type": "string",
-            "description": "Unique identifier for the distribution.\nOPTIONAL for embedded distributions (may use JSON-LD blank nodes).\nREQUIRED on standalone Distribution objects per Eclipse Data Space Protocol."
+            "description": "Unique identifier for the distribution; optional for embedded distributions."
         },
         "hasPolicy": {
             "type": "array",
             "items": {
                 "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolOfferBase"
             },
-            "description": "Array of ODRL policies (Offers) as required by DS Protocol.\n\nREQUIRED per Eclipse Data Space Protocol spec.\nMust contain at least one IOdrlOffer.\nCurrently only single offer is supported, but array structure\nallows for future multi-offer support.",
+            "description": "Optional array of ODRL offers; when present, must contain at least one entry.",
             "minItems": 1
         },
         "accessService": {
@@ -30,11 +30,11 @@
                     "$ref": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolDataServiceBase"
                 }
             ],
-            "description": "Access service.\nIt can be a URI pointing to an access service or inline the access service itself."
+            "description": "Access service URI or inline access service definition."
         },
         "format": {
             "type": "string",
-            "description": "Distribution format.\nREQUIRED per Eclipse Data Space Protocol."
+            "description": "Distribution format identifier."
         }
     },
     "required": [

package/dist/es/schemas/DataspaceProtocolEndpointProperty.json

@@ -2,20 +2,20 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolEndpointProperty",
     "title": "DataspaceProtocolEndpointProperty",
-    "description": "Interface for Dataspace Protocol Transfer Messages.\nhttps://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/#lower-level-types",
+    "description": "Interface for a Dataspace Protocol endpoint property key-value pair.",
     "type": "object",
     "properties": {
         "@type": {
             "const": "EndpointProperty",
-            "description": "LD Type."
+            "description": "The JSON-LD type."
         },
         "name": {
             "type": "string",
-            "description": "Property name."
+            "description": "The property name."
         },
         "value": {
             "type": "string",
-            "description": "Property value."
+            "description": "The property value."
         }
     },
     "required": [

package/dist/es/schemas/DataspaceProtocolOffer.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolOffer",
     "title": "DataspaceProtocolOffer",
-    "description": "Offer interface compliant with Eclipse Data Space Protocol.\n\nExtends IOdrlOffer with DS Protocol-specific constraints:\n- `@id` is REQUIRED (used as the primary offer identifier in DS Protocol)\n- `@context` is omitted (inherited from the parent Dataset/Distribution)",
+    "description": "Offer interface compliant with Eclipse Data Space Protocol, requiring an id and context.",
     "type": "object",
     "properties": {
         "@id": {
@@ -11,7 +11,7 @@
         },
         "@context": {
             "$ref": "https://schema.twindev.org/w3c-odrl/OdrlContextType",
-            "description": "LD Context."
+            "description": "The JSON-LD context."
         }
     },
     "required": [

package/dist/es/schemas/DataspaceProtocolOfferBase.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolOfferBase",
     "title": "DataspaceProtocolOfferBase",
-    "description": "Offer interface compliant with Eclipse Data Space Protocol without JSON-LD context.\nThis is the context-free variant of IDataspaceProtocolOffer, intended for embedding\noffers inline within other objects where the context is provided by the enclosing document.\n\nExtends IOdrlOffer with DS Protocol-specific constraints:\n- '@id' is REQUIRED (used as the primary offer identifier in DS Protocol)\n- '@context' is omitted (context is inherited from the parent object)",
+    "description": "Context-free offer interface compliant with Eclipse Data Space Protocol, for embedding within parent documents.",
     "type": "object",
     "properties": {
         "@id": {

package/dist/es/schemas/DataspaceProtocolPolicy.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolPolicy",
     "title": "DataspaceProtocolPolicy",
-    "description": "Policy interface compliant with Eclipse Data Space Protocol.\n\nExtends IOdrlPolicy with DS Protocol-specific constraints:\n- `@id` is REQUIRED (used as the primary policy identifier in DS Protocol)\n- `@context` is omitted (inherited from the parent Dataset/Distribution)",
+    "description": "Policy interface compliant with Eclipse Data Space Protocol, requiring an id and omitting context.",
     "type": "object",
     "properties": {
         "@id": {

package/dist/es/schemas/DataspaceProtocolSet.json

@@ -2,7 +2,7 @@
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "https://schema.twindev.org/dataspace-protocol/DataspaceProtocolSet",
     "title": "DataspaceProtocolSet",
-    "description": "Set interface compliant with Eclipse Data Space Protocol.\n\nExtends IOdrlSet with DS Protocol-specific constraints:\n- `@id` is REQUIRED (used as the primary set identifier in DS Protocol)\n- `@context` is omitted (inherited from the parent Dataset/Distribution)",
+    "description": "Set interface compliant with Eclipse Data Space Protocol, requiring an id and omitting context.",
     "type": "object",
     "properties": {
         "@id": {