1. WP2200 Identifiers and Citability
Topic: Access
WP2200 Identifiers and Citability
Maurizio Lunghi,
Fondazione Rinascimento Digitale
APARSEN Second Review Meeting
Luxembourg, 25–26 March 2013

2. APARSEN topic: Access - Persistent Identifiers
The meaning of Persistent Identifiers (PI) in digital preservation is fundamental not only for stable identification/access and citation of digital contents, but also for trust and other significant properties.
PI are instrumental for APARSEN to set up some services in line with expectations of VCoE potential users.
Very fragmented situation with different technologies and isolated user domains and communities It’s not reasonable to have a unique PI system
PI for actors are emerging …. 2

3. WP22: Identifiers & Citation – what’s wrong?
ISO 2108:2005 International Standard Book Number (ISBN)
ISO 3297:2007 International Standard Serial Number (ISSN)
ISO 3901:2001 International Standard Recording Code (ISRC)
ISO 10957:2009 International Standard Music Number (ISMN)
ISO :2002 International Standard Audiovisual Number (ISAN) Part 1 work identifier
ISO :2007 International Standard Audiovisual Number (ISAN) Part 2: version identifier
ISO 15707:2001 International Standard Musical Work Code (ISWC)
ISO 21047:2009 International Standard Text Code (ISTC)
ISO 26324:2012 Digital object identifier system35 (DOI)
ISO 27729:2012 International Standard Name Identifier (ISNI)
ISO 27730:2012 International Standard Collection Identifier (ISCI) 3

4. Persistent Identifiers what’s that ??
PI are not only a number, it’s a service based on a contract between user community or content holders and service-providers responsible for the implementation and maintenance of the PI-service. In addition to access for a resource we need to check other significant properties:
stable identification (PI) … multiple too
authenticity + integrity
provenance + author
owner + rights +
relations with other resources & with actors

5. Persistent Identifiers systems
PI technologies help make stable reference to digital resources, even if it is well-known that persistency is not only a technical issue, no technology can exist indefinitely or guarantee services without a trusted organization behind and a clearly defined policy.
PI systems are meant as:
a) available technology
b) trusted organization
c) precise policies for digital preservation

6. WP22: Identifiers and Citation - Objectives
GOAL: to defragment EU initiatives on PI
GOAL: not new technology but a way to cooperate and use data from PI domains isolated, a common format to expose data and to develop interoperability and services tailored on user requirements
GOAL: community building and experts involvement, engagement of relevant projects in the domain (PI user scenarios + usergroup + workshop + Webinar) 6

7. WP22: Identifiers and Citation
2011
2012
2013
2014 7

8. WP22  Activity 2011
User requirements analysis and survey of current practices with PI systems (questionnaire > 100 cultural and scientific user communities)
User scenarios description and expectations in terms of services (12 scenarios)
First proposal of the Interoperability Framework (IF) model and ontology 8

9. User Requirements and User Scenarios
TRUST CERTIFICATION CROSS-DOMAINS
Scenarios on Citability and Metrics services
Scenarios on Global Resolution Services
Scenarios on Digital Object Certification
WHO
WHAT
WHY
WHERE
WHEN
HOW
ISSUES
USE CASES 9

10. WP22  Activity 2012
Validation of the IF model through a user group with 30 experts on PI [March-October 2012]
Definition and set up of a demonstrator with data from different PI domains and for objects, people [November-December 2012]
Refinement of the IF model and ontology, new proposal (FRBRoo) presented at the workshop in Florence on 13 Dec 10

11. Interoperability Framework (IF): assumptions
MAIN ASSUMPTIONS:
In the IF we consider only entities identified by at least one PI
Only PI Domains (PIDs) that meet some criteria are eligible to be considered in the IF: trusted PI systems
We delegate the responsibility to define relations among resources and actors to the trusted PIDs
We don’t address digital preservation policy but delegate that to the trusted PI domains 11

12. WP22: Trusted PI systems: criteria
Having at least one Registration Agency.
Having one Resolver accessible on the Internet.
Uniqueness of the assigned PIs within the PI domain.
Guaranteeing the persistence of the assigned PIs.
User communities of the PID should implement policies for digital preservation (e.g. trusted digital repositories)
Reliable resolution.
Uncoupling the PIs from the resolver.
Managing the relations between the PIs within the domain. 12

13. Interoperability Framework (IF): main concepts
Criteria – entities – properties - relations
Definition: A Digital Object is any kind of digital resource, which is identified by at least one PI assigned by a trusted PID.
Relationships:
Is identified by at least one digital object PI (<hasPI_do>)
Is created by an Author (<created_by>);
Is related to other digital objects (<related_to>);
Is associated to Policies (<associated_to>);
Can be described by metadata (<has_metadata>);
Digital Object
Persistent Identifier (PI)
Other PI
Resolver
Author (PI)
Institution (PI)
Other Entities
Metadata 13

14. Scenario 1: Registration Authorities and Persistent Identifiers
Registration Authority
Issues new identifiers to registered users/institutions
Maintains registries of identifiers
Persistent Identifier
String used to uniquely identify a resource within a domain regardless of where the resource is located 14

15. Scenario 2: Persistent Identifiers, Actors and Works
People (individually or in groups) performing intentional actions for which they can be held responsible
Authors, Contributors …
Institutions
Definition of Roles 15

16. Scenario 3: Identifiers and Objects
Physical or Digital (Type)
Carrier of the Edition
Actors
Publisher (role)
Participated in … Publication (Event) 16

17. Scenarios Integration1 2 3 17

18. Use cases translation and service design
Atomic Service
Resolution services (use cases 1,2,9)
Resolution counter
Get Entity PI list
Service Structure
Composite Services
Entity relationship service (use cases 4,10)
Metadata Integration Service
Selection and apprisal preservation service
(use cases 5,8)
Cluster Services
Scientific Career assessment (use cases 4,7)
Archival Curation service (use case 8,9) 18 18

19. Example of atomic services – PI-Alternative PI
Input: PI
Output: PIs list
Description: The PI-alternative PIs service retrieve alternative PIs of a given PI exploiting the co-reference relations among PIs exposed in the Interoperability Framework presenting them with the same level of service. 19 19

20. Example of cluster service – Scientific carreer assessment
Input: Author PI
Output: list of publications (metadata + PI) filtered
Description: This service retrieves all the objects associated to the author PI satisfying the search criteria from all PI domains and presents them in a common format with the same metadata schema. The final output is the list of publications of the author, which responds to the specified criteria. 20 20

21. WP22: Scientific Results and dissemination
IPRES 2012
Maurizio Lunghi, Emanuele Bellini, Chiara Cirinnà, Barbara Bazzanella, Paolo Bouquet, David Giaretta and René van Horik - Interoperability Framework for Persistent Identifiers systems - iPRES2012 – Toronto
IEEE SITIS 2012
Bellini E., Luddi, C. ;  Cirinnà, C. ;  Lunghi, M. ;  Felicetti, A. ;  Bazzanella, B. ;  Bouquet, P. -  Interoperability Knowledge Base for Persistent Identifiers Interoperability Framework - Eighth International Conference on Signal Image Technology and Internet Based Systems (SITIS), Nov. 2012 - Napoli
Workshop APARSEN
Bellini, E. Luddi, C. ;  Cirinnà, C. ;  Lunghi, M. ;  Felicetti, A. ;  Bazzanella, B. ;  René van Horik . – Workshop on interoperability for Persistent Identifiers systems – 13 Dec 2012 - Florence
Webinar 
Bellini, E.;  Lunghi, M. -  Webinar on Interoperability for Persistent Identifiers systems – 15 Feb 2013 21

22. Workshop on interoperability for Persistent Identifiers systems
WP22: Workshop APARSEN
Workshop on interoperability for Persistent Identifiers systems
13 Dec 2012 - Florence
EUDAT
SARA
EUROPEANA
EPIC
RDA
SCAPE
OPF
PersID
DATACITE
DOI Foundation 22

23. WP22: Prototype Implementation
DANS
Schema
Protocols
Dublin Core
DNB
SRU
IKB
SPARQL
Dublin Core S1
JLIS
D2R PI
SQL
RDF
OAI-PMH
Dublin Core
FRD S2
ORCID
OAI-PMH
CERN
WEB
MARCXML
Interoperability
Services
DC-FRBR mapping
MARCXML – FRBR mapping
WEB
CERN - Author
proprietary 23 23

24. WP22: INTEROPERABILITY FRAMEWORK (IF)
Contents from all PI domains now
are accessible in the same way
ISNI
VIAF
INTEROPERABILITY
FRAMEWORK
CERN
ORCID
New services
cross-domains
for users requirements
FRD
DNB
DANS
NBN
Handle
DOI
ARK
STM
GLOBIT
CERN

25. WP22  Action Plan
Validation of the new IF model and ontology through the HLEG with new experts [February-May 2013]
Expansion of the demonstrator on a distributed environment with content providers on LOD [April-June 2013]
Proposal of few services and development on a cross PI Domains (PIDs) basis [July-October 2013]
Check user satisfaction on services and community building to implement and populate the IF [November-December  Dec 2014] 25

26. INTEROPERABILITY FRAMEWORK (IF)
Contents from all PI domains expose
on LOD in the same way
 Ring of Trust
IF on LOD
CERN
New services
cross-domains
for users requirements
DNB
FRD
DANS

27. WP22: Identifiers and Citation  VCoE
Implications for common vision and VCoE –
Promoting the use of a common terminology within stream 2 and other streams – GLOSSARY
Common understanding with a wide user community of PI terms & functions and agreement on the Interoperability Framework elements – ONTOLOGY
Implementation of the Interoperability Framework, initially on LOD and then on Semantic Web, populating it with real data and relations – RING of TRUST
Development of some services tailored on user requirements cross PI-domains thanks to the common format – SERVICES 27

28. WP22: Identifiers and Citation - Deliverables
D22.1 PI system framework (M12)
D22.2 Demonstrator set up and definition of added value services: Part 1 (M24)
D22.3 Demonstrator set up and definition of added value services: Part 2 (M36)
D22.4 The Interoperability Framework implementation with added value services (M48) 28

29. D22.1 Authors and Contributors
Emanuele Bellini (FRD) Maurizio Lunghi (FRD)Chiara Cirinnà (FRD) Achille Felicetti (FRD), Cinzia Luddi (FRD)
Barbara Bazzanella (UNITN), Paolo Bouquet (UNITN)
Salvatore Mele (CERN), Hervé L'Hours (UESSEX), Yannis Tzitzikas (FORTH), Marjan Grootveld (DANS), Rene van Horik (DANS), Gerald Jaeschke (GLOBIT), Eefke Smit (STM), Sabine Schrimpf (DNB), Kirnn Kaur (BL), Heikki Helin (CSC), David Giaretta (APA) 29

30. Network of Excellence