@twin.org/standards-dataspace-protocol 0.0.3-next.27 → 0.0.3-next.29

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

@@ -1,96 +1,89 @@
 // Copyright 2025 IOTA Stiftung.
 // SPDX-License-Identifier: Apache-2.0.
 /**
- * W3ID-based endpoint type identifiers from the IDSA namespace.
+ * TWIN Data Space Protocol Profile endpoint type identifiers.
  *
- * These persistent identifiers follow the W3ID (https://w3id.org) system
- * used by the International Data Spaces Association (IDSA) to provide
- * stable, semantic identifiers for data space endpoint types.
+ * 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.
  *
- * W3ID URLs are designed to be:
- * - Persistent (permanent identifiers that don't break)
- * - Resolvable (can be dereferenced to get definitions)
- * - Semantic (provide meaning through linked data)
+ * The TWIN vocabulary uses persistent identifiers under the
+ * https://schema.twindev.org namespace to provide stable, semantic
+ * identifiers for data space endpoint types.
  *
  * References:
- * - IDSA W3ID Namespace: https://w3id.org/idsa/
- * - IDS Information Model: https://github.com/International-Data-Spaces-Association/InformationModel
- * - DSP Specification: https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/
+ * - TWIN RFC 006: https://github.com/twinfoundation/rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md
+ * - TWIN DS Protocol Context: https://github.com/twinfoundation/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/twinfoundation/rfcs/blob/main/rfcs/data-space-connector/001-data-space-connector-query.md
  */
 // eslint-disable-next-line @typescript-eslint/naming-convention
 export const DataspaceProtocolEndpointType = {
     // ========================================
-    // IDSA W3ID Namespace (Standardized)
+    // TWIN Data Space Protocol Profile (RFC 006)
+    // Namespace: https://schema.twindev.org/dspace/v1/
     // ========================================
     /**
-     * HTTP endpoint (IDSA W3ID v4.1).
+     * HTTPS Query Endpoint (TWIN DS Profile).
      *
-     * Persistent identifier for HTTP-based data access endpoints.
-     * This W3ID URL is used as a semantic identifier in JSON-LD contexts.
-     *
-     * @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).
+     * 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.
      *
-     * Persistent identifier for HTTPS-based secure data access endpoints.
-     * This W3ID URL is used as a semantic identifier in JSON-LD contexts.
+     * 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
      *
-     * @see https://w3id.org/idsa/v4.1/HTTPS
-     * @see https://github.com/International-Data-Spaces-Association/InformationModel
+     * @see https://github.com/twinfoundation/rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md#data-transfer-profile-vocabulary
+     * @see https://github.com/twinfoundation/rfcs/blob/main/rfcs/data-space-connector/001-data-space-connector-query.md
      */
-    HTTPS: "https://w3id.org/idsa/v4.1/HTTPS",
-    // ========================================
-    // Non-W3ID Endpoint Types (De facto standards)
-    // ========================================
+    HttpsQueryEndpoint: "https://schema.twindev.org/dspace/v1/Https-Query-Endpoint",
     /**
-     * HTTPS Activity Stream endpoint (Activity Streams 2.0).
+     * HTTPS Activity Stream Endpoint (TWIN DS Profile).
      *
-     * Used for ActivityPub/Activity Streams protocol endpoints.
-     * This is used in PUSH transfer scenarios where the provider
-     * sends data to the consumer's Activity Stream inbox.
+     * 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
+     *
+     * @see https://github.com/twinfoundation/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/
      */
-    HttpsActivityStream: "Https-Activity-Stream-Endpoint",
+    HttpsActivityStreamEndpoint: "https://schema.twindev.org/dspace/v1/Https-Activity-Stream-Endpoint",
+    // ========================================
+    // IDSA W3ID Namespace (Interoperability)
+    // ========================================
     /**
-     * Amazon S3 bucket endpoint.
-     *
-     * Used for S3-based data transfer (both PULL and PUSH).
-     * Note: Not currently part of IDSA W3ID namespace.
+     * HTTP endpoint (IDSA W3ID v4.1).
      *
-     * @see https://aws.amazon.com/s3/
-     */
-    S3: "S3",
-    /**
-     * Azure Blob Storage endpoint.
+     * Persistent identifier for HTTP-based data access endpoints.
+     * This W3ID URL is used as a semantic identifier in JSON-LD contexts.
      *
-     * Used for Azure cloud storage-based data transfer.
-     * Note: Not currently part of IDSA W3ID namespace.
+     * Note: For TWIN-specific implementations, prefer using `HttpsQueryEndpoint`.
+     * This constant is provided for interoperability with IDSA-based systems.
      *
-     * @see https://azure.microsoft.com/en-us/products/storage/blobs
+     * @see https://w3id.org/idsa/v4.1/HTTP
+     * @see https://github.com/International-Data-Spaces-Association/InformationModel
      */
-    AzureStorage: "AzureStorage",
+    HTTP: "https://w3id.org/idsa/v4.1/HTTP",
     /**
-     * Apache Kafka topic endpoint.
-     *
-     * Used for streaming data via Kafka message broker.
-     * Note: Not currently part of IDSA W3ID namespace.
+     * HTTPS endpoint (IDSA W3ID v4.1).
      *
-     * @see https://kafka.apache.org/
-     */
-    Kafka: "Kafka",
-    /**
-     * SFTP (SSH File Transfer Protocol) endpoint.
+     * Persistent identifier for HTTPS-based secure data access endpoints.
+     * This W3ID URL is used as a semantic identifier in JSON-LD contexts.
      *
-     * Used for secure file transfer over SSH.
-     * Note: Not currently part of IDSA W3ID namespace.
+     * Note: For TWIN-specific implementations, prefer using `HttpsQueryEndpoint`.
+     * This constant is provided for interoperability with IDSA-based systems.
      *
-     * @see https://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol
+     * @see https://w3id.org/idsa/v4.1/HTTPS
+     * @see https://github.com/International-Data-Spaces-Association/InformationModel
      */
-    SFTP: "SFTP"
+    HTTPS: "https://w3id.org/idsa/v4.1/HTTPS"
 };
 //# sourceMappingURL=dataspaceProtocolEndpointType.js.map

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,qCAAqC;IACrC,2CAA2C;IAE3C;;;;;;;;OAQG;IACH,IAAI,EAAE,iCAAiC;IAEvC;;;;;;;;OAQG;IACH,KAAK,EAAE,kCAAkC;IAEzC,2CAA2C;IAC3C,+CAA+C;IAC/C,2CAA2C;IAE3C;;;;;;;;;OASG;IACH,mBAAmB,EAAE,gCAAgC;IAErD;;;;;;;OAOG;IACH,EAAE,EAAE,IAAI;IAER;;;;;;;OAOG;IACH,YAAY,EAAE,cAAc;IAE5B;;;;;;;OAOG;IACH,KAAK,EAAE,OAAO;IAEd;;;;;;;OAOG;IACH,IAAI,EAAE,MAAM;CACH,CAAC","sourcesContent":["// Copyright 2025 IOTA Stiftung.\n// SPDX-License-Identifier: Apache-2.0.\n\n/**\n * W3ID-based endpoint type identifiers from the IDSA namespace.\n *\n * These persistent identifiers follow the W3ID (https://w3id.org) system\n * used by the International Data Spaces Association (IDSA) to provide\n * stable, semantic identifiers for data space endpoint types.\n *\n * W3ID URLs are designed to be:\n * - Persistent (permanent identifiers that don't break)\n * - Resolvable (can be dereferenced to get definitions)\n * - Semantic (provide meaning through linked data)\n *\n * References:\n * - IDSA W3ID Namespace: https://w3id.org/idsa/\n * - IDS Information Model: https://github.com/International-Data-Spaces-Association/InformationModel\n * - DSP Specification: https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/\n */\n// eslint-disable-next-line @typescript-eslint/naming-convention\nexport const DataspaceProtocolEndpointType = {\n\t// ========================================\n\t// IDSA W3ID Namespace (Standardized)\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 * @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 * @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\n\t// ========================================\n\t// Non-W3ID Endpoint Types (De facto standards)\n\t// ========================================\n\n\t/**\n\t * HTTPS Activity Stream endpoint (Activity Streams 2.0).\n\t *\n\t * Used for ActivityPub/Activity Streams protocol endpoints.\n\t * This is used in PUSH transfer scenarios where the provider\n\t * sends data to the consumer's Activity Stream inbox.\n\t *\n\t * @see https://www.w3.org/TR/activitystreams-core/\n\t * @see https://www.w3.org/TR/activitypub/\n\t */\n\tHttpsActivityStream: \"Https-Activity-Stream-Endpoint\",\n\n\t/**\n\t * Amazon S3 bucket endpoint.\n\t *\n\t * Used for S3-based data transfer (both PULL and PUSH).\n\t * Note: Not currently part of IDSA W3ID namespace.\n\t *\n\t * @see https://aws.amazon.com/s3/\n\t */\n\tS3: \"S3\",\n\n\t/**\n\t * Azure Blob Storage endpoint.\n\t *\n\t * Used for Azure cloud storage-based data transfer.\n\t * Note: Not currently part of IDSA W3ID namespace.\n\t *\n\t * @see https://azure.microsoft.com/en-us/products/storage/blobs\n\t */\n\tAzureStorage: \"AzureStorage\",\n\n\t/**\n\t * Apache Kafka topic endpoint.\n\t *\n\t * Used for streaming data via Kafka message broker.\n\t * Note: Not currently part of IDSA W3ID namespace.\n\t *\n\t * @see https://kafka.apache.org/\n\t */\n\tKafka: \"Kafka\",\n\n\t/**\n\t * SFTP (SSH File Transfer Protocol) endpoint.\n\t *\n\t * Used for secure file transfer over SSH.\n\t * Note: Not currently part of IDSA W3ID namespace.\n\t *\n\t * @see https://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol\n\t */\n\tSFTP: \"SFTP\"\n} as const;\n\n/**\n * Type representing all valid Dataspace Protocol endpoint types.\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;;;;;;;;;;;;;;;;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/twinfoundation/rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md\n * - TWIN DS Protocol Context: https://github.com/twinfoundation/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/twinfoundation/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/twinfoundation/rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md#data-transfer-profile-vocabulary\n\t * @see https://github.com/twinfoundation/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/twinfoundation/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"]}

package/dist/types/models/transferProcess/types/dataspaceProtocolEndpointType.d.ts

@@ -1,90 +1,89 @@
 /**
- * W3ID-based endpoint type identifiers from the IDSA namespace.
+ * TWIN Data Space Protocol Profile endpoint type identifiers.
  *
- * These persistent identifiers follow the W3ID (https://w3id.org) system
- * used by the International Data Spaces Association (IDSA) to provide
- * stable, semantic identifiers for data space endpoint types.
+ * 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.
  *
- * W3ID URLs are designed to be:
- * - Persistent (permanent identifiers that don't break)
- * - Resolvable (can be dereferenced to get definitions)
- * - Semantic (provide meaning through linked data)
+ * The TWIN vocabulary uses persistent identifiers under the
+ * https://schema.twindev.org namespace to provide stable, semantic
+ * identifiers for data space endpoint types.
  *
  * References:
- * - IDSA W3ID Namespace: https://w3id.org/idsa/
- * - IDS Information Model: https://github.com/International-Data-Spaces-Association/InformationModel
- * - DSP Specification: https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/
+ * - TWIN RFC 006: https://github.com/twinfoundation/rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md
+ * - TWIN DS Protocol Context: https://github.com/twinfoundation/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/twinfoundation/rfcs/blob/main/rfcs/data-space-connector/001-data-space-connector-query.md
  */
 export declare const DataspaceProtocolEndpointType: {
     /**
-     * HTTP endpoint (IDSA W3ID v4.1).
+     * HTTPS Query Endpoint (TWIN DS Profile).
      *
-     * Persistent identifier for HTTP-based data access endpoints.
-     * This W3ID URL is used as a semantic identifier in JSON-LD contexts.
-     *
-     * @see https://w3id.org/idsa/v4.1/HTTP
-     * @see https://github.com/International-Data-Spaces-Association/InformationModel
-     */
-    readonly HTTP: "https://w3id.org/idsa/v4.1/HTTP";
-    /**
-     * HTTPS endpoint (IDSA W3ID v4.1).
+     * 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.
      *
-     * Persistent identifier for HTTPS-based secure data access endpoints.
-     * This W3ID URL is used as a semantic identifier in JSON-LD contexts.
+     * 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
      *
-     * @see https://w3id.org/idsa/v4.1/HTTPS
-     * @see https://github.com/International-Data-Spaces-Association/InformationModel
+     * @see https://github.com/twinfoundation/rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md#data-transfer-profile-vocabulary
+     * @see https://github.com/twinfoundation/rfcs/blob/main/rfcs/data-space-connector/001-data-space-connector-query.md
      */
-    readonly HTTPS: "https://w3id.org/idsa/v4.1/HTTPS";
+    readonly HttpsQueryEndpoint: "https://schema.twindev.org/dspace/v1/Https-Query-Endpoint";
     /**
-     * HTTPS Activity Stream endpoint (Activity Streams 2.0).
+     * 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.
      *
-     * Used for ActivityPub/Activity Streams protocol endpoints.
-     * This is used in PUSH transfer scenarios where the provider
-     * sends data to the consumer's Activity Stream inbox.
+     * 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
      *
+     * @see https://github.com/twinfoundation/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/
      */
-    readonly HttpsActivityStream: "Https-Activity-Stream-Endpoint";
+    readonly HttpsActivityStreamEndpoint: "https://schema.twindev.org/dspace/v1/Https-Activity-Stream-Endpoint";
     /**
-     * Amazon S3 bucket endpoint.
-     *
-     * Used for S3-based data transfer (both PULL and PUSH).
-     * Note: Not currently part of IDSA W3ID namespace.
+     * HTTP endpoint (IDSA W3ID v4.1).
      *
-     * @see https://aws.amazon.com/s3/
-     */
-    readonly S3: "S3";
-    /**
-     * Azure Blob Storage endpoint.
+     * Persistent identifier for HTTP-based data access endpoints.
+     * This W3ID URL is used as a semantic identifier in JSON-LD contexts.
      *
-     * Used for Azure cloud storage-based data transfer.
-     * Note: Not currently part of IDSA W3ID namespace.
+     * Note: For TWIN-specific implementations, prefer using `HttpsQueryEndpoint`.
+     * This constant is provided for interoperability with IDSA-based systems.
      *
-     * @see https://azure.microsoft.com/en-us/products/storage/blobs
+     * @see https://w3id.org/idsa/v4.1/HTTP
+     * @see https://github.com/International-Data-Spaces-Association/InformationModel
      */
-    readonly AzureStorage: "AzureStorage";
+    readonly HTTP: "https://w3id.org/idsa/v4.1/HTTP";
     /**
-     * Apache Kafka topic endpoint.
-     *
-     * Used for streaming data via Kafka message broker.
-     * Note: Not currently part of IDSA W3ID namespace.
+     * HTTPS endpoint (IDSA W3ID v4.1).
      *
-     * @see https://kafka.apache.org/
-     */
-    readonly Kafka: "Kafka";
-    /**
-     * SFTP (SSH File Transfer Protocol) endpoint.
+     * Persistent identifier for HTTPS-based secure data access endpoints.
+     * This W3ID URL is used as a semantic identifier in JSON-LD contexts.
      *
-     * Used for secure file transfer over SSH.
-     * Note: Not currently part of IDSA W3ID namespace.
+     * Note: For TWIN-specific implementations, prefer using `HttpsQueryEndpoint`.
+     * This constant is provided for interoperability with IDSA-based systems.
      *
-     * @see https://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol
+     * @see https://w3id.org/idsa/v4.1/HTTPS
+     * @see https://github.com/International-Data-Spaces-Association/InformationModel
      */
-    readonly SFTP: "SFTP";
+    readonly HTTPS: "https://w3id.org/idsa/v4.1/HTTPS";
 };
 /**
  * Type representing all valid Dataspace Protocol endpoint types.
+ *
+ * All values are valid URIs as required by the DS Protocol JSON-LD context
+ * which defines endpointType as @type:@vocab.
+ *
+ * Includes:
+ * - TWIN RFC 006 types: HttpsQueryEndpoint, HttpsActivityStreamEndpoint
+ * - IDSA W3ID types: HTTP, HTTPS
  */
 export type DataspaceProtocolEndpointType = (typeof DataspaceProtocolEndpointType)[keyof typeof DataspaceProtocolEndpointType];

package/docs/changelog.md

@@ -1,5 +1,39 @@
 # Changelog
 
+## [0.0.3-next.29](https://github.com/twinfoundation/standards/compare/standards-dataspace-protocol-v0.0.3-next.28...standards-dataspace-protocol-v0.0.3-next.29) (2026-02-03)
+
+
+### Features
+
+* adding twin protocol endpoins constants ([#133](https://github.com/twinfoundation/standards/issues/133)) ([3592c81](https://github.com/twinfoundation/standards/commit/3592c811c368b23046ef8b60f6cca0eb8356ad87))
+
+
+### Dependencies
+
+* The following workspace dependencies were updated
+  * dependencies
+    * @twin.org/standards-w3c-dcat bumped from 0.0.3-next.28 to 0.0.3-next.29
+    * @twin.org/standards-w3c-odrl bumped from 0.0.3-next.28 to 0.0.3-next.29
+  * devDependencies
+    * @twin.org/standards-ld-contexts bumped from 0.0.3-next.28 to 0.0.3-next.29
+
+## [0.0.3-next.28](https://github.com/twinfoundation/standards/compare/standards-dataspace-protocol-v0.0.3-next.27...standards-dataspace-protocol-v0.0.3-next.28) (2026-02-03)
+
+
+### Miscellaneous Chores
+
+* **standards-dataspace-protocol:** Synchronize repo versions
+
+
+### Dependencies
+
+* The following workspace dependencies were updated
+  * dependencies
+    * @twin.org/standards-w3c-dcat bumped from 0.0.3-next.27 to 0.0.3-next.28
+    * @twin.org/standards-w3c-odrl bumped from 0.0.3-next.27 to 0.0.3-next.28
+  * devDependencies
+    * @twin.org/standards-ld-contexts bumped from 0.0.3-next.27 to 0.0.3-next.28
+
 ## [0.0.3-next.27](https://github.com/twinfoundation/standards/compare/standards-dataspace-protocol-v0.0.3-next.26...standards-dataspace-protocol-v0.0.3-next.27) (2026-02-03)
 
 

package/docs/reference/type-aliases/DataspaceProtocolEndpointType.md

@@ -3,3 +3,10 @@
 > **DataspaceProtocolEndpointType** = *typeof* [`DataspaceProtocolEndpointType`](../variables/DataspaceProtocolEndpointType.md)\[keyof *typeof* [`DataspaceProtocolEndpointType`](../variables/DataspaceProtocolEndpointType.md)\]
 
 Type representing all valid Dataspace Protocol endpoint types.
+
+All values are valid URIs as required by the DS Protocol JSON-LD context
+which defines endpointType as @type:@vocab.
+
+Includes:
+- TWIN RFC 006 types: HttpsQueryEndpoint, HttpsActivityStreamEndpoint
+- IDSA W3ID types: HTTP, HTTPS

package/docs/reference/variables/DataspaceProtocolEndpointType.md

@@ -2,115 +2,95 @@
 
 > `const` **DataspaceProtocolEndpointType**: `object`
 
-W3ID-based endpoint type identifiers from the IDSA namespace.
+TWIN Data Space Protocol Profile endpoint type identifiers.
 
-These persistent identifiers follow the W3ID (https://w3id.org) system
-used by the International Data Spaces Association (IDSA) to provide
-stable, semantic identifiers for data space endpoint types.
+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.
 
-W3ID URLs are designed to be:
-- Persistent (permanent identifiers that don't break)
-- Resolvable (can be dereferenced to get definitions)
-- Semantic (provide meaning through linked data)
+The TWIN vocabulary uses persistent identifiers under the
+https://schema.twindev.org namespace to provide stable, semantic
+identifiers for data space endpoint types.
 
 References:
-- IDSA W3ID Namespace: https://w3id.org/idsa/
-- IDS Information Model: https://github.com/International-Data-Spaces-Association/InformationModel
-- DSP Specification: https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/
+- TWIN RFC 006: https://github.com/twinfoundation/rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md
+- TWIN DS Protocol Context: https://github.com/twinfoundation/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/twinfoundation/rfcs/blob/main/rfcs/data-space-connector/001-data-space-connector-query.md
 
 ## Type Declaration
 
-### HTTP
-
-> `readonly` **HTTP**: `"https://w3id.org/idsa/v4.1/HTTP"` = `"https://w3id.org/idsa/v4.1/HTTP"`
-
-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.
-
-#### See
-
- - https://w3id.org/idsa/v4.1/HTTP
- - https://github.com/International-Data-Spaces-Association/InformationModel
+### HttpsQueryEndpoint
 
-### HTTPS
+> `readonly` **HttpsQueryEndpoint**: `"https://schema.twindev.org/dspace/v1/Https-Query-Endpoint"` = `"https://schema.twindev.org/dspace/v1/Https-Query-Endpoint"`
 
-> `readonly` **HTTPS**: `"https://w3id.org/idsa/v4.1/HTTPS"` = `"https://w3id.org/idsa/v4.1/HTTPS"`
+HTTPS Query Endpoint (TWIN DS Profile).
 
-HTTPS endpoint (IDSA W3ID v4.1).
+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.
 
-Persistent identifier for HTTPS-based secure data access endpoints.
-This W3ID URL is used as a semantic identifier in JSON-LD contexts.
+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
 
 #### See
 
- - https://w3id.org/idsa/v4.1/HTTPS
- - https://github.com/International-Data-Spaces-Association/InformationModel
+ - https://github.com/twinfoundation/rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md#data-transfer-profile-vocabulary
+ - https://github.com/twinfoundation/rfcs/blob/main/rfcs/data-space-connector/001-data-space-connector-query.md
+
+### HttpsActivityStreamEndpoint
 
-### HttpsActivityStream
+> `readonly` **HttpsActivityStreamEndpoint**: `"https://schema.twindev.org/dspace/v1/Https-Activity-Stream-Endpoint"` = `"https://schema.twindev.org/dspace/v1/Https-Activity-Stream-Endpoint"`
 
-> `readonly` **HttpsActivityStream**: `"Https-Activity-Stream-Endpoint"` = `"Https-Activity-Stream-Endpoint"`
+HTTPS Activity Stream Endpoint (TWIN DS Profile).
 
-HTTPS Activity Stream endpoint (Activity Streams 2.0).
+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.
 
-Used for ActivityPub/Activity Streams protocol endpoints.
-This is used in PUSH transfer scenarios where the provider
-sends data to the consumer's Activity Stream inbox.
+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
 
 #### See
 
+ - https://github.com/twinfoundation/rfcs/blob/main/rfcs/data-space-protocol/006-data-space-protocol-profile.md#data-transfer-profile-vocabulary
  - https://www.w3.org/TR/activitystreams-core/
  - https://www.w3.org/TR/activitypub/
 
-### S3
-
-> `readonly` **S3**: `"S3"` = `"S3"`
-
-Amazon S3 bucket endpoint.
-
-Used for S3-based data transfer (both PULL and PUSH).
-Note: Not currently part of IDSA W3ID namespace.
-
-#### See
-
-https://aws.amazon.com/s3/
+### HTTP
 
-### AzureStorage
+> `readonly` **HTTP**: `"https://w3id.org/idsa/v4.1/HTTP"` = `"https://w3id.org/idsa/v4.1/HTTP"`
 
-> `readonly` **AzureStorage**: `"AzureStorage"` = `"AzureStorage"`
+HTTP endpoint (IDSA W3ID v4.1).
 
-Azure Blob Storage endpoint.
+Persistent identifier for HTTP-based data access endpoints.
+This W3ID URL is used as a semantic identifier in JSON-LD contexts.
 
-Used for Azure cloud storage-based data transfer.
-Note: Not currently part of IDSA W3ID namespace.
+Note: For TWIN-specific implementations, prefer using `HttpsQueryEndpoint`.
+This constant is provided for interoperability with IDSA-based systems.
 
 #### See
 
-https://azure.microsoft.com/en-us/products/storage/blobs
-
-### Kafka
-
-> `readonly` **Kafka**: `"Kafka"` = `"Kafka"`
-
-Apache Kafka topic endpoint.
-
-Used for streaming data via Kafka message broker.
-Note: Not currently part of IDSA W3ID namespace.
-
-#### See
+ - https://w3id.org/idsa/v4.1/HTTP
+ - https://github.com/International-Data-Spaces-Association/InformationModel
 
-https://kafka.apache.org/
+### HTTPS
 
-### SFTP
+> `readonly` **HTTPS**: `"https://w3id.org/idsa/v4.1/HTTPS"` = `"https://w3id.org/idsa/v4.1/HTTPS"`
 
-> `readonly` **SFTP**: `"SFTP"` = `"SFTP"`
+HTTPS endpoint (IDSA W3ID v4.1).
 
-SFTP (SSH File Transfer Protocol) endpoint.
+Persistent identifier for HTTPS-based secure data access endpoints.
+This W3ID URL is used as a semantic identifier in JSON-LD contexts.
 
-Used for secure file transfer over SSH.
-Note: Not currently part of IDSA W3ID namespace.
+Note: For TWIN-specific implementations, prefer using `HttpsQueryEndpoint`.
+This constant is provided for interoperability with IDSA-based systems.
 
 #### See
 
-https://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol
+ - https://w3id.org/idsa/v4.1/HTTPS
+ - https://github.com/International-Data-Spaces-Association/InformationModel

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@twin.org/standards-dataspace-protocol",
-	"version": "0.0.3-next.27",
+	"version": "0.0.3-next.29",
 	"description": "Models which define the structure of Dataspace Protocol",
 	"repository": {
 		"type": "git",
@@ -17,8 +17,8 @@
 		"@twin.org/core": "next",
 		"@twin.org/data-core": "next",
 		"@twin.org/data-json-ld": "next",
-		"@twin.org/standards-w3c-dcat": "0.0.3-next.27",
-		"@twin.org/standards-w3c-odrl": "0.0.3-next.27",
+		"@twin.org/standards-w3c-dcat": "0.0.3-next.29",
+		"@twin.org/standards-w3c-odrl": "0.0.3-next.29",
 		"@twin.org/web": "next"
 	},
 	"main": "./dist/es/index.js",