Biblissima et IIIFLinked Data et interopérabilité des images sur le Web

Maison de l’Archéologie et de l’Ethnologie (MAE, Nanterre) - 08/04/2016

Stefanie Gehrke

Équipex Biblissimawww.biblissima-condorcet.fr

Partenaires Biblissima

Volet 1 de Biblissima : “Observatoire”

http://biblissima-condorcet.fr/fr/projet/volet-1-observatoire-biblissima

Bibliothèque des bibliothèques du Moyen Âge et de la Renaissance ...

http://data.bnf.fr/10663423/antonius_sanderus/

http://data.bnf.fr/12071684/bernard_de_montfaucon/

http://demos.biblissima-condorcet.fr/prototype

http://www.libraria.fr/sites/default/files/Montfaucon%20BBN%20sur%20Libraria.pdf

http://nossl.demo.logilab.fr/biblissima/

http://irht.hypotheses.org/767

… basée sur les technologies du Web sémantique

Auteur LangueÉtablissement

de conservation (<1644 ; 1739)

“Bibliotheca Belgica Manuscripta” (1641-44)

“Bibliotheca bibliothecarum manuscriptorum nova” (1739)

1 point d’accès unique à 40 bases de données

http://www.biblissima-condorcet.fr/fr/ressources/ressources-biblissima

1 point d’accès unique à 3 entrepôts d’images

http://www.biblissima-condorcet.fr/fr/ressources/ressources-biblissima

Workflow

Alignements + Nettoyage de données

Biblissima

http://nossl.demo.logilab.fr/biblissima/

http://demos.biblissima-condorcet.fr/prototype

Intégration de Mirador dans les pages Web

IIIF - besoins de Biblissima

sc:Manifests et métadonnées (I)

- Images

- Transcriptions- Annotations

sc:Manifests et métadonnées (II)

Shared Canvas, IIIF et la TEI

- non intégré à la TEI

- un sc:Manifest peut être généré à partir d’un fichier TEI

- probablement pas une alternative à la TEI

(qui encoderait une transcription dans un fichier JSON-LD ?)

- supporte l’affichage des transcriptions provenant des fichiers TEI dans un visualiseur

Générer un sc:Manifest à partir d’un fichier TEIMétadonnées sur l’objet physique (métadonnées descriptives):

msDesc/… => metadata: « label » - « value » pairs

Métadonnées structurelles :

msItem/locus @from, @to, @on => sc:Range

msPart => sc:Range

Transcription:

text/body/div/pb => sc:AnnotationList par sc:Canvas

facsimile/surface + graphic + zone => sc:Canvas+image+chars on URI.json#xywh=X,Y,W,H

Démo Biblissima - Roman du Mont Saint-Michelhttp://demos.biblissima-condorcet.fr/roman-bl-caen/m1/

XSLT: https://github.com/stefaniegehrke/TEI-2-SC

JSON-LD: http://demos.biblissima-condorcet.fr/iiif/metadata/BL_Add_10289/list/transscript_8v.json

- Description (?)

- Height + Width Physical Object

- Images

- Transcriptions- Annotations

sc:Manifests et métadonnées (III)

seeAlso

A link to a machine readable document that semantically describes the resource with the seeAlso property, such as an XML or RDF description. This document could be used for search and discovery or inferencing purposes, or just to provide a longer description of the resource. The profile and format properties of the document should be given to help the client to make appropriate use of the document.

related

A link to an external resource intended to be displayed directly to the user, and is related to the resource that has the related property. Examples might include a video or academic paper about the resource, a website, an HTML description, and so forth. A label and the format of the related resource should be given to assist clients in rendering the resource to the user.

sc:Manifests et métadonnées (IV)

attribution

A human readable label that must be displayed when the resource it is associated with is displayed or used. For example, this could be used to present copyright or ownership statements, or simply an acknowledgement of the owning and/or publishing institutions.

license

A link to an external resource that describes the license or rights statement under which the resource is being used. The rationale for this being a URI and not a human readable label is that typically there is one license for many resources, and the text is too long to be displayed to the user along with the object. If displaying the text is a requirement, then it is recommended to include the information using the attribution property instead.

sc:Manifests et métadonnées (V)

Les créateurs de sc:Manifests

sc:Manifests et métadonnées (VI)

métadonnées

Publication Web Sémantique

Information géospatiale dans le web sémantique

La réutilisation de vocabulaires existants a été privilégiée pour favoriser l'interopérabilité

Exprimer un concept, thésaurusDécrire des concepts Documents numérisés - modèle de données basé sur OA

Favoriser l'indexation par les moteurs

Intégration de métadonnées dans les pages web

Décrire les entités et les relations du modèle FRBR pour les données bibliographiques, les données d'autorité et les sujets

Décrire les types de relations présentes entre ou à l’intérieur des textes

Une infrastructure ouverte, basée sur le Web sémantique, pouvant gérer l’étendue et la richesse des standards spécifiques à la communauté

Principales classes de Shared Canvas (I)

sc:Canvas

sc:Range

sc:Sequence

sc:Manifest

sc:Collection

- a JSON-LD file

- “The Manifest is what ties everything together. It is an Aggregation of the Layers, AnnotationLists and Sequences that make up the description of the facsimile. As such the Manifest is representative of the Book, Newspaper, Scroll or whatever physical object is being represented in the facsimile.”

- “The manifest resource represents a single object and any intellectual work or works embodied within that object. In particular it includes the descriptive, rights and linking information for the object. It then embeds the sequence(s) of canvases that should be rendered to the user.”

sc:Canvas

sc:Range

sc:Sequence

sc:Manifest

sc:Collection

- “A Shared Canvas is a two dimensional rectangular space with an aspect ratio that represents a single logical view of some part of the physical item.”

- “A virtual container that represents a page or view and has content resources associated with it or with parts of it (...) provides a frame of reference for the layout of the page (...) the display starts from a blank canvas and images, text and other resources are “painted” on to it.”

Principales classes de Shared Canvas (II)

Numérisation et FRBRoo

F33 Reproduction Event :

Example : The BnF’s making in 2003 a digitisation, identified by call number ‘IFN 7701015’, of the collection of drawings (held by the BnF) that were made by Étienne-Louis Boullée in 1784 for his project of a ‘Newton Cenotaph’

Domaine et Range : “E84_Information_Carrier” = Objet fabriqué

P138 represents (in a shortcut):

Example : - the design on the reverse of a Swiss coin (E36) represents Helvetia (E28) mode of representation Profile (E55)

“P138_represents” semble un peu vague

Information Carrier versus Information Object

E84_Information_Carrier :

This class comprises all instances of E22 Man-Made Object that are explicitly designed to act as persistent physical carriers for instances of E73 Information Object. This allows a relationship to be asserted between an E19 Physical Object and its immaterial information contents. An E84 Information Carrier may or may not contain information, e.g., a diskette. Note that any E18 Physical Thing may carry information, such as an E34 Inscription. However, unless it was specifically designed for this purpose, it is not an Information Carrier. Therefore the property P128 carries (is carried by) applies to E18 Physical Thing in general.

E73_Information_Object :

This class comprises identifiable immaterial items, such as a poems, jokes, data sets, images, texts, multimedia objects, procedural prescriptions, computer program code, algorithm or mathematical formulae, that have an objectively recognizable structure and are documented as single units.An E73 Information Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. Instances of E73 Information Object of a linguistic nature should be declared as instances of the E33 Linguistic Object subclass. Instances of E73 Information Object of a documentary nature should be declared as instances of the E31 Document subclass.

Manuscriptefrbr:F4_Manifestation_Singleton

edm:ProvidedCHO

Digital Facsimile on Server

ecrm:E84_Information_Carrier

sc:Manifest rdf:type sc:Manifest

ecrm:E31_Document

Component

Folio

sc:Canvas

ecrm:E36_Visual_Item

sc:Image 1sc:Image

edm:WebResource

ecrm:E73_Information_Object

ecrm:P46_is_composed_ofecrm:P46_is_composed_of

oa:Motivation sc:Paintingoa:hasTarget

ecrm:P165_incorporates

oa:Annotation

wdrs:describedby

wdrs:describedby

ecrm:P70i_is_documented_in

ecrm:P165i_is_incorporated_in

Digital Facsimile edm:WebResource

ecrm:E73_Information_Object

edm:isShownBy

edm:isShownBy

ecrm:P165i_is_incorporated_in

efrbroo:R31i_has_Reproduction ecrm:P128_carries

ecrm:P106i_forms_part_of

ecrm:P138i_has_representationecrm:P130i_features_are_also_found_on

oa:hasBody

sc:Canvas -> ecrm:P138_represents -> E53_Place -> ecrm:P59_is_located_on_or_within -> Folio

IIIF - besoins de Biblissima (I)

ecrm:P70i_is_documented_in

sc:Canvas

IIIF - besoins de Biblissima (II)

MERCI

Stefanie Gehrke

Équipex Biblissimawww.biblissima-condorcet.fr