Publishing and Accessing Services via EDC

[albert-lopez]

Hi EDC team,

I have a few questions regarding the publication of services exposed via REST API and its consumption:

Catalog representation of the services:
I saw in this post that a service can be published as an Asset, but doing this, the service is published in the catalog as a dcat:Dataset. I can include custom metadata in the properties to identify it as a "dcat:DataService" however, this metadata is only meaningful within my own ecosystem and breaks interoperability with other data spaces that expect actual dcat:DataService entries in the catalog.
Is there a recommended way to publish REST-based services as dcat:DataService in the catalog? Are there any plans to support this natively?

Configuring service access in the dataAddress
How I should define the dataAddress of the Asset to make a REST API consumable through the data plane? I have seen parameters as proxyMethod, proxyBody, proxyPath, and proxyQueryParams but I don't know how they should be used. to enable access to a service that uses GET / POST method with query parameters?
Are there best practices or examples available for configuring such service-style access in the connector?

Support for WebSocket-based services
Is there current support, or a roadmap, for enabling access to services that use WebSocket protocols through the EDC data plane? I have seen HttpData-PULL-Websocket but If i try to use the connector says that the dataplane is not available.**

Thanks in advance for your help!

[jimmarino]

Hi EDC team,

I have a few questions regarding the publication of services exposed via REST API and its consumption:

Catalog representation of the services: I saw in this post that a service can be published as an Asset, but doing this, the service is published in the catalog as a dcat:Dataset. I can include custom metadata in the properties to identify it as a "dcat:DataService" however, this metadata is only meaningful within my own ecosystem and breaks interoperability with other data spaces that expect actual dcat:DataService entries in the catalog. Is there a recommended way to publish REST-based services as dcat:DataService in the catalog? Are there any plans to support this natively?

EDC concepts such as Asset are mapped to DSP terms such as Dataset. Please read the EDC documentation and DSP specifications to understand how this works. Custom vocabularies are supported, but they will only be useful in the context of your dataspace.

Configuring service access in the dataAddress How I should define the dataAddress of the Asset to make a REST API consumable through the data plane? I have seen parameters as proxyMethod, proxyBody, proxyPath, and proxyQueryParams but I don't know how they should be used. to enable access to a service that uses GET / POST method with query parameters? Are there best practices or examples available for configuring such service-style access in the connector?

Please look at the documentation and samples. There is plenty of information in those sources.

Support for WebSocket-based services Is there current support, or a roadmap, for enabling access to services that use WebSocket protocols through the EDC data plane? I have seen HttpData-PULL-Websocket but If i try to use the connector says that the dataplane is not available.**

There are no plans and it is highly unlikely this will be done. We are encouraging other projects to create their own data planes since requirements for data transfers tend to be very specific.

[albert-lopez]

Hi EDC team,
I have a few questions regarding the publication of services exposed via REST API and its consumption:
Catalog representation of the services: I saw in this post that a service can be published as an Asset, but doing this, the service is published in the catalog as a dcat:Dataset. I can include custom metadata in the properties to identify it as a "dcat:DataService" however, this metadata is only meaningful within my own ecosystem and breaks interoperability with other data spaces that expect actual dcat:DataService entries in the catalog. Is there a recommended way to publish REST-based services as dcat:DataService in the catalog? Are there any plans to support this natively?

EDC concepts such as Asset are mapped to DSP terms such as Dataset. Please read the EDC documentation and DSP specifications to understand how this works. Custom vocabularies are supported, but they will only be useful in the context of your dataspace.

I understand that using @type = "Asset" when calling api/management/v3/assets results in an entry that is mapped to dcat:Dataset. What I would like to know is whether there is a predefined @type (I couldn't find one in https://w3id.org/edc/connector/management/v0.0.1) that maps to dcat:DataService, which is the standard way to represent a service in DCAT.

In other words, what is the recommended approach to create a catalog entry for a service, instead of relying on the workaround of registering it as an Asset? I’ve reviewed the documentation but couldn’t find a clear answer on this.

Configuring service access in the dataAddress How I should define the dataAddress of the Asset to make a REST API consumable through the data plane? I have seen parameters as proxyMethod, proxyBody, proxyPath, and proxyQueryParams but I don't know how they should be used. to enable access to a service that uses GET / POST method with query parameters? Are there best practices or examples available for configuring such service-style access in the connector?

Please look at the documentation and samples. There is plenty of information in those sources.
I have seen that the following configuration works:

"dataAddress": {
"@type": "DataAddress",
"type": "HttpData",
"baseUrl": "http://example:5050/suma",
"proxyPath": "true",
"proxyQueryParams": "true",
"proxyBody": "true",
"proxyMethod": "true"
}

However, according to the connector's code, all the proxy* parameters have been deprecated since release 0.12.0 (HttpDataAddress.java). But if I don't use them, it doesn't work.
What is the recommended approach now?
The MVD, despite using snapshot 0.13.0, still relies on these parameters.

Support for WebSocket-based services Is there current support, or a roadmap, for enabling access to services that use WebSocket protocols through the EDC data plane? I have seen HttpData-PULL-Websocket but If i try to use the connector says that the dataplane is not available.**

There are no plans and it is highly unlikely this will be done. We are encouraging other projects to create their own data planes since requirements for data transfers tend to be very specific.

Ok .

Thanks in advance

[jimmarino]

Hi EDC team,
I have a few questions regarding the publication of services exposed via REST API and its consumption:
Catalog representation of the services: I saw in this post that a service can be published as an Asset, but doing this, the service is published in the catalog as a dcat:Dataset. I can include custom metadata in the properties to identify it as a "dcat:DataService" however, this metadata is only meaningful within my own ecosystem and breaks interoperability with other data spaces that expect actual dcat:DataService entries in the catalog. Is there a recommended way to publish REST-based services as dcat:DataService in the catalog? Are there any plans to support this natively?

EDC concepts such as Asset are mapped to DSP terms such as Dataset. Please read the EDC documentation and DSP specifications to understand how this works. Custom vocabularies are supported, but they will only be useful in the context of your dataspace.

I understand that using @type = "Asset" when calling api/management/v3/assets results in an entry that is mapped to dcat:Dataset. What I would like to know is whether there is a predefined @type (I couldn't find one in https://w3id.org/edc/connector/management/v0.0.1) that maps to dcat:DataService, which is the standard way to represent a service in DCAT.

In other words, what is the recommended approach to create a catalog entry for a service, instead of relying on the workaround of registering it as an Asset? I’ve reviewed the documentation but couldn’t find a clear answer on this.

Configuring service access in the dataAddress How I should define the dataAddress of the Asset to make a REST API consumable through the data plane? I have seen parameters as proxyMethod, proxyBody, proxyPath, and proxyQueryParams but I don't know how they should be used. to enable access to a service that uses GET / POST method with query parameters? Are there best practices or examples available for configuring such service-style access in the connector?

Please take a look again at the documentation and the DSP specification. A DataService is generated based on the connector URL. It is not something added through the Management API.

Please look at the documentation and samples. There is plenty of information in those sources.
I have seen that the following configuration works:

"dataAddress": { "@type": "DataAddress", "type": "HttpData", "baseUrl": "http://example:5050/suma", "proxyPath": "true", "proxyQueryParams": "true", "proxyBody": "true", "proxyMethod": "true" }

However, according to the connector's code, all the proxy* parameters have been deprecated since release 0.12.0 (HttpDataAddress.java). But if I don't use them, it doesn't work. What is the recommended approach now? The MVD, despite using snapshot 0.13.0, still relies on these parameters.

Support for WebSocket-based services Is there current support, or a roadmap, for enabling access to services that use WebSocket protocols through the EDC data plane? I have seen HttpData-PULL-Websocket but If i try to use the connector says that the dataplane is not available.**

You can create your own data plane or extend the data plane framework. The latter is as easy as creating a JAX-RS controller and registering it in the data plane runtime.

[albert-lopez]

I found the information you mentioned in the IDSA documentation about Data Services specifying an endpoint supporting the Dataspace Protocol, such as a Connector.

Now, I have a follow-up question: Is it possible to publish value-added services like AI or data processing services in the catalog? If so, how should this be done while ensuring interoperability with other data spaces?

Thanks again for your help!

[jimmarino]

I don't know what IDSA documentation you are referring to, but the only official EDC documentation is the DSP Specification and the documentation linked from here.

You can model your AI or other services as Assets. This scenario is also described in the EDC documentation. Otherwise if you want to create custom catalog resources, you could potentially either extend the EDC or use management domains (again, described in the EDC documentation). However, the former will not be interoperable in the sense that clients can understand the custom extensions.

You will need to do your own investigation on how to extend the EDC with custom resource types if you chose to go that direction as that type of use case does not promote interop.