Download - Records in Contexts (RiC) - International Council on Archives · PDF fileRecords in Contexts (RiC) ... accumulation and use is essential to understanding the interrelations among them

RecordsinContexts(RiC)

AnArchivalDescriptionDraftStandard

INTERNATIONALCOUNCILONARCHIVESEXPERTSGROUPONARCHIVALDESCRIPTION

ICACongress

Seoul

2016

ICAExpertsGrouponArchivalDescriptionRecordsinContexts

PresentationOverview

Introduction:Background,Context,PivotalChangesDanielPitti

InstituteforAdvancedTechnologyintheHumanities,UniversityofVirginia

RecordsinContexts-ConceptualModel(RiC-CM)

BillStocktingRoyalLibraryandRoyalArchives,UnitedKingdom

RecordsinContexts-Ontology(RiC-O)

FlorenceClavaudArchivesnationales,France

ICAExpertsGrouponArchivalDescription

RecordsinContexts(RiC):IntroductionDanielPittiInstituteforAdvancedTechnologyintheHumanities,UniversityofVirginiaEGADChair/President


ExpertsGrouponArchivalDescription(EGAD)

• FormedbytheICAProgrammeCommissioninlate2012• PartialsuccessortotheCommitteeonBestPracticesandStandards(CBPS)• Term2012-2016• ChargedwithdevelopingaConceptualModelforArchivalDescription• BasedonfourcurrentICAdescriptivestandards• Employingformalinformationmodelingtechniques


ICAStandardsforArchivalDescription1988-2008

Standard Edition DevelopmentDates PublicationDate

Principles (1988)1989-1992 1992

ISAD 1st 1990-1993 1994

ISAAR 1st 1993-1995 1996

ISAD 2nd 1996-2000 1999

ISAAR 2nd 2000-2004 2004

ISDF 1st 2005-2007 2007

ISDIAH 1st 2005-2008 2008


ArchivalPrinciples:RecordsinContexts

• PrincipleofProvenance• Respectdesfonds

• TheRecordscreated,accumulated,andusedbyapersonorgroupinthecourseoflifeandworkaretobekepttogetherandnotintermixedwithrecordsfromothersources

• RespectforOriginalOrder• Theintellectualgroupingofandsequencingimposedontherecordsinthecontextofaccumulationanduseisessentialtounderstandingtheinterrelationsamongthemaswellasbeingevidenceofhowtheywereused

• Generalinternationalconsensusontheprinciple• Buthistorical,culturaldifferencesinunderstandings• RecordsinContexts

• Embodiesbothfacetsoftheprinciple• ThoughmoreexpansiveunderstandingofProvenance• Basedonintellectualandpracticalcritiqueofarchivaldescription• Recordsandthepeoplethatcreate,manage,andusethemdonotexistinisolationbutincomplexlayersofinterrelated,interdependentcontexts


HistoricalContext

• Sinceatleastmid-19thcentury,culturalheritagecommunities• Reimaginedescriptioninrelationtoemergingandnewcommunicationtechnologies• Trend• Separatethecomponentsofdescription• Toefficientlyandmoreeffectivelycreateprevailingaccesstool(e.g.,bookcatalog,findingaids)• Atthesametime,enablenewtools,newperspectives,newpaths,basedonrecombiningthecomponents

• FourICAstandardsreflectthistrend• Thoughtheseparationandnewperspectivesnotrealized


CurrentandEmergingTechnologyLandscape

• Network,ofcourse,andMarkup(XML),andDatabase(SQL)…• XMLandSQLhavedominatedbut…• EmergenceofGraphtechnologies:RDF,SemantictechnologiesandLinkedOpenData• Moreexpressive,butalsomorechallenging:complexity,quality…

• Opportunities:separation,recombining,interrelating,openingdomainborders,newperspectives,newpaths…• Repositioncommunitytotakeadvantageoftheopportunities


TheRiCProducts

• Conceptual Modelforarchival description(RiC-CM)

• TheConceptual Modelresembles thecurrent ICAstandards

• Documentsthekeyentities ofarchival descriptionandtheproperties ofeach

• With diagrams illustrating howthecomponentsareinterrelated toform complete archival

description

• RiC-CMavailable forcommentuntil 31December 2016.

• AnOntology forarchival description(RiC-O)

• Based onRiC-CM

• Expressed using theW3COWLlanguage

• Willmap archival descriptionconceptstosimilar conceptsemployed byallied communities:

integrated access toculturalheritage

• Willenable archival community toparticipate onits own terms,so-to-speak

• RiC-O draft available late 2016


FromISAD(G)

• Predominantformofarchivaldescriptiontoday

• Hierarchical(top-down)descriptionofasinglefonds

• Descriptionofthewhole,thepartsofthewhole,partsoftheparts

• Largelyifnotexclusivelyself-contained,inward“looking”

• Thatis,notconnectedtothebroadercontext

• Allcontainedinasingleapparatus

• ISAD(G)amodelforthisapproach;EADamethodforcommunicatingit


•ToRiC

• Torepeat• RecordsinContexts• MoreexpansiveunderstandingofProvenance• Recordsandthepeoplethatcreate,manage,andusethemdonotexistinisolationbutincomplexlayersofinterrelated,interdependentcontexts


ToRiC:PivotalChanges

• Recordsandaggregationsofrecordstreatedastwodistinctentities

• Records

• RecordSets

• Overthecourseofitsexistence,arecordmaybeamemberofmorethanonerecordset,andatthesametime

• Multileveldescription

• Multilevelorhierarchicaldescriptiononeamongotherpossiblemethodsofdescription

• Multileveldescriptionpredominates,andwilldosofortheforeseeablefuture:wellunderstoodandeconomic

• Multidimensionaldescription

• Encompassesmultileveldescription

• Withinanetworkofinterrelatedrecords,fonds,people…:contextwithincontext

• Enablesmoreflexibledescription(relationalandgraph)thatismoreexpressiveofthecomplexrealitiesofrecordsthanpossible

inasinglehierarchicaldescription

• Descriptionasavastsocial-documentnetwork


Thankyou!

RecordsinContexts-ConceptualModel(RiC-CM)BillStocktingRoyalLibraryandRoyalArchives,UnitedKingdomEGADmember


Introduction

TodayIwilltalkabout:

•Whatwemeanbya‘ConceptualModel’asa

document– RecordsinContext(RiC)

•AtourofthedraftofRiCputoutforconsultation

•Nextsteps...

A‘Conceptual’Model?

Theconceptualmodelisadocumentthat:

•Describeskeyhighlevelconceptsforarchival

description:

– Entities(Record,Agent,Functionetc.)

– Theirproperties(id,name,descriptionetc.)

– Therelationsbetweenthem(Record‘was

createdby’Agent)

•Ageneralisedviewofarchivaldescriptionthat

doesnotreplace:

– detailedlogicalandphysicaldatamodels

– cataloguingguidelines(e.g.DACSandother

nationalguidelines)

– XMLschemafordatatransmission(e.g.EAD3

orMARC)

A‘Conceptual’Model?

Theconceptualmodelwillbeadocumentthat:

•framesandrespectscurrentpractice,systems

andprocessyetprovidesabasisfortheir

ongoingdevelopment

•informsongoingprofessionaldiscussions,

educationandtraining

•enablesustocollaboratewithother

informationprofessionals

•ensuresarchivestaketheirproperplaceinthe

digitalworld

ModelsComparison:Data

ModelsComparison:Findings

Wefound:

• Differencesinperspectiveduetothe

differingcontextsofmodelling

• Agreatdealofagreementnow

reflectedinRiC:

– keyentitiesforarchivists:Record,

Agent,andBusinessentities

– contextualentitiessharedwith

others:Places,Dates,Topics,

Eventsetc

– significantpropertiesof,and

relationsbetween,entitiesfor

archivaldescription

RecordEntities:

CurrentlywehavethreeRecordentitiesinRiC:

• Record:‘linguistic,symbolic,orgraphic

informationrepresentedinanypersistent

form,onanydurablecarrier,byany

method,byanAgentinthecourseoflife

orworkeventsandActivities’- the‘item’

levelinISAD(G)

• RecordComponent:thepartsthatmake

upaRecord

• RecordSet:thegroupsoraggregationsof

whichaRecordmaybeamember

RecordSet

RecordComponent

Record

RecordComponent

’hasmember’/’ismemberof’

’haspart’/‘ispartof’ ’haspart’/‘ispartof’

RecordEntities:RecordSet

RecordSet:

• RecordsgroupedtogetherbyanAgent

basedonsharedpropertiesinorderto

servetheirownends:provenance,topic,

placeetc

• Mayholdotherrecordsetsinahierarchyso

catersfortraditionalmulti-levelprovenance

baseddescriptionatfondsorseries‘level’,

andothertypesof‘collections’

• Alsoallowsrecordstobegroupedinother

waysbycreators,archivistsandusers,

simultaneouslyorovertime

RecordSet:usercollection:

recordsrelatingtomyresearch

RecordSet:fonds[orcollection]

RecordSet:series

Record1 Record2 Record3

RecordSet:series

Record1 Record2 Record3

’hasmember/‘ismemberof’

‘ismemberof’/’hasmember’

‘ismemberof’/’hasmember’

’hasmember/‘ismemberof’

RecordEntities:DocumentaryForm

WealsohavetheDocumentaryFormentity,

which:

• allowsthedefinitionofthemodelthat

prescribestheparticularformatofa

Record:acharter,aletter,ane-mail,awill

etc

• connectsRiCtoDiplomatics

Record

DocumentaryForm

‘hasdocumentaryform’/’isdocumentaryformof’

PeopleEntities:

Agententity:

• includesthefollowingtypes:

– Persons

– Groups:corporatebodies;families

– Delegate-Agents:software,robots,

probes

• allowsdefinitionofidentitytypes:

– Given

– Assumed

• hastworelatedentities

– Occupation:professionortrade

– Position:rolewithinacorporatebody

Agent:person

‘occupies’/’isoccupiedby’

PositionOccupation

‘pursues’/’ispursuedby’

‘isassociatedwith’/’isassociatedwith

BusinessEntities:

FromISDF,RiChastwoseparate

entitiesfor:

• Function: anAgent’sbroadgoals

orpurposes

• Activity:actionsperformedbyan

Agentinfulfilmentoffunctions:

Botharedefinedasbeingwithina

specificculturalcontextsoinorder

toseegenericfunctions

independentofcontextthereis

alsoFunction(Abstract)

‘isperformedby’/’performs’

‘isfulfilledby’/‘fulfills’

Function(Abstract)

Function

Activity

Agent

‘hasexample’/Isexampleof’

‘isfulfilledbyperformanceof’/

‘isperformedtofulfill’

BusinessEntities:

Mandate:

• authorityorrulesthatdefinethe

functionsandactivitiesofAgents

• sourceofauthorityforanAgentto

act,whichmayeitherbe:

– impliedbysocialcustomsorpersonal

motivation

– expressedindocumentssuchaslaws,

regulations,standards(e.g.RiC!)

• abstractandnottobeconfused

withthosedocumentsthatmay

giveitexpression

Agent

Function

Record

‘defined’/’wasdefinedby’

‘authorized’/‘wasauthorizedby’

Mandate

‘isevidencedby’/‘isevidenceof’

Activity

EntitiesSharedwithOthers:Place

Place:

• Anygeographicoradministrative

pointorarea

• enablingdescriptionofspatial

contextsofotherentities

Place

Mandate

Agent

Record’washoldinglocationof’/‘hasholdinglocation’

‘isjurisdictionof’/’hasjurisdiction’

’wasbirthplaceof’/‘hadbirthplace’

EntitiesSharedwithOthers:Date

Date:

• chronologicalinformationbased

onanyformat

• enablingdescriptionoftemporal

contextsofotherentities

Date

Mandate

Agent

RecordSet

’wascreationdateof’/‘hadcreationdate’

’wasactivedateof’/‘wasactivedate’

’wasbirthdateof’/‘hadbirthdate’

EntitiesSharedwithOthers:Concept/Thing

Concept/Thing:

• broadtopicsthatmaybethe

subjectofotherentities

• includesabstractideas,material

things,events,includingthosethat

arelegendaryorfictitious

Record

Concept/Thing

Place

Agent

’hassubject’/‘issubjectof’



Properties:

Entitieshavetwotypesofproperty:

• Thosethatidentifytheentitythatarecommon

toall:

– GloballyPersistentIdandother‘local’ids

– Name

– GeneralNote

• Thosethatdescribetheentitywhichwilldiffer

duetothedifferentnatureoftheentities

• ManyfamiliarfromISAD(G)etc:

– Recordhasproperties‘scopeandcontent’,‘language

information’,‘conditionsofaccess’etc.

– butnot‘creator’asthatmodelledasarelationbetween

aRecordandanAgent

Agent:

GlobalPersistentId:Type:Name:LanguageInformation:History:…

Record:

GlobalPersistentId:Name:LanguageInformation:ConditionsofAccessScopeandContent:…

‘created’/’wascreatedby’

Properties:Record(andRecordComponent)Specific

Content:

• AuthenticityandIntegrityNote

• ContentType:text,music…

• ContentExtent:1letter…

• QualityofInformation

• ScopeandContent

Representation:

• EncodingFormat:text/csv;audio/mp4…

• LanguageInformation

• MediaType:computer,unmediated…

• ProductionTechnique:handwriting,recording…

Carrier:

• Medium:paper,magneticdisk…

• PhysicalorLogicalExtent:5pages…

• PhysicalCharacteristicsNote

ManagementandUse:

• Classification

• ConditionsofAccess

• ConditionsofUse

• History

• RecordState:draft,copy…

Properties:RecordSetSpecific

PropertiesoftheRecordsSet:

• AccrualNote

• AccrualStatus

• Arrangement

• AuthenticityandIntegrityNote

• Classification

• History

• Type:fonds,series,file,collection…

PropertiesthatmaybeSharedbyAllMembersofa

RecordSet:

• ConditionsofAccess

• ConditionsofUse

• ContentType

• EncodingFormat


• MediaType

• Medium

• ProductionTechnique

• RecordState

PropertiesSummarizingtheMembers

ofaRecordSet:

• ContentExtent

• PhysicalorLogicalExtent

• ScopeandContent

Properties:AgentSpecific

Shared(allTypes):

• Type:person,group,delegate-agent…

• IdentityType:given,assumed…


• History

PropertyspecifictoType=‘person’:

• Gender

PropertyspecifictoType=‘delegate-agent’:

• TechnicalCharacteristics

PropertiesspecifictoType=‘corporatebody’:

• ServicestothePublic

• ContactInformation

• OperatingHours

• Facilities

Properties:SpecificToOtherEntities

Date:

• Calendar

• Type

Activity,DocumentaryForm,Function,Function

(Abstract),Mandate,Occupation,Position:

• Description

• History

• Type

Place:

• Address

• GeographicCoordinates

• Type

Concept/Thing:

• Description

• Type

Relations

Relationsbetweenentitiesareexpressedinsimple

binaryformatinbothdirections:

• relationsarenamedinthepasttensewherethe

actionsexpressedhavecompleted

• allentitieshavegeneral‘isassociatedwith’and

‘wasassociatedwith’relationswitheachother

aswellasmorespecificrelations

Thelistinthedraftremainssuggestivenotcomplete

withthosereflecting:

• thewho,whatandwhereofrecords’creation,

transmission,managementanduse

Relations

Thelistinthedraftremainssuggestivenot

completewiththosereflecting:

• subjectsofrecords

• temporal(successor/predecessor)and

hierarchical(superior/subordinate)relations

betweeninstancesofthesameentity

• Thedoingofbusinessbyagentsandthewhen

andwheretheyaredoingit

• familyrelationsforpersons

TheadditionofDateandPlacepropertiesallows

expressionofgreatercontextforsome

relations

Agent

Record

‘isassociatedwith’/‘isassociatedwith’

‘created’/‘wascreatedby’

Date:2016-09-16Place:Seoul

NextSteps

Soafirstdraftbutstillthingstodo:

•Receive,digestandrespondtofeedback•Model‘control’informationrecreationandmanagementofdescriptions•Discussanddeveloptheobligationandrepeatabilitystatusoftheproperties•Agreeanddefinethefullsetofrelationsforthemodel•Agreethefinaldocumentationnecessary,includingexplanation,diagramsandexamples

Thankyou!

RecordsinContexts-Ontology(RiC-O)FlorenceClavaudArchivesnationales,FranceEGADmember,RiC-Odevelopmentlead


WhatIsIt,BrieflyStated?

- amachinereadableversionoftheconceptualmodel

- atoolforwiderintegrationandsharingofarchivaldescription

- anopportunityfortestingandcommunityfeedback

WhatIsIt,BrieflyStated?AFormalRepresentationOfRiC-CM

- BASICALLY,AFORMALVERSIONOFTHECONCEPTUALMODEL...

- amachinereadableandprocessableone;justlike,forexample,EAC-CPF,aformalrepresentationofISAAR(CPF)- samescopeasRiC-CM- generic- multilingualannotations

- …USINGTHEW3CSEMANTICWEBSTANDARDSFORDEFININGENTITIESANDTHEIRRELATIONS- RDF(ResourceDescriptionFramework;aW3Crecommendationsince1999,currentversion:RDF1.1;seehttp://www.w3.org/RDF/);- RDFS(theRDFSchemalanguage;aW3Crecommendationsince2004;seehttp://www.w3.org/TR/rdf-schema/);- OWL(WebOntologyLanguage,firstversiondated2004,2nd onedated2009;seehttp://www.w3.org/2001/sw/wiki/OWL)

WhySuchAnOntology?tobeAbletoPutArchivalMetadataonthe(Semantic)Web

- Archivaldescriptiontoday:alotofdescriptivedata,storedinalotofformats(e.g.relationaldatabases,EAD/XML,EAC-CPF/XML...)andlanguages,inalotofdifferentinformationsystems,allovertheworld.

- Theweb:thelargestandmostpowerfulinformationsystemeverbuilt;currentlyevolvingtowardsa« semanticnetwork »(baseduponconnecteddatasets,viewableasgraphs)

- Inordertopopulatethisnetwork,needtobuildrichmachine-processablemetadatafromourdata,havingtheRDFstandardizedformofsimpletriples(three-componentphrases)

Ex.(inpseudo-RDFTurtlesyntax) :RDFsubject RDFpredicateRDFobject

anf:LucienFebvre RiC-O:created anf:fonds591AP .anf:fonds591AP rdf:type RiC-O:RecordSet .

eachofthecomponents(resources)havingitsuniqueidentifier(URI).

Why?

- TOLINKTHEDATATOOTHERDATA(tobuildrichLinkedDatasets)Ex. :anf:LucienFebvre RiC-O:created anf:fonds591AP.anf:LucienFebvre owl:sameAs http://data.bnf.fr/ark:/12148/cb119024609#foaf:Person.anf:LucienFebvre owl:sameAs http://viaf.org/viaf/61545548.

- TOACCURATELYQUERYTHERDFDATAANDMAKEINFERENCESBASEDONTHEMEx.visualize(orcreatefromseveralgraphscomingfromseveraldatasets)agraphconcerningaperson;discover,readingwhatotherinstitutionsknowabouthim/her,thathe/shelivedorwasbornatsomedateandplace,thathe/sheusedseveralnames,haddifferentactivities,thenbeabletoenrichone'sowndata ;discoverthearchivalrecordshe/shecreated,thebookshe/shewrote,whereallthoseculturalheritageobjectsare,etc.

- LINKEDDATA:ANOPENWORLD,NOTACLOSED,FULLYDEFINEDDATABASEButofcourse,ifmany(all)archivalinstitutionsusethesameontologytocreatetheirRDFmetadata,itmay :- stronglyenhancethequeryandprocessingresults(keypointforinteroperability!)- helpmakeourconceptsanddataaccessible,understandable,unambiguous,reusable

TheArchivalWorldasaGraphofEntitiesandRelations:ASmallandSimpleExample

Lucien Febvre(Person)

Teaching history(Activity)

Fonds 591AP

(Record setof type fonds)

Letters 591AP52-55

(Record Setof type series)

Letter 1(Record)

created

performed

resulted in

has member

has member

has member

TheSameStatementsintheDiagram,ExpressedUsingRDFTriples

anf:LucienFebvre RiC-O:created anf:fonds591AP .

anf:LucienFebvre rdf:type RiC-O:Person.

anf:fonds591AP rdf:type RiC-O:RecordSet .

anf:fonds591AP RiC-O:hasMember anf:letters591AP52To55 .

anf:letters591AP52To55 rdf:type RiC-O:RecordSet .

anf:letters591AP52To55 RiC-O:hasMember anf:letter1 .

anf:letter1 rdf:type RiC-O:Record .

anf:LucienFebvre RiC-O:performed anf:teachingHistory .

anf:teachingHistory rdf:type RiC-O:Activity .

anf:teachingHistory RiC-O:resultedIn anf:Lectures591AP2to3 .

anf:Lectures591AP2to3 rdf:type RiC-O:RecordSet .

anf:fonds591AP RiC-O:hasMember anf:Lectures591AP2to3 .

BuildingRDFArchivalDataSets:TheRoleofRIC-O

TheRiContologywilldefine:

- theclassesneeded(correspondingtotheentitiesoftheconceptualmodel),suchasPerson,Record,RecordSet,Activity(plusotherclasses);

-theobjectpropertiesneeded(correspondingtotherelationsbetweenentitiesoftheconceptualmodel),suchascreated,hasMember,performs,resultedIn(andmuchmore);

- somedataproperties(tobeusedifyouwanttosaythataninstanceofaclasshassomefeatureexpressedasastringEx. :anf:letters591AP52To55hasLocalIdentifier"591AP/52-55"

- the(possiblemultiple)hierarchy(ies)existingbetweensomeclassesorsomeproperties;

- therulesthatgovernthoseclassesandproperties,andthatyoumustconformtowhenyouusethoseclassesandproperties.

Inshort,itwillbeboththevocabularyneededandthegrammarnecessarytousethevocabulary,expressedformally.

AMoreComplexGraph,WhereDataFromTwoArchivalInstitutionsAreLinked

HowWeBuildRIC-O:TheTeam

AfewEGADmembers:

- FlorenceClavaud,Archivesnationales(France)(leaderoftheteam);

- PeteJohnston,ArchivesHub(UnitedKingdom) ;

- DanielPitti,UniversityofVirginia(U.S.A.)(chairofEGAD);

- AaronRubinstein,UniversityofMassachusettsAmherst(U.S.A.);

- SalvatoreVassallo,ArchivumRomanumSocietatisJesu(Italy).

HowWeBuildRIC-O:Principlesl COMPLETENESSAdomainontology,takingintoaccountanyconcept/entityoftherealarchivalworld,sometoplevelabstractnotions,andalotofpointsofviewand« functional »needs.

l CLARITY/ACCURACY- Accuratedefinitionsoftheclasses,oftheirproperties,thedomainandrangeoftheproperties,etc.- Specialcareforgenuinearchivalconceptsandfeatures:functionsandthebusinessentities,recordset(andorderingsets),representingthehistoryofentities,provenanceandsomecurationevents...- Multilingualdocumentationintheend- Examples

l FLEXIBILITY- Allowingtouseeitherthecoreentitiesonly,orsomeverypreciselydefinedlowlevelones(e.g.Record,orRecordanditscomponents ;Set) ;thewholeontologyorapartofit- Allowingtoexpresssomerelationsverysimplyasdirectbinaryones(usingoneverbtolinktwoclasses),ortousemorecomplexpaths,sothattherelationbecomesaclassandcanbedescribed,givenadate,acertainty,etc.- Extensibility- Openness(providing'hooks'forothercommunities)

HowWeBuildRIC-O:Principles

MAPPINGS(FORABETTERINTEGRATIONOFOURDATATOLINKEDDATA)

Thearchivaldomainislinkedto(orpartof)manyotherones.Itisveryimportantthatourconcepts(classesorproperties)becomparedwith,andwhenappliable,aligned,withconceptsdefinedinotherontologies:

- ontologiesforotherdomainsofculturalheritage:- CIDOC-CRM(www.cidoc-crm.org/official_release_cidoc.html)- FRBRoo(http://www.cidoc-crm.org/frbr_inro.html)

- ontologiesfordescribingentitiesoreventssomewhatcloseorlinkedtothearchivalone:- ThePROVOntology(PROV-O)(http://www.w3.org/TR/prov-o/)- TheOrganizationontology (http://www.w3.org/TR/vocab-org/)- OpenArchivesInitiative-ObjectReuseandExchange(OAI-ORE)

(https://www.openarchives.org/ore/)- generic,widelyused,ontologies:

- FOAF(FriendofaFriend)(http://xmlns.com/foaf/spec/)- DublinCoreMetadataInitiativeTerms(dcterms)(http://dublincore.org/documents/dcmi-terms/)- LODE:AnontologyforLinkingOpenDescriptionsofEvents

(http://linkedevents.org/ontology/)

HowWeBuildRIC-O:Method

l THREEKINDSOFSIMULTANEOUS/ITERATIVEACTIONS:- investigatingon:technicalspecifications,mainconceptsofaformalontology,toolsandmethodsforbuildinganontology,designpatterns,goodpractices;- analyzingseveralexistingontologiesormodels;- iterativelycreatingtheontologyfileandmakingsometests,usingProtégéopensourcesoftware

l ALOTOFDISCUSSIONSANDCOLLECTIVEWORK:- mailinglist- specificconferencecalls- workwithotherEGADmembers

l FEEDBACKLOOP:developingandtestingtheontologywillhelpusbuildandrefinetheconceptualmodel

l USINGAPRIVATEGITREPOSITORY

OverviewoftheCurrentStatusoftheOntology(AWorkinProgress):ABranchintheClassSystem

ROADMAP

l First,developacore(maindomainentitiesandproperties)Testandrevieweverythingiteratively

l Then,improveandenrichtheontology:

- addmorepropertiesandtheclassesthatareneededinordertoexpressmorecomplexanalysisofsomesituationsandanaccuraterepresentationofthehistoryoftheentitiesinvolved,suchas:"event"and"role"classesandtheirownproperties(certainty,source,date,place....),n-aryrelationships- aligntheclassesandpropertieswiththoseofotherontologies(mappings)- addsomevocabularies(SKOSrepresentationofsomefeatures,suchassome"types" :typeofrecordsets,…)- prepareanexternaldocumentation- continuecheckingconformancetoCM

l Milestones:

- firstdraft(betaversion),andcallforcomments:bytheendof2016

- version1,with,ifpossible,ashowcase:bytheendofspring2017

AllversionswillbereleasedonGitHub:http://github.com/ICA-EGAD

Thankyou!

DraftRIC-CMavailableat:http://www.ica.org/egad-ric-conceptual-model

Commentswelcomeat:[email protected]