Skip to main content

3 posts tagged with "Ontologie"

View All Tags

Ontology driven

┌────────────────────────────────────────────┐
│ What if ontology drove the application?    |
│--------------------------------------------│
│       Ontology               Application   |
│   ┌───────────────┐                        │
│   │    O---O---O  │                        │
│   │   /   / \  |  │          ┌─────────┐   │ 
│   │  O---O---O-O  │  <====>  |   App   │   │
│   │   \ /     \|  │          └─────────┘   │
│   │   O-O---O--0  │                        |
│   └───────────────┘                        │
└────────────────────────────────────────────┘

An old dream of (IT) ontologists is to be able to manage / parameterise / control the operation of an application directly via one or more ontologies.

This is a long-term objective for SemApps, but it is still a long way off.

In this portal, we will therefore only give recommendations on this subject.

We'll talk about what's missing in SemApps, the improvements that have been made and what we hope to see in the future.

See Recommendations > Ontology-driven

Publication of the ontology in HTML format

┌────────────────────────┐
│  / /  HeCo V1.0        |
│-/ /--------------------│
│/ /                     │
│ / Version              │
│/  Authors              │
│   Abstract             │
│   Graph                │
│ ┌────────────────────┐ │
│ │  O---O-----O O     │ │
│ │   \ /      |/ \    │ │
│ │    O ------O   O   │ │
│ └────────────────────┘ │
│   Classes...           │
│   Properties...        │
└────────────────────────┘

To make the HeCo ontology easier to consult, we have added a new more readable publication format for non-technical profiles.

In addition to the ontology in OWL/TTL format, the summary, the schema, and the PDF document, we provide an HTML interface.

We used WIDOCO to automatically generate this interface from our OWL file.

WIDOCO is increasingly becoming a standard in ontology delivery. This format is increasingly common on the web.

It describes all classes and properties, providing links for easier navigation within the document.

WIDOCO creates two HTML outputs, one in French and one in English.

A networked graph of the ontology is also available, enabling the ontology to be viewed using WebVOWL software.

To take advantage of this new interface, visit the HeCo Ontology.

Relation(s) betwin competences and jobs/commitment/training

Need to see only my personal data​

┌────────────────────────┐
│    MY-competences      |
│------------------------│
│ ┌────────────────────┐ │
│ │ My jobs            │ │
│ │ My commitments     │ │
│ │ My trainings       │ │
│ └────────────────────┘ │
└────────────────────────┘

On the My-competences interface, it is possible to link skills to positions, contributions and training.

The aim of My-skills is for users to see only their personal details and not those filled in by others, as in the back office.

We have therefore filtered the choice lists so that each user can only create links to the posts, contributions or training courses that they have created.

For more information, see the My-competences user manual.

Use of a single predicate​

┌───────────────────────┐       ┌────────────┐
│ Competences           │       │ Discipline │
│-----------------------│       │------------│
│ id                    │   ┌──>│ uri        │
│ title                 │   │   │ title      │
│ description           │   │   │ description│
│ heco:hasDiscipline    │───┘   └────────────┘
│ xxxxxx                │       ┌────────────┐
│ xxxxxx                │       │ Job      │
│ xxxxxx                │       │------------│
│ xxxxxx                │   ┌──>│ uri        │
│ xxxxxx                │   │   │ title      │
│ xxxxxx                │   │   │ description│
│ heco:isCompAcquiredIn │───┘?  └────────────┘
└───────────────────────┘   │   ┌──────────────┐
                            │   │ Commitment   │
                            │   │--------------│
                            └──>│ uri          │
                                │ titre        │
                                │ description  │
                                └──────────────┘

At the HeCo ontology level, we wanted to use just one predicate (relationship) between a skill and a position / contribution / training. This way, the day we add a new object, we won't have to change the ontology.

To enable this, we had to add a customisation on the server side, so that it would make the client believe that it was using a different predicate for each object, while keeping a single predicate in the base.

For more information about HeCo, follow Ontologie HeCo