Post on 05-Dec-2014
description
Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) http://creativecommons.org/licenses/by-sa/4.0/
Zeri e LODEExtracting the Zeri photo archive to Linked Open Data: formalizing the conceptual model
Ciro Mattia Gonano – ciromattia@gmail.com Francesca Mambelli – francesca.mambelli6@unibo.it
Silvio Peroni – silvio.peroni@unibo.it Francesca Tomasi – francesca.tomasi@unibo.it
Fabio Vitali – fabio@cs.unibo.it
Digital Libraries 2014 ACM/IEEE Joint Conference on Digital Libraries (JCDL 2014) International Conference on Theory and Practice of Digital Libraries (TPDL 2014) London, 8th-12th September 2014
Summary
• The Zeri Photo Archive ✦ Zeri’s legacy ✦ Zeri Foundation ✦ “Zeri e LODE” project
• F Entry Ontology ✦ Main ontological entities ✦ Examples and queries ✦ Mapping to CIDOC-CRM
• Conclusions
The Zeri Photo Archive
Federico Zeri
• Federico Zeri (August 21, 1921 - October 5, 1998) was an Italian art historian, and a specialist in Italian Renaissance painting
• During his life, he collected 290,000 photographs of artworks and monuments, that he organised, expanded and improved throughout his entire career creating one of the most important photo collection in the world on art history
• Federico Zeri considered the photo archive a fundamental tool for studying as well as for philological analysis of the artworks
• Complex cross-reference system, in the form of handwritten and printed annotations on the photos ✦ provenance ✦ attributions ✦ restoration
Federico Zeri
• Federico Zeri (August 21, 1921 - October 5, 1998) was an Italian art historian, and a specialist in Italian Renaissance painting
• During his life, he collected 290,000 photographs of artworks and monuments, that he organised, expanded and improved throughout his entire career creating one of the most important photo collection in the world on art history
• Federico Zeri considered the photo archive a fundamental tool for studying as well as for philological analysis of the artworks
• Complex cross-reference system, in the form of handwritten and printed annotations on the photos ✦ provenance ✦ attributions ✦ restoration
(Ed.ni Brogi) 19637. PARIGI. Museo del Louvre. Testa della Gioconda; Leonardo da Vinci. (Riprod. interdetta).
An example of some metadata written on a photograph of Mona Lisa
http://www.fondazionezeri.unibo.it/foto/80000/78800/78415.jpg
Federico Zeri
• Federico Zeri (August 21, 1921 - October 5, 1998) was an Italian art historian, and a specialist in Italian Renaissance painting
• During his life, he collected 290,000 photographs of artworks and monuments, that he organised, expanded and improved throughout his entire career creating one of the most important photo collection in the world on art history
• Federico Zeri considered the photo archive a fundamental tool for studying as well as for philological analysis of the artworks
• Complex cross-reference system, in the form of handwritten and printed annotations on the photos ✦ provenance ✦ attributions ✦ restoration
(Ed.ni Brogi) 19637. PARIGI. Museo del Louvre. Testa della Gioconda; Leonardo da Vinci. (Riprod. interdetta).
author of the photograph
id location of the artwork (city) (building)
subject of the photograph
author of the artwork
permissions
An example of some metadata written on a photograph of Mona Lisa
http://www.fondazionezeri.unibo.it/foto/80000/78800/78415.jpg
Brogi 19637 Paris Louvre Museum Mona Lisa’s head Leonardo da Vinci Not to be reproduced
The Zeri Photo Archive
• Federico Zeri Foundation (http://www.fondazionezeri.unibo.it/) ✦ constituted in 2002 ✦ focus: make accessible to scholars and students all Zeri’s photographs by cataloguing,
digitalising and making them available online
• Cataloguing, issues: ✦ to adopt an entry that was compatible with national catalographic standards issued by the
Italian Cultural Heritage Ministry and structured to respect the specificity and organisation of the Zeri Library
✦ to save and standardise all the levels of information on the photographs, combined with that of conveying the hierarchical structure of the Zeri Library
Scheda F
• Each record includes two primary catalogue units: ✦ one describing the photograph (Scheda F, or F Entry in English) ✦ the other describing the artwork represented in such photograph (Scheda OA, or OA Entry in English)
• These two entries and their connections give rise to a symmetrical database that allows two-sided research by users and transversal navigation
• Scheda F is a standard of the Italian Central Institute for Cataloging and Documentation, and allows us torecord: ✦ photographer ✦ chronology of the positive ✦ place and date of the shot ✦ location and classification of the photo ✦ previous locations of the photo ✦ technical data of the photograph ✦ editing and publishing ✦ copyright ✦ codes
✦ subject ✦ title ✦ state of preservation
Scheda F
• Each record includes two primary catalogue units: ✦ one describing the photograph (Scheda F, or F Entry in English) ✦ the other describing the artwork represented in such photograph (Scheda OA, or OA Entry in English)
• These two entries and their connections give rise to a symmetrical database that allows two-sided research by users and transversal navigation
• Scheda F is a standard of the Italian Central Institute for Cataloging and Documentation, and allows us torecord: ✦ photographer ✦ chronology of the positive ✦ place and date of the shot ✦ location and classification of the photo ✦ previous locations of the photo ✦ technical data of the photograph ✦ editing and publishing ✦ copyright ✦ codes
✦ subject ✦ title ✦ state of preservation
<SCHEDA intestazione="Gabinetto Fotografico della Soprintendenza Speciale per il ! Patrimonio Storico, Artistico ed Etnoantropologico e per il Polo Museale della città di ! Firenze , Roma - Galleria Nazionale d'Arte Antica, Corsini. Beato Angelico - ! Particolare" sercdf="112321" sercdoa="12725"> <PARAGRAFO etichetta="CLASSIFICATION"> <SERCD etichetta="SERCD">112321</SERCD> <SERCDOA etichetta="SERCDOA">12725</SERCDOA> <INVN etichetta="Inventory number">34927</INVN> <UBFP etichetta="Collection">Fototeca Zeri</UBFP> <UBFS etichetta="Archive series">Pittura italiana</UBFS> <UBFN etichetta="Container number">0146</UBFN> <UBFT etichetta="Container heading">Pittura italiana sec. XV. Firenze. Beato ! Angelico: tavole minori, affreschi</UBFT> <UBFF etichetta="Folder number">1</UBFF> <UBFU etichetta="Folder heading">Beato Angelico: piccoli trittici</UBFU> <UBFC etichetta="Shelfmark">PI_0146/1/12</UBFC> </PARAGRAFO> <PARAGRAFO etichetta="SUBJECT"> <SGTI etichetta="Subject">Giudizio Universale, Ascensione di Cristo, ! Pentecoste</SGTI> <OGTD etichetta=“Object">dipinto</OGTD>! … </PARAGRAFO>! …!</SCHEDA>
An excerpt of the XML exportation of a Scheda F of a photograph included in the Zeri Foundation’s Library
Scheda F
• Each record includes two primary catalogue units: ✦ one describing the photograph (Scheda F, or F Entry in English) ✦ the other describing the artwork represented in such photograph (Scheda OA, or OA Entry in English)
• These two entries and their connections give rise to a symmetrical database that allows two-sided research by users and transversal navigation
• Scheda F is a standard of the Italian Central Institute for Cataloging and Documentation, and allows us torecord: ✦ photographer ✦ chronology of the positive ✦ place and date of the shot ✦ location and classification of the photo ✦ previous locations of the photo ✦ technical data of the photograph ✦ editing and publishing ✦ copyright ✦ codes
✦ subject ✦ title ✦ state of preservation
<SCHEDA intestazione="Gabinetto Fotografico della Soprintendenza Speciale per il ! Patrimonio Storico, Artistico ed Etnoantropologico e per il Polo Museale della città di ! Firenze , Roma - Galleria Nazionale d'Arte Antica, Corsini. Beato Angelico - ! Particolare" sercdf="112321" sercdoa="12725"> <PARAGRAFO etichetta="CLASSIFICATION"> <SERCD etichetta="SERCD">112321</SERCD> <SERCDOA etichetta="SERCDOA">12725</SERCDOA> <INVN etichetta="Inventory number">34927</INVN> <UBFP etichetta="Collection">Fototeca Zeri</UBFP> <UBFS etichetta="Archive series">Pittura italiana</UBFS> <UBFN etichetta="Container number">0146</UBFN> <UBFT etichetta="Container heading">Pittura italiana sec. XV. Firenze. Beato ! Angelico: tavole minori, affreschi</UBFT> <UBFF etichetta="Folder number">1</UBFF> <UBFU etichetta="Folder heading">Beato Angelico: piccoli trittici</UBFU> <UBFC etichetta="Shelfmark">PI_0146/1/12</UBFC> </PARAGRAFO> <PARAGRAFO etichetta="SUBJECT"> <SGTI etichetta="Subject">Giudizio Universale, Ascensione di Cristo, ! Pentecoste</SGTI> <OGTD etichetta=“Object">dipinto</OGTD>! … </PARAGRAFO>! …!</SCHEDA>
An excerpt of the XML exportation of a Scheda F of a photograph included in the Zeri Foundation’s Library
The Scheda F as shown in the Zeri Foundation website
“Zeri e LODE” project from DB to LOD
Zeri Foundation database
The project is organised in 4 steps:
“Zeri e LODE” project from DB to LOD
Zeri Foundation database
F Entry Ontology OA Entry Ontology
Create the ontology from E/R model and
data in DB
The project is organised in 4 steps:
1. Developing ontologies for Scheda F and Scheda OA
“Zeri e LODE” project from DB to LOD
Zeri Foundation database
F Entry Ontology OA Entry Ontology
Create the ontology from E/R model and
data in DB
SPAR’s FaBiOF R B R PROV-O
use entities defined in
The project is organised in 4 steps:
1. Developing ontologies for Scheda F and Scheda OA 1bis. Reuse existing
models
“Zeri e LODE” project from DB to LOD
Zeri Foundation database
F Entry Ontology OA Entry Ontology
Create the ontology from E/R model and
data in DB
Convert DB data into RDF according to the ontologies
SPAR’s FaBiOF R B R PROV-O
use entities defined in
The project is organised in 4 steps:
1. Developing ontologies for Scheda F and Scheda OA
2. Data conversion into RDF
1bis. Reuse existing models
“Zeri e LODE” project from DB to LOD
Zeri Foundation database
F Entry Ontology OA Entry Ontology
Create the ontology from E/R model and
data in DB
Convert DB data into RDF according to the ontologies
Add links to LOD
SPAR’s FaBiOF R B R PROV-O
use entities defined in
The project is organised in 4 steps:
1. Developing ontologies for Scheda F and Scheda OA
2. Data conversion into RDF 3. Publishing in LOD
through RDF links
1bis. Reuse existing models
“Zeri e LODE” project from DB to LOD
Zeri Foundation database
F Entry Ontology OA Entry Ontology
Create the ontology from E/R model and
data in DB
Convert DB data into RDF according to the ontologies
Add links to LOD
Different devices for browsing
Create a responsive website based on a public faceted user
interface for browsing RDF data
SPAR’s FaBiOF R B R PROV-O
use entities defined in
The project is organised in 4 steps:
1. Developing ontologies for Scheda F and Scheda OA
2. Data conversion into RDF 3. Publishing in LOD
through RDF links
4. Developing smart applications that use such data for real
1bis. Reuse existing models
F Entry Ontology (FEO)
F Entry Ontology
• SAMOD outcomes: ✦ ontology source ✦ documentation ✦ examples of usage ✦ exemplar queries
• Reuse of ontologies ✦ FRBR: describes online library
catalogues and bibliographic databases from a user’s perspective
✦ FaBiO: it allows us to record and publish on the Semantic Web bibliographic records of scholarly endeavours and other cultural object
✦ PROV-O: used to represent and interchange provenance information generated in different systems and under different contexts
Available at http://www.essepuntato.it/2014/03/fentry
SAMOD methodology is available at http://www.essepuntato.it/samod
F Entry Ontology
• SAMOD outcomes: ✦ ontology source ✦ documentation ✦ examples of usage ✦ exemplar queries
• Reuse of ontologies ✦ FRBR: describes online library
catalogues and bibliographic databases from a user’s perspective
✦ FaBiO: it allows us to record and publish on the Semantic Web bibliographic records of scholarly endeavours and other cultural object
✦ PROV-O: used to represent and interchange provenance information generated in different systems and under different contexts
Available at http://www.essepuntato.it/2014/03/fentry
SAMOD methodology is available at http://www.essepuntato.it/samod
F Entry Ontology
• SAMOD outcomes: ✦ ontology source ✦ documentation ✦ examples of usage ✦ exemplar queries
• Reuse of ontologies ✦ FRBR: describes online library
catalogues and bibliographic databases from a user’s perspective
✦ FaBiO: it allows us to record and publish on the Semantic Web bibliographic records of scholarly endeavours and other cultural object
✦ PROV-O: used to represent and interchange provenance information generated in different systems and under different contexts
Available at http://www.essepuntato.it/2014/03/fentry
SAMOD methodology is available at http://www.essepuntato.it/samod
F Entry Ontology
• SAMOD outcomes: ✦ ontology source ✦ documentation ✦ examples of usage ✦ exemplar queries
• Reuse of ontologies ✦ FRBR: describes online library
catalogues and bibliographic databases from a user’s perspective
✦ FaBiO: it allows us to record and publish on the Semantic Web bibliographic records of scholarly endeavours and other cultural object
✦ PROV-O: used to represent and interchange provenance information generated in different systems and under different contexts
Available at http://www.essepuntato.it/2014/03/fentry
SAMOD methodology is available at http://www.essepuntato.it/samod
Main ontological entities
Main ontological entities
• fentry:FEntry It is the class describing all the documents containing metadata about a photograph and (some) metadata about the concrete object portrayed by the photograph. It is subclass of fabio:EntityMetadata, which is used to describe the photograph and its subject, including for example the name of photograph, the subject creator, the title of the subject, and the date and place of the shot, etc.
Main ontological entities
• fentry:FEntry It is the class describing all the documents containing metadata about a photograph and (some) metadata about the concrete object portrayed by the photograph. It is subclass of fabio:EntityMetadata, which is used to describe the photograph and its subject, including for example the name of photograph, the subject creator, the title of the subject, and the date and place of the shot, etc.
• fentry:describesIt allows one to link a Scheda F to the photograph and the portrayed object the Scheda F describes.
Main ontological entities
• fentry:FEntry It is the class describing all the documents containing metadata about a photograph and (some) metadata about the concrete object portrayed by the photograph. It is subclass of fabio:EntityMetadata, which is used to describe the photograph and its subject, including for example the name of photograph, the subject creator, the title of the subject, and the date and place of the shot, etc.
• fentry:describesIt allows one to link a Scheda F to the photograph and the portrayed object the Scheda F describes.
• fentry:Photograph It is a static, visual representation of some concrete object (or part of it) or a group of different objects. It is subclass of fabio:StillImage, a class that describe any recorded static visual representation, such as diagrams, drawings, graphs, graphic designs, plans, maps, photographs and prints.
An examples (in Turtle)
• A Scheda F describes that
:f-entry-1 a fentry:FEntry ;!! fentry:describes
An examples (in Turtle)
• A Scheda F describes that ✦ the Federico Zeri
Foundation owns a photograph
:f-entry-1 a fentry:FEntry ;!! fentry:describes
:madonna-and-child-photo-item a fabio:AnalogueItem ;!! prov:wasAttributedTo :federico-zeri-foundation ;
! ! :madonna-and-child-photo-item ,
An examples (in Turtle)
• A Scheda F describes that ✦ the Federico Zeri
Foundation owns a photograph
:f-entry-1 a fentry:FEntry ;!! fentry:describes
:madonna-and-child-photo-item a fabio:AnalogueItem ;!! prov:wasAttributedTo :federico-zeri-foundation ;
! ! :madonna-and-child-photo-item ,
:madonna-and-child-photo-work a fentry:Photograph ;!! fabio:hasPortrayal :madonna-and-child-photo-item ;!! prov:wasAttributedTo :bruckmann ;
! ! :madonna-and-child-photo-work ,
✦ the photograph was authored by the publisher Bruckmann
An examples (in Turtle)
• A Scheda F describes that ✦ the Federico Zeri
Foundation owns a photograph
:f-entry-1 a fentry:FEntry ;!! fentry:describes
:madonna-and-child-photo-item a fabio:AnalogueItem ;!! prov:wasAttributedTo :federico-zeri-foundation ;
! ! :madonna-and-child-photo-item ,
:madonna-and-child-photo-work a fentry:Photograph ;!! fabio:hasPortrayal :madonna-and-child-photo-item ;!! prov:wasAttributedTo :bruckmann ;
! ! :madonna-and-child-photo-work ,
! frbr:subject :madonna-and-child-item .
! ! :madonna-and-child-item ,
✦ the photograph was authored by the publisher Bruckmann
✦ the photograph portrays the Madonna and Child
An examples (in Turtle)
• A Scheda F describes that ✦ the Federico Zeri
Foundation owns a photograph
:f-entry-1 a fentry:FEntry ;!! fentry:describes
:madonna-and-child-photo-item a fabio:AnalogueItem ;!! prov:wasAttributedTo :federico-zeri-foundation ;
! ! :madonna-and-child-photo-item ,
:madonna-and-child-photo-work a fentry:Photograph ;!! fabio:hasPortrayal :madonna-and-child-photo-item ;!! prov:wasAttributedTo :bruckmann ;
! ! :madonna-and-child-photo-work ,
! frbr:subject :madonna-and-child-item .
! ! :madonna-and-child-item ,! ! :madonna-and-child-work .
:madonna-and-child-work a fabio:ArtisticWork ;!! prov:wasAttributedTo :leonardo-da-vinci ;!! fabio:hasPortrayal :madonna-and-child-item .
✦ the photograph was authored by the publisher Bruckmann
✦ the photograph portrays the Madonna and Child
✦ Madonna and Child was made by Leonardo da Vinci
An examples (in Turtle)
• A Scheda F describes that ✦ the Federico Zeri
Foundation owns a photograph
:f-entry-1 a fentry:FEntry ;!! fentry:describes
:madonna-and-child-photo-item a fabio:AnalogueItem ;!! prov:wasAttributedTo :federico-zeri-foundation ;
! ! :madonna-and-child-photo-item ,
:madonna-and-child-photo-work a fentry:Photograph ;!! fabio:hasPortrayal :madonna-and-child-photo-item ;!! prov:wasAttributedTo :bruckmann ;
! ! :madonna-and-child-photo-work ,
! frbr:subject :madonna-and-child-item .
! ! :madonna-and-child-item ,! ! :madonna-and-child-work .
:madonna-and-child-work a fabio:ArtisticWork ;!! prov:wasAttributedTo :leonardo-da-vinci ;!! fabio:hasPortrayal :madonna-and-child-item .
:madonna-and-child-creation a prov:Activity ; !! prov:startedAtTime "1470-01-01T00:00:00"^^xsd:dateTime ; !! prov:endedAtTime "1478-01-01T00:00:00"^^xsd:dateTime ;!! prov:wasAssociatedWith :leonardo-da-vinci ;!! prov:generated :madonna-and-child-item .
✦ the photograph was authored by the publisher Bruckmann
✦ the photograph portrays the Madonna and Child
✦ Madonna and Child was made by Leonardo da Vinci
✦ Madonna and Child was made between 1470 and 1478
An examples (in Turtle)
• A Scheda F describes that ✦ the Federico Zeri
Foundation owns a photograph
:f-entry-1 a fentry:FEntry ;!! fentry:describes
:madonna-and-child-photo-item a fabio:AnalogueItem ;!! prov:wasAttributedTo :federico-zeri-foundation ;
! ! :madonna-and-child-photo-item ,
:madonna-and-child-photo-work a fentry:Photograph ;!! fabio:hasPortrayal :madonna-and-child-photo-item ;!! prov:wasAttributedTo :bruckmann ;
! ! :madonna-and-child-photo-work ,
! frbr:subject :madonna-and-child-item .
! ! :madonna-and-child-item ,! ! :madonna-and-child-work .
:madonna-and-child-work a fabio:ArtisticWork ;!! prov:wasAttributedTo :leonardo-da-vinci ;!! fabio:hasPortrayal :madonna-and-child-item .
:madonna-and-child-creation a prov:Activity ; !! prov:startedAtTime "1470-01-01T00:00:00"^^xsd:dateTime ; !! prov:endedAtTime "1478-01-01T00:00:00"^^xsd:dateTime ;!! prov:wasAssociatedWith :leonardo-da-vinci ;!! prov:generated :madonna-and-child-item .
! frbr:partOf :box0360-issue1 .!!:box0360-issue1 a fabio:AnalogueItem ;!! frbr:partOf :box0360 .!!:box0360 a fabio:AnalogueItem .
✦ the photograph was authored by the publisher Bruckmann
✦ the photograph portrays the Madonna and Child
✦ Madonna and Child was made by Leonardo da Vinci
✦ Madonna and Child was made between 1470 and 1478
✦ the photograph is part of the box 0360, issue 1
A query (in SPARQL)
• What are all the photographs that portray some detail of a larger work?
• When were all the subjects of photographs created and by whom (if any)?
A query (in SPARQL)
• What are all the photographs that portray some detail of a larger work?
• When were all the subjects of photographs created and by whom (if any)?
SELECT DISTINCT ?photo ?subj ?part WHERE { !! ?photo a fentry:Photograph ;!! ! frbr:subject ?subj .!! ?subj (^fabio:hasPortrayal|^fabio:hasManifestation)*/frbr:partOf ?part .!}
A query (in SPARQL)
• What are all the photographs that portray some detail of a larger work?
• When were all the subjects of photographs created and by whom (if any)?
SELECT DISTINCT ?subj ?author ?s ?e WHERE { !! ?photo a fentry:Photograph ; frbr:subject ?subj .!! ?activity a prov:Activity ;!! ! prov:generated ?subj ;!! ! prov:startedAtTime ?s ;!! ! prov:endedAtTime ?e!! OPTIONAL { ?activity prov:wasAssociatedWith ?author } }
SELECT DISTINCT ?photo ?subj ?part WHERE { !! ?photo a fentry:Photograph ;!! ! frbr:subject ?subj .!! ?subj (^fabio:hasPortrayal|^fabio:hasManifestation)*/frbr:partOf ?part .!}
Mapping Scheda F concepts to CIDOC-CRM
E22 Man-Made Object E22 Man-Made ObjectP62 is depicted by
E39 Actor
E12 Production
P108 has produced
P14 performed
E31 Document
P70 documents P70 documents
E57 Material
E54 Dimension
E55 Type
P45 consist of
P43 has dimension
P32 used technique
E65 Creation
P94 has created
E28 Conceptual Object
P14 performed
E53 Place
E4 Period
P7 took place P7 took place
P10 falls within P10 falls within
P2 has type
Mapping Scheda F concepts to CIDOC-CRM
E22 Man-Made Object E22 Man-Made ObjectP62 is depicted by
E39 Actor
E12 Production
P108 has produced
P14 performed
E31 Document
P70 documents P70 documents
E57 Material
E54 Dimension
E55 Type
P45 consist of
P43 has dimension
P32 used technique
E65 Creation
P94 has created
E28 Conceptual Object
P14 performed
E53 Place
E4 Period
P7 took place P7 took place
P10 falls within P10 falls within
P2 has type
Scheda F
Mapping Scheda F concepts to CIDOC-CRM
E22 Man-Made Object E22 Man-Made ObjectP62 is depicted by
E39 Actor
E12 Production
P108 has produced
P14 performed
E31 Document
P70 documents P70 documents
E57 Material
E54 Dimension
E55 Type
P45 consist of
P43 has dimension
P32 used technique
E65 Creation
P94 has created
E28 Conceptual Object
P14 performed
E53 Place
E4 Period
P7 took place P7 took place
P10 falls within P10 falls within
P2 has type
Scheda FPhotograph
Mapping Scheda F concepts to CIDOC-CRM
E22 Man-Made Object E22 Man-Made ObjectP62 is depicted by
E39 Actor
E12 Production
P108 has produced
P14 performed
E31 Document
P70 documents P70 documents
E57 Material
E54 Dimension
E55 Type
P45 consist of
P43 has dimension
P32 used technique
E65 Creation
P94 has created
E28 Conceptual Object
P14 performed
E53 Place
E4 Period
P7 took place P7 took place
P10 falls within P10 falls within
P2 has type
Scheda F
Subject
Photograph
Mapping Scheda F concepts to CIDOC-CRM
E22 Man-Made Object E22 Man-Made ObjectP62 is depicted by
E39 Actor
E12 Production
P108 has produced
P14 performed
E31 Document
P70 documents P70 documents
E57 Material
E54 Dimension
E55 Type
P45 consist of
P43 has dimension
P32 used technique
E65 Creation
P94 has created
E28 Conceptual Object
P14 performed
E53 Place
E4 Period
P7 took place P7 took place
P10 falls within P10 falls within
P2 has type
Scheda F
Subject
Photograph
Mapping between Scheda F and CIDOC-CRM
!
Conclusions
Towards the next steps
• The F Entry Ontology (FEO) is the first outcome of our “Zeri e LODE” project on converting the DB data of the Zeri Foundation’s Photo Library into RDF
• Lot of works still to be done ✦ Alignment with
✴ CIDOC-CRM (by using part of FRBR-OO) [in-progress] ✴ OAI Object Reuse and Exchange (OAI-ORE)
✦ Extending FEO introducing an explicit FRBR expression entity (e.g., Shot), so as to associate to it metadata concerning when/where a photo was taken [in-progress]
✦ Development of a new ontology for OA Entry [in-progress] ✦ Converting DB data into RDF according to the ontologies [in-progress] ✦ Publishing all data as Open Linked Data
Thank you for your attention
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
did it pass model, data, query tests?
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
nGo to the previous milestone
did it pass model, data, query tests?
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
nGo to the previous milestone
Merge the modelet with the current final model
milestone y
did it pass model, data, query tests?
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
OEs merge the modelet of the new test case with the current model produced by the end of the last process iteration (first iteration: modelet becomes current model)
2.
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
nGo to the previous milestone
Merge the modelet with the current final model
milestone y
did it pass model, data, query tests?
did it pass model, data, query tests?
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
OEs merge the modelet of the new test case with the current model produced by the end of the last process iteration (first iteration: modelet becomes current model)
2.
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
nGo to the previous milestone
n
Merge the modelet with the current final model
milestone y
did it pass model, data, query tests?
did it pass model, data, query tests?
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
OEs merge the modelet of the new test case with the current model produced by the end of the last process iteration (first iteration: modelet becomes current model)
2.
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
nGo to the previous milestone
n
Merge the modelet with the current final model
milestone y
Refactor the current final model
milestone y did it pass model, data, query tests?
did it pass model, data, query tests?
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
OEs merge the modelet of the new test case with the current model produced by the end of the last process iteration (first iteration: modelet becomes current model)
2.OEs refactor (important: reuse existing knowledge) the current model, focussing on the last part added in the previous step
3.
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
nGo to the previous milestone
n
Merge the modelet with the current final model
milestone y
Refactor the current final model
milestone y did it pass model, data, query tests?
did it pass model, data, query tests?
did it pass model, data, query tests?
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
OEs merge the modelet of the new test case with the current model produced by the end of the last process iteration (first iteration: modelet becomes current model)
2.OEs refactor (important: reuse existing knowledge) the current model, focussing on the last part added in the previous step
3.
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
nGo to the previous milestone
n
n
Merge the modelet with the current final model
milestone y
Refactor the current final model
milestone y did it pass model, data, query tests?
did it pass model, data, query tests?
did it pass model, data, query tests?
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
OEs merge the modelet of the new test case with the current model produced by the end of the last process iteration (first iteration: modelet becomes current model)
2.OEs refactor (important: reuse existing knowledge) the current model, focussing on the last part added in the previous step
3.
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
nGo to the previous milestone
n
n
Merge the modelet with the current final model
milestone y
Refactor the current final model
milestone y
y
is there any further scenario?
did it pass model, data, query tests?
did it pass model, data, query tests?
did it pass model, data, query tests?
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
OEs merge the modelet of the new test case with the current model produced by the end of the last process iteration (first iteration: modelet becomes current model)
2.OEs refactor (important: reuse existing knowledge) the current model, focussing on the last part added in the previous step
3.
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
nGo to the previous milestone
n
n
Merge the modelet with the current final model
milestone y
Refactor the current final model
milestone y
y
is there any further scenario?
did it pass model, data, query tests?
did it pass model, data, query tests?
did it pass model, data, query tests?
end of process
n
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
OEs merge the modelet of the new test case with the current model produced by the end of the last process iteration (first iteration: modelet becomes current model)
2.OEs refactor (important: reuse existing knowledge) the current model, focussing on the last part added in the previous step
3.
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
y
nGo to the previous milestone
n
n
Merge the modelet with the current final model
milestone y
Refactor the current final model
milestone y
y
is there any further scenario?
did it pass model, data, query tests?
did it pass model, data, query tests?
did it pass model, data, query tests?
end of process
n
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
OEs merge the modelet of the new test case with the current model produced by the end of the last process iteration (first iteration: modelet becomes current model)
2.OEs refactor (important: reuse existing knowledge) the current model, focussing on the last part added in the previous step
3.
Developing an ontology for Scheda F with SAMOD http://www.essepuntato.it/samod
Collect requirements and develop a modeletmilestone
y
nGo to the previous milestone
n
n
Merge the modelet with the current final model
milestone y
Refactor the current final model
milestone y
y
is there any further scenario?
did it pass model, data, query tests?
did it pass model, data, query tests?
did it pass model, data, query tests?
end of process
n
if we need to extend the model in the future
SAMOD is an agile methodology for the development of ontologies by means of small steps of an iterative process that focuses on creating well-developed and documented models through using significative exemplar of data
Ontology Engineers (OEs) collect all the information about a specific domain, with the help of Domain Experts (DEs), build a modelet formalising the domain in consideration, and then create a new test case
1.
OEs merge the modelet of the new test case with the current model produced by the end of the last process iteration (first iteration: modelet becomes current model)
2.OEs refactor (important: reuse existing knowledge) the current model, focussing on the last part added in the previous step
3.