Re: [dataspace-protocol-base-dev] About the distribution.format property

["Weiss, Arno" <arno.weiss@xxxxxxx>]

Hi José,

format maps to dct:format, as you can see in the context [1]. DSP is agnostic to its content and adopters need to decide how to use it. In short: you have identified an extension point for a transport profile - more on that in the best practices [2]. 

Cheers,

Arno

[1] https://w3id.org/dspace/2025/1/context.jsonld

[2] BestPractices/profiling/data-transfer-profiles at main · eclipse-dataspace-protocol-base/BestPractices

---

From: dataspace-protocol-base-dev <dataspace-protocol-base-dev-bounces@xxxxxxxxxxx> on behalf of José Cantera via dataspace-protocol-base-dev <dataspace-protocol-base-dev@xxxxxxxxxxx>
Sent: Wednesday, 12 November 2025 13:42
To: dataspace-protocol-base developer discussions <dataspace-protocol-base-dev@xxxxxxxxxxx>
Cc: José Cantera <jose.cantera@xxxxxxxx>
Subject: [dataspace-protocol-base-dev] About the distribution.format property

 

Hello,

Checking https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/#transfer-request-message it seems that `format` is being used to mean "delivery method or access method" instead of media type (there is another property in DCAT also for that) ... is that correct?

 If so are there any specified values or ontology that can be use to represent possible values? 

Thank you very much

All the best

--

José Manuel Cantera Fonseca

IOTA

Senior Architect & Project Lead