@twin.org/dataspace-models 0.0.3-next.27 → 0.0.3-next.28

package/dist/es/models/dataspaceTransferFormat.js

@@ -2,7 +2,7 @@
 // SPDX-License-Identifier: Apache-2.0.
 /**
  * TWIN transfer format identifiers used in TransferRequestMessage.format.
- * Follows the Eclipse EDC canonical pattern: <DestinationType-FlowType>.
+ * Follows the Eclipse EDC canonical pattern: DestinationType-FlowType.
  * See RFC-007 Data Transfer Profile.
  */
 // eslint-disable-next-line @typescript-eslint/naming-convention

package/dist/es/models/dataspaceTransferFormat.js.map

@@ -1 +1 @@
-{"version":3,"file":"dataspaceTransferFormat.js","sourceRoot":"","sources":["../../../src/models/dataspaceTransferFormat.ts"],"names":[],"mappings":"AAAA,gCAAgC;AAChC,uCAAuC;AAEvC;;;;GAIG;AACH,gEAAgE;AAChE,MAAM,CAAC,MAAM,uBAAuB,GAAG;IACtC;;;OAGG;IACH,aAAa,EAAE,gBAAgB;IAE/B;;;;OAIG;IACH,aAAa,EAAE,gBAAgB;IAE/B;;;;OAIG;IACH,aAAa,EAAE,gBAAgB;CACtB,CAAC","sourcesContent":["// Copyright 2025 IOTA Stiftung.\n// SPDX-License-Identifier: Apache-2.0.\n\n/**\n * TWIN transfer format identifiers used in TransferRequestMessage.format.\n * Follows the Eclipse EDC canonical pattern: <DestinationType-FlowType>.\n * See RFC-007 Data Transfer Profile.\n */\n// eslint-disable-next-line @typescript-eslint/naming-convention\nexport const DataspaceTransferFormat = {\n\t/**\n\t * PULL mode: consumer queries data via a bearer-token-protected endpoint.\n\t * Data flows: Consumer GET provider endpoint (with token).\n\t */\n\tHttpProxyPull: \"HttpProxy-PULL\",\n\n\t/**\n\t * Consumer-initiated PUSH mode: consumer supplies their /inbox endpoint in the\n\t * TransferRequestMessage. Provider pushes ActivityStreams objects to that endpoint.\n\t * Data flows: Provider POST to consumer's /inbox.\n\t */\n\tHttpProxyPush: \"HttpProxy-PUSH\",\n\n\t/**\n\t * Provider-initiated PUSH mode (inverted flow): consumer supplies no dataAddress.\n\t * Provider returns its own /inbox URL + signed JWT. Consumer then posts data there.\n\t * Data flows: Consumer POST to provider's /inbox.\n\t */\n\tHttpProxyPost: \"HttpProxy-POST\"\n} as const;\n\n/**\n * Type for the DataspaceTransferFormat const values.\n */\nexport type DataspaceTransferFormat =\n\t(typeof DataspaceTransferFormat)[keyof typeof DataspaceTransferFormat];\n"]}
+{"version":3,"file":"dataspaceTransferFormat.js","sourceRoot":"","sources":["../../../src/models/dataspaceTransferFormat.ts"],"names":[],"mappings":"AAAA,gCAAgC;AAChC,uCAAuC;AAEvC;;;;GAIG;AACH,gEAAgE;AAChE,MAAM,CAAC,MAAM,uBAAuB,GAAG;IACtC;;;OAGG;IACH,aAAa,EAAE,gBAAgB;IAE/B;;;;OAIG;IACH,aAAa,EAAE,gBAAgB;IAE/B;;;;OAIG;IACH,aAAa,EAAE,gBAAgB;CACtB,CAAC","sourcesContent":["// Copyright 2025 IOTA Stiftung.\n// SPDX-License-Identifier: Apache-2.0.\n\n/**\n * TWIN transfer format identifiers used in TransferRequestMessage.format.\n * Follows the Eclipse EDC canonical pattern: DestinationType-FlowType.\n * See RFC-007 Data Transfer Profile.\n */\n// eslint-disable-next-line @typescript-eslint/naming-convention\nexport const DataspaceTransferFormat = {\n\t/**\n\t * PULL mode: consumer queries data via a bearer-token-protected endpoint.\n\t * Data flows: Consumer GET provider endpoint (with token).\n\t */\n\tHttpProxyPull: \"HttpProxy-PULL\",\n\n\t/**\n\t * Consumer-initiated PUSH mode: consumer supplies their /inbox endpoint in the\n\t * TransferRequestMessage. Provider pushes ActivityStreams objects to that endpoint.\n\t * Data flows: Provider POST to consumer's /inbox.\n\t */\n\tHttpProxyPush: \"HttpProxy-PUSH\",\n\n\t/**\n\t * Provider-initiated PUSH mode (inverted flow): consumer supplies no dataAddress.\n\t * Provider returns its own /inbox URL + signed JWT. Consumer then posts data there.\n\t * Data flows: Consumer POST to provider's /inbox.\n\t */\n\tHttpProxyPost: \"HttpProxy-POST\"\n} as const;\n\n/**\n * Type for the DataspaceTransferFormat const values.\n */\nexport type DataspaceTransferFormat =\n\t(typeof DataspaceTransferFormat)[keyof typeof DataspaceTransferFormat];\n"]}

package/dist/types/models/dataspaceTransferFormat.d.ts

@@ -1,6 +1,6 @@
 /**
  * TWIN transfer format identifiers used in TransferRequestMessage.format.
- * Follows the Eclipse EDC canonical pattern: <DestinationType-FlowType>.
+ * Follows the Eclipse EDC canonical pattern: DestinationType-FlowType.
  * See RFC-007 Data Transfer Profile.
  */
 export declare const DataspaceTransferFormat: {

package/docs/changelog.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## [0.0.3-next.28](https://github.com/iotaledger/twin-dataspace/compare/dataspace-models-v0.0.3-next.27...dataspace-models-v0.0.3-next.28) (2026-05-12)
+
+
+### Features
+
+* typescript 6 update ([340f10e](https://github.com/iotaledger/twin-dataspace/commit/340f10e4767f6285c694938944f7e044474f9aaa))
+
+
+### Bug Fixes
+
+* docs ([652f4f2](https://github.com/iotaledger/twin-dataspace/commit/652f4f2fec8601bb3772e054b2c823f599ef68dc))
+
 ## [0.0.3-next.27](https://github.com/iotaledger/twin-dataspace/compare/dataspace-models-v0.0.3-next.26...dataspace-models-v0.0.3-next.27) (2026-05-08)
 
 

package/docs/reference/variables/DataspaceTransferFormat.md

@@ -3,7 +3,7 @@
 > `const` **DataspaceTransferFormat**: `object`
 
 TWIN transfer format identifiers used in TransferRequestMessage.format.
-Follows the Eclipse EDC canonical pattern: <DestinationType-FlowType>.
+Follows the Eclipse EDC canonical pattern: DestinationType-FlowType.
 See RFC-007 Data Transfer Profile.
 
 ## Type Declaration

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@twin.org/dataspace-models",
-	"version": "0.0.3-next.27",
+	"version": "0.0.3-next.28",
 	"description": "Defines shared entities, interfaces, and data types used by control plane and data plane components.",
 	"repository": {
 		"type": "git",