me4dcap v0.1: a method for the development of dublin core application profiles

TOC Motivation Introduction Research Methodology Me4DCAP V0.1 Future Work Conclusions Questions THE END

Me4DCAP V0.1: A method for the development of DublinCore Application Profiles

Mariana Curado Malta & Ana Alice BaptistaAlgoritmi Center, University of Minho

[email protected]@dsi.uminho.pt

ELPUB, Karlskrona - Sweden 2013

This project is financed with FEDER funds by the Programa Operacional Fatores de Competitividade – COMPETE

and by Portuguese National Funds through FCT – Fundacao para a Ciencia e Tecnologia for the project:

FCOMP-01-0124-FEDER-022674

Mariana Malta & Ana Alice Baptista

Me4DCAP V0.1: A method for the development of Dublin Core Application Profiles

Motivation

Introduction

Research Methodology

Me4DCAP V0.1

Conclusions

Questions

Semantic Web, Metadata, RDF

I Semantic Web related project

I the Semantic Web is about common formats for theintegration and combination of data from different sources

I Its architecture has several layers

I One layer, the “Data interchange: RDF“ has to do withmetadata

I Metadata: data that describes resources with information,and that follows well defined rules of metadata-schemes

I Metadata-scheme: a set of elements designed for a specificpurpose - to describe a particular resource

DCAM, DCAP

I Dublin Core Metadata Initiative (DCMI1), created newinstruments with a goal: to speak a common language

I Dublin Core Abstract Model (DCAM): a model developed forDCMI syntax specifications

I presents the components and constructs used in DCMIdatabases

I one of them is the Dublin Core Application Profiles (DCAP)

I A DCAP is a generic construct for designing metadatarecords

1http://dublincore.org/Mariana Malta & Ana Alice Baptista

DCAM, DCAP

I Dublin Core Metadata Initiative (DCMI1), created newinstruments with a goal: to speak a common language

I Dublin Core Abstract Model (DCAM): a model developed forDCMI syntax specifications

I presents the components and constructs used in DCMIdatabases

I one of them is the Dublin Core Application Profiles (DCAP)

I A DCAP is a generic construct for designing metadatarecords

1http://dublincore.org/Mariana Malta & Ana Alice Baptista

DCAP: a construct that enhances interoperability

INTEROPERABILITY

Research Problem

I A DCAP development is a complex taskI it needs an adequate support

I A study we have performed [7] shows that:I (to the best of our knowledge)

there is no formal method for the development of DCAP

I It is imperative to have such a method

Research Problem

I A DCAP development is a complex taskI it needs an adequate support

I A study we have performed [7] shows that:I (to the best of our knowledge)

I It is imperative to have such a method

Design Science Research - Introduction

Design Science Research (DSR)

I DSR aims at the development of innovative artifacts thatsolve real-world problems [8]

I An artifact is something that is artificial, constructed byhumans [10]

I These artifacts can be constructs, models, methods, orinstantiations of one of these 3 [11]

I ”Artifacts must be improved upon existing solutions to aproblem or perhaps provide a first solution to an importantproblem” [10, p.6]

I Our artifact is a method: A method for the developmentof DCAP (Me4DCAP)

I Me4DCAP is an exaptation2

2according to Hevner and Gregor in the recently published MISQ journal article - June 2013

Design Science Research - Introduction

Design Science Research (DSR)

I DSR aims at the development of innovative artifacts thatsolve real-world problems [8]

I An artifact is something that is artificial, constructed byhumans [10]

I These artifacts can be constructs, models, methods, orinstantiations of one of these 3 [11]

I ”Artifacts must be improved upon existing solutions to aproblem or perhaps provide a first solution to an importantproblem” [10, p.6]

I Our artifact is a method: A method for the developmentof DCAP (Me4DCAP)

I Me4DCAP is an exaptation2

2according to Hevner and Gregor in the recently published MISQ journal article - June 2013

Design Science Research - Application

We used A. Hevner [11] framework:I 3 cycles:

I The Relevance Cycle: Metadata Community - provides therequisites for the Construction moments of the Design Cycleand an application context for Field Testing

I The Design Cycle - construction and evaluation moments(experimental situation with a group of the SSE worldcommunity - DCAP-SSE)

I The Rigor Cycle - gives the Ground Theories for the DesignCycle Construction moments and than Theorises and Justifiesabout the design process and the results

Take a deep breath....... here we go!

Starting point

A DCAP is defined in the Singapore Framework for Dublin CoreApplication Profiles [5]

I Functional Requirements (Mandatory)

I Domain Model (Mandatory)

I Description Set Profile (Mandatory)

I Usage guidelines (optional)

I Encoding Syntax guidelines (optional)

Introduction

I The development of a DCAP is a process by stages

I Me4DCAP defines:I The composition of the work-team and

I ... the type of work each work-team-member should do

I The deliverables at every stage

I The techniques used to develop those deliverables

I The process workflow

Phases

Me4DCAP V0.1 phases

Deliverables Workflow

Me4DCAP V0.1 deriverables Workflow

Deliverables Sequence development

Me4DCAP V0.1 deriverables sequence development

Work-Team

The work-team should have at least one person of each of thefolowing profiles:

I Manager: has knowledge of the application domain

I System Analyst: has technical skills in data modeling and inrequirements elicitation

I Metadata Programmer: understands the Semantic Webconcepts

I Final User: works with the Web System that will be using theDCAP in development

Glossary

A Glossary should be developed during the whole processdevelopment

I It is a very important deliverable because of themultidisciplinarity of the work-team

I it is important that members of the work-team speak all acommon language

I A Glossary is a text document with the keywords (and itsdescription) used in the process

I All work-team members should contribute to the Glossary

Functional Requirements

To build the Functional Requirements Me4DCAP obliges thedevelopment of the following deliverables:

I Work-Plan: time planning of the project activities (e.g aGantt Chart) (all team; Manager leads)

I Vision Statement: shows what developers want to reachwith the DCAP development; it defines the scope of theDCAP(all team; Manager leads)

I Use Cases High Level: a list of the Use-Cases to bedescribed in the Use-Case Model (all team; System analyst leads)

(continues...)

(Continued from last page...)

I Use-Cases Model. It is composed by:I the UML Use-Cases diagrams with the actors that interact in

the Use-CasesI the set of all detailed Use-Cases: the sequence of actions.

(all team; System analyst leads)

Domain Model

The Domain Model “captures the most important types of objectsin the context of the system.” [13, p. 119]

I based on the Functional Requirements and on the Use-CasesModel deliverables

I and on other information or documents, if available

I An UML class diagram with details suppressed:I The diagram identifies the classes of objects and the

relationships among them

I classes’ methods and attributes are omitted

(all team; System Analyst leads)

Domain Model

The Domain Model “captures the most important types of objectsin the context of the system.” [13, p. 119]

I based on the Functional Requirements and on the Use-CasesModel deliverables

I and on other information or documents, if available

I An UML class diagram with details suppressed:I The diagram identifies the classes of objects and the

relationships among them

I classes’ methods and attributes are omitted

(all team; System Analyst leads)

Description Set Profile

To build the Description Set Profile Me4DCAP obliges thedevelopment of the following deliverables:

I The Integration Dossier

I The Validation Dossier (in laboratory)

Description Set Profile - Integration Dossier

The Integration Dossier is composed by 3 mandatory deliberables:I An ORM/NIAM diagram:

I classes of objects (defined in the Domain Model);I attributes of the classes of objects;I attributes’ constraints, such as their repeatability and range

(all team; System analyst leads)

Craftsman

(Name)

Product

(Name)

is made by makes

(Title)costs. . . at

The Integration Dossier is composed by 3 mandatory deliberables:

I An ORM/NIAM diagram:I classes of objects (defined in the Domain Model);I attributes of the classes of objects;I attributes’ constraints, such as their repeatability and range

I A State Of The Art report: A State of the art to existingmetadata schemes that are described in RDF (Metadata Programmer)

I If the metadata schemes of the State of The Art report doesnot fullfill the needs of properties descriptions the work-teamwill have to coin new RDF properties

I A Document of Integration: shows, in a matrix, per line,every property or class and its constraints, described by theproperties of the metadata schemes and encoding schemeschosen (Metadata Programmer)

Description Set Profile - Validation Dossier (in laboratory)

The Validation Dossier (in laboratory) is composed by 3mandatory deliberables:

I A Validation Report (all team): to check the DCAP adequacy towhat has been defined in the “Vision Statement”

I A Document of Validation (all team - Metadata Programer leads):I To check the DCAP adequacy to the resources that are going

to be described by itI To apply the DCAP descriptors to a resource sample

I A Questionnaire: Answer to a set of questions to assess thedifficulties of the validation process (all team; Manager leads)

I According to the results of the Validation Dossier, the processiterates or follows to the Description Set Profile development

Guidelines

I The Usage Guidelines and Syntax Guidelines are notmandatory in the Singapore Framework

I Me4DCAP recommends that they should be developed

I the developing of the Usage Guidelines should start at thesame time as the Domain Model development (Managers and Metadata

Programers)

I The development of the Syntax Guidelines (Metadata Programers)needsthat the Integration Dossier has been already developed in acertain stage in order to have already some maturity

Deliverables sequence

Guidelines

Programers)

Guidelines

Programers)

Validation in Production

I Use of log registration technique

I observing final-users working with a system that implementedthe DCAP (metadata programers)

I the results of this validation in production are reported to thewhole team in order to review and access the DCAPdefinitions

I I If there is any new information to add, the process starts fromBlock 1

Next steps:

I The construction of DCAP-SSE is still in place - finishing theDesign Cycle

I The Evaluation of Me4DCAP V0.1 will be executed(Relevance Cycle)

I Me4DCAP V0.2

Future Work:

I Me4DCAP V0.2 field testing - call for testing

I Work in another Me4DCAP Version ??

I A DCAP is a very important construct to implementinteroperability

I (to the best of our knowledge)

I We have presented a first version of a contribution for such amethod: Me4DCAP V0.1

I We have presented Me4DCAP:

I The composition of the work-team and

I ... the type of work each work-team-member should do

I The deliverables at every stage

I The techniques used to develop those deliverables

I The process workflow

Mariana Curado Malta & Ana Alice Baptista

Algoritmi Center, University of Minho

[email protected]@dsi.uminho.pt

Further Information:http://algoritmi.uminho.pt

QUESTIONS?

Look for references in the paper

me4dcap v0.1: a method for the development of dublin core application profiles

Education