-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Deploying to gh-pages from @ ee6dc3e 🚀
- Loading branch information
1 parent
c63a1a9
commit e83d28f
Showing
5 changed files
with
1,671 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,207 @@ | ||
| <!DOCTYPE html> | ||
| <html lang="en"> | ||
| <head> | ||
| <meta charset="utf-8"> | ||
| <meta name="viewport" content="width=device-width,initial-scale=1"> | ||
| <title>Untitled :: SEMIC</title> | ||
| <meta name="generator" content="Antora 3.0.0"> | ||
| <link rel="stylesheet" href="../_/css/site.css"> | ||
| </head> | ||
| <body class="article"> | ||
| <header class="header"> | ||
| <nav class="navbar"> | ||
| <div class="navbar-brand"> | ||
| <a class="navbar-item" href="..">SEMIC</a> | ||
| </div> | ||
| </nav> | ||
| </header> | ||
| <div class="body"> | ||
| <div class="nav-container" data-component="ROOT" data-version="public-review"> | ||
| <aside class="nav"> | ||
| <div class="panels"> | ||
| <div class="nav-panel-menu is-active" data-panel="menu"> | ||
| <nav class="nav-menu"> | ||
| <button class="nav-menu-toggle" aria-label="Toggle expand/collapse all" style="display: none"></button> | ||
| <h3 class="title"><a href="index.html">SEMIC Core Vocabularies Handbook</a></h3> | ||
| <ul class="nav-list"> | ||
| <li class="nav-item" data-depth="0"> | ||
| <ul class="nav-list"> | ||
| <li class="nav-item" data-depth="1"> | ||
| <a class="nav-link" href="introduction.html">Introduction</a> | ||
| </li> | ||
| <li class="nav-item" data-depth="1"> | ||
| <a class="nav-link" href="semic-core-vocabularies.html">SEMIC Core Vocabularies</a> | ||
| </li> | ||
| <li class="nav-item" data-depth="1"> | ||
| <a class="nav-link" href="conceptual-framework.html">Conceptual framework</a> | ||
| </li> | ||
| <li class="nav-item" data-depth="1"> | ||
| <button class="nav-item-toggle"></button> | ||
| <span class="nav-text">Back matter</span> | ||
| <ul class="nav-list"> | ||
| <li class="nav-item" data-depth="2"> | ||
| <a class="nav-link" href="references.html">References</a> | ||
| </li> | ||
| <li class="nav-item" data-depth="2"> | ||
| <span class="nav-text">xref:[Handbook as a whole]</span> | ||
| </li> | ||
| </ul> | ||
| </li> | ||
| </ul> | ||
| </li> | ||
| </ul> | ||
| </nav> | ||
| </div> | ||
| <div class="nav-panel-explore" data-panel="explore"> | ||
| <div class="context"> | ||
| <span class="title">SEMIC Core Vocabularies Handbook</span> | ||
| <span class="version">public-review</span> | ||
| </div> | ||
| <ul class="components"> | ||
| <li class="component is-current"> | ||
| <div class="title"><a href="index.html">SEMIC Core Vocabularies Handbook</a></div> | ||
| <ul class="versions"> | ||
| <li class="version is-current is-latest"> | ||
| <a href="index.html">public-review</a> | ||
| </li> | ||
| </ul> | ||
| </li> | ||
| </ul> | ||
| </div> | ||
| </div> | ||
| </aside> | ||
| </div> | ||
| <main class="article"> | ||
| <div class="toolbar" role="navigation"> | ||
| <button class="nav-toggle"></button> | ||
| <a href="index.html" class="home-link"></a> | ||
| <nav class="breadcrumbs" aria-label="breadcrumbs"> | ||
| </nav> | ||
| <div class="edit-this-page"><a href="https://github.com/SEMICeu/core-vocs-handbook/edit/feature/bootstrap-repo/docs/modules/ROOT/pages/glossary.adoc">Edit this Page</a></div> | ||
| </div> | ||
| <div class="content"> | ||
| <aside class="toc sidebar" data-title="Contents" data-levels="2"> | ||
| <div class="toc-menu"></div> | ||
| </aside> | ||
| <article class="doc"> | ||
| <div class="sect1"> | ||
| <h2 id="_glossary"><a class="anchor" href="#_glossary"></a>Glossary</h2> | ||
| <div class="sectionbody"> | ||
| <div class="sect2"> | ||
| <h3 id="_application_profile"><a class="anchor" href="#_application_profile"></a><strong>Application Profile</strong></h3> | ||
| <div class="paragraph"> | ||
| <p><strong><em>Alternative names:</em></strong> AP, context-specific semantic data specification<br> | ||
| <strong><em>Definition:</em></strong> Semantic data specification aimed to facilitate the data exchange in a well-defined application context.<br> | ||
| <strong><em>Additional info:</em></strong> It re-uses concepts from one or more semantic data specifications, while adding more specificity, by identifying mandatory, recommended, and optional elements, addressing particular application needs, and providing recommendations for controlled vocabularies to be used.<br> | ||
| <strong><em>Source/Reference:</em></strong> <a href="https://semiceu.github.io/style-guide/1.0.0/style-guide-whole.html#sec:what-is-an-ap-specification">SEMIC Style Guide</a></p> | ||
| </div> | ||
| </div> | ||
| <div class="sect2"> | ||
| <h3 id="_conceptual_model"><a class="anchor" href="#_conceptual_model"></a><strong>Conceptual model</strong></h3> | ||
| <div class="paragraph"> | ||
| <p><strong><em>Alternative names:</em></strong> conceptual model specification<br> | ||
| <strong><em>Definition:</em></strong> An abstract representation of a system that comprises well-defined concepts, their qualities or attributes, and their relationships to other concepts.<br> | ||
| <strong><em>Additional info:</em></strong> A system is a group of interacting or interrelated elements that act according to a set of rules to form a unified whole.<br> | ||
| <strong><em>Source/Reference:</em></strong> <a href="https://semiceu.github.io/style-guide/1.0.0/style-guide-whole.html#sec:what-is-a-conceptual-model">SEMIC Style Guide</a></p> | ||
| </div> | ||
| </div> | ||
| <div class="sect2"> | ||
| <h3 id="_core_vocabulary"><a class="anchor" href="#_core_vocabulary"></a><strong>Core Vocabulary</strong></h3> | ||
| <div class="paragraph"> | ||
| <p><strong><em>Alternative names:</em></strong> CV<br> | ||
| <strong><em>Definition:</em></strong> A basic, reusable and extensible semantic data specification that captures the fundamental characteristics of an entity in a context-neutral fashion.<br> | ||
| <strong><em>Additional info:</em></strong> Its main objective is to provide terms to be reused in the broadest possible context.<br> | ||
| <strong><em>Source/Reference:</em></strong> <a href="https://semiceu.github.io/style-guide/1.0.0/style-guide-whole.html#sec:what-is-a-cv-specification">SEMIC Style Guide</a></p> | ||
| </div> | ||
| </div> | ||
| <div class="sect2"> | ||
| <h3 id="_data_model"><a class="anchor" href="#_data_model"></a><strong>Data model</strong></h3> | ||
| <div class="paragraph"> | ||
| <p><strong><em>Definition:</em></strong> A structured representation of data elements and relationships used to facilitate semantic interoperability within and across domains.<br> | ||
| <strong><em>Additional info:</em></strong> Data models represent common languages to facilitate semantic interoperability in a data space, including ontologies, data models, schema specifications, mappings and API specifications that can be used to annotate and describe data sets and data services. They are often domain-specific.<br> | ||
| <strong><em>Source/Reference:</em></strong> <a href="https://dssc.eu/space/BVE/357075098/Data+Models">Data Spaces Blueprint</a></p> | ||
| </div> | ||
| </div> | ||
| <div class="sect2"> | ||
| <h3 id="_information_exchange_data_model"><a class="anchor" href="#_information_exchange_data_model"></a><strong>Information exchange data model</strong></h3> | ||
| <div class="paragraph"> | ||
| <p><strong><em>Alternative names:</em></strong> data schema<br> | ||
| <strong><em>Definition:</em></strong> Information exchange data model is a technology-specific framework for data exchange, detailing the syntax, structure, data types, and constraints necessary for effective data communication between systems. It serves as a practical blueprint for implementing an application profile in specific data exchange contexts.<br> | ||
| <strong><em>Additional info:</em></strong> An ontology and an exchange data model serve distinct yet complementary roles across different abstraction levels within data management systems. While a Data Schema specifies the technical structure for storing and exchanging data, primarily concerned with the syntactical and structural aspects of data, it is typically articulated using metamodel standards such as JSON Schema and XML Schema.<br> | ||
| In contrast, ontologies and data shapes operate at a higher conceptual level, outlining the knowledge and relational dynamics within a particular domain without delving into the specifics of data storage or structural implementations. Although a Data Schema can embody certain elements of an ontology or application profile—particularly attributes related to data structure and cardinalities necessary for data exchange—it does not encapsulate the complete semantics of the domain as expressed in an ontology.<br> | ||
| Thus, while exchange data models are essential for the technical realisation of data storage and exchange, they do not replace the broader, semantic understanding provided by ontologies. The interplay between these layers ensures that data schemas contribute to a holistic data management strategy by providing the necessary structure and constraints for data exchange, while ontologies offer the overarching semantic framework that guides the meaningful interpretation and utilisation of data across systems. Together, they facilitate a structured yet semantically rich data ecosystem conducive to advanced data interoperability and effective communication.<br> | ||
| <strong><em>Source/Reference:</em></strong> <a href="https://dssc.eu/space/BVE/357075098/Data+Models#Conceptual-model">Data Spaces Blueprint</a></p> | ||
| </div> | ||
| </div> | ||
| <div class="sect2"> | ||
| <h3 id="_data_specification_artefact"><a class="anchor" href="#_data_specification_artefact"></a><strong>Data specification artefact</strong></h3> | ||
| <div class="paragraph"> | ||
| <p><strong><em>Alternative names:</em></strong> specification artefact, artefact<br> | ||
| <strong><em>Definition:</em></strong> A materialisation of a semantic data specification in a concrete representation that is appropriate for addressing one or more concerns (e.g. use cases, requirements).<br> | ||
| <em>Source/Reference:</em> <a href="https://semiceu.github.io/style-guide/1.0.0/style-guide-whole.html#sec:what-is-an-artefact">SEMIC Style Guide</a></p> | ||
| </div> | ||
| </div> | ||
| <div class="sect2"> | ||
| <h3 id="_data_specification_document"><a class="anchor" href="#_data_specification_document"></a><strong>Data specification document</strong></h3> | ||
| <div class="paragraph"> | ||
| <p><strong><em>Alternative names:</em></strong> specification document<br> | ||
| <strong><em>Definition:</em></strong> The human-readable representation of an ontology, a data shape, or a combination of both.<br> | ||
| <strong><em>Additional info:</em></strong> A semantic data specification document is created with the objective of making it simple for the end-user to understand (a) how a model encodes knowledge of a particular domain, and (b) how this model can be technically adopted and used for a purpose. It is to serve as technical documentation for anyone interested in using (e.g. adopting or extending) a semantic data specification.<br> | ||
| <strong><em>Source/Reference:</em></strong> <a href="https://semiceu.github.io/style-guide/1.0.0/style-guide-whole.html#sec:what-is-a-specification-document">SEMIC Style Guide</a></p> | ||
| </div> | ||
| </div> | ||
| <div class="sect2"> | ||
| <h3 id="_data_shape_specification"><a class="anchor" href="#_data_shape_specification"></a><strong>Data shape specification</strong></h3> | ||
| <div class="paragraph"> | ||
| <p><strong><em>Alternative names:</em></strong> data shape constraint specification, data shape constraint, data shape<br> | ||
| <strong><em>Definition:</em></strong> A set of conditions on top of an ontology, limiting how the ontology can be instantiated.<br> | ||
| <strong><em>Additional info:</em></strong> The conditions and constraints that apply to a given ontology are provided as shapes and other constructs expressed in the form of an RDF graph. We assume that the data shapes are expressed in SHACL language.<br> | ||
| <strong><em>Source/Reference:</em></strong> <a href="https://semiceu.github.io/style-guide/1.0.0/style-guide-whole.html#sec:what-is-a-data-shape-contraint">SEMIC Style Guide</a></p> | ||
| </div> | ||
| </div> | ||
| <div class="sect2"> | ||
| <h3 id="_ontology"><a class="anchor" href="#_ontology"></a><strong>Ontology</strong></h3> | ||
| <div class="paragraph"> | ||
| <p><strong><em>Alternative names:</em></strong> ontology specification<br> | ||
| <strong><em>Definition:</em></strong> A formal specification describing the concepts and relationships that can formally exist for an agent or a community of agents (e.g. domain experts)<br> | ||
| <strong><em>Additional info:</em></strong> It encompasses a representation, formal naming, and definition of the categories, properties, and relations between the concepts, data, and entities that substantiate one, many, or all domains of discourse.<br> | ||
| <strong><em>Source/Reference:</em></strong> <a href="https://semiceu.github.io/style-guide/1.0.0/style-guide-whole.html#sec:what-is-an-ontology">SEMIC Style Guide</a></p> | ||
| </div> | ||
| </div> | ||
| <div class="sect2"> | ||
| <h3 id="_semantic_data_specification"><a class="anchor" href="#_semantic_data_specification"></a><strong>Semantic data specification</strong></h3> | ||
| <div class="paragraph"> | ||
| <p><strong><em>Alternative names:</em></strong> data specification<br> | ||
| <strong><em>Definition:</em></strong> An union of machine- and human-readable artefacts addressing clearly defined concerns, interoperability scope and use-cases.<br> | ||
| <strong><em>Additional info:</em></strong> A semantic data specification comprises at least an ontology and a data shape (or either of them individually) accompanied by a human-readable data specification document.<br> | ||
| <strong><em>Source/Reference:</em></strong> <a href="https://semiceu.github.io/style-guide/1.0.0/style-guide-whole.html#sec:what-is-a-semantic-data-specification">SEMIC Style Guide</a></p> | ||
| </div> | ||
| </div> | ||
| <div class="sect2"> | ||
| <h3 id="_vocabulary"><a class="anchor" href="#_vocabulary"></a><strong>Vocabulary</strong></h3> | ||
| <div class="paragraph"> | ||
| <p><strong><em>Definition:</em></strong> An established list of preferred terms that signify concepts or relationships within a domain of discourse. All terms must have an unambiguous and non-redundant definition. Optionally it may include synonyms, notes and their translation to multiple languages.</p> | ||
| </div> | ||
| </div> | ||
| <div class="sect2"> | ||
| <h3 id="_upper_ontology"><a class="anchor" href="#_upper_ontology"></a><strong>Upper Ontology</strong></h3> | ||
| <div class="paragraph"> | ||
| <p><strong><em>Definition:</em></strong> An upper ontology is a highly generalised ontology that includes very abstract concepts applicable across all domains, such as "object," "property," and "relation." Its primary role is to facilitate broad semantic interoperability among numerous domain-specific ontologies by offering a standardised foundational framework. This framework assists in harmonising diverse domain ontologies, allowing for consistent data interpretation and efficient information exchange.</p> | ||
| </div> | ||
| </div> | ||
| </div> | ||
| </div> | ||
| </article> | ||
| </div> | ||
| </main> | ||
| </div> | ||
| <footer class="footer"> | ||
| <p style="text-align:center">This document is created by the European Comission and is licensed under the terms of EUPL-1.2 license</a>. | ||
| <br/>This page was built using the Antora default UI. The source code for this UI is licensed under the terms of | ||
| the MPL-2.0 license. | ||
| </p> | ||
| </footer> | ||
| <script id="site-script" src="../_/js/site.js" data-ui-root-path="../_"></script> | ||
| <script async src="../_/js/vendor/highlight.js"></script> | ||
| </body> | ||
| </html> |
Oops, something went wrong.