Home › Rulebook › R6

R6Value creation

This chapter in shortCatalogues, publication, services, federation, community and participant satisfaction.

DSSC dimension: Value creation 6 topics ~3 min readv1.0 draft

Highlight what applies to

R6.1Catalogues

Applies toData providersData consumersService & compute providers

In shortTwo catalogues, one for data and one for services, searchable in the portal and readable by machines.

Catalogues

Data catalogue: all offers, searchable in the portal and available in machine-readable form (DCAT-AP and Ocean Enterprise metadata).
Service catalogue: algorithms and value-creation services, with their service terms.
Federated offers are shown with their data space of origin and are clearly separated from EMPOWER-X's own offers.

What every offer must contain

Title and description; data holder and provider; licence (R3.4); access level (R5.2); personal-data flag; data model and version; update frequency; known limitations; for algorithms, the input they expect and what they return. The 12-point checklist on Publish an offer turns this into checks.

Machine-readableoffers/offer-profile.shacl.ttl

R6.2Publication rules

Applies toData providers

In shortPublish real things, once, pointing to production. The checklist on Publish an offer is how it is checked.

Publication rules

Offers in production point to production endpoints (node.empower-x.io), never to development or internal addresses.
Each offer is published once in production. If an offer also exists on a test network, its description says which network each listing belongs to.
Offers must describe real data or services. Example offers are published only in the test environment.
The operator reviews new offers against that checklist within 5 working days and may hide offers that do not comply until they are fixed.

Machine-readableoffers/offer-profile.shacl.ttl

R6.3Service management

Applies toService & compute providers

In shortEvery service has a version, an owner and a support contact, and changes are announced in advance.

Service management

Services have a version, an owner and a support contact. Breaking changes are announced 30 days ahead; retired services stay listed as deprecated for 90 days.

R6.4Federation

Applies toEveryone

In shortEMPOWER-X connects to another data space only under a written agreement, and keeps its offers separate.

Federation agreements

EMPOWER-X federates with another data space only under a written federation agreement, which covers at least:

Mutual authorisation of nodes, so that each side's node is on the other's list of authorised nodes.
Catalogue visibility in both directions, including any labels or filters needed for offers to appear.
Recognition of each other's participant credentials, or the rules for cross-onboarding.
Which rules, licences and support apply to each side's offers.
A joint test that proves an order and use in each direction.

Federated offers

Federated offers remain under the rules and licences of their data space of origin. EMPOWER-X does not change their licences or descriptions.
Federated offers, their orders and their tests are not counted as EMPOWER-X activity.
Problems with a federated offer are referred to the data space of origin.

Current federations

EMPOWER-X is federating with the SENSE data space. Federation is reported as bidirectional only once all elements of R6.4 are in place and confirmed in writing by both parties.

R6.5Community and reuse

Applies toEveryone

In shortThe list of participants and roles is shared with participants, the community meets at least once a year, and reuse of data is measured.

Community

The Governance Authority keeps the list of participants and their roles available to participants, holds an open community meeting at least once a year, and invites participants to propose use cases and services.

Data reuse

The Governance Authority reports every year how many offers are used by more than one consumer, as a measure of data reuse.

R6.6Participant satisfaction

Applies toEveryone

In shortFour short surveys, and results that come back to participants with an action plan.

Participant satisfaction

Survey	Sent to	When
Onboarding survey	New participants	30 days after activation
Use pulse	Consumers and providers	After a participant's first completed use, and at most once a quarter after that
Annual survey	All participants	Every year before the General Assembly
Exit survey	Departing participants	On offboarding

Surveys are sent automatically from the portal where possible, and answers are handled under the GDPR. Results are presented at the General Assembly together with an action plan, and the follow-up of that plan is reported the next year. Each survey is a short questionnaire sent from the portal.