Endpoint (proxy): /api/connector-1
Start by pasting a valid resource URL to chain the full analysis.
Recommended formats for analysis: `.pdf`, `.txt`, `.md`, `.csv`, `.xls`, `.xlsx`, `.doc`, `.docx`.
Paste a valid URL to generate the analysis and metadata suggestions automatically.
Analyze a URL to propose a policy aligned with the resource content.
Publishing here creates an asset in the DataSpaceHealth catalogue. To also appear in HealthData@EU, mark it in the "Destination" column: the bridge picks it up, which is a separate process.
One query by a standard code reaches nodes that call it differently.
From this connector you can accept policies and download resources after a completed negotiation.
Ledger across all deployed connectors.
Append-only and hash-chained: a line that was changed or removed breaks the chain.
Review who is requesting provider, consumer, or both access. The connector is deployed only after approval.
Approved connectors with identity, contact email and assigned operational role.
This section is only served to the owner of an entity connector. The profile you assign cannot exceed the one this connector has declared.
| Name | Requested | Profile | Action |
|---|
| Name | Membership | Profile | Status |
|---|
This platform routes the request and records the answer. The holder of the data decides.
Participant self-assessment, the node GDPR role and incident notification. Kept apart from the publishing flow.
Registration number: · Issuer (notary):
Loading…
The headquarters address is the legal address.
Article 12 of the draft. A significant incident alerts the administrator and the node's security contacts.
This node declares its GDPR role for the processing it exposes to the data space.