Enabling Interoperable Europe

The SEMIC Support Centre is the first step on a journey to become an interoperable European administration. In line with the Interoperable Europe Act, the SEMIC community stands for co-creation and sharing best practices. The Support Center is also home to a community of adopters that share tooling, standards and good practices to promote semantic interoperability.  

Who is it for?

Are you a policy officer or a technical expert working on data sharing and reuse? SEMIC and its support centre offers several services that aim to help public administrations share their experience with each other and help each other out in making the single market of data a reality.

In the spotlight: SEMIC Roadshow in Romania

On 9 and 10 March 2023, our colleagues from Romania hosted the SEMIC Team in Bucharest to exchange good practices and learn from each other on various interoperability topics. Find out more about it here.

SEMIC Services

SEMIC's goal is to deliver pragmatic support to help build an interoperable Europe.

SEMIC supported DG GROW in evaluating the needs from Member States in harmonised semantics for tourism data. More than 80 experts from various tourism activities and European countries to shared their views. Learn more.

The European Railway Agency (ERA) implemented an “alert change” use case based on the SEMIC incubated Linked Data Event Stream (LDES) technology. Before, ERA and its customers struggled to synchronise data about the modifications occurring on the European railway infrastructures. Learn more.

Datavindplaats (the place to find data) is the first initiative in Flanders combining public and private datasets and APIs in one place. Thanks to SEMIC specifications, all metadata have been bridged semantically into the consolidated DCAT (2.0) standard. Learn more.

Core Public Organisation Vocabulary

• Mar 14 | Political dependences attributes

BregDCAT-AP

• Mar 10 | Is "Public Registry Service" defined in BRegDCAT-AP a Public Service in CPSV-AP?

Core Business Vocabulary

• Mar 8 | Other documents related to Legal Entity
• Dec 16 | Change legal entity activity usage note to require/prefer usage of NACE
• Dec 15 | "identifies" uses wrong IRI scheme in RDFS version of the vocabulary

DCAT-AP

• Feb 28 | Indication dataset being part of NSIP/ESAP, similarly to HVD datasets
• Feb 27 | Specific property for conditions for re-use instead of dct:rights in the context of NSIP/ESAP
• Feb 23 | HVD C8. Indicate in reporting the MS responsability
• Feb 23 | HVD C7. Adhere to specific data requirements
• Feb 23 | HVD C6. Point of contact
• Feb 23 | HVD C5. API representation
• Feb 23 | HVD C4. Bulk download
• Feb 23 | HVD C3. License information
• Feb 23 | HVD C2. Identifiers for each HVD entity in the DCAT-AP metadata
• Feb 23 | HVD C1. Being part of HVD scope

Core Person Vocabulary

• Jan 10 | Publishing of the RDF/OWL or JSON-LD version with resolvable URIs and content negotiation on EU server

Core Criterion and Core Evidence Vocabulary

• Jan 4 | Wrong range for the properties “endtime” and “starttime” in the class “Period of Time”?

Core Public Event Vocabulary

• Dec 16 | Use case: Status of the event

Core Location Vocabulary

• Dec 14 | Location of RDFS definition of m8g:* properties and classes