Since SemApps is fully used in this project, it seemed important to give it a full place in this portal.
At the same level as SOLID, we added a reference page, with a link to https://semapps.org, which has recently been updated with a new stable release.
We have added a schema, explaining the notion of "semantic toolbox" which summarizes what SemApps is.
In order to offer another media than applications to Carto4ch partners, we have added to this portal the mock-ups that we used to develop our applications.
These mock-ups can give another view of what we want to propose as interfaces to users, to enter their skills.
They can be updated regularly according to the evolution of the project (as well as the schemas).
They can also be reused or completed by the partners.
En ce début 2023, nous avons ajouté au démonstrateur de nouveaux concepts, en lien avec l'ontologie version 0.7.
A présent, vous allez en quelque sorte pouvoir "remplir votre CV" dans votre profil. Pour cela, plusieurs nouveaux concepts sont à votre disposition :
Une fois ces objets créés dans la base, vous allez pouvoir les ajouter dans votre profil, et visualiser votre CV personnel. Le profil des utilisateur étant public par défaut, tout le monde peut ainsi parcourir les "compétences" des autres utilisateurs.
In 2022, we had used two différent hosts (OVH & Huma-Num) for our two servers A and B. The goal was to show interoperability to the end.
For reasons of simplification and maintenance of the demonstrator, we migrated the instance A to the same Huma-Num hosting as the instance B.
The particularity of this new multi-instance infrastructure is that both applications share the same triplestore, but having within it two independent datasets. The data is therefore not mixed. This is technically the same as before, we just gain in maintenance, cost, energy, and we are sure to have the same machine power for both instances, which was not the case before because the two hostings were not identically sized.
To understand the difference in the server infrastructure, you can consult the infrastructure diagram
In order to capture skills in a richer way, we needed to be able to run what is called in semantic web reified relations (or ternary relations).
This is the possibility to bring additional information on top of a "simple" relationship.
For example, let's start with a relation like "Bob knows Alice"
| Subject | Predicate | Object |
|---|---|---|
| Bob | foaf:knows | Alice |
If we want to qualify the relationship between these two people more precisely, we call this a reification (and there are several ways to do this).
This is for example what we did ( see Schema > Architecture ) to manage the roles between a person and an organization.
After a first work of the Carto4CH core team, we have stabilized a first version of the HeCo ontology (version 0.5).
This version will allow us to have a first support to exchange with the partners of the project.
The objective is that this ontology is questioned, tested, until it stabilizes to be used in the cartography.
For more information on this ontology, see this page
In order to maintain the link between the core team and the partners, we have set up regular meetings called "skills workshops".
For more information on these workshops, see this page
It is now possible to query repositories such as ESCO or Wikidata to help with competences entry.
We have implemented this in the demonstrator:
We are using an "in-house" ESCO server, maintained by a SemApps team member of the Virtual Assembly, containing a copy (RDF) of the ESCO repository. This homegrown server has the advantage of providing a SPARQL endpoint (although for the moment we are not using it), which is no longer active in the production server. This will also allow us in the future to complete it with content more specific to the world of cultural heritage.
The summer months were the opportunity for the SemApps team to finish the development of interoperability in SemApps.
This means that from now :
We have updated the A and B servers of the demonstrator to test these new features.
The notion of mirrors can be used later by the "central" server of the competences cartography.
You will find diagrams explaining these two new concepts.
The summer months were the opportunity to finish the glossary, as well as the SOLID tutorial.
These two deliverables are closely linked, because one is based on the code of the other. Indeed, this lexicon is also there to show you what we can do with SOLID.
We could imagine later on a shared lexicon based on SOLID servers distributed in the field of French (or even European) cultural heritage... But this is not the purpose of this project, and we will be satisfied with a small lexicon and a modest tutorial... :)
To consult it, go to : Project documentation > Glossary
This glossary can be completed throughout the project.