# 2024-12-01 11:41:19.287266 UTC (+0000)
Introducing Gopher Dataspaces
You hate yourself?
Get into WWW Dataspaces:
https://github.com/International-Data-Spaces-Association/ids-specification
> The specifications are organized into the following documents:
>
> Dataspace Model and Dataspace Terminology documents that define key terms.
> Common Functionalities and their Binding in HTTPS declares cross-cutting functions as, e.g., the declaration of supported versions of this Dataspace Protocol.
> Catalog Protocol and Catalog HTTPS Binding documents that define how DCAT Catalogs are published and accessed as HTTPS endpoints respectively.
> Contract Negotiation Protocol and Contract Negotiation HTTPS Binding documents that define how Contract Negotiations are conducted and requested via HTTPS endpoints.
> Transfer Process Protocol and Transfer Process HTTPS Binding documents that define how Transfer Processes using a given data transfer protocol are governed via HTTPS endpoints.
>
> This specification does not cover the data transfer process as such.
>
> While the data transfer is controlled by the Transfer Process Protocol mentioned above, e.g. the initation of the transfer channels or their decomissioning, the data transfer itself and especially the handling of technical exceptions is an obligation to the Transport Protocol.
>
> As an implication, the data transfer can be conducted in a separated process if required, as long as this process is to the specified extend controlled by the Transfer Process Protocol.
>
> Nevertheless, illustrative message examples are provided in the Transfer Process Protocol section. The best practices section may contain further non-normative examples and explanations.
You love yourself?
Get into Gopher Dataspaces:
gophers://bitreich.org/1/dataspace
You are welcome. :---)
Sincerely yours,
20h
Chief Simplicity Officer (CSO)
