# The Standardization Survival Kit (SSK)

Marie Puren, Charles Riondet, Laurent Romary, Dorian Seillier, Lionel Tadjou

## ► To cite this version:

Marie Puren, Charles Riondet, Laurent Romary, Dorian Seillier, Lionel Tadjou. The Standardization Survival Kit (SSK): Bringing best practices to research communities in the Humanities. Digital Humanities Benelux 2018, Jun 2018, Amsterdam, Netherlands. hal-01850075

HAL Id: hal-01850075

https://hal.science/hal-01850075

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

informatics mathematics
Inria

DH Benelux 2018, 6-8 June 2018

# The Standardization
# Survival Kit (SSK)

Bringing best practices to research communities in the
Humanities

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

**Marie Puren**, Charles Riondet, Laurent Romary, Dorian Seillier, Lionel Tadjou
Inria, PARTHENOS

<figure><img src="image_4.png" /></figure>
# Why using **standards**?

Manage your data, don't let your data manage you...

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

... and produce **interoperable, sustainable & reusable** results for research.
# 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)
# What are standards?

To be called "standards", they must fulfill three requirements:

* They express a **consensus**

* They are published and easily **accessible**

* They are **maintained**
<figure><img src="image_6.png" /></figure>

# The SSK : a toolkit for Humanities scholars

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

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

PARTHENOS

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

HOME

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

EXPLORE

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

CONTRIBUTE

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

PARTNERS

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

GLOSSARY

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

MAIN SITE

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

Log in

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

SSK</>

The Standardization Survival Kit :
for a wider use of standards within Arts and
Humanities

BROWSE BY

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

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

## WHY STANDARDS ?

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

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

They express a consensus.

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

They are accessible to anyone.
<figure><img src="image_21.png" /></figure>

# The SSK : a toolkit for Humanities scholars

* Documenting

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

* Supporting

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

* Training

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

* Communicating

<figure><img src="image_25.png" /></figure>
<figure><img src="image_26.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_27.png" /></figure>
<figure><img src="image_28.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?

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

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_30.png" /></figure>

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

# A high-level research guide

## Collaborative Digital Edition of a Musical Corpus

A project aims to do a digital edition of a musical corpus. The researchers need to be able to encode a broad range of musical documents in a machine-readable structure. The data to be encoded may include the musical content as provided by the composer (notes, pitches, durations, dynamics, etc.), information on the score (incipit, lyrics writer, etc.), information added by a performer when interpreting the content (timing, phrasing, various annotations, etc.), information on the visual appearance of the score (page layout, musical font, etc.) and analyses of the content in any of the other domains. The edition will be structured around a database in order to allow the users to explore it more easily. Furthermore, the project intends to be collaborative, which means it will offer anyone interested the possibility to contribute.

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

Techniques

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

Encoding

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

### 1. Create a digital corpus of musical compositions.

Select resources to be included in the corpus. After collecting original musical sources, transcribe them adding critical editorial signs and normalizing, where applicable, ancient poetic texts to modern usage. To get directly MEI files, use MEISE (MEI Score Editor).
<figure><img src="image_36.png" /></figure>

# Resources and best practices

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

## GENERAL RESOURCES

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

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

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

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

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

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

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

## PROJECT-SPECIFIC RESOURCES

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

**paper**
Laurent Romary, Charles Riondet
EAD-ODD: A solution for project-specific EAD schemes
"2018/03/21"

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

**paper**
Laurent Romary, Charles Riondet
Towards multiscale archival digital data
"2017/09/12"

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

**tutorial**
XPath and Schematron for TEI Customization

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

**report**
hal

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

**code**
# Three layers

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

## Scenario

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

<figure><img src="image_51.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_52.png" /></figure>

## Resource

A standardized tool / service /
document guiding the
researcher in her/his tasks
completion.
# Managing resources

Standards documentation
(ISO, TEI)

Official publications and
reports (D4Science, HAL,
Zenodo)

Documentation

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

Reference libraries
organised by domains and
standards

Maintenance with Zotero

Bibliography

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

Code snippets (GitHub)

Tools & services
(D4Science)

Technical
resources

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

Wikis

Blog posts
(Hypotheses.org)

Discussion lists

User
communities

<figure><img src="image_56.png" /></figure>
# 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.
# What is 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_57.png" /></figure>

# Test the SSK!

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

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

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

ssk@inria.fr

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

Why standards?: https://youtu.be/ULNztgzTKkU
Thank you for your attention!

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

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

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

@Parthenos_EU

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

@PARTHENOSproject

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

contact@parthenos-project.eu