# Le Standardization Survival Kit (SSK)

Marie Puren, Dorian Seillier, Charles Riondet, Lionel Tadjou

## ► To cite this version:

Marie Puren, Dorian Seillier, Charles Riondet, Lionel Tadjou. Le Standardization Survival Kit (SSK) : Faciliter l'usage des standards dans les Humanités. Rencontres de la TGIR Huma-Num, Jun 2018, Ecully, France. hal-01850078

HAL Id: hal-01850078

https://hal.science/hal-01850078

Submitted on 26 Jul 2018

HAL is a multi-disciplinary open access
archive for the deposit and dissemination of sci-
entific research documents, whether they are pub-
lished or not. The documents may come from
teaching and research institutions in France or
abroad, or from public or private research centers.

L'archive ouverte pluridisciplinaire HAL, est
destinée au dépôt et à la diffusion de documents
scientifiques de niveau recherche, publiés ou non,
émanant des établissements d'enseignement et de
recherche français ou étrangers, des laboratoires
publics ou privés.

<figure><img src="image_1.png" /></figure>

Distributed under a Creative Commons Attribution 4.0 International License
<figure><img src="image_2.png" /></figure>

PARTHENOS

Pooling Activities, Resources and Tools
for Heritage E-research Networking.
Optimization and Synergies

<figure><img src="image_3.png" /></figure>

Rencontres Huma-Num

2018

Valpré - 11 au 14 juin 2018

# Le Standardization Survival Kit (SSK)

Faciliter l'usage des standards dans les Humanités

<figure><img src="image_4.png" /></figure>

Marie Puren, Dorian Seillier, Charles Riondet, Lionel Tadjou Inria, PARTHENOS

<figure><img src="image_5.png" /></figure>
# About us

* INRIA Paris

<figure><img src="image_6.png" /></figure>

* Project-Team ALMAnaCH (Automatic Language Modeling and Analysis & Computational Humanities)
About us

<figure><img src="image_7.png" /></figure>

PARTHENOS

Pooling Activities, Resources and Tools
for Heritage E-research Networking,
Optimization and Synergies

http://www.parthenos-project.eu/
# Why standards?

* **Consensus**: a wide (and possibly international) community of experts has developed them

* **Publication and accessibility**: anyone who wants to know their content is able to access it.

* **Maintenance**: they are regularly updated, replaced or deprecated depending on the technical and scientific evolution of the field.
# Why using **standards**?

> "Standards are a key to great digital research, which helps to discover and understand our cultural and societal life."

Laurent Romary

Chairman of the Technical Committee "Terminology and other language and content resources" of the International Organization for Standardization (ISO)
# Why using standards ?

To **produce interoperable, sustainable
& reusable results for research.**

Here the **SSK** comes into play ...
# LES AVENTURES DE MORK ET TORK!

<figure><img src="image_8.png" /></figure>

Why standards? https://www.youtube.com/watch?v=iiUb6wgA9FI
<figure><img src="image_9.png" /></figure>

# The SSK: a toolkit for Humanities scholars

<figure><img src="image_10.png" /></figure>

* Documenting

<figure><img src="image_11.png" /></figure>

<figure><img src="image_12.png" /></figure>

* Supporting

<figure><img src="image_13.png" /></figure>

<figure><img src="image_14.png" /></figure>

* Training

<figure><img src="image_15.png" /></figure>

<figure><img src="image_16.png" /></figure>

* Communicating

<figure><img src="image_17.png" /></figure>
What the SSK is not

≠ A software where you can perform actions

≠ A data repository

≠ A catalog of standards or resources
<figure><img src="image_18.png" /></figure>

# The scenarios

Providing contextual
information and
relevant examples on
how standards can be
applied in a given
research project.

<figure><img src="image_19.png" /></figure>
<figure><img src="image_20.png" /></figure>

# Huma-Num and the scenarios

* Close collaboration with the 3D Consortium:

* White paper: *Digital 3D Objects in Art and Humanities* (2017) [hal-01526713v2]

* Two scenarios 3D in progress (presented during *DH Mexico* at the end of June)

* And a third will be delivered

* Scenarios provided by Huma-Num:

* “Encode and modelize field surveys for their online dissemination”

* “Collaborative digital edition of a musical corpus” (Consortium Musica)

* Huma-Num's strong contribution to:

* “Perform Statistical analysis on Historical and contemporary occupations”

* “Digitizing textual material”
Huma-Num and the
scenarios

<figure><img src="image_21.png" /></figure>

<figure><img src="image_22.png" /></figure>
<figure><img src="image_23.png" /></figure>

What Tork & Mork tell us

Hey Mork! With some of my **colleagues**, I'd like to put **musical scores online**. But I don't know **what I can do** and how to proceed! Can you help me?

Well Tork, **use the SSK!** I think the scenario **"Collaborative Digital Edition of a Musical Corpus"** can be very useful for you. It will guide you through all the **necessary steps** to put these scores online, and present the **best practices** associated to each of these steps.

<figure><img src="image_24.png" /></figure>

<figure><img src="image_25.png" /></figure>

<figure><img src="image_26.png" /></figure>
# Three layers

<figure><img src="image_27.png" /></figure>

## Scenario

A complete and generic research use case composed of several steps to be followed.

<figure><img src="image_28.png" /></figure>

## Step

A unique task to be performed inside a scenario with the help and recommendation of one or several resources.

<figure><img src="image_29.png" /></figure>

## Resource

A standardized tool / service / document guiding the researcher in her/his tasks completion.
# The TEI model

The scenarios are described using the **TEI** format (**Text Encoding Initiative**). All the information displayed within the SSK proceed from TEI files.

```xml
<text>
  <body>
    <div type="scenario" xml:id="sc_schemaCustomization">
      <head xml:lang="en" type="scenarioTitle">Harmonization of digitized textual resources with the DTABf</head>
      <desc type="definition" xml:lang="en">Currently, initiatives for the digitization of textual resources and their provision to the interested community are manifold and various. Hence, scholars who want to base their research on digitized texts,
```

```xml
<listEvent>
  <event ref="step_OtICoP_171117" type="researchStep" xml:id="s1"/>
  <event ref="step_CaC_171117" type="researchStep" xml:id="s2"/>
  <event ref="step_SaD_171117" type="researchStep" xml:id="s3"/>
  <event ref="step_A_171117" type="researchStep" xml:id="s4"/>
  <event ref="step_CiSF_171117" type="researchStep" xml:id="s5"/>
  <event ref="step_TtI_171117" type="researchStep" xml:id="s6"/>
```
# How the TEI works in the SSK ?

* A scenario is a list of events (tei:listEvents), each step in a scenario is an event (tei:event).

* TEI files are all available on Github (https://github.com/ParthenosWP4/SSK).

* Documentation: https://parthenoswp4.github.io/SSK/SSKspec.html
# Handling the resources

Standards documentation
(ISO, TEI)

Official publications and
reports (D4Science, HAL,
Zenodo)

Documentation

<figure><img src="image_30.png" /></figure>

Reference libraries
organised by domains and
standards

Maintenance with Zotero

Bibliography

<figure><img src="image_31.png" /></figure>

Code snippets (GitHub)

Tools & services
(D4Science)

Technical
resources

<figure><img src="image_32.png" /></figure>

Wikis

Blog posts
(Hypotheses.org)

Discussion lists

User
communities

<figure><img src="image_33.png" /></figure>
# Our ontologies

* Disciplines (AureHAL)

* Research objects (TaDiRAH, NeDiMAH)

* Research activities (TaDiRAH, CIDOC-CRMsci)

* Research techniques (TaDiRAH)

* Standards (our own knowledge base)
# Testing the web interface

A usability test is the **simulated experience** of a information system by
potential users who are asked to perform **realistic tasks** with it.

It helps get users' **feedback** (reactions, comments, feelings) by
**observing** and **listening**.
# Objectives of the test

* Determine the **degree of usability** of the tools based on several criteria

* Identify the **flaws / bugs** of the interface

* Evaluate the user experience of a **first contact** with the tool

* Assess if the SSK meets the needs and expectations of the user
# Main results

Two categories of users emerged from the test:

* **beginners in DH or standards** who struggle a lot to understand most of the terminology and the general aim of the website

* **more experienced users** who were pleased by the initiative but wanted more detailed scenarios and more resources to work with

> "The SSK is clear enough for researchers familiar with Digital Humanities, but too technical for others who may want to start following these practices"
# Design requirements

In order to improve the platform and make it more user-friendly, SSK's design should take into account:

* the **difference of expertise and experience among users**: it should be as adaptable as possible, even if it suits better the need of more advanced researchers in DH. At least, it should guide learners towards training materials.

* the resources we want researchers to use when following a scenario have to be **clear, up-to-date, relevant** and **connected to the step**.

* a good balance needs to be found between completeness and lightness to **avoid information overload**, which leads to the loss of the user.
# What's next?

* Browsing **vocabularies** and **bibliography**

* Creating an **account**:

* to manage **bookmarks**

* to customize **scenarios** (by combining existing steps from SSK's research scenarios)

* **Contributing** (in TEI or directly on the interface):

* creation

* edition

* customization

* Accessing a **multilingual** interface
<figure><img src="image_34.png" /></figure>

Let's test it!

https://ssk-application.parthenos.d4science.org/ssk/

You can ask questions at : ssk@inria.fr

<figure><img src="image_35.png" /></figure>
# Involving research communities

* **Living memory** of research best practices

* **Teaching** materials

* Need of a **strong community**

* reviewers

* creators => **new scenarios** could be provided by **Huma-Num Consortia**
The SSK needs **you!**

<figure><img src="image_36.png" /></figure>

ssk@inria.fr

<figure><img src="image_37.png" /></figure>
Thank you for your attention!

<figure><img src="image_38.png" /></figure>

http://www.parthenos-project.eu/

<figure><img src="image_39.png" /></figure>

@Parthenos_EU

<figure><img src="image_40.png" /></figure>

@PARTHENOSproject

<figure><img src="image_41.png" /></figure>

contact@parthenos-project.eu

<figure><img src="image_42.png" /></figure>

https://www.youtube.com/channel/UCnKJnFo_IFfoAI3VH51t1hw