INTERNATIONAL COUNCIL ON ARCHIVES CONSEIL · PDF fileinternational council on archives conseil...
Transcript of INTERNATIONAL COUNCIL ON ARCHIVES CONSEIL · PDF fileinternational council on archives conseil...
INTERNATIONALCOUNCILONARCHIVES
CONSEILINTERNATIONALDESARCHIVES
EXPERTSGROUPONARCHIVALDESCRIPTION
RECORDSINCONTEXTSACONCEPTUALMODELFORARCHIVALDESCRIPTION
ConsultationDraftv0.1
September2016
TableofContents
1.Introduction..............................................................................................................................................................1
1.1ExpertsGrouponArchivalDescription(EGAD)...................................................................................................1
1.2OverviewofCurrentandPlannedWork.............................................................................................................1
1.3Audiences............................................................................................................................................................2
1.4TheEssentialRoleofRecordsandRecordKeeping............................................................................................3
1.5Provenance,Context,andDescription...............................................................................................................4
1.6RoleofRecordDescription.................................................................................................................................6
1.6.1ManagementofRecords.............................................................................................................................6
1.6.2PreservationofRecords..............................................................................................................................7
1.6.3OngoingUseandReuseofRecords.............................................................................................................7
1.7RecordDescriptioninTransition.........................................................................................................................7
1.8FromISAD(G),ISAAR(CPF),ISDF,andISDIAHtoRiC-CM.....................................................................................9
1.8.1FromUnitofDescriptiontoRecordandRecordSet.................................................................................10
1.8.2FromMultilevelDescriptiontoMultidimensionalDescription.................................................................10
1.9TransitiontoRiC-CM.........................................................................................................................................11
1.10Acknowledgements.........................................................................................................................................12
2.Entities.....................................................................................................................................................................13
RiC-E1Record..........................................................................................................................................................13
RiC-E2RecordComponent......................................................................................................................................13
RiC-E3RecordSet....................................................................................................................................................13
RiC-E4Agent...........................................................................................................................................................14
RiC-E5Occupation..................................................................................................................................................15
RiC-E6Position........................................................................................................................................................15
RiC-E7Function.......................................................................................................................................................16
RiC-E8Function(Abstract)......................................................................................................................................16
RiC-E9Activity.........................................................................................................................................................16
RiC-E10Mandate....................................................................................................................................................17
RiC-E11DocumentaryForm....................................................................................................................................18
RiC-E12Date...........................................................................................................................................................18
RiC-E13Place..........................................................................................................................................................18
RiC-E14Concept/Thing...........................................................................................................................................18
3.PropertiesofEntities...............................................................................................................................................21
3.1SharedPropertiesofallEntities........................................................................................................................21
RiC-P1GlobalPersistentIdentifier.....................................................................................................................21
RiC-P2LocalIdentifier........................................................................................................................................21
RiC-P3Name.......................................................................................................................................................21
RiC-P4GeneralNote...........................................................................................................................................21
3.2PropertiesofRecord.........................................................................................................................................22
3.2.1ContentInformation..................................................................................................................................22
RiC-P5AuthenticityandIntegrityNote..............................................................................................................22
RiC-P6ContentType...........................................................................................................................................22
RiC-P7ContentExtent........................................................................................................................................22
RiC-P8QualityofInformation.............................................................................................................................22
RiC-P9ScopeandContent..................................................................................................................................23
3.2.2InformationaboutRepresentation............................................................................................................23
RiC-P10EncodingFormat...................................................................................................................................23
RiC-P11LanguageInformation...........................................................................................................................23
RiC-P12MediaType............................................................................................................................................23
RiC-P13ProductionTechnique...........................................................................................................................24
3.2.3InformationaboutCarrier.........................................................................................................................24
RiC-P14Medium.................................................................................................................................................24
RiC-P15PhysicalorLogicalExtent......................................................................................................................24
RiC-P16PhysicalCharacteristicsNote................................................................................................................24
3.2.4InformationaboutManagementandUse.................................................................................................24
RiC-P17Classification.........................................................................................................................................24
RiC-P18ConditionsofAccess.............................................................................................................................25
RiC-P19ConditionsofUse..................................................................................................................................25
RiC-P20History...................................................................................................................................................25
RiC-P21RecordState..........................................................................................................................................26
3.3PropertiesofRecordComponent.....................................................................................................................26
3.4PropertiesofRecordSet...................................................................................................................................26
RiC-P22AuthenticityandIntegrityNote............................................................................................................26
RiC-P23Type.......................................................................................................................................................26
RiC-P24AccrualNote..........................................................................................................................................27
RiC-P25AccrualStatus........................................................................................................................................27
RiC-P26Arrangement.........................................................................................................................................27
RiC-P27Classification.........................................................................................................................................27
RiC-P28History...................................................................................................................................................28
3.5PropertiesSummarizingtheMembersofaRecordSet....................................................................................28
RiC-P29ContentExtent......................................................................................................................................28
RiC-P30PhysicalorLogicalExtent......................................................................................................................28
RiC-P31ScopeandContent................................................................................................................................29
3.6PropertiesSharedbyAllMemberRecordsofaRecordSet..............................................................................29
3.7PropertiesSharedbyAllAgents........................................................................................................................29
RiC-P32Type.......................................................................................................................................................29
RiC-P33IdentityType.........................................................................................................................................30
RiC-P34LanguageInformation...........................................................................................................................30
RiC-P35History...................................................................................................................................................30
3.8AdditionalPropertySpecifictoPersonandPersonAssumedIdentity.............................................................31
RiC-P36Gender..................................................................................................................................................31
3.9AdditionalPropertySpecifictoDelegate-Agent...............................................................................................31
RiC-P37TechnicalCharacteristics.......................................................................................................................31
3.10AdditionalPropertiesSpecifictoCorporateBodyandCorporateBodyAssumedIdentity............................31
RiC-P38ServicestothePublic............................................................................................................................31
RiC-P39ContactInformation..............................................................................................................................31
RiC-P40OperatingHours....................................................................................................................................32
RiC-P41Facilities.................................................................................................................................................32
3.11PropertiesofOccupation................................................................................................................................32
RiC-P42Type.......................................................................................................................................................32
RiC-P43Description............................................................................................................................................33
RiC-P44History...................................................................................................................................................33
3.12PropertiesofPosition.....................................................................................................................................33
RiC-P45Type.......................................................................................................................................................33
RiC-P46Description............................................................................................................................................33
RiC-P47History...................................................................................................................................................33
3.13PropertiesofFunction....................................................................................................................................34
RiC-P48Type.......................................................................................................................................................34
RiC-P49Description............................................................................................................................................34
RiC-P50History...................................................................................................................................................34
3.14PropertyofFunction(Abstract)......................................................................................................................34
RiC-P51Description............................................................................................................................................34
3.15PropertiesofActivity......................................................................................................................................35
RiC-P52Type.......................................................................................................................................................35
RiC-P53Description............................................................................................................................................35
RiC-P54History...................................................................................................................................................35
3.16PropertiesofMandate....................................................................................................................................35
RiC-P55Type.......................................................................................................................................................35
RiC-P56Description............................................................................................................................................36
RiC-P57History...................................................................................................................................................36
3.17PropertiesofDocumentaryForm...................................................................................................................36
RiC-P58Type.......................................................................................................................................................36
RiC-P59Description............................................................................................................................................36
RiC-P60History...................................................................................................................................................37
3.18PropertiesofDate...........................................................................................................................................37
RiC-P61Type.......................................................................................................................................................37
RiC-P62Calendar................................................................................................................................................37
3.19PropertiesofPlace..........................................................................................................................................37
RiC-P63Type.......................................................................................................................................................37
RiC-P64GeographicCoordinates........................................................................................................................37
RiC-P65Address..................................................................................................................................................38
3.20PropertiesofConcept/Thing...........................................................................................................................38
RiC-P66Type.......................................................................................................................................................38
RiC-P67Description............................................................................................................................................38
4.Relations..................................................................................................................................................................39
4.1ListofRelationsbyDomainEntity....................................................................................................................39
4.1.1RecordRelations........................................................................................................................................40
4.1.2.RecordComponentRelations...................................................................................................................44
4.1.3.RecordSetRelations.................................................................................................................................48
4.1.4.AgentRelations.........................................................................................................................................52
4.1.5.OccupationRelations................................................................................................................................61
4.1.6.PositionRelations.....................................................................................................................................64
4.1.7.FunctionRelations....................................................................................................................................67
4.1.8.Function(Abstract)Relations...................................................................................................................70
4.1.9.ActivityRelations......................................................................................................................................72
4.1.10.MandateRelations.................................................................................................................................76
4.1.11.DocumentaryFormRelations.................................................................................................................78
4.1.12.DateRelations........................................................................................................................................81
4.2.13.PlaceRelations........................................................................................................................................84
4.2.14.Concept/ThingRelations........................................................................................................................88
4.2SharedPropertiesofaRelation........................................................................................................................91
RiC-P68Date.......................................................................................................................................................91
RiC-P69Place......................................................................................................................................................91
AppendixI:ExampleofArchivalDescriptionConformingtoRiC-CM.........................................................................93
AppendixII:ExpertsGrouponArchivalDescriptionMembers...................................................................................95
AppendixII:Bibliography............................................................................................................................................97
RiC-CMConsultationDraftv0.1 September2016 1
1.Introduction
1.1ExpertsGrouponArchivalDescription(EGAD)
Inlate2012,theInternationalCouncilonArchives(ICA)ProgrammeCommissionformedtheExpertsGrouponArchivalDescription(EGAD)asthepartialsuccessortotheCommitteeonBestPracticesandStandards.ICAchargedEGADwithdevelopingastandardforthedescriptionofrecordsbasedonarchivalprinciples.Forthe2012–2016term,EGADisspecificallychargedwithdevelopingacomprehensivedescriptivestandardthatreconciles,integrates,andbuildsonthefourexistingstandards:GeneralInternationalStandardArchivalDescription(ISAD(G))1;InternationalStandardArchivalAuthorityRecords—CorporateBodies,Persons,andFamilies(ISAAR(CPF))2;InternationalStandardforDescribingFunctions(ISDF)3;andInternationalStandardforDescribingInstitutionswithArchivalHoldings(ISDIAH)4.
Developinginternationalconsensusonastandardforarchivaldescriptionisadauntingchallenge.Culturaldifferencesandestablishedanddifferingtheoriesandpracticesareatthecoreofthechallenge.ThemembersofEGADrepresentmany(thoughcertainlynotall)ofthesedifferences.Atthesametime,theyshareacommoncommitmenttodevelopingasharedstandardthatrespectsandaccommodatesthepast,andthatrespectsandaccommodatesdifferenceswhileremainingintellectuallycoherentandworkable.EGADalsorecognizesthatdevelopingaconsensuswillnecessarilybeanongoingprocess,afieldofnegotiation.
EGADhastwenty-onemembersfromthirteencountries(pleaseseeAppendixIIforalistofmembers).Whilethemembersarebroadlyrepresentativeoftheglobalarchivalcommunity,therearemanyareaswithlonganddistinguishedhistoriesofadministrationandgovernance,andconcomitanttraditionsofrecordcreation,use,andmanagementthatarenotrepresented,suchasAsia,southwestAsia,andeasternEurope.AndwhileAfrica,centralEurope,andSouthAmericaarerepresented,therepresentationcouldbebroader.Giventhis,themembersofEGADwelcomebroaderinternationalparticipationintheongoingdevelopmentofaninternationalarchivaldescriptionstandard,soastostrengthentheintellectualfoundationofthestandard,andensurethatthestandardrepresentsabroadconsensusandaddressestheneedsoftheglobalarchivalcommunity.1.2OverviewofCurrentandPlannedWork
ThestandardintheinitialstageofdevelopmentbyEGADisnamedRecordsinContexts(RiC).EGADenvisionsatwo-partstandard:aconceptualmodelforarchivaldescription(RiC-CM),andanontology(RiC-O).EGADhasbegunitsworkbydevelopingRiC-CMand,withinRiC-CM,identifyinganddefiningtheprimarydescriptiveentitiesandtheirinterrelationsthatconstitutearchivaldescription.EGADhasfocusedondescribingtheworldfromanarchivalperspective,thatis,aperspectivesituatedinthe
1Availableathttp://www.ica.org/en/isadg-general-international-standard-archival-description-second-
edition<accessed20/06/2016>2Availableathttp://www.ica.org/en/isaar-cpf-international-standard-archival-authority-record-
corporate-bodies-persons-and-families-2nd<accessed20/06/2016>3Availableathttp://www.ica.org/en/isdf-international-standard-describing-functions<accessed
20/06/2016>4Availableathttp://www.ica.org/en/isdiah-international-standard-describing-institutions-archival-
holdings<accessed20/06/2016>
RiC-CMConsultationDraftv0.1 September2016 2
specificmandateofarchivesandgroundedinthefundamentalassumptionsandprinciplesthatgoverntheactivitiesperformedinfulfilmentofthemandate.
ThecurrentdraftisintendedtocoveralloftheessentialcontentofthefourexistingICAdescriptionstandards,except“control.”Itthusincludesthecoredescriptiveentities,thepropertiesorattributesoftheseentities,andessentialrelationsamongthem.Furtherspecifyinganddefiningtherelationsamongtheentitiesremainsanoutstandingtask,astherelationsinthecurrentdraftareintendedtobesuggestiveandnotcompleteornormative.RiC-CMalsodoesnotyetofferamodeloftheroleofthearchivistandtheactivitiesheorsheperformsintheformulationandongoingmaintenanceofdescription.EGADwillextendthemodelinthisrespectasanextstep.
Whencomplete,RiC-CMwillalsoinclude,inadditiontotextdefiningthecoreentities,attributes,andrelations,extensivediagramsoftheentitiesinrelationtooneanotherandexamples.Oncethemodelisstable,itwillbetranslatedintoFrenchandotherlanguages.
ThedevelopmentoftheRiC-Oisinthepreliminarystages.FulldevelopmentispendingastabledraftofRiC-CM,astheontologymustbealignedwiththeconceptualmodel.RiC-OwilltranslateRiC-CMusingtheW3CstandardOWL5.RiC-OwillprovidethearchivalcommunitywiththeabilitytomakearchivaldescriptionavailableusingthetechniquesofLinkedOpenData(LOD)andemployaconceptualvocabularyandstructurethatisspecifictoarchivaldescription.ThefirstdraftofRiC-Owillbemadeavailableinlate2016.1.3Audiences
RiC’sprimaryaudienceisthearchivalcommunity,sothemodeltakesasitspointofdepartureestablishedarchivaldescriptionprinciplesandpractices.Atthesametime,themodeltakesintoconsiderationemergingcommunicationandnetworktechnologiesthatopenupnewopportunitiestoimprovedescriptivepractices,aswellasongoingscholarlyandpracticalcritiquesofarchivaldescriptionprinciplesandpractice.WhilethecurrentICAdescriptionstandardslargelyemergedinaworldofnon-digitalrecords,RiCaspirestoaddressdescriptionnotonlyoftraditionalanaloguerecordsbutalsoelectronicrecords.
RiCisalsointendedtobeofinteresttotherecordsmanagementcommunity.Theworkofrecordsmanagersandarchivistsoverlaps:descriptionandintellectualcontrolareessentialcomponentsofthemanagementofrecordsinthecontextsinwhichtheyarecreated,accumulated,andused,andforarchivistswhoassumeresponsibilityforpreservingandprovidingaccesstothoserecordssubsequently.Intheworldofanaloguerecords,cooperationandcollaborationbetweenrecordsmanagersandarchivistswashighlydesiredandperhapsessentialinenablingarchivalrepositoriestocopewithvastquantitiesofrecordstransferredintotheircustody.Theexplosivegrowthofelectronicrecordsmakessuchcollaborationandcooperationnotmerelydesirablebutanabsolutenecessity.Archivalrepositories,quitesimplystated,areandwillcontinuetobeunabletocopewiththehugevolumesofelectronicrecordsifthoserecordsarenotcreated,used,andmanagedinawaythatamelioratessubsequentpreservationandaccesschallenges.Cooperationbetweenrecordsmanagersandarchivistsisanurgentnecessity.Suchcooperationnecessarilyincludesdescription,butitneedstobeextendedtoaddressmanytechnologicalchallenges.WehopethatRiCwillbeofinteresttorecordsmanagers,andthatdescriptivepracticesbetweenthetwoprofessionalcommunitiescanbealigned.
5Forfurtherinformation,seehttps://www.w3.org/OWL/<accessed20/06/2016>
RiC-CMConsultationDraftv0.1 September2016 3
RiCwill,furthermore,beofinteresttothealliedculturalheritagecommunities.Integratedaccesstoculturalheritageheldbylibraries,archives,museums,andcuratedculturalsitesandmonumentsisincreasinglythefocusofprofessionalcommunities,policymakers,fundingagencies,andusercommunities.Differentculturalheritagecommunitieshavefundamentallydifferentunderstandingsofthenatureoftheobjectsforwhichtheyhavecuratorialresponsibility.Theseunderstandingsandpracticesarewell-establishedandadapted(andadapting)totheparticularchallengesofeachcommunityandthenatureoftheobjectsintheircare.Whilemanyoftheeffortstorealizetheobjectiveofintegratedaccesshavefocusedondevelopingasharedstandardfordescription,reducingthedifferentdescriptivepracticestooneisintellectuallyandpoliticallychallenging.Thisobjective,though,doesnotrequiresuchareduction,asthecommunitiesneedonlyidentifyandcooperatewherethereareshared(orlargelyshared)conceptsandpractices.RiC-Owillfacilitatealigningarchivaldescriptionwiththedescriptionofalliedprofessionalswherethereisconceptualoverlap,furtheringeffortstoprovideintegratedaccesstoculturalheritage.
ItisessentialthatdevelopersofrecordsmanagementandrecorddescriptionandaccesssystemsarepartofRiC’saudience.RiCisdetailedandcomplex,andthereforesuccessfulimplementationandusewillrequirethedevelopmentofmethodsthatwillamelioratetheintellectual,technological,andeconomicchallengeofdatacreationandmaintenance.
Finally,RiCisintendedtobeofinteresttotheresearchusersofarchives,inparticulartoscholarsinterestedinreusingarchivalrecords.ThoughRiCprimarilyfocusesondescriptionthatisbasedonarchivalprinciplesandresponsibilities,itmaybeusedtosupportscholarlydescriptionsofindividualrecordsorsetsofrecordsthatarebasedonotherperspectivesandrequirements.1.4TheEssentialRoleofRecordsandRecordKeeping
Themaking,use,andkeepingofrecordsbeganapproximately4000yearsbeforetheinventionofwriting.TheearliestevidenceofrecordkeepingcoincidedwiththeemergenceofagricultureinMesopotamiaaround8000BCE.Tokensofvariousshapeswereusedtorepresentbothquantitiesandkindsofagriculturalproducts.Fixingthisinformationinenduringformsmadeitpossibletoextendthelimitsofhumanmemoryandmaketheinformationreliablyrecoverable.
Withtheadventofwriting,recordkeepingfurtherenabledtheaccumulationofmemoryandknowledge,andtherebyenabledthedevelopmentandmanagementoflarge,complexsocialstructuresandmonumentalcollectiveundertakings.6TheinventionofwritinginthelatefourthmillenniumBCEcoincidedwiththerapidemergenceofcity-states,ofcomplexsocialhierarchies,ofhierarchiesofauthorityandpower,andofhighlydifferentiatedlabourtiedtoone’spositioninthesocialhierarchy.Recordmakingandkeepingemergedtogetherwithincreasinglyorganized,large,rankedgroupsofindividualsfulfillingdifferentroles,withtheformerplayinganessentialroleinenablingtheongoing
6Fixinginformationinenduringformsisnottheonlymethodofpreservingmemory,asmanysocietiesemployoral-basedmethodsfortransmittingknowledgeacrossgenerations;inmanyinstancesacrossmany,manygenerations.Whatisdistinctaboutwrittenrecordsisthattheyenabletheaccumulationofknowledgeandthemanagementofmonumentalsocialandmaterialundertakingsthattranscendlocalizedsocietiesandcultures.Thisdifferencedoesnotmakewrittenrecordssuperior,thoughithasledtoasymmetricalpowerrelationsthatoften(ifnotalways)havehadtragiceffectsontraditionalsocietiesandcultures.Withrespecttotherelationbetweenpeopleandtheenvironment,arguablytraditionalsocietiesutilizingoral-basedmethodsaresustainablewhilesocietiesbasedonwrittenrecordsultimatelyarenot,giventhelatter’svoraciousconsumptionofnaturalresources.
RiC-CMConsultationDraftv0.1 September2016 4
developmentofthelatter.Withtheadventofwrittenlanguage,therolesandpurposesofrecordmakingexpanded,astherangeanddepthofwhatcouldberecordedandcommunicatedvastlyexceededthelimitedsemanticrepertoireoftokens.7
ThebondbetweenrecordsandtheongoingdevelopmentofevermorecomplexsocialandmaterialhumanexistencerepresentsacontinuoushistoryfromtheeighthmillenniumBCEdowntothepresentday.Bothpeacefulandhostilerelationsamongdifferentcommunitiesproducedanincreasinglyglobalsocialanddocumentarynetwork,sincehumanactivityandrecordshavebeenandcontinuetobeinextricablyintertwined.Recordsemergewithinasocialanddocumentarycontext,andtheimmediatecontextisitselfwithinabroaderspatialandtemporalcontext.
Theprimaryfunctionofrecordsandrecordkeeping,theenablingofhighlyorganized,large-scalesocialandmaterialexistence,hasremainedmoreorlessconstantoverhistory.Inparticular,betweenthesixteenthandeighteenthcenturiesarchiveswereconsideredprimarily“arsenaldel'authorité”andwerejealouslykeptandusedalmostexclusivelyintheinterestofpoliticalandadministrativeauthorities.Intheseventeenthandeighteenthcenturiesnotonlycurrentbutalsohistoricalarchivesweresometimesclassifiedaccordingtotopicsandsubjectratherthanpreservingthearrangementthatemergedinanddocumentedthecontextofcreationanduse.WiththeemergenceofantiquarianandhistoricalinterestineighteenthandnineteenthcenturyEurope,recordsbecamevaluableformorethantheirimmediateutility,asaftertheirpracticalusefulnesswasexhaustedtheybecomeusefulashistoricalevidence.Thenineteenthcenturywitnessedtheemergenceofnation-states,nationalarchives,andmodernhistorythatemphasizednarrativesbasedonreliableevidence.Itwasatthistimethatitwasrecognizedthatarrangementbasedonpertinence,whileitmaybenefitcertaintypesofpracticalandevenantiquarianinterests,diminishedifnotdestroyedtheinherentinterrelationsandinterdependenceofrecords,andtherebydiminishedtheirevidentiaryvalueandunderminedscholarlyunderstandingandinterpretation.Suchpracticesde-contextualizedrecords.TheestablishmentofthePrincipleofProvenancewasintendedtocorrectthesepractices.81.5Provenance,Context,andDescription
ThePrincipleofProvenanceemergedinthenineteenthcentury,andoverthecourseofthecenturybecameestablishedasthefoundationofarchivaltheoryandpracticeinthemodernWest.Theprincipleisunderstoodtohavetwomajorfacets.ThefirstisexpressedintheFrenchRespectdesfonds:therecordscreated,accumulated,andusedbyapersonorgroupinthecourseoflifeandworkaretobekepttogetherandnotintermixedwithrecordsfromothersources.TheruleofRespectdesfondsrecognizesthattherecordsthatonepersonorgroupaccumulatesoverthecourseofhis,her,oritsexistencereflectanddocumentthatexistence,andthattogethertheyconstituteaninterrelatedwhole,acoherentbodyofevidence.Theprincipleisintendedtoensuretheintegrityoftheaccumulation.Thesecondfacet,Respectfororiginalorder,recognizesthattheintellectualgroupingofandsequencing
7DeniseSchmandt-Besserat.HowWritingCameAbout.Austin:UniversityofTexasPress,1996.8RobertHenryBautier."Laphasecrucialedel'histoiredesarchives:laconstitutiondesdépôtsd'archives
etlanaissancedel'archivistique(XVI-débutduXIXsiècle)"ArchivumXVIII,1968,pp.139-149;Archiviestorianell'EuropadelXIXsecolo:alleradicidell'identitàculturaleeuropea,IreneCottaandRosaliaMannoTolueds.,Roma:MinisteroperiBenieleAttivitàculturali,Direzionegeneralepergliarchivi,2006;LucianaDuranti."TheOdysseyofRecordsManagers"RecordsManagementQuarterly23,3and4(1989):3-11and3-11;andStefanBerger."TheroleofnationalarchivesinconstructingnationalmasternarrativesinEurope"ArchivalScience13,1(2013):1-22.
RiC-CMConsultationDraftv0.1 September2016 5
imposedontherecordsinthecontextofaccumulationanduseisessentialtounderstandingtheinterrelationsamongthemaswellasbeingevidenceofhowtheywereused.Applyingeachfacetoftheprincipleinvolvesboththemannerinwhichtherecordsarestored(kepttogetherandorderimposedandmaintained)andtheintellectualdescription(descriptionofthewholeandoftheparts).Whilemanagementofthestorageandtheintellectualdescriptionarecommonlycloselyrelated,thetwoactivitiesaredistinct,andtherelationbetweenthemisnotessential.9
ThePrincipleofProvenance,astraditionallyunderstood,hasbeenquestionedandcriticizedbybotharchivaltheoristsandpractitioners.TheruleofRespectdesfondsemphasizesandprivilegesthepersonorgroupthathasaccumulatedabodyofrecords,andoftendoesnotreflectthesocialandmaterialcomplexityoftheoriginsoftherecords.Individualsinteractwithoneanotherandwithgroups,andgroupswithindividualsandothergroups.Recordsbyoneindividualorgroupareoftenfoundintherecordsofanotherindividualorgroup.Theintellectualcontentofrecordsmayberelatedtothecontentofoneormoreotherrecords.Asinglerecord,orsinglefondsorotheraccumulationofrecords,maybejointlycreatedbymorethanoneindividualorgroup.Morethanonepersonorgroupmayhavedifferingrolesinrelationtoonerecordoronesetofrecords.Peoplecreateanduserecords,andarefrequentlythesubjectofrecords.Boththeemergenceofcollaborativeeditinginthenetworkeddigitalenvironment,whichiscreatingmanyrecordsthathavecomplexauthorship,andtheuseofremotestorageservicesthatarenotfullycontrolledbytheusers,raiseissuesofownershipandcustody.Alloftheseobservationsandmoreleadtotheconclusionthatprovenanceismuchmorecomplexthanthelongestablishedunderstandingoffonds:afondsdoesnotexistinisolation,butwithinlayersofinterconnectedcontexts,past,present,andfuture.
Respectfororiginalorderalsohasgivenrisetocriticism,thoughnotallofthecriticismisnew.ThemeaningofRespectfororiginalorderhasbeenamatterofcontentionand,somewouldsay,confusion.Doesitmeantheoriginalorderoftherecordsthemselves,ortheintellectualorder?Increasinglyitisunderstoodas,firstandforemost,theintellectualorder,andsecondarily,ifatall,thephysicalorderoftherecords.Butthisviewdoesnotrepresentaconsensus.Anongoingchallengehasbeenthatfondsmayarriveinanarchivewithnodiscernibleorder.Insuchcases,thearchivististaskedwithreconstructingit,aswellasispossible,basedonevidenceembodiedintherecordsthemselves.Morerecentcriticismhasquestionedthemeaningof“originalorder,”asitcanonlybeunderstoodasthestateoftherecordsatagivenmoment,themomentwhentherecordsaretransferredfromthecontextofcreationandusetothecontextofthearchive.Overthecourseofthetimewhenabodyofrecordsisaccumulating,theorderoftherecordsisdynamic,changing,fluid.Recordsmay,infact,bereordered,andmorethanonce.
BoththeRespectdesfondsandtheRespectfororiginalorderarearchivalprinciples,notrecordsmanagementprinciples.Bothareretrospective,whereas,inthecontextofcreationanduse,theperspectiveofapersonmanaginghisorherownrecordsortheperspectiveofadesignatedrecordsmanagerisfocusedontheimmediateneedsofthepersonorthegroup.Thefondsanditsinternalorderareinastateofbecoming.
9Thedimensionsofbothanalogueanddigitalrecordsandthephysicalfacilitiesinoronwhichtherecords
arestoreddeterminetheboundariesofthestorageunit,andstorageboundariesarenotthesameastheintellectualboundariesofarecordorsetofrecords.Therelationbetweentheintellectualandstoragecollocationandarrangement,whenthereisone,primarilyservesmanagementpurposes.Whetherthereisorisnotarelation,itisafacetofthecontextoftherecords.
RiC-CMConsultationDraftv0.1 September2016 6
WhilealmostallarchivistsacceptthetheoreticalvalidityofProvenance,manyhavebecomeincreasinglyself-consciousandself-criticalabouttherolethatarchivistsandtheapplicationofarchivalprinciplesplayinwhatisrememberedandhowitisremembered.Thiscriticismnecessarilyencompassesmorethandescription,asitalsoincludesappraisal,theevaluationsthatleadtowhatischosentoberememberedandwhatisnot.Viewedbroadly,appraisaldetermineswhichrecordsarekeptandwhicharenot.Memoryisselective:whatarchivistschoosetokeepdirectlydetermineswhetherthememoryisrepresentativeofsociety.Thesedeterminationshaveprofoundepistemologicalandethicalimplications.Appraisalsbybothrecordsmanagersandarchivists,aswellasaccidentallossordispersalofrecords,alsodirectlydeterminetherelativeintegrityorlackthereofofthefonds.Boththerecordskeptandthoselostorintentionallyremovedarepartofthestoryofthefonds,andthusanimportantfacetofthecontextnecessaryforevaluatingandunderstandingrecordsbyusers.
Increasingly,archivistsobservethatthearchivalperspectiveisoneamongmanypossibleperspectivesthatmaybeemployedintheunderstandingofrecords,thattheythemselvesareperformingtheirjobsinaparticularhistorical(cultural,social,material)context,thattheirjudgementsandactsareshapedandinformedbythecontextswithinwhichtheyliveandwork.Atthesametime,archivistsincreasinglyareobservingthatthecontextsinwhichrecordsemergeandinwhichtheyexistovertimeareirreduciblydynamicandcomplex.
Whentakentogether,thetwoobservationsleadtotheconclusionthatarchivaldescriptionisnotandneverwillbeperfect,buttheyalsoforegroundthechallengeofmakingitbetter,ofimprovingit,ofmakingitpossibletomorefullyexpressthecomplexityofcontextandcontexts,ofmakingexplicitthedifferentrolesoftherecordsmanagersandarchivistsinselectingandformingmemory,andofbeingaccommodatingtotheperspectivesandvaluesofothers.
RiCisintendedtoenablearchiviststoimprovearchivaldescription,tomakeitbetter.1.6RoleofRecordDescription
Thedescriptionofrecordsplaysseveralessentialpurposes.1.6.1ManagementofRecords
Whilerecordedinformationcreatedinthecontextofpeople’slivesandworkservesmanypurposes,oneofitsessentialfunctionsistoservetoextendthelimitsofhumanmemory,tobeanenduringwitnessofeventsandactivities.Asrecordsproliferate,keepingtrackofthemandlocatingthemwhenneededbecomesitselfachallengetohumanmemory.Managementofrecordsinvolvesaninterrelatedcombinationofphysicalandintellectualtechniques.Foranaloguerecords,therecordsaretypicallystoredinasystematichierarchicalmannerthatreflectsthefunctions,activities,andtransactionstheyfacilitateanddocument,combinedwiththeuseoflabelsandothermetadatatofacilitatethestoring,retrieving,andongoinguseoftherecords.Fordigitalrecords,filesystemsmediatethestorageofdigitalfiles,mostcommonlyusingahierarchicaldirectorystructurethatisananalogueofthehierarchicalstorageofphysicalfiles,includingtheuseofdirectoryandfolderlabelsandothermetadata.Inordertoestablishintellectualcontroloverrecordsandfacilitate,locate,identify,retrieve,andusethem,however,itisnecessarytoaugmenttherudimentarymetadataassociatedwiththephysicalordigitalmanagementofrecordswithadditionaldescriptionofcontexts.
ComprehensivedescriptionassuggestedinRIC-CMisessentialfortheeffectivemanagementofrecords.
RiC-CMConsultationDraftv0.1 September2016 7
1.6.2PreservationofRecords
Preservationofrecordshasmultiplefacets.Foranaloguerecords,thisinvolvesstoringtherecordsinenvironmentsthatmitigatephysicalrisks,andongoingmaintenanceofrecordsthathavesuffereddamageorareatrisk.Thechallengebecomesmuchmorecomplexforelectronicrecords,asthecarrier,encodingformat,mediationdeviceandmethodmustbecarefullyandpersistentlymanagedinordertopreservetherecords.Forbothanalogueanddigitalrecords,theauthenticityandintegrityoftherecordsmustbesafeguarded.Suchsafeguarding,inadditiontophysicallymanagingtherecordsassuch,alsoinvolvespreservingthecontextwithinwhichtherecordswerecreated,accumulated,maintained,andusedbydescribingitbasedonavailableevidence.
Recordsemergenotinisolation,butwithinacontext,andwithinthatcontext,inrelationtooneanotherandinrelationtothepeoplecreating,using,andkeepingthem.Thusrecordscannotbeunderstoodinisolationfromthesocial-documentcontextwithinwhichtheyemerge.Documentingthecontextbydescribingitisessentialtothepreservationofrecords.Thispointstoafundamentaltensioninarchivalpractice.Ontheonehand,recordsareevidence,andmaintainingandensuringtheintegrityandauthenticityoftherecordasevidenceleadstoanecessaryfocusonfixityandmaintainingthefixityoftheinformation.Ontheotherhand,recordsoriginateandexistovertimeindynamicenvironments,anddocumentingasfullyaspossibleboththecomplexoriginsandongoinghistoryisessentialforbothevaluatingtheevidentiaryqualityofrecords,andforunderstandingthem.
ComprehensivedescriptionassuggestedinRIC-CMisessentialfortheeffectivepreservationofrecords.1.6.3OngoingUseandReuseofRecords
Thedescriptioncreatedtofacilitatemanagementandpreservationalsoservesthoseinterestedinrecordsaswitnessestolifeandworkactivities,topeople,tohuman-madeandnaturalevents,tothingsmade,thingsstudied,thingsdone,andmore.Anythingandeverythingmaybethesubjectofrecords.Forpeoplewhowanttouserecordsasevidenceforscholarly,business,personal,orotherpurposes,descriptionfacilitatesdiscovering,locating,identifying,retrieving,evaluating,andunderstandingthem.Suchongoinguseandreuseoftherecordsbecomespartofthehistoryoftherecords;itre-contextualizesthem.Theuseandreusegenerateotherrecords,therebyextendingthesocial-documentnetwork.
ComprehensivedescriptionassuggestedinRIC-CMisessentialfortheeffectiveuseandreuseofrecords.1.7RecordDescriptioninTransition
ThepredominantformofarchivaldescriptionisbasedonthetraditionalunderstandingofthePrincipleofProvenance.Thepredominantformisalargely(ifnotexclusively)self-contained,inward-lookinghierarchicaldescriptionofasinglefonds.Thedescriptionbeginswithadescriptionofthefonds,andproceedstodescribethecomponentsofthefonds,andthesubcomponentsofthecomponents,andsoon.Whilethehierarchymayterminateinthedescriptionofanindividualrecord,itcommonlydoesnot.Suchdescriptionsarecurrentlycreatedandmaintainedusingavarietyofcommunicationtechnologies(forexample,wordprocessors,databases,orEncodedArchivalDescription(EAD10)XML-encodeddocuments)butallanticipatetheproductionofthetraditionalprintfindingaid,oranonlinepresentationthatismoreorlessananalogueofit.
10Forfurtherinformationseehttps://www.loc.gov/ead/<accessed20/06/2016>
RiC-CMConsultationDraftv0.1 September2016 8
ItisthismodelofarchivaldescriptionthatisembodiedinISAD(G).Thefonds-downdescriptionprescribedinISAD(G)containsadescriptionofthefondsanddependentaggregationsofrecords,aswellasadescriptionoftheperson,corporatebody,orfamilythatcreated,accumulatedandusedtherecords,andtheholdingrepository.Descriptionoftherecordsandthecontextoftherecordsiscombinedinasingle,standalonedescription,withlittleornorelationtotheworldoutsideoftheimmediatecontext.
OverthecourseofthefourteenyearsfollowingthedevelopmentofISAD(G),threeotherstandardsweredeveloped:ISAAR-CPF,ISDF,andISDIAH.Theyenvisionedtheseparationofprimarycomponentsofthearchivaldescription(creator-accumulatorofafonds;thefunctionsthattherecordsaccumulateddocument;andtherepositorythatheldthefonds).Theseadditionalstandardswereintendedtoencouragethedevelopmentofsystemsofdescriptioninwhichthecomponentsofdescriptionswereseparatelymaintainedandinterrelated,andthenused,ondemand,toproducecompletearchivaldescriptionasithastraditionallybeenunderstood,andatthesametime,enableproducingnewandpotentiallypowerfulperspectivesthatfacilitatetheuseandunderstandingofrecords.
However,thefourstandardsweredevelopedindependentlyofoneanotheroveranextendedperiodoftimeandwithoutanoverarchingandpersistentvisionofhowsuchseparationwouldworkinpractice,andasaresultthestandardsdonotrepresentacoherent,consistentmodelofarchivaldescription.Ofthefourstandards,ISAD(G)hassignificantlyinfluencedinternationalarchivaldescriptivepractice,withISAAR(CPF)havingsomeuse,andbothISDFandISDIAHverylittle.EvenifnewtypesoffindingaidsandarchivaldescriptivesystemsbasedonthefourICAstandardshavebeendevelopedinthepasttenyears,thepredominantmodelofarchivaldescriptionremainsthefonds-downhierarchicaldescriptionprescribedinISAD(G).Foravarietyofreasons,itislikelytoremaintheprevailingapproachtoarchivaldescriptionforthenearfuture:itaddressesthetraditionalunderstandingofthePrincipleofProvenance;itiswellunderstoodbythecommunity;avarietyofexistingmethodsandsystemsexisttofacilitatecreation,maintenance,andpublication;andfinally,itisarelativelyeconomicapproachtoanexceptionallycomplex,labour-intensivechallenge.
Archivaldescription(andresourcedescriptioningeneral)isdependentonavailablecommunicationtechnologies.Asnewmethodsofrepresentingandcommunicatinginformationbecomeavailable,theyoffertheopportunitytore-envisionarchivaldescription.Thisre-envisioninggenerallyemphasizesseparatingandinterrelatingkeycomponentsofdescriptiontoaccommodatetheproductionoffamiliarandprovenmodesofaccessandatthesametimeopennewpathsintoandpresentnewperspectivesondescribedresources.Twointerdependentmotivationsfortheseparationarecommonlycited:improvingtheeconomyandaccuracyofdescription;andenhancingaccesstoandunderstandingofthedescribedresources.
Communicationtechnologiesthatemergedinthelasttwodecadesofthetwentiethcenturyhavegraduallybeentransformingthemethodsusedbyarchiviststodescribeandprovideaccesstothem.Bothmarkup(XMLandrelatedstandards)andrelational(SQL)technologies,inparticular,haveenabledmanyarchivestosuccessfullytransitionfrompaper-basedproductionoffindingaidstocomputer-basedproduction.
Aspowerfulasthetwotechnologieshavebeen,muchandperhapsmostrealworldinformationisnotrepresentedwellineitheroneortheother.Archivaldescription,particularlyinthesinglefonds-leveldescription,isadequatelybutnotoptimallyaccommodatedbydatabasetechnologiesinsomepartsandinotherpartsbymarkuptechnologies.Thatneithertechnologyclearlydominatesthearchival
RiC-CMConsultationDraftv0.1 September2016 9
implementationlandscapereflectsthebetwixtandbetweennatureofthetraditionalsingledescription.Manydescriptionsystemsuseeitheroneortheotheroracarefullycraftedcombinationofthetwo.Technologicaldevelopmentswithinandbetweenthetwotechnologiesameliorateifnoteliminatetheweaknessofeachandthushelpsustaintheirdominanceovertherepresentationlandscape.But,giventhattherealworldwithinwhichweliveandworkmaybeunderstoodasavast,dynamicallyinterrelatednetworkofpeopleandobjectssituatedinspaceandtime,graphtechnologiesoffernewandmoreexpressiveformsofrepresentation.
Graphtechnologieshaveexistedinvariousformssincethe1960s,thoughtheirusedidnotbecomewidespreaduntilthelate1990swhentheW3CreleasedResourceDescriptionFramework(RDF11),astandardfortherepresentationofgraphdata.Graphtechnologiesintroducedatarepresentationasstatements,typicallycharacterizedassubject-predicate-object,witheachstatementcalleda“triple.”WhileXMLsupportsaspecificformofgraphs,thehierarchy(or“tree”),triplesenableunboundedrepresentationofnetworksofinterconnecteddataobjectsaswellasrealworldobjects(representedbydata).
Itiswithinthecontextofestablishedandemergingcommunicationtechnologies,andofanexpandedunderstandingofprovenance,thatRiC-CMisbeingdeveloped.RiC-CMisintendedtoaccommodateexistingdescriptionpracticesandatthesametimetoacknowledgenewunderstandings,andtopositionarchivestotakeadvantageofopportunitiespresentedbynewandemergingcommunicationtechnologies.RiC-CMaspirestoreflectbothfacetsofthePrincipleofProvenance,asthesehavetraditionallybeenunderstoodandpracticed,andatthesametimerecognizeamoreexpansiveanddynamicunderstandingofprovenance.Itisthismoreexpansiveunderstandingthatisembodiedintheword“Contexts.”RiC-CMisintendedtoenableafuller,ifforeverincomplete,descriptionofthecontextsinwhichrecordsemergeandexist,soastoenablemultipleperspectivesandmultipleavenuesofaccess.1.8FromISAD(G),ISAAR(CPF),ISDF,andISDIAHtoRiC-CM
RiC-CMincorporatesthefourexistingICAdescriptionstandards,ISAD(G),ISAAR(CPF),ISDF,andISDIAH.Intheprocessofintegratingandinterrelatingthefourexistingstandards,therehasbeenextensiveanalysisofeachoftheexistingstandards,andthishasledtofurtheridentificationanddifferentiationoftheprimarydescriptionentities,particularlywithaviewtowardshowtomostefficientlymaintainandinterrelatethemtoformcompletedescription.
Theprimarydescriptionentitiesare:
• Record• RecordComponent• RecordSet• Agent• Occupation• Position• Function• Function(Abstract)• Activity• Mandate
11Forfurtherinformationseehttps://www.w3.org/RDF/<accessed20/06/2016>
RiC-CMConsultationDraftv0.1 September2016 10
• DocumentaryForm• Date• Place• Concept/Thing
GiventhatISAD(G)envisionsalldescriptionentitiesorcomponentscombinedinasingledescriptiveapparatus,RiC-CMmaybeunderstoodasembodyingallofISAD(G).Atthesametime,RiC-CMalsoincorporatesandfurtherdifferentiatesthedescriptionentitiesrepresentedintheotherthreeICAstandards.Forexample,AgentembodiesbothISAAR(CPF)andISDIAH,andFunctionandActivityembodiesISDF.1.8.1FromUnitofDescriptiontoRecordandRecordSet
AmainstayinISAD(G)is“unitofdescription.”ISAD(G)(andamajorportionoftheprofessionalliteratureondescription)assumesthatindividualrecordsandaggregationsofrecordsmaybeeachdescribedinthesameway,and,implicitly,thattheyarethesamekindofthing.Althoughinpracticearchivistshavelongrecognizedthatthisisnotthecase,therehasbeennoclearguidance,whichhasledtoconfusedandinconsistentdescription.RiC-CMtreatseachasadistinctkindofthing,andthoughtherearemanysharedproperties,themannerinwhichoneshouldbedescribedisnotthesameasthemannerinwhichtheothershouldbedescribed.Treatingeachasadistinctkindofthing,createdatdifferenttimesandfordifferentpurposes,enablesdescriptionthatisunambiguousandclear.1.8.2FromMultilevelDescriptiontoMultidimensionalDescription
AnadditionalmainstayofISAD(G)is“multileveldescription.”ISAD(G)isbasedona“multilevel”model.Thestandardassumes(thoughdoesnotprescribe)thatthescopeofasingledescriptionisafonds,andthatthedescriptionbeginswithadescriptionofthefonds,asasingleandcompleteentity,andmaythenproceedtodescribepartsofthewhole,andpartsoftheparts,alllinkedtogethertoformasingle,self-containedhierarchy.
RiC-CMmodelswhatmaybedescribedas“multidimensionaldescription.”Ratherthanahierarchy,thedescriptionmaytaketheformofagraphornetwork.Modellingdescriptionasagraphaccommodatesthesingle,fonds-based,multileveldescriptionmodelledinISAD(G),butalsoenablesaddressingthemoreexpansiveunderstandingofprovenancedescribedabove.Themultidimensionalmodelthusenablesthedescriptionofthefonds,butalsoseesthefondsexistinginabroadercontext,inrelationtootherfonds.Inamultidimensionalapproachtodescription,theRecordsandSetsofRecords,theirinterrelationswithoneanother,theirinterrelationswithAgents,Functions,Activities,Mandates,etc.,andeachofthesewithoneanother,arerepresentedasanetworkwithinwhichindividualfondsaresituated.Theproximatecontextofeachfondsisestablished,thoughitsboundariesarepermeable,asitexistswithinlayersofadditionalcontextcontainingotherfonds.ThemodelenablesthefulfilmentoftheRespectdesfonds,butalsoenablesaddressingothertypesofRecordSetswithcomplexorigination(forexample,aseriesthatdocumentsonefunctionthatisperformedseriallybyasuccessionofdifferentAgents).
WhileRiC-CMisamodelthatmakesitpossibletodescriberecordsandtheenvironmentsinwhichtheyarecreated,accumulated,used,andmanagedinawaythatmorefullycapturesandexpressesthecomplexcontextualrealitiesthancanbedoneusingasinglehierarchicaldescription,itdoesnotrepudiatehierarchicaldescriptionassuch.Infact,themodelassumesthatRecordSets,inadditionto
RiC-CMConsultationDraftv0.1 September2016 11
thepossibilityofhavingindividualmemberRecords,mayalsohavememberRecordSets,hierarchicallyarranged,suchasahierarchythatrepresentsaseriesthatcontainssubseriesthatinturncontainfiles.
InthemodellingofRecordSet,specialcareistakentodistinguishbetweenthepropertiesandrelationsoftheRecordSetassuch,andindividualRecordscontainedintheSet.ARecordSet,forexample,hasitsownprovenance.WhiletheprovenanceoftheRecordSetmayberelatedtotheprovenanceofsomeifnotallofthecontainedRecords,theprovenanceoftheRecordSetisdistinctfromtheprovenanceofthecontainedRecords.Inotherwords,whilethecreatorofaRecordSetmaybethesameasthecreatorofallorsomeofthecontainedRecords,theactofcreatingtheRecordisdistinctfromtheactofcreatingtheRecordSet.
DescriptionoftheRecordscontainedinaRecordSetisfurtherdifferentiatedintotwocategories:summarydescriptionofthecontainedRecords(forexample,adaterangeforthespanoftimewithinwhichthecontainedRecordswerecreated),andthesharedpropertiesorrelationstheRecordshavethatdesignatethemasmembersofaRecordSet(forexample,allcontainedRecordsdocumentthesameFunction,orallsharethesameDocumentaryForm).
DistinguishingthekindsandscopeofpropertiesandrelationswithintheRecordSetisintendedtobringgreaterintellectualclaritytothedescriptionandtomakeitpossibletomakeexplicitandmachine-actionable“theinheritanceofdescription.”DescriptionoftheRecordSetassuch,andsummarydescriptionofthecontainedRecordsisonlyintellectuallyinheritableas“context”forthecontainedRecords.ThesummarypropertiesarenotpropertiesofthecontainedRecordsassuch,butanoverviewofthem,reducedtoanabstract.ThesharedpropertiesorrelationsrecordedattheleveloftheRecordSet,however,arelegitimatelypropertiesorrelationsofeachofthememberRecordsofaRecordSet.Forexample,ifalloftheRecordsinaRecordSetreflectaparticularFunction,thenthedescriptionofeachindividualRecordmayalsoincludearelationtotheFunction.1.9TransitiontoRiC-CM
ThoughRiC-CMaccommodatestheexistingpredominantdescriptionpracticethatiscodifiedinISAD(G),italsogoeswellbeyondthecurrentICAdescriptionstandards,bothconceptuallyandstructurally.RiC-CMisintendedtoprovidethesemanticandstructuralfoundationfordevelopingrecorddescriptionsystemsordescriptionmoduleswithinrecordsmanagementsystems.Itattemptstoidentifyandaccommodateawidevarietyofdescriptionandaccessneeds,andisintendedtobesufficientlydetailedandpreciseinthemodellingtosupportgraphandsemantictechnologies.
RiC-CMthusconceptuallydiffersfromandismuchmorecomplexanddetailedthantheexistingfourICAstandards.ItisanticipatedthatmasteringtheintellectualandtechnologicalcomplexityofRiC-CMbyrecordsmanagers,archivists,andthedevelopersofsystemsthatsupporttheirworkwilltaketime.Transitioningfromtheprevailingapproachtorecordsdescription(thesingle,stand-alonefonds-basedhierarchicaldescription)toamoreflexible,open,graph-ornetwork-basedapproachwillbegradual.
Archivesandlibraries,museums,andotherculturalheritageinstitutionswitharchivalholdingsvarygreatlyinsizeandresources,andtheyexistinmanydifferentsocialandpoliticalcontexts.IndevelopingRiC-CM,EGADrecognizesthatmanyinstitutionswillsimplynothavetheresourcestoimmediatelyembraceRiC-CM.Atthesametime,thereareinstitutionsthathavetheneedandmeanstobeginimplementingdescriptionbasedontheRiC-CMmodel,andtheseinstitutionswillbeabletocontribute
RiC-CMConsultationDraftv0.1 September2016 12
feedbacktobenefittheongoingdevelopmentofRiC,andalso“topavetheway”forothers,demonstratingboththevalueoftheRiCmodel,andthemethodsrequiredtosuccessfullyimplementit.
DevelopersofrecordsmanagementandrecorddescriptionandaccesssystemswillalsobeessentialinthepromulgationandongoingdevelopmentofRiC.Developerswithagoodunderstandingofarchivalprinciplesandpractice,aswellascompetencyinthedevelopmentofrelationalandgraphtechnologieswillneedtodesignsystemsthatamelioratetheintellectual,technological,andeconomicchallengeofdatacreationandmaintenance.
EGADalsorecognizestheneedtodevelopImplementationGuidelines,anditisanticipatedthatsuchguidelineswillfollowthereleaseofstableversionsofRiC-CMandRiC-O.1.10Acknowledgements
ICAProgrammeCommission(PCOM)hasgenerouslyprovidedfundingforEGADmeetingsinBelgium(2013),Spain(2014),Romania(2015),andFrance(2016).InadditiontosupportfromthePCOM,theICASecretaryGeneralandotherstaffhaveprovidedbothmoralandlogisticsupporttoEGAD.LocalsupportformeetingswasprovidedbyArchivesgénéralesduRoyaume/AlgemeenRijksarchief(Belgium),ArxiuMunicipaldeGirona(Spain),ArhiveleNaţionalealeRomâniei,ArchivesnationalesdeFrance,andServiceinterministérieldesArchivesdeFrance.EGADmembers’homeinstitutionshavealsoprovidedmemberswithadditionalsupportforbothtravelandwork.
RiC-CMConsultationDraftv0.1 September2016 13
2.Entities
# Name DefinitionRiC-E1Record Linguistic,symbolic,orgraphicinformationrepresentedinanypersistent
form,onanydurablecarrier,byanymethod,byanAgentinthecourseoflifeorworkeventsandActivities.
ScopeNotes Suchinformationmayserveavarietyofpurposes,includingdocumentingtheeventsandActivities.BecauseofitsrelationtotheeventsandActivities,itservesasevidenceforthemnomatteritsqualityforuseinaparticularcontext.OneormoreRecordsinonecontextmaybesubsumedorincorporatedintoaRecordinanothercontexttoformanewRecord.This‘compoundRecord’shouldnotbeconfusedwithaRecordSet,asitisevidenceofasingletransactionbyanAgentratherthanagroupingofdistinctRecordsaspartoftheirmanagementanduse.
Examples deedappointingJohnBambridge,SheriffofLeicestershire,with3rdGreatSealofCharlesIappended;sketchMapoftheQatarPeninsula;emailmessageconcerninganagreementtoparticipateintheICASeoulCongresscontainingtwoattachmentsanddigitallysigned
# Name DefinitionRiC-E2RecordComponent PartofaRecordwithdiscreteinformationcontentthatcontributestothe
Record'sphysicalorintellectualcompleteness.
ScopeNotes
Ifremovedthecompletenessoftherecordiscompromised.
Examples 3rdGreatSealofCharlesI;twodigitalphotographsattachedtoanemailmessage
# Name DefinitionRiC-E3RecordSet OneormoreRecordsthatareintellectuallybroughttogetheratsomeDate,
byanAgent,wherevertheRecordsmayresideandwhateverthesharedpropertiesorrelationsamongthemmaybe.
ScopeNotes Inaparticularcontext,anAgent(e.g.administrator,recordsmanager,archivist,end-user,etc.)selectsthememberRecordsofaRecordSetbasedonasharedpropertyorproperties,orasharedRelationorRelations.ThegroupingoftheRecordsservesapurposeorpurposesspecifictothecontextoftheAgent.Byexception,someRecordsarebroughttogetherbasedontheirnotbelonginginthecontextofselectiontootherdesignatedgroups:a‘Miscellaneous’seriesforexample.Theselectionandgrouping,forexample,mayrepresenttheactofclassifyingtheRecordsinaccordancewithaformalclassificationschemethatmaybebasedonfunction,subject,organizationalstructure,orothercriteria;anactofarchivalarrangement(e.g.basedoncommonprovenance);orsomeotherselectionandgroupingthatfulfilsaparticular
RiC-CMConsultationDraftv0.1 September2016 14
purposeorpurposes(e.g.aclassificationthatreflectsorsupportsthepurposesofaresearcher).TheRecordSetcreatedbyanAgentinthecourseoflifeorworkeventsandActivitiesshouldbekeptinamannerthatpreservescontextandevidentialvalue.RecordsSetsmayalsocontainotherRecordsSets.BothaRecordSetandaRecordmaysimultaneouslybeamemberofmorethanoneRecordSet,andoverthecourseofitsexistence,aRecordSetorRecordmaybeamemberofanindeterminatenumberofRecordSetsinanindeterminatenumberofcontexts.RecordSetsandRecordscontainedwithinaRecordSetmaybeorderedintoasequencebasedonacommonpropertyorrelation,orcommonpropertiesorrelations(e.g.alphabeticalbyAgentorrelatedPlacename);chronologicalorderbyanallocatedDate;orsomeothercriterion(e.g.animposedorderbyrelevance).OneormoreRecordsinonecontextmaybesubsumedorincorporatedintoaRecordinanothercontexttoformanewRecord.Sucha‘compoundRecord’shouldnotbeconfusedwithaRecordSet.
Examples CottonManuscriptsCollection;miscellaneouspapersandfragments;papersoftheEarlsofLiverpool;officialcorrespondenceofthe1stEarlofLiverpool
# Name DefinitionRiC-E4Agent Apersonorgroup,oranentitycreatedbyapersonorgroup,thatis
responsibleforactionstakenandtheireffects.
ScopeNotes AnAgentisknownbyoneormoreidentities;anidentityisaconstellationofpropertiesorrelationsthattogether“identify”theAgent.Personsorgroupscommonlyhaveoneidentity,thoughtheyalsomayhaveoneormoreassumedorfictitiousidentities.Suchassumedidentitiesmaybesharedbymorethanonepersonorgroup.Assumedidentitiesincludebutarenotlimitedtopseudonyms,heteronyms,DBA(DoingBusinessAs),andtradeidentities.AnassumedidentityshouldnotbeconfusedwithPositionsincorporatebodies,forexample,presidents,primeministers,governors,popes,royalty,orbishops.Norshouldanassumedidentitybeconfusedwithavariantofthesameidentity.AgentalsoincludesentitiescreatedbyapersonorgroupthatactonbehalfofthecreatingAgentinanautonomousorsemi-autonomousmanner.ExamplesofsuchDelegate-Agentsaresoftwareagents,robots,andspaceandunderwaterprobesthatgeneratedata(records)infulfilmentofthefunctionassignedtoandtheinstructionsgiventothembythecreatingpersonorgroup.Typicallyarchivistswillwanttoattributeresponsibilityforactingtothepersonorpersons,orgrouporgroups‘behind’theassumedidentity,butdocumentationofassumedidentitiesandrelatingthemtothepersonsorgroupswhomtheyrepresentisimportantforseveralreasons:anassumed
RiC-CMConsultationDraftv0.1 September2016 15
identitymaybetheonlyoneknownbyauser,andthusdocumentationofanassumedidentityandrelatingittothepersonorgroupidentityrepresentedbyitfacilitatesaccess;anassumedidentitymaybeasignificantcomponentofthehistoryofthepersonorgroupitrepresents;anassumedidentitymaybethesubjectofrecords;and,anassumedidentitymayelidethegivenidentityofthepersonorgroupitrepresents,thuseffectivelyeclipsingorreplacingthegivenidentity.
Examples AustralianHearingServices;GilbertandGeorge;LibraryandArchivesCanada;NelsonMandela;Noelfamily,ViscountsCampden;TheWho;FacultyofScience,UniversityofStrathclyde;France,MinistèredelaCultureetdelaCommunication,directiongénéraledespatrimoines
# Name DefinitionRiC-E5Occupation Aprofession,trade,orcraftpursuedbyapersoninfulfilmentofaFunction.
ScopeNotes ThepursuitofanOccupationinvolvestheperformanceofanActivityin
fulfilmentofaFunction.SuccessfulperformanceoftheActivityisbasedontheabilitytoperformsuccessfully(acompetency).Thiscompetencymaybeacquiredthrougheducationorexperience,oracombinationofboth.TheauthorityofthepersontopursuetheOccupationmaybederivedtacitlyorexplicitlyfromanexternalAgent,basedonademonstratedmasteryofthecompetency.OccupationshouldnotbeconfusedwithPosition,forexample,alawyerthatholdsthePositionoflegalcounselinanagency.ThoughOccupationisrelatedtoadomainorfieldofActivity,itshouldnotbeconfusedwiththisdomain,forexample,anarchivistworksinthedomainofarchivalscience.AnOccupationmaybepursuedindependentlybyaperson,orpursuedwithinagroup,contributingtothefulfillmentoftheFunctionofthegroup.
Examples archivist;doctor;lawyer;recordsmanager;teacher
# Name DefinitionRiC-E6Position Arolethatmaybeassignedtoaperson(ortoseveralpersons
simultaneously)withinacorporatebody,andthatexistsindependentlyoftheperson(s)whomayholdit.
ScopeNotes APositionisoftendefinedinaMandate,whichmayspecifytheFunctionsandcompetenciesnecessarytofulfillit,aswellastheActivitiestobeperformed.APositionisoftengivenatitle/name.APositionmaybetiedtoaprojectortoasetoftasksandthushaveadefinedduration.APositionmaychangeovertime,asthecorporatebodythatestablishesitchangesovertime.
RiC-CMConsultationDraftv0.1 September2016 16
PositionisnottobeconfusedwithOccupation,whichisaprofession,trade,orcraftpursuedbyapersoninfulfilmentofaFunction;norwithFunction,whichistheAgent’sgoal;norwithActivity,whichisthesetsofactionsperformedbyanAgent.WithintheRecordscreatedbyacorporatebody,thePositionentitymaybeusedtoidentifytheRecordSetsresultingfromActivitiesperformedbypersonswhoholdaPositionovertime,withoutnecessarilyidentifyingordescribingthosepersons,oridentifyingwhichRecordswerecreatedbyeachofthem.
Examples head,presidentordirectorofacorporatebodyorunitofacorporatebody;executivemanager;technicaladvisor;assistantofadirector;gatekeeper;primeminister
# Name DefinitionRiC-E7Function Anenduringgoal,purpose,orobjectiveofanAgent.
ScopeNotes AFunctionexistsinaspecificsocialandculturalcontext,andwithinthat
contextissubjecttochangeovertime.ItshouldnotbeconfusedwithFunction(Abstract)whichdefinesaFunctionindependentofaparticularcontext.AFunctionmaybecomposedofotherFunctions.AFunctionmayberelatedtomorethanoneAgentsimultaneouslyorovertime.ThefulfilmentofaFunctionrequirestheperformanceofoneormoreActivities.BoththeFunctionandperformanceoftheActivitiesaregovernedbyoneormoreexplicitorimplicitMandates.
Examples teaching,UniversityofGlasgow;marketing,Army&NavyStoresLtd.;providinghearingservices,researchanddevelopment,andconductingeducationabouthearingservices,AustralianHearingServices
# Name DefinitionRiC-E8Function(Abstract) DesignationanddefinitionofaFunctionindependentoftheinstancesofthe
Functionthatisspecifictoaparticularsocialandculturalcontext.
ScopeNotes Function(Abstract)shouldnotbeconfusedwithFunction,whichdefinesthegoals,purposesorobjectivesofanAgentwithinitsspecificcontext.Function(Abstract)willbedefinedinbothglobalanddomain-specificvocabularies.
Examples financialbudgeting;fundraising;hearingservices;research;teaching;marketing;sales;humanresources
# Name DefinitionRiC-E9Activity AsetofcoordinatedactionsortransactionsperformedbyanAgentin
fulfilmentofaFunction,orinthepursuitofanOccupation.
RiC-CMConsultationDraftv0.1 September2016 17
ScopeNotes Activitiesexistinaspecificsocialandculturalcontext,andwithinthatcontextaresubjecttochangeovertime.ActivitiesmaybecomposedofotherActivities.AnActivitymaybeperformedinfulfilmentofoneormoreFunctionsorinthepursuitofoneormoreOccupations,bymorethanoneAgentatthesametimeorovertime.TheperformanceoftheActivitiesisgovernedbyoneormoreexplicitorimplicitMandates.
Examples financialaccounting,UniversityofGlasgow;fundraisingcampaignmanagement,UniversityofGlasgow
# Name DefinitionRiC-E10Mandate AuthorityorrulesthatgoverntheactionsofanAgentwithinaspecificsocial
andculturalcontext.
ScopeNotes AMandatespecifiesorauthorizestheFunctions(goals)ofanAgent(who);ortheActivitiestobeperformedbyanAgentinfulfillmentoftheFunction(means);orthepoliciesorproceduresthatgoverntheperformanceoftheActivity(how);andthePlace(jurisdiction)andDate(timeperiod)withinwhichanAgentmayperformtheActivities(whereandwhen).AMandateestablishestherulesthatgoverntheactionsandconfertheauthorityorcompetenciesofAgentstofulfilldesignatedFunctionsorperformdesignatedActivities.Mandatesexistinaspecificsocialandculturalcontext,andwithinthatcontextaresubjecttochangeovertime.WhileaMandatemaybetacit,inwholeorpart,itmaybeexplicitlyexpressedinavarietyofdocumentarysources(forexample,constitutions,legislation,(legal)acts,statutes,legalcodes,ordinances,charges,charters,missionstatements,regulations,policies,procedures,orstandards).ThesourceorsourcesofsomeMandatesareexternaltotheAgent(forexample,expressedinelections,socialmores,customs,communityexpectations,laws,regulations,standardsandbestpracticecodes),whileothersareexpressedwithintheAgent’simmediatecontext(forexample,policies,orwrittenorverbalinstructions).TheevidenceforidentifyingaMandatemaybefoundinitsentiretyinonedocumentarysource(forexample,alaworregulation),ormaybefoundintwoormoresources.AMandateshouldnotbeconfusedwiththeoneormoredocumentarysourcesthatserveasevidenceofitsidentity.
Examples authoritygrantedbyelectorstoapersontorepresenttheminParliament;authorityofaMayortograntbuildingauthorisations;rulesset
RiC-CMConsultationDraftv0.1 September2016 18
outinRecordsinContext:AConceptualModelforArchivalDescription,adocumentpublishedbytheInternationalCouncilonArchives(ICA)whichdefineshowanarchivistdescribesarchivalmaterial;themandateoftheAustralianHearingServices,assetoutbytheAustralianHearingServicesAct1991(s7),istoprovidehearingservices,carryoutresearchanddevelopmentinrelationtohearingservicesandacousticdevelopment,andconducteducationabouthearingservices,inadditiontoanyotherfunctionsconferredontheAuthority(s8).ThepowertoperformthesefunctionsisexercisedbytheAuthority(s9)abodycorporategovernedbyaBoardofDirectors(ss7,13,14,15and16),whichissubjecttothedirectionoftheMinisterforHumanServices(s12).TheManagingDirectormanagestheAuthority,undertheBoard(s42).(Adaptedfromsource:https://www.humanservices.gov.au/corporate/about-us/legislation)
# Name DefinitionRiC-E11DocumentaryForm TherulesusedinthecreationofaRecordthatprescribestheparticular
physicalorintellectualelementsthatmustbepresent.
ScopeNotes TheDocumentaryFormplaysanimportantroleindeterminingthetypeofinformationaRecordmaycomprise,itsstatusofperfection,anditsauthenticityandreliability.Documentaryformsexistinaspecificsocialandculturalcontext,andwithinthatcontextaresubjecttochangeovertime.
Examples deedofgift;email;letter;papalbull;charter;letterspatent;birthcertificate;will
# Name DefinitionRiC-E12Date Chronologicalinformationassociatedwithanentitythatcontributestoits
identificationandcontextualization.
ScopeNotes --
Examples 1925-1957;20thCentury;3HenryVIII;4March1842;9ThermidorAnII;c.1860s
# Name DefinitionRiC-E13Place Jurisdictionsandanygeographicoradministrativepointorarea.
ScopeNotes Includessettlementsofanykind(towns,villages,etc.),historicalregions,
andpoliticalandadministrativedistricts.
Examples AmazonRiver;NovaScotia;Paris;NorthLanarkshireDistrict;ManchesterDiocese;RugbyUrbanSanitaryDistrict
# Name DefinitionRiC-E14Concept/Thing
Anyideaornotion,materialthing,oreventoroccurrencethatcanbeassociatedwith,orinsomecasesbethesubjectof,otherentities.
RiC-CMConsultationDraftv0.1 September2016 19
ScopeNotes IncludesallRiCentitiesaswellasthefollowing:abstractconcepts;culturalmovements,namedperiodsandevents;namedthings,objectsandworks;legendary,mythicalorfictitiousfigures,charactersorbeings.
Examples airplanes;BattleoftheSomme;impressionism;Puck;renaissance;slavery;BeforeChristianEra(BCE);FrenchRevolution
RiC-CMConsultationDraftv0.1 September2016 20
RiC-CMConsultationDraftv0.1 September2016 21
3.PropertiesofEntities
3.1SharedPropertiesofallEntities
# Name DefinitionRiC-P1GlobalPersistentIdentifier Globallyuniqueandpersistentlyresolvableidentifierfortheentity.
Scope --
DataType URI
Examples http://n2t.net/ark:/99166/w6v1266v[exampleofanArchivalResourceKey
persistentidentifierforaRecord];http://isni.org/0000000073572182[exampleofapersistentInternationalStandardNameIdentifierforaperson]
# Name DefinitionRiC-P2LocalIdentifier Localidentifier(s)assignedtotheentity.
Scope ThiscoversallidentifiersotherthanGlobalPersistentIdentifiers.
DataType Text
Examples BUD-01-F002[exampleofaclassificationnumberfromacorporatefileplan];
NAS1/A/1.1[exampleoflocalidentifierforaRecord];F1204[exampleofalocalidentifierforaRecordSetassignedbyarepository]
# Name DefinitionRiC-P3Name Atitleortermdesignatingtheentity.
Scope
--
DataType Text,orControlledPhrase,orControlledTerm,orControlledFormat
Examples 4March1842;2016-08-24[DateformattedaccordingtoISO8601];deedofgift;doctor;fundraising,UniversityofGlasgow;hearingservices;NelsonMandela;PapersoftheEarlsofLiverpool;Paris;primeminister;SketchMapoftheQatarPeninsula
# Name DefinitionRiC-P4GeneralNote Descriptionoftheentitythatisnototherwiseaddressed.
Scope IncludesinformationontherelationoftheentitytoanyotherRiCentitythat
isnototherwiseprovided.
DataType Text
Examples --
RiC-CMConsultationDraftv0.1 September2016 22
3.2PropertiesofRecord3.2.1ContentInformation# Name DefinitionRiC-P5AuthenticityandIntegrityNote
DescriptionoffeaturesoftheRecordattestingtohowitisgenuine,reliable,trustworthy,wholeandcomplete.
Scope --
DataType Text
Examples therecordmissingitslowerleftcorneroftextandbearsthesealoftheKing;therecordiselectronicallysignedandthesignatureisvalidatthemomentofdescription;thedatabase(.dbf)filehasthechecksumSHA-1:bb165836546e13c8d80e97aa44e8f4369608e9f8
# Name DefinitionRiC-P6ContentType ThefundamentalformofcommunicationinwhichaRecordisexpressedand
thehumansensethroughwhichitisintendedtobeperceived.
Scope --
DataType ControlledTerm
Examples cartographicimage;notatedmusic;spokenword;stillimage;text
# Name DefinitionRiC-P7ContentExtent CountablecharacteristicsofthecontentoftheRecord,expressedasa
quantity.
Scope Contentextentinformationisindependentofcarrierextentinformation;thenumber,sizeordurationofthecontentunit(s)wouldremainthesameevenifthenumberorsizeofthecarriersitwascontainedondiffered.
DataType Text
Examples duration:3minutesand24seconds;6maps;34poems
# Name DefinitionRiC-P8QualityofInformation ConditionsofaRecordthatimpactthelegibilityorcompletenessofits
information,andthustheviabilityofitsuse.
Scope SuchconditionsmaybeassociatedwithdeficienciesintheprocessesofRecordcreationorcapture,orthedeteriorationoftheRecord(e.g.itscarrier)causinglossofinformationovertime.
DataType Text
Examples somelossofinformationduetopoorqualityimagecapture;somelossoftextduetorodentdamage
RiC-CMConsultationDraftv0.1 September2016 23
# Name DefinitionRiC-P9ScopeandContent Summaryofthescope(suchas,timeperiods,geography)andcontent(such
assubjectmatter,administrativeprocesses)oftheRecord.
Scope MayincludedescriptionofrelationswithAgents,otherRecords,Functions,Activities,DatesandPlaces.MayalsoincludedescriptionofcomponentsoftheRecordwhenconsideredsignificantandnotconsideredseparately.
DataType Text
Examples IncludesadetailedlistofthelandsandvillagesgivenbytheKingtotheAbbey;amongthewitnesses,thedukeofNormandy;theauthorexplainswhyhedoesnotagreewiththedecisionmadeandaddsthatitcannotbeapplied
3.2.2InformationaboutRepresentation# Name DefinitionRiC-P10EncodingFormat Informationaboutthelogicalformofdigitallyrepresentedcontent.
Scope --
DataType ControlledTerm(Mimetypes:http://www.iana.org/assignments/media-
types/media-types.xhtml)
Examples text/csv;image/tiff;audio/mp4;application/pdf
# Name DefinitionRiC-P11LanguageInformation AspokenorwrittenhumanlanguagerepresentedintheRecords.
Scope Informationincludesthelanguage,thescriptofthelanguage,andthescript
transliterationschemewhenappropriate.MorethanonelanguagemayberepresentedinaRecord.
DataType ControlledCodeorTerm(ISO639Codesfortherepresentationofnamesoflanguages;ISO15924Codesfortherepresentationofnamesandscripts)
Examples Languages:Arabic(ara);Chinese(chi)English(eng);French(fre);Spanish(spa)Scripts:Arabic(Arab);Han(Hans);Latin(Latn)Transliterationscheme:ISO233-2:1993Informationanddocumentation-TranslationofArabiccharactersintoLatincharacters-Part2:Arabiclanguage-Simplifiedtransliteration;ISO843:1997Informationanddocumentation--ConversionofGreekcharactersintoLatincharacters
# Name DefinitionRiC-P12MediaType Thegeneraltypeofintermediationdevicerequiredtorenderthecontentofa
Record.
Scope --
RiC-CMConsultationDraftv0.1 September2016 24
DataType ControlledTerm
Examples audio;computer;microform;unmediated;video
# Name DefinitionRiC-P13ProductionTechnique ThemethodusedintherepresentationofinformationontheRecordcarrier.
Scope --
DataType TextorControlledTerm
Examples manuscription(handwriting);engraving;magneticrecording;optical
recording
3.2.3InformationaboutCarrier# Name DefinitionRiC-P14Medium Physicalmaterialinoronwhichinformationisrepresented.
Scope Includesphysicalcarriersinoronwhichinformationisrepresentedthatdo
notrequireanintermediationdevice.
DataType ControlledTerm
Examples claytablets;papyrus;magneticdisk;opticaldisk;paper;parchment;film;vinyldisk;magnetictape
# Name DefinitionRiC-P15PhysicalorLogicalExtent Numberofphysicalunitsand/orphysicaldimensionsofRecordcarriersor,in
thecaseofdigitalmediacarriers,thesizeofstoragespaceoccupied.
Scope --
DataType Text
Examples 1page;5folios;17x34.5cm;1USBstick;3GB
# Name DefinitionRiC-P16PhysicalCharacteristicsNote
InformationaboutthephysicalcharacteristicsoftheRecord.
Scope Includesinformationaboutthephysicalnatureandconditionsuchasconservationstatus.
DataType Text
Examples Recordheavilyfoxed;emulsionflaking;watermarked;BritishLibrarybinding
3.2.4InformationaboutManagementandUse# Name DefinitionRiC-P17Classification InformationonthecriterionorcriteriathatmaybeusedtoidentifyaRecord
RiC-CMConsultationDraftv0.1 September2016 25
asamemberofaRecordSet.
Scope Thisinformationmaybeintheformoftext,oratermorcodemaintainedinaclassificationscheme.ThecriterionorcriteriamayberepresentedinaRiCpropertyorthrougharelation,forexample,toaDocumentaryFormoraFunction(Abstract).TheRecordssharingthispropertyorrelationincommonidentifythemasmembersofaparticularRecordSet.
DataType TextorControlledCodeorTerm
Examples BUD-01-F002[exampleofaclassificationnumberfromacorporatefileplan];humanresourcemanagement;studentregistration;financialaffairs;digitization
# Name DefinitionRiC-P18ConditionsofAccess ConditionsaffectingtheavailabilityofaRecordforconsultation.
Scope Suchconditionsmaybelaws,regulationsandpolicies,includingpoliciesand
requirementspertainingtoprivacy,securityconcernsorrestrictions;ortheymaypertaintothephysicalstateoftheRecord,forexample,conditionsthatrequirepreservationtreatment;ortheymayspecifyanysoftware/hardwarenecessarytoaccesstheRecord.
DataType Text
Examples Open;Closedunderdataprotectionlegislation;Closedasawaitingconservationtreatment;
# Name DefinitionRiC-P19ConditionsofUse ConditionsaffectingtheavailabilityoftheRecordforuseafteraccesshas
beenprovided.
Scope IncludesconditionsgoverningreproductionoftheRecordunderapplicablecopyright(intellectualproperty)orpropertylegislation.
DataType Text
Examples freelyusablewithoutrestrictions;thepermissionoftheowneroftheRecordmustbeobtainedbeforeuse
# Name DefinitionRiC-P20History AnaccountofthehistoryoftheRecord.Totheextentknown,thismaycover
theentirehistoryoftheRecordfromitsinceptiontothedateofthedescription.
Scope Thehistorymayincludeeventsassociatedwithcustody,actionstakenontheRecordaspartofitsmanagement(appraisal,description,classificationandreclassification,datastoragemigration,encodingtypeconversions,andsoon)thathavecontributedtoitsstateatthetimeofdescription.Whenknown,provideDatesofandAgentsassociatedwiththeevents.
RiC-CMConsultationDraftv0.1 September2016 26
DataType Text
Examples --
# Name DefinitionRiC-P21RecordState DescriptionoftheproductionorreproductionstatusoftheRecord.
Scope --
DataType TextorControlledTerm
Examples draft;finaldraft;original;simplecopy;certifiedcopy
3.3PropertiesofRecordComponentEditor’sNote:Inmanycases,describingatthecomponentlevelwillberareduetopracticalresourceconstraints,andparticularlywherethewholeRecordexistsandisdescribed.However,insomecases,descriptionsforseparatedRecordComponentsmayberequired.Inthissituation,allpropertiesidentifiedins.4.2forRecordapply.WhilethisdraftreleaseoftheRiCCMdoesnotincludedetailsforeachpropertyasitwouldapplytoaRecordComponent,afutureversionoftheRiCCMwouldincludethisinformation,aswellasexamplesofeachpropertyasappliedtoaRecordComponent.3.4PropertiesofRecordSet# Name DefinitionRiC-P22AuthenticityandIntegrityNote
DescriptionoffeaturesoftheRecordSetattestingtohowitisgenuine,reliable,trustworthy,wholeandcomplete.
Scope --
DataType Text
Examples --
# Property DefinitionRiC-P23Type AbroadcategorizationofthetypeofRecordSet.
Scope ForlegacypurposesthistypeistheequivalentoftheLevelofDescription
elementinISAD(G)(3.1.4)exceptforthevalue“item”,whichequatestotheRecordentityinRiC.RecordSetTypemaybeextendedtoreflecttypesofRecordSetsthatarenotarchival.
DataType ControlledTerm
Examples fonds;series;file;class;piece;collection;accrual;accession;project
RiC-CMConsultationDraftv0.1 September2016 27
# Property DefinitionRiC-P24AccrualNote InformationonanticipatedaccessionstotheRecordSet.
Scope SuchaccessionsmaybesingleRecordsorRecordSets.
DataType Text
Examples Thereisanagreementwiththecreatorthatadditionalsnapshotsoftheire-
maildirectorywillbeaccessionedatyearlyintervals.
# Property DefinitionRiC-P25AccrualStatus WhetherornottheRecordSetisopenforadditionalaccessionsofRecordsor
RecordSets.
Scope ClosedindicatesthatnoadditionalRecordsorRecordSetswill(orareanticipatedto)beaddedtotheRecordSet.OpenindicatesthatadditionalRecordsorRecordSetswill(orareexpectedto)beaddedtotheRecordSet.
DataType ControlledTerm
Examples closed;open;unknown
# Property DefinitionRiC-P26Arrangement CriteriaandprinciplesusedtoordertheRecordsorRecordsSetswithinthe
RecordSet.
Scope Encompassesonlyintellectualarrangementinformation.Physicalarrangementinformationisoutofscope.
DataType Text
Examples arrangedaccordingtothealphabeticalorderoftheplacesconcerned;arrangedchronologically
# Property DefinitionRiC-P27Classification Informationonthecriterionorcriteriausedinselectingthemembersofthe
RecordSet.
Scope Thisinformationmaybeintheformoftext,oratermorcodemaintainedinaclassificationscheme.ThecriterionorcriteriamayberepresentedinaRiCpropertyorrelationthatissharedbythemembersintheRecordSet.ThissharedpropertyorrelationmaybelongtoboththeRecordandRecordSet,andmayalsobeinheritedbydescendantmembersofaRecordSet.Itdependsonhowitisrepresentedinthedescription:ifitisadescriptionofthecriteriausedinformingorassemblingtheRecordSet,thenitisapropertyoftheRecordSet;ifitisatermorcodethatappliestoalldescendantRecords,thenitisamongthepropertiesthataresharedbythedescendantRecords.
RiC-CMConsultationDraftv0.1 September2016 28
DataType TextorControlledCodeorTerm
Examples BUD-01-F002[exampleofaclassificationnumberfromacorporatefileplan];humanresourcemanagement;studentregistration;financialaffairs;digitization
# Property DefinitionRiC-P28History
AnaccountofthehistoryoftheRecordSet.Totheextentknown,thismaycovertheentirehistoryoftheRecordSetfromitsinceptiontothedateofthedescription.
Scope Totheextentknown,thehistorymaycovertheentirehistoryoftheRecordSetfromitsinceptiontothedateofthedescription.SignificantEventsincludebutarenotlimitedtocreationorformationoftheRecordSet,transfersofcustodyorownership,changesincustodialresponsibility,changesinthearrangement,additions(accruals)orremovingorseparationofmemberRecordsorRecordSets,andusesoftheRecordSet.DescriptionoftheeventsshouldincludeAgent(s),theDate(s)oftheevent(s),andthePlace(s)wheretheevent(s)occurred.RecordSetsarenotstatic,themembershipisdynamic,thatismemberRecordsmaycomeandgo.SignificantchangesinclassificationwouldconstitutetheformulationofnewRecordSets.
DataType Text
Examples ThemanuscriptsarepartofthecollectionsofRobertHarley(d1724)andEdwardHarley(d1741),1stand2ndEarlsofOxford,thatwerebroughtbyParliamentandtransferredtotheBritishMuseumin1753.ThosematerialswerethenseparatedintothiscollectionandthoseforHarleyChartersandHarleyRollsandbecamepartofthecollectionsoftheBritishLibraryin1972.
3.5PropertiesSummarizingtheMembersofaRecordSet# Property DefinitionRiC-P29ContentExtent CountablecharacteristicsofthecontentoftheRecordSet,expressedasa
quantity.
Scope Contentextentinformationisindependentofcarrierextentinformation;thenumber,sizeordurationofthecontentunit(s)wouldremainthesameevenifthenumberorsizeofthecarriersitwascontainedondiffered.
DataType Text
Examples duration:3minutesand24seconds;6photographs;2films;6maps
# Property DefinitionRiC-P30PhysicalorLogicalExtent
Numberofphysicalunitsand/orphysicaldimensionsofRecordSetcarriersor,inthecaseofdigitalmediacarriers,thesizeofstoragespaceoccupied.
RiC-CMConsultationDraftv0.1 September2016 29
Scope --
DataType Text
Examples 40pages;5folios;25m2;1USBstick;35GB
# Property DefinitionRiC-P31ScopeandContent Summaryofthescope(suchas,timeperiods,geography)andcontent(such
ascontenttype,documentaryforms,subjectmatter,administrativeprocesses)ofthememberRecordsorRecordSets.
Scope --
DataType Text
Examples --
3.6PropertiesSharedbyAllMemberRecordsofaRecordSetEditor’snote:Thefollowingproperties,whichhavethesamedefinitionsasthosegivenforRecord,maybeusedwhentheyaresharedbyallmemberRecordsofaRecordSet:
• RiC-P6ContentType• RiC-P10EncodingFormat• RiC-P11LanguageInformation• RiC-P12MediaType• RiC-P13ProductionTechnique• RiC-P14Medium• RiC-P17ConditionsofAccess• RiC-P18ConditionsofUse• RiC-P20RecordState
MembersofaRecordSetmustshareatleastonecommonproperty(thebasisforformingtheset);theymayallsharemorethanonecommonproperty.
3.7PropertiesSharedbyAllAgents# Property DefinitionRiC-P32Type SpecifickindofAgent.
Scope Thetopleveltypesdefinegroups(includingfamilies,corporatebodiesand
conferences),personsanddelegate-agentscreatedbyapersonorgroupthatactonbehalfofthecreatingAgentinanautonomousorsemi-autonomousmanner.Ifthetypeisunknownthatthisshouldbestated.Eachtypemaybeextendedtocovermorespecificcategorization,forexample,todistinguishbetweenpublicandprivatecorporatebodies,ortospecifythelegalstatusoftheAgentaccordingtosomeinternationalorlocalscheme.
RiC-CMConsultationDraftv0.1 September2016 30
NotallpropertiesunderAgentapplytoalltypes.
DataType ControlledTerm
Examples group;corporatebody;conference;family;person;delegate-agent;unknown
# Property DefinitionRiC-P33IdentityType ThespecifickindofidentityofanAgent.
Scope Agivenidentityistheidentitythatiscommonlyconsideredtheidentityof
the‘real’Agent.Anassumedidentityisanidentityinventedbyoneormore‘real’Agents,withthe‘real’AgentorAgentsactingundertheguiseoftheassumedidentity.
DataType ControlledTerm
Examples given;individualassumed;jointassumed;unknown
# Property DefinitionRiC-P34LanguageInformation AspokenorwrittenhumanlanguageusedbytheAgent.
Scope Informationincludesthelanguage,thescriptofthelanguage,andthescript
transliterationschemewhenappropriate.AnAgentmayuseoneormorelanguage.
DataType ControlledCodeorTerm(ISO639Codesfortherepresentationofnamesoflanguages;ISO15924Codesfortherepresentationofnamesandscripts)
Examples Languages:Arabic(ara);Chinese(chi)English(eng);French(fre);Spanish(spa)Scripts:Arabic(Arab);Han(Hans);Latin(Latn)Transliterationscheme:ISO233-2:1993Informationanddocumentation-TranslationofArabiccharactersintoLatincharacters-Part2:Arabiclanguage-Simplifiedtransliteration;ISO843:1997Informationanddocumentation--ConversionofGreekcharactersintoLatincharacters
# Property DefinitionRiC-P35History ConcisehistoryoftheAgent.
Scope Historymayincorporatethegeneralsocial,cultural,oreconomiccontextin
whichtheAgentlivedorexistedwhensuchcontextaidsinunderstandingtheAgent’sFunctions,Occupations,PositionsorActivities.
DataType Text
Examples --
RiC-CMConsultationDraftv0.1 September2016 31
3.8AdditionalPropertySpecifictoPersonandPersonAssumedIdentity# Property DefinitionRiC-P36Gender Thegenderwithwhichaperson(orpersonassumedidentity)identifies.
Scope --
DataType ControlledTerm
Examples male;female;unknown
3.9AdditionalPropertySpecifictoDelegate-Agent# Property DefinitionRiC-P37TechnicalCharacteristics Descriptionofthetechnicalcharacteristicsofthedelegate-Agent.
Scope --
DataType Text
Examples --
3.10AdditionalPropertiesSpecifictoCorporateBodyandCorporateBodyAssumedIdentity# Property DefinitionRiC-P38ServicestothePublic Descriptionofpublicservicespolicies,inparticularwithrespectto
qualificationstousetheservices,andrights,privileges,andresponsibilitiesofusersoftheservices.
Scope --
DataType Text
Examples --
# Property DefinitionRiC-P39ContactInformation Contactinformationtorequestinformationaboutavailablepublicservices,
servicepolicies,andsoon.
Scope --
DataType Text
Examples 29cheminduMoulinDetesta13090Aix-en-Provence(France)Siteweb:http://www.archivesnationales.culture.gouv.fr/caom/fr/index.htmlFrance.DirectiondesArchivesdeFranceNote:FortheinstitutionArchivesnationalesd’outre-mer
RiC-CMConsultationDraftv0.1 September2016 32
Téléphone:+33(0)442933850Télécopie:+33(0)442933899Adresseélectronique:[email protected]:FortheinstitutionArchivesnationalesd’outre-merCoordenaçãoRegionalnoDistritoFederal,emBrasília(COREG):SIG–Q6Lote800–AnexoaoprédiodaImprensaNacional70610-460–Brasília–DFBrasilwww.arquivonacional.gov.brBrazil.ArquivoNacionalNote:FortheinstitutionArquivoNacional
# Property DefinitionRiC-P40OperatingHours DaysandhoursofdayduringwhichpublicservicesofanAgentareavailable.
Scope --
DataType Text
Examples Open:Mon-Fri9.15-4.45;Sat9.15-12.30,1.30-4.30.LateopeningThursto
7.30pmClosed:OneweekearlyDecemberUnitedKingdom,TheNationalArchivesNote:FortheinstitutionWestSussexRecordOfficeAperturaalpúblico:LunesaViernesde8.00am-15.00pmHorasdeAperturaSemanales:35Cerradoalpúblico:SábadosyDomingos.Festivos:1y6deenero,28defebrero,JuevesyViernesSanto,1mayo,30demayo,CorpusChristi,15deagosto,1denoviembre,6,8,24,25y31dediciembre.Spain.SubdirecciónGeneraldelosArchivosEstatalesNote:FortheinstitutionArchivoGeneraldeIndias
# Property DefinitionRiC-P41Facilities DescriptionofphysicalfacilitieswhereanAgentprovidespublicservices.
Scope Includesissuesofphysicalaccessibility,suchaswheelchairaccess,andother
provisionsforuserswithphysicaldisabilities.
DataType Text
Examples --
3.11PropertiesofOccupation# Property DefinitionRiC-P42Type CategorizationoftheOccupation.
Scope --
RiC-CMConsultationDraftv0.1 September2016 33
DataType ControlledTerm
Examples healthprofessionals;legalprofessionals;serviceandsalesworkers
# Property DefinitionRiC-P43Description DescriptionoftheOccupationincludingtheFunctionsfulfilledandthe
Activitiesinvolved.
Scope --
DataType Text
Examples --
# Property DefinitionRiC-P44History ConcisehistoryoftheOccupationanditschangesovertime,including
changesconcerningtherulesgoverningitandthepersonswhopursuedit.
Scope --
DataType Text
Examples --
3.12PropertiesofPosition# Property DefinitionRiC-P45Type CategorizationofthePositionusingeitheralistoftypesestablishedexternal
toorwithintheinstitution.
Scope --
DataType ControlledTerm
Examples academic;administrativeandprofessional;operational;technical
# Property DefinitionRiC-P46Description DescriptionofthePositionasdefinedbyandwithinthecontrollingcorporate
body.
Scope TheremitofthePosition.
DataType Text
Examples --
# Property DefinitionRiC-P47History HistoryofthePosition,ofitscreationanddefinition,andofitschangesover
time,includingchangesconcerningthecompetenciesrequired,theauthorityandFunctionsassigned,andthepersonsholdingthePosition.
RiC-CMConsultationDraftv0.1 September2016 34
Scope --
DataType Text
Examples --
3.13PropertiesofFunction# Property DefinitionRiC-P48Type CategorizationoftheFunction.
Scope --
DataType ControlledTerm
Examples function;sub-function
# Property DefinitionRiC-P49Description Descriptionofthenature,scopeandmeaningoftheFunction.
Scope --
DataType Text
Examples Thefunctionofundertakingacademicresearchcoverstheconductofall
academicresearch,whetheritisfundedbytheuniversityitself,byexternalorganizations,orbyboth.Italsocoversresearchundertakenincollaborationwithotherinstitutions[exampleforresearch,UniversityofStrathclyde].
# Property DefinitionRiC-P50History Historyoforiginanddevelopmentofthegoals,purposes,orobjectives
definedinaFunction.
Scope InformationmayincludedescriptionoftheroleorrolesplayedbyAgentsinauthorizingorfulfillingtheFunctionandhowtheychangedovertime,andtheActivitiesperformedinfulfillmentoftheFunction.
DataType Text
Examples --
3.14PropertyofFunction(Abstract)# Property DefinitionRiC-P51Description DefinitionoftheFunction(Abstract).
Scope --
DataType Text
Examples Thesystematicinvestigationintoandstudyofmaterialsandsourcesinorder
RiC-CMConsultationDraftv0.1 September2016 35
toestablishfactsandresearchnewconclusions[examplefor‘research’].
3.15PropertiesofActivity# Property DefinitionRiC-P52Type CategorizationoftheActivity.
Scope --
DataType ControlledTerm
Examples activity;businessprocess;action;task;transaction
# Property DefinitionRiC-P53Description Descriptionofcoordinatedactionsortransactionsperformedinfulfillmentof
aFunction,orpursuitofanOccupation.
Scope IncludesdescriptionofconstituentActivities.Informationmayincludedescriptionofprocesses,plans,procedures,methods,andtoolsthatcontributetoanunderstandingofanActivity.
DataType Text
Examples Tasksinvolvedindevelopingandestablishingtheuniversity’sresearchstrategyinclude:identifyingrequirementsforaneworrevisedstrategy;undertakingresearch;developingstrategyproposals;consultingonstrategyproposals;reviewingandrevisingstrategyproposalsinlightofcommentsreceived;draftingstrategydocuments;consultingonstrategydocuments;reviewingdraftstrategydocumentsinlightofcommentsreceived;producingfinalstrategydocuments;submittingfinalstrategydocumentsforformalendorsement;formallyendorsingstrategydocuments;disseminatingstrategydocuments;reviewingstrategies[exampleforresearchstrategydevelopment,UniversityofStrathclyde].
# Property DefinitionRiC-P54History HistoryoforiginanddevelopmentoftheActivity.
Scope InformationmayincludedescriptionofthePositionsheldbyAgentsin
authorizingorperformingtheActivityandhowtheychangedovertime;changesinhowtheActivitywasperformed;andchangesinActivities’constituentActivities.
DataType Text
Examples --
3.16PropertiesofMandate# Property DefinitionRiC-P55Type CategorizationoftheMandate.
RiC-CMConsultationDraftv0.1 September2016 36
Scope --
DataType ControlledTerm
Examples decree;legislation;rule;standard;letterofappointment
# Property DefinitionRiC-P56Description Informationdescribingtheauthority,Functions,Activities,policies,or
proceduresthatcomprisetheMandate;thejurisdictionallimitsandthetemporalperiodwithinwhichtheMandateiseffectiveorvalid;andtheAgentorAgentsthataregovernedbytheMandate.
Scope --
DataType Text
Examples --
# Property DefinitionRiC-P57History InformationdescribingtheoriginanddevelopmentoftheMandate.
Scope SuchinformationincludesdescriptionoftheAgentorAgentsthat
participatedinthecreationordevelopmentoftherulesthatcomprisetheMandate;revisionofthejurisdictionallimitsortemporalperiodwithinwhichtheMandateiseffectiveorvalid;andchangesintheAgentorAgentsthatarecontrolledorguidedbytheMandate.
DataType Text
Examples --
3.17PropertiesofDocumentaryForm# Property DefinitionRiC-P58Type CategorizationoftheDocumentaryForm.
Scope --
DataType ControlledTerm
Examples longplayingrecord(LP);charter;register
# Property DefinitionRiC-P59Description DescriptionoftheDocumentaryFormincludingitsmainextrinsicand
intrinsiccharacteristics.
Scope --
DataType Text
Examples --
RiC-CMConsultationDraftv0.1 September2016 37
# Property DefinitionRiC-P60History HistoryoftheDocumentaryFormincludingthecontextinwhichitfirst
appearedoritsusagedeveloped,inwhichitwasused,itschangesovertime,andtheAgentswhousedit.
Scope --
DataType Text
Examples --
3.18PropertiesofDate# Property DefinitionRiC-P61Type CategorizationoftheDate.
Scope --
DataType ControlledTerm
Examples single;range
# Property DefinitionRiC-P62Calendar CalendarwithwhichtheliteralexpressionoftheDate(Dateasexpressedand
understoodbyhumanAgents)isexpressed.
Scope --
DataType Text
Examples Gregorian;FrenchRevolutioncalendar
3.19PropertiesofPlace# Property DefinitionRiC-P63Type AnindicationofthecategoryofPlace,especiallytodistinguishnaturaland
humannotions.
Scope --
DataType ControlledTermorPhrase
Examples settlement;administrativedivision;country;mountain;river
# Property DefinitionRiC-P64GeographicCoordinates LongitudinalandlatitudinalinformationofthePlace.
Scope --
DataType ControlledCodeorTerm(ISO6709Standardrepresentationofgeographic
RiC-CMConsultationDraftv0.1 September2016 38
pointlocationbycoordinates)
Examples --
# Property DefinitionRiC-P65Address PhysicallocationofthePlace.
Scope Includesanylocationinformationexclusiveofgeographiccoordinates.
DataType Text
Examples 59rueGuynemer,F-93383Pierrefitte-sur-SeineCedex
3.20PropertiesofConcept/Thing# Property DefinitionRiC-P66Type CategorizationoftheConcept/Thing.
Scope --
DataType ControlledTerm
Examples --
# Property DefinitionRiC-P67Description DescriptionoftheConcept/Thing.
Scope --
DataType Text
Examples --
RiC-CMConsultationDraftv0.1 September2016 39
4.Relations
4.1ListofRelationsbyDomainEntityEditor’sNotes:1.Thefollowingareknownlimitationstothepresentationoftherelationsinthisconsultationdraft,toberesolvedinfutureversionsofthisdocument.
a. Therelationsinthecurrentdraftareintendedtobesuggestiveandnotcompleteornormative.b. Eachrelationidentifiedislackingadefinitionandexamples.Asaresult,theremaybesomeambiguity
regardingthemeaningandintendeduse.c. SequentialorderingofRecordsorRecordSets,accordingtochronologyorsomeothercriteria,hasnot
yetbeenfullyaccommodated. 2.Thisdraftpresentstherelationsaccordingtodomainentity.FutureversionsofRiC-CMmayofferadifferentpresentationoftherelations. 3.AllentitiesinRiCareassociatedwithallotherentities.Forexample:‘RecordisassociatedwithRecordSet’.Further,the‘isassociatedwith’relationisthemostgeneralorabstracttypeofrelation,whileallotherrelationstatementsaremorespecificphrasingsorrepresentations.Forexample,‘hascopy’isaspecifictypeofassociationrelationbetweentwoRecords.4.Severalentitiessharea‘hassubject’/’issubjectof’relation.Thisistosaythatoneentitycomprisesthetopic,theme,orcontentmatteroftheotherentity.Forexample,‘RecordhassubjectAgent’indicatesthattheinformationalcontentoftheRecordis‘about’(depicts,describes,orconcerns)theAgent.Severalotherrelations(suchas‘ismemberof’,‘ispartof’,‘ispredecessorof’,‘isevidenceof’,‘resultedfrom’,‘isheldby’,‘wascreatedby’,and‘hadcreationdate’)andtheirinverserelationsmaybeconsideredsharedbytwoormoreentities.Forexample,thechronologicalrelation‘ispredecessorof’canbeusedforRecord,RecordComponent,RecordSet,Agent,Occupation,Position,Function,Activity,andMandate.Fornow,eachoccurrenceoftheserelationsisdistinct;however,thestatusoftheserelationswillbeclarifiedinafutureversionofRiC-CMandinRiC-Ontology,andsomewilllikelybemergedintooneuniquerelation. 5.Almostallrelationsareexpressedinpresenttense,whichpermitsdescribingeitherpermanenttraitsorcurrentsituations.However,describingarchivalcontextoftenrequiresquotingpastsituationsandnon-permanenttraits.Forexample,'J.F.KennedyoccupiespositionpresidentoftheUnitedStatesofAmerica'isnotcurrentlytrue;sothisrelationshouldbestatedusingthepasttense:'J.F.KennedyoccupiedpositionpresidentoftheUnitedStatesofAmerica'.Also,‘RecordisheldbyAgent’referstoaRecordinthecurrentcustodyofanarchives,while‘RecordwasheldbyAgent’meansthattheRecordwasheld,onlyatacertaintime,inthecustodyofanAgent.Therefore,thelistsbelowprovide,forsomerelationtypes,botharelationusingthepresenttenseandarelationusingthepasttense.TheP68Datepropertycanalsobeusedtoclarifywhenarelationwasactive.
RiC-CMConsultationDraftv0.1 September2016 40
4.1.1RecordRelations
RelationNumber
RelationDomain
RelationName RelationRange
InverseRelationNameandNumber
Comments
RiC-R1 Record hascopy Record iscopyof(RiC-R6)
RiC-R2 Record hasdraft Record isdraftof(RiC-R7)
RiC-R3 Record hasoriginal Record isoriginalof(RiC-R8)
RiC-R4 Record hassubject Record issubjectof(RiC-R10)
RiC-R5 Record isassociatedwith Record isassociatedwith(RiC-R5) SeealsoRiC-R12
RiC-R6 Record iscopyof Record hascopy(RiC-R1)
RiC-R7 Record isdraftof Record hasdraft(RiC-R2)
RiC-R8 Record isoriginalof Record hasoriginal(RiC-R3)
RiC-R9 Record ispredecessorof Record issuccessorof(RiC-R11)
RiC-R10 Record issubjectof Record hassubject(RiC-R4)
RiC-R11 Record issuccessorof Record ispredecessorof(RiC-R9)
RiC-R12 Record wasassociatedwith Record wasassociatedwith(RiC-R12)
SeealsoRiC-R5
RiC-R13 Record hadpart RecordComponent
waspartof(RiC-R77) SeealsoRiC-R14
RiC-R14 Record haspart RecordComponent
ispartof(RiC-R75) SeealsoRiC-R13
RiC-R15 Record isassociatedwith RecordComponent
isassociatedwith(RiC-R74) SeealsoRiC-R16
RiC-R16 Record wasassociatedwith RecordComponent
wasassociatedwith(RiC-R76)
SeealsoRiC-R15
RiC-R17 Record isassociatedwith RecordSet isassociatedwith(RiC-R136) SeealsoRiC-R19
RiC-R18 Record ismemberof RecordSet hasmember(RiC-R135) SeealsoRiC-R20
RiC-R19 Record wasassociatedwith RecordSet wasassociatedwith(RiC-R137)
SeealsoRiC-R17
RiC-CMConsultationDraftv0.1 September2016 41
RelationNumber
RelationDomain
RelationName RelationRange
InverseRelationNameandNumber
Comments
RiC-R20 Record wasmemberof RecordSet hadmember(RiC-R134) SeealsoRiC-R18
RiC-R21 Record hadrightsheldby Agent wasrightsholderof(RiC-R217)
SeealsoRiC-R22
RiC-R22 Record hasrightsheldby Agent isrightsholderof(RiC-R209) SeealsoRiC-R21
RiC-R23 Record hassubject Agent issubjectof(RiC-R210)
RiC-R24 Record isassociatedwith Agent isassociatedwith(RiC-R207) SeealsoRiC-R28
RiC-R25 Record isheldby Agent isholderof(RiC-R208) SeealsoRiC-R32
RiC-R26 Record isownedby Agent owns(RiC-R212) SeealsoRiC-R33
RiC-R27 Record wasaddressedto Agent wasaddresseeof(RiC-R214)
RiC-R28 Record wasassociatedwith Agent wasassociatedwith(RiC-R215)
SeealsoRiC-R24
RiC-R29 Record wasauthoredby Agent authored(RiC-R204)
RiC-R30 Record wascollectedby Agent collected(RiC-R205)
RiC-R31 Record wascreatedby Agent created(RiC-R206)
RiC-R32 Record washeldby Agent washolderof(RiC-R216) SeealsoRiC-R25
RiC-R33 Record wasownedby Agent owned(RiC-R211) SeealsoRiC-R26
RiC-R34 Record wassentby Agent sent(RiC-R213)
RiC-R35 Record waswrittenby Agent wrote(RiC-R218)
RiC-R36 Record hassubject Occupation issubjectof(RiC-R336)
RiC-R37 Record isassociatedwith Occupation isassociatedwith(RiC-R335) SeealsoRiC-R39
RiC-R38 Record resultedfrom Occupation resultedin(RiC-R337)
RiC-R39 Record wasassociatedwith Occupation wasassociatedwith(RiC-R338)
SeealsoRiC-R37
RiC-R40 Record hassubject Position issubjectof(RiC-R376)
RiC-CMConsultationDraftv0.1 September2016 42
RelationNumber
RelationDomain
RelationName RelationRange
InverseRelationNameandNumber
Comments
RiC-R41 Record isassociatedwith Position isassociatedwith(RiC-R375) SeealsoRiC-R43
RiC-R42 Record resultedfrom Position resultedin(RiC-R377)
RiC-R43 Record wasassociatedwith Position wasassociatedwith(RiC-R378)
SeealsoRiC-R41
RiC-R44 Record hassubject Function issubjectof(RiC-R426)
RiC-R45 Record isassociatedwith Function isassociatedwith(RiC-R424) SeealsoRiC-R47
RiC-R46 Record isevidenceof Function isevidencedby(RiC-R425)
RiC-R47 Record wasassociatedwith Function wasassociatedwith(RiC-R427)
SeealsoRiC-R45
RiC-R48 Record hassubject Function(Abstract)
issubjectof(RiC-R478)
RiC-R49 Record isassociatedwith Function(Abstract)
isassociatedwith(RiC-R477) SeealsoRiC-R50
RiC-R50 Record wasassociatedwith Function(Abstract)
wasassociatedwith(RiC-R479)
SeealsoRiC-R49
RiC-R51 Record hassubject Activity issubjectof(RiC-R510)
RiC-R52 Record isassociatedwith Activity isassociatedwith(RiC-R509) SeealsoRiC-R54
RiC-R53 Record resultedfrom Activity resultedin(RiC-R511)
RiC-R54 Record wasassociatedwith Activity wasassociatedwith(RiC-R512)
SeealsoRiC-R52
RiC-R55 Record hassubject Mandate issubjectof(RiC-R563)
RiC-R56 Record isassociatedwith Mandate isassociatedwith(RiC-R561) SeealsoRiC-R58
RiC-R57 Record isevidenceof Mandate isevidencedby(RiC-R562)
RiC-R58 Record wasassociatedwith Mandate wasassociatedwith(RiC-R564)
SeealsoRiC-R56
RiC-R59 Record hasdocumentaryform DocumentaryForm
isdocumentaryformof(RiC-R615)
RiC-CMConsultationDraftv0.1 September2016 43
RelationNumber
RelationDomain
RelationName RelationRange
InverseRelationNameandNumber
Comments
RiC-R60 Record isassociatedwith DocumentaryForm
isassociatedwith(RiC-R614) SeealsoRiC-R61
RiC-R61 Record wasassociatedwith DocumentaryForm
wasassociatedwith(RiC-R616)
SeealsoRiC-R60
RiC-R62 Record hadcreationdate Date wascreationdateof(RiC-R646)
RiC-R63 Record isassociatedwith Date isassociatedwith(RiC-R644) SeealsoRiC-R64
RiC-R64 Record wasassociatedwith Date wasassociatedwith(RiC-R645)
SeealsoRiC-R63
RiC-R65 Record hadholdinglocation Place washoldinglocationof(RiC-R712)
SeealsoRiC-R66
RiC-R66 Record hasholdinglocation Place isholdinglocationof(RiC-R708)
SeealsoRiC-R65
RiC-R67 Record hassubject Place issubjectof(RiC-R709)
RiC-R68 Record isassociatedwith Place isassociatedwith(RiC-R707) SeealsoRiC-R69
RiC-R69 Record wasassociatedwith Place wasassociatedwith(RiC-R710)
SeealsoRiC-R68
RiC-R70 Record wascreatedat Place wascreationlocationof(RiC-R711)
RiC-R71 Record hassubject Concept/Thing issubjectof(RiC-R763)
RiC-R72 Record isassociatedwith Concept/Thing isassociatedwith(RiC-R762) SeealsoRiC-R73
RiC-R73 Record wasassociatedwith Concept/Thing wasassociatedwith(RiC-R764)
SeealsoRiC-R72
RiC-CMConsultationDraftv0.1 September2016 44
4.1.2.RecordComponentRelations
RelationNumber
RelationDomain RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R74 RecordComponent isassociatedwith Record isassociatedwith(RiC-R15)
SeealsoRiC-R76
RiC-R75 RecordComponent ispartof Record haspart(RiC-R14) SeealsoRiC-R77
RiC-R76 RecordComponent wasassociatedwith
Record wasassociatedwith(RiC-R16)
SeealsoRiC-R74
RiC-R77 RecordComponent waspartof Record hadpart(RiC-R13) SeealsoRiC-R75
RiC-R78 RecordComponent isassociatedwith RecordComponent
isassociatedwith(RiC-R78)
SeealsoRiC-R81
RiC-R79 RecordComponent ispredecessorof RecordComponent
issuccessorof(RiC-R80)
RiC-R80 RecordComponent issuccessorof RecordComponent
ispredecessorof(RiC-R79)
RiC-R81 RecordComponent wasassociatedwith
RecordComponent
wasassociatedwith(RiC-R81)
SeealsoRiC-R78
RiC-R82 RecordComponent isassociatedwith RecordSet isassociatedwith(RiC-R138)
SeealsoRiC-R83
RiC-R83 RecordComponent wasassociatedwith
RecordSet wasassociatedwith(RiC-R139)
SeealsoRiC-R82
RiC-R84 RecordComponent hadrightsheldby Agent wasrightsholderof(RiC-R230)
SeealsoRiC-R85
RiC-R85 RecordComponent hasrightsheldby Agent isrightsholderof(RiC-R224)
SeealsoRiC-R84
RiC-R86 RecordComponent hassubject Agent issubjectof(RiC-R225)
RiC-R87 RecordComponent isassociatedwith Agent isassociatedwith(RiC-R222)
SeealsoRiC-R90
RiC-R88 RecordComponent isheldby Agent isholderof(RiC-R223)
SeealsoRiC-R94
RiC-CMConsultationDraftv0.1 September2016 45
RelationNumber
RelationDomain RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R89 RecordComponent isownerof Agent owns(RiC-R227) SeealsoRiC-R95
RiC-R90 RecordComponent wasassociatedwith
Agent wasassociatedwith(RiC-R228)
SeealsoRiC-R87
RiC-R91 RecordComponent wasauthoredby Agent authored(RiC-R219)
RiC-R92 RecordComponent wascollectedby Agent collected(RiC-R220)
RiC-R93 RecordComponent wascreatedby Agent created(RiC-R221)
RiC-R94 RecordComponent washeldby Agent washolderof(RiC-R229)
SeealsoRiC-R88
RiC-R95 RecordComponent wasownerof Agent owned(RiC-R226) SeealsoRiC-R89
RiC-R96 RecordComponent waswrittenby Agent wrote(RiC-R231)
RiC-R97 RecordComponent hassubject Occupation issubjectof(RiC-R340)
RiC-R98 RecordComponent isassociatedwith Occupation isassociatedwith(RiC-R339)
SeealsoRiC-R100
RiC-R99 RecordComponent resultedfrom Occupation resultedin(RiC-R341)
RiC-R100 RecordComponent wasassociatedwith
Occupation wasassociatedwith(RiC-R342)
SeealsoRiC-R98
RiC-R101 RecordComponent hassubject Position issubjectof(RiC-R380)
RiC-R102 RecordComponent isassociatedwith Position isassociatedwith(RiC-R379)
SeealsoRiC-R104
RiC-R103 RecordComponent resultedfrom Position resultedin(RiC-R381)
RiC-R104 RecordComponent wasassociatedwith
Position wasassociatedwith(RiC-R382)
SeealsoRiC-R102
RiC-R105 RecordComponent hassubject Function issubjectof(RiC-R430)
RiC-CMConsultationDraftv0.1 September2016 46
RelationNumber
RelationDomain RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R106 RecordComponent isassociatedwith Function isassociatedwith(RiC-R428)
SeealsoRiC-R108
RiC-R107 RecordComponent isevidenceof Function isevidencedby(RiC-R429)
RiC-R108 RecordComponent wasassociatedwith
Function wasassociatedwith(RiC-R431)
SeealsoRiC-R106
RiC-R109 RecordComponent hassubject Function(Abstract)
issubjectof(RiC-R481)
RiC-R110 RecordComponent isassociatedwith Function(Abstract)
isassociatedwith(RiC-R480)
SeealsoRiC-R111
RiC-R111 RecordComponent wasassociatedwith
Function(Abstract)
wasassociatedwith(RiC-R482)
SeealsoRiC-R110
RiC-R112 RecordComponent hassubject Activity issubjectof(RiC-R514)
RiC-R113 RecordComponent isassociatedwith Activity isassociatedwith(RiC-R513)
SeealsoRiC-R115
RiC-R114 RecordComponent resultedfrom Activity resultedin(RiC-R515)
RiC-R115 RecordComponent wasassociatedwith
Activity wasassociatedwith(RiC-R516)
SeealsoRiC-R113
RiC-R116 RecordComponent hassubject Mandate issubjectof(RiC-R566)
RiC-R117 RecordComponent isassociatedwith Mandate isassociatedwith(RiC-R565)
SeealsoRiC-R118
RiC-R118 RecordComponent wasassociatedwith
Mandate wasassociatedwith(RiC-R567)
SeealsoRiC-R117
RiC-R119 RecordComponent hasdocumentaryform
DocumentaryForm
isdocumentaryformof(RiC-R618)
RiC-R120 RecordComponent isassociatedwith DocumentaryForm
isassociatedwith(RiC-R617)
SeealsoRiC-R121
RiC-CMConsultationDraftv0.1 September2016 47
RelationNumber
RelationDomain RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R121 RecordComponent wasassociatedwith
DocumentaryForm
wasassociatedwith(RiC-R619)
SeealsoRiC-R120
RiC-R122 RecordComponent hadcreationdate Date wascreationdateof(RiC-R649)
RiC-R123 RecordComponent isassociatedwith Date isassociatedwith(RiC-R647)
SeealsoRiC-R124
RiC-R124 RecordComponent wasassociatedwith
Date wasassociatedwith(RiC-R648)
SeealsoRiC-R123
RiC-R125 RecordComponent hadholdinglocation
Place washoldinglocationof(RiC-R718)
SeealsoRiC-R126
RiC-R126 RecordComponent hasholdinglocation
Place isholdinglocationof(RiC-R714)
SeealsoRiC-R125
RiC-R127 RecordComponent hassubject Place issubjectof(RiC-R715)
RiC-R128 RecordComponent isassociatedwith Place isassociatedwith(RiC-R713)
SeealsoRiC-R129
RiC-R129 RecordComponent wasassociatedwith
Place wasassociatedwith(RiC-R716)
SeealsoRiC-R128
RiC-R130 RecordComponent wascreatedat Place wascreationlocationof(RiC-R717)
RiC-R131 RecordComponent hassubject Concept/Thing issubjectof(RiC-R766)
RiC-R132 RecordComponent isassociatedwith Concept/Thing isassociatedwith(RiC-R765)
SeealsoRiC-R133
RiC-R133 RecordComponent wasassociatedwith
Concept/Thing wasassociatedwith(RiC-R767)
SeealsoRiC-R132
RiC-CMConsultationDraftv0.1 September2016 48
4.1.3.RecordSetRelations
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R134 RecordSet hadmember Record wasmemberof(RiC-R20)
SeealsoRiC-R135
RiC-R135 RecordSet hasmember Record ismemberof(RiC-R18) SeealsoRiC-R134
RiC-R136 RecordSet isassociatedwith Record isassociatedwith(RiC-R17)
SeealsoRiC-R137
RiC-R137 RecordSet wasassociatedwith Record wasassociatedwith(RiC-R19)
SeealsoRiC-R136
RiC-R138 RecordSet isassociatedwith RecordComponent isassociatedwith(RiC-R82)
SeealsoRiC-R139
RiC-R139 RecordSet wasassociatedwith RecordComponent wasassociatedwith(RiC-R83)
SeealsoRiC-R138
RiC-R140 RecordSet hadmember RecordSet wasmemberof(RiC-R147)
SeealsoRiC-R141
RiC-R141 RecordSet hasmember RecordSet ismemberof(RiC-R143)
SeealsoRiC-R140
RiC-R142 RecordSet isassociatedwith RecordSet isassociatedwith(RiC-R142)
SeealsoRiC-R146
RiC-R143 RecordSet ismemberof RecordSet hasmember(RiC-R141) SeealsoRiC-R147
RiC-R144 RecordSet ispredecessorof RecordSet issuccessorof(RiC-R145)
RiC-R145 RecordSet issuccessorof RecordSet ispredecessorof(RiC-R144)
RiC-R146 RecordSet wasassociatedwith RecordSet wasassociatedwith(RiC-R146)
SeealsoRiC-R142
RiC-R147 RecordSet wasmemberof RecordSet hadmember(RiC-R140)
SeealsoRiC-R143
RiC-R148
RecordSet hadrightsheldby Agent wasrightsholderof(RiC-R249)
SeealsoRiC-R149
RiC-CMConsultationDraftv0.1 September2016 49
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R149 RecordSet hasrightsheldby Agent isrightsholderof(RiC-R239)
SeealsoRiC-R148
RiC-R150 RecordSet hassubject Agent issubjectof(RiC-R240)
RiC-R151 RecordSet isassociatedwith Agent isassociatedwith(RiC-R237)
SeealsoRiC-R159
RiC-R152 RecordSet isheldby Agent isholderof(RiC-R238) SeealsoRiC-R162
RiC-R153 RecordSet ismanagedby Agent manages(RiC-R242) SeealsoRiC-R163
RiC-R154 RecordSet isownedby Agent owns(RiC-R244) SeealsoRiC-R164
RiC-R155 RecordSet wasaccumulatedby Agent accumulated(RiC-R232)
RiC-R156 RecordSet wasaddressedto Agent wasaddresseeof(RiC-R246)
RiC-R157 RecordSet wasarrangedby Agent arranged(RiC-R233)
RiC-R158 RecordSet wasassembledby Agent assembled(RiC-R234)
RiC-R159 RecordSet wasassociatedwith Agent wasassociatedwith(RiC-R247)
SeealsoRiC-R151
RiC-R160 RecordSet wascollectedby Agent collected(RiC-R235)
RiC-R161 RecordSet wascreatedby Agent created(RiC-R236)
RiC-R162 RecordSet washeldby Agent washolderof(RiC-R248)
SeealsoRiC-R152
RiC-R163 RecordSet wasmanagedby Agent managed(RiC-R241) SeealsoRiC-R153
RiC-R164 RecordSet wasownedby Agent owned(RiC-R243) SeealsoRiC-R154
RiC-R165 RecordSet wassentby Agent sent(RiC-R245)
RiC-R166 RecordSet hassubject Occupation issubjectof(RiC-R344)
RiC-R167 RecordSet isassociatedwith Occupation isassociatedwith(RiC-R343)
SeealsoRiC-R169
RiC-CMConsultationDraftv0.1 September2016 50
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R168 RecordSet resultedfrom Occupation resultedin(RiC-R345)
RiC-R169 RecordSet wasassociatedwith Occupation wasassociatedwith(RiC-R346)
SeealsoRiC-R167
RiC-R170 RecordSet hassubject Position issubjectof(RiC-R384)
RiC-R171 RecordSet isassociatedwith Position isassociatedwith(RiC-R383)
SeealsoRiC-R173
RiC-R172 RecordSet resultedfrom Position resultedin(RiC-R385)
RiC-R173 RecordSet wasassociatedwith Position wasassociatedwith(RiC-R386)
SeealsoRiC-R171
RiC-R174 RecordSet hassubject Function issubjectof(RiC-R434)
RiC-R175 RecordSet isassociatedwith Function isassociatedwith(RiC-R432)
SeealsoRiC-R177
RiC-R176 RecordSet isevidenceof Function isevidencedby(RiC-R433)
RiC-R177 RecordSet wasassociatedwith Function wasassociatedwith(RiC-R435)
SeealsoRiC-R175
RiC-R178 RecordSet hassubject Function(Abstract) issubjectof(RiC-R484)
RiC-R179 RecordSet isassociatedwith Function(Abstract) isassociatedwith(RiC-R483)
SeealsoRiC-R180
RiC-R180 RecordSet wasassociatedwith Function(Abstract) wasassociatedwith(RiC-R485)
SeealsoRiC-R179
RiC-R181 RecordSet hassubject Activity issubjectof(RiC-R518)
RiC-R182 RecordSet isassociatedwith Activity isassociatedwith(RiC-R517)
SeealsoRiC-R184
RiC-R183 RecordSet resultedfrom Activity resultedin(RiC-R519)
RiC-R184 RecordSet wasassociatedwith Activity wasassociatedwith(RiC-R520)
SeealsoRiC-R182
RiC-CMConsultationDraftv0.1 September2016 51
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R185 RecordSet hassubject Mandate issubjectof(RiC-R570)
RiC-R186 RecordSet isassociatedwith Mandate isassociatedwith(RiC-R568)
SeealsoRiC-R188
RiC-R187 RecordSet isevidenceof Mandate isevidencedby(RiC-R569)
RiC-R188 RecordSet wasassociatedwith Mandate wasassociatedwith(RiC-R571)
SeealsoRiC-R186
RiC-R189 RecordSet isassociatedwith DocumentaryForm isassociatedwith(RiC-R620)
SeealsoRiC-R190
RiC-R190 RecordSet wasassociatedwith DocumentaryForm wasassociatedwith(RiC-R621)
SeealsoRiC-R189
RiC-R191 RecordSet hadcreationdate Date wascreationdateof(RiC-R653)
RiC-R192 RecordSet hascoveragedate Date iscoveragedateof(RiC-R651)
RiC-R193 RecordSet isassociatedwith Date isassociatedwith(RiC-R650)
SeealsoRiC-R194
RiC-R194 RecordSet wasassociatedwith Date wasassociatedwith(RiC-R652)
SeealsoRiC-R193
RiC-R195 RecordSet hadholdinglocation Place washoldingplaceof(RiC-R724)
SeealsoRiC-R196
RiC-R196 RecordSet hasholdinglocation Place isholdingplaceof(RiC-R720)
SeealsoRiC-R195
RiC-R197 RecordSet hassubject Place issubjectof(RiC-R721)
RiC-R198 RecordSet isassociatedwith Place isassociatedwith(RiC-R719)
SeealsoRiC-R199
RiC-R199 RecordSet wasassociatedwith Place wasassociatedwith(RiC-R722)
SeealsoRiC-R198
RiC-R200 RecordSet wascreatedat Place wascreationplaceof(RiC-R723)
RiC-CMConsultationDraftv0.1 September2016 52
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R201 RecordSet hassubject Concept/Thing issubjectof(RiC-R769)
RiC-R202 RecordSet isassociatedwith Concept/Thing isassociatedwith(RiC-R768)
SeealsoRiC-R203
RiC-R203 RecordSet wasassociatedwith Concept/Thing wasassociatedwith(RiC-R770)
SeealsoRiC-R202
4.1.4.AgentRelations
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R204 Agent authored Record wasauthoredby(RiC-R29)
RiC-R205 Agent collected Record wascollectedby(RiC-R30)
RiC-R206 Agent created Record wascreatedby(RiC-R31)
RiC-R207 Agent isassociatedwith Record isassociatedwith(RiC-R24)
SeealsoRiC-R215
RiC-R208 Agent isholderof Record isheldby(RiC-R25) SeealsoRiC-R216
RiC-R209 Agent isrightsholderof Record hasrightsheldby(RiC-R22)
SeealsoRiC-R217
RiC-R210 Agent issubjectof Record hassubject(RiC-R23)
RiC-R211 Agent owned Record wasownedby(RiC-R33) SeealsoRiC-R212
RiC-R212 Agent owns Record isownedby(RiC-R26) SeealsoRiC-R211
RiC-R213 Agent sent Record wassentby(RiC-R34)
RiC-R214 Agent wasaddresseeof Record wasaddressedto(RiC-R27)
RiC-CMConsultationDraftv0.1 September2016 53
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R215 Agent wasassociatedwith Record wasassociatedwith(RiC-R28)
SeealsoRiC-R207
RiC-R216 Agent washolderof Record washeldby(RiC-R32) SeealsoRiC-R208
RiC-R217 Agent wasrightsholderof Record hadrightsheldby(RiC-R21)
SeealsoRiC-R209
RiC-R218 Agent wrote Record waswrittenby(RiC-R35)
RiC-R219 Agent authored RecordComponent wasauthoredby(RiC-R91)
RiC-R220 Agent collected RecordComponent wascollectedby(RiC-R92)
RiC-R221 Agent created RecordComponent wascreatedby(RiC-R93)
RiC-R222 Agent isassociatedwith RecordComponent isassociatedwith(RiC-R87)
SeealsoRiC-R228
RiC-R223 Agent isholderof RecordComponent isheldby(RiC-R88) SeealsoRiC-R229
RiC-R224 Agent isrightsholderof RecordComponent hasrightsheldby(RiC-R85)
SeealsoRiC-R230
RiC-R225 Agent issubjectof RecordComponent hassubject(RiC-R86)
RiC-R226 Agent owned RecordComponent wasownerof(RiC-R95) SeealsoRiC-R227
RiC-R227 Agent owns RecordComponent isownerof(RiC-R89) SeealsoRiC-R226
RiC-R228 Agent wasassociatedwith RecordComponent wasassociatedwith(RiC-R90)
SeealsoRiC-R222
RiC-R229 Agent washolderof RecordComponent washeldby(RiC-R94) SeealsoRiC-R223
RiC-R230 Agent wasrightsholderof RecordComponent hadrightsheldby(RiC-R84)
SeealsoRiC-R224
RiC-CMConsultationDraftv0.1 September2016 54
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R231 Agent wrote RecordComponent waswrittenby(RiC-R96)
RiC-R232 Agent accumulated RecordSet wasaccumulatedby(RiC-R155)
RiC-R233 Agent arranged RecordSet wasarrangedby(RiC-R157)
RiC-R234 Agent assembled RecordSet wasassembledby(RiC-R158)
RiC-R235 Agent collected RecordSet wascollectedby(RiC-R160)
RiC-R236 Agent created RecordSet wascreatedby(RiC-R161)
RiC-R237 Agent isassociatedwith RecordSet isassociatedwith(RiC-R151)
SeealsoRiC-R247
RiC-R238 Agent isholderof RecordSet isheldby(RiC-R152) SeealsoRiC-R248
RiC-R239 Agent isrightsholderof RecordSet hasrightsheldby(RiC-R149)
SeealsoRiC-R249
RiC-R240 Agent issubjectof RecordSet hassubject(RiC-R150)
RiC-R241 Agent managed RecordSet wasmanagedby(RiC-R163)
SeealsoRiC-R242
RiC-R242 Agent manages RecordSet ismanagedby(RiC-R153)
SeealsoRiC-R241
RiC-R243 Agent owned RecordSet wasownedby(RiC-R164)
SeealsoRiC-R244
RiC-R244 Agent owns RecordSet isownedby(RiC-R154) SeealsoRiC-R243
RiC-R245 Agent sent RecordSet wassentby(RiC-R165)
RiC-R246 Agent wasaddresseeof RecordSet wasaddressedto(RiC-R156)
RiC-CMConsultationDraftv0.1 September2016 55
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R247 Agent wasassociatedwith RecordSet wasassociatedwith(RiC-R159)
SeealsoRiC-R237
RiC-R248 Agent washolderof RecordSet washeldby(RiC-R162) SeealsoRiC-R238
RiC-R249 Agent wasrightsholderof RecordSet hadrightsheldby(RiC-R148)
SeealsoRiC-R239
RiC-R250 Agent controlled Agent wascontrolledby(RiC-R280)
SeealsoRiC-R251
RiC-R251 Agent controls Agent iscontrolledby(RiC-R263)
SeealsoRiC-R250
RiC-R252 Agent created Agent(oftypedelegate-agent)
wascreatedby(RiC-R281)
RiC-R253 Agent hadfunctionalrelationwith
Agent hadfunctionalrelationwith(RiC-R253)
SeealsoRiC-R257
RiC-R254 Agent(oftypegroup)
hadmember Agent wasmemberof(RiC-R284)
SeealsoRiC-R258
RiC-R255 Agent(oftypegroup)
hadpart Agent(oftypegroup) waspartof(RiC-R286) SeealsoRiC-R259
RiC-R256 Agent hasassumedidentity Agent isassumedidentityof(RiC-R261)
RiC-R257 Agent hasfunctionalrelationwith
Agent hasfunctionalrelationwith(RiC-R257)
SeealsoRiC-R253
RiC-R258 Agent(oftypegroup)
hasmember Agent ismemberof(RiC-R266) SeealsoRiC-R254
RiC-R259 Agent(oftypegroup)
haspart Agent(oftypegroup) ispartof(RiC-R268) SeealsoRiC-R255
RiC-R260 Agent isassociatedwith Agent isassociatedwith(RiC-R260)
SeealsoRiC-R278
RiC-R261 Agent isassumedidentityof
Agent hasassumedidentity(RiC-R256)
RiC-CMConsultationDraftv0.1 September2016 56
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R262 Agent(oftypeperson)
ischildof Agent(oftypeperson)
isparentof(RiC-R267) SeealsoRiC-R279
RiC-R263 Agent iscontrolledby Agent controls(RiC-R251) SeealsoRiC-R280
RiC-R264 Agent(oftypecorporatebody)
isdirectedby Agent(oftypeperson)
isdirectorof(RiC-R265) SeealsoRiC-R282
RiC-R265 Agent(oftypeperson)
isdirectorof Agent(oftypecorporatebody)
isdirectedby(RiC-R264) SeealsoRiC-R283
RiC-R266 Agent ismemberof Agent(oftypegroup) hasmember(RiC-R258) SeealsoRiC-R284
RiC-R267 Agent(oftypeperson)
isparentof Agent(oftypeperson)
ischildof(RiC-R262) SeealsoRiC-R285
RiC-R268 Agent(oftypegroup)
ispartof Agent(oftypegroup) haspart(RiC-R259) SeealsoRiC-R286
RiC-R269 Agent ispredecessorof Agent issuccessorof(RiC-R273)
RiC-R270 Agent(oftypeperson)
issiblingof Agent(oftypeperson)
issiblingof(RiC-R270) SeealsoRiC-R287
RiC-R271 Agent(oftypeperson)
isspouseof Agent(oftypeperson)
isspouseof(RiC-R271) SeealsoRiC-R288
RiC-R272 Agent issubordinateof Agent issuperiorof(RiC-R274) SeealsoRiC-R289
RiC-R273 Agent issuccessorof Agent ispredecessorof(RiC-R269)
RiC-R274 Agent issuperiorof Agent issubordinateof(RiC-R272)
SeealsoRiC-R290
RiC-R275 Agent(oftypedelegate-agent)
isusedby Agent uses(RiC-R277) SeealsoRiC-R291
RiC-CMConsultationDraftv0.1 September2016 57
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R276 Agent used Agent(oftypedelegate-agent)
wasusedby(RiC-R291) SeealsoRiC-R277
RiC-R277 Agent uses Agent(oftypedelegate-agent)
isusedby(RiC-R275) SeealsoRiC-R276
RiC-R278 Agent wasassociatedwith Agent wasassociatedwith(RiC-R278)
SeealsoRiC-R260
RiC-R279 Agent(oftypeperson)
waschildof Agent(oftypeperson)
wasparentof(RiC-R285) SeealsoRiC-R262
RiC-R280 Agent wascontrolledby Agent controlled(RiC-R250) SeealsoRiC-R263
RiC-R281 Agent(oftypedelegate-agent)
wascreatedby Agent created(RiC-R252)
RiC-R282 Agent(oftypecorporatebody)
wasdirectedby Agent(oftypeperson)
wasdirectorof(RiC-R283)
SeealsoRiC-R264
RiC-R283 Agent(oftypeperson)
wasdirectorof Agent(oftypecorporatebody)
wasdirectedby(RiC-R282)
SeealsoRiC-R265
RiC-R284 Agent wasmemberof Agent(oftypegroup) hadmember(RiC-R254) SeealsoRiC-R266
RiC-R285 Agent(oftypeperson)
wasparentof Agent(oftypeperson)
waschildof(RiC-R279) SeealsoRiC-R267
RiC-R286 Agent(oftypegroup)
waspartof Agent(oftypegroup) hadpart(RiC-R255) SeealsoRiC-R268
RiC-R287 Agent(oftypeperson)
wassiblingof Agent(oftypeperson)
wassiblingof(RiC-R287) SeealsoRiC-R270
RiC-R288 Agent(oftypeperson)
wasspouseof Agent(oftypeperson)
wasspouseof(RiC-R288)
SeealsoRiC-R271
RiC-CMConsultationDraftv0.1 September2016 58
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R289 Agent wassubordinateof Agent wassuperiorof(RiC-R290)
SeealsoRiC-R272
RiC-R290 Agent wassuperiorof Agent wassubordinateof(RiC-R289)
SeealsoRiC-R274
RiC-R291 Agent(oftypedelegate-agent)
wasusedby Agent used(RiC-R276) SeealsoRiC-R275
RiC-R292 Agent isassociatedwith Occupation isassociatedwith(RiC-R347)
SeealsoRiC-R295
RiC-R293 Agent pursued Occupation waspursuedby(RiC-R350)
SeealsoRiC-R294
RiC-R294 Agent pursues Occupation ispursuedby(RiC-R348) SeealsoRiC-R293
RiC-R295 Agent wasassociatedwith Occupation wasassociatedwith(RiC-R349)
SeealsoRiC-R292
RiC-R296 Agent(oftypegroup)
established Position wasestablishedby(RiC-R390)
RiC-R297 Agent isassociatedwith Position isassociatedwith(RiC-R387)
SeealsoRiC-R300
RiC-R298 Agent(oftypeperson)
occupied Position wasoccupiedby(RiC-R391)
SeealsoRiC-R299
RiC-R299 Agent(oftypeperson)
occupies Position isoccupiedby(RiC-R388)
SeealsoRiC-R298
RiC-R300 Agent wasassociatedwith Position wasassociatedwith(RiC-R389)
SeealsoRiC-R297
RiC-R301 Agent fulfilled Function wasfulfilledby(RiC-R439)
SeealsoRiC-R302
RiC-R302 Agent fulfils Function isfulfilledby(RiC-R437) SeealsoRiC-R301
RiC-R303 Agent isassociatedwith Function isassociatedwith(RiC-R436)
SeealsoRiC-R304
RiC-CMConsultationDraftv0.1 September2016 59
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R304 Agent wasassociatedwith Function wasassociatedwith(RiC-R438)
SeealsoRiC-R303
RiC-R305 Agent isassociatedwith Function(Abstract) isassociatedwith(RiC-R486)
SeealsoRiC-R306
RiC-R306 Agent wasassociatedwith Function(Abstract) wasassociatedwith(RiC-R487)
SeealsoRiC-R305
RiC-R307 Agent isassociatedwith Activity isassociatedwith(RiC-R521)
SeealsoRiC-R310
RiC-R308 Agent performed Activity wasperformedby(RiC-R524)
SeealsoRiC-R309
RiC-R309 Agent performs Activity isperformedby(RiC-R522)
SeealsoRiC-R308
RiC-R310 Agent wasassociatedwith Activity wasassociatedwith(RiC-R523)
SeealsoRiC-R307
RiC-R311 Agent isassociatedwith Mandate isassociatedwith(RiC-R573)
SeealsoRiC-R312
RiC-R312 Agent wasassociatedwith Mandate wasassociatedwith(RiC-R574)
SeealsoRiC-R311
RiC-R313 Agent wasauthorizedby Mandate authorized(RiC-R572)
RiC-R314 Agent isassociatedwith DocumentaryForm isassociatedwith(RiC-R622)
SeealsoRiC-R315
RiC-R315 Agent wasassociatedwith DocumentaryForm wasassociatedwith(RiC-R623)
SeealsoRiC-R314
RiC-R316 Agent hadactivedate Date wasactivedateof(RiC-R657)
SeealsoRiC-R321
RiC-R317 Agent(oftypeperson)
hadbirthdate Date wasbirthdateof(RiC-R659)
RiC-R318
Agent(oftypeperson)
haddeathdate Date wasdeathdateof(RiC-R660)
RiC-CMConsultationDraftv0.1 September2016 60
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R319 Agent(oftypegroup)
hadenddate Date wasenddateof(RiC-R661)
SeealsoRiC-R322
RiC-R320 Agent(oftypegroup)
hadstartdate Date wasstartdateof(RiC-R662)
RiC-R321 Agent hasactivedate Date isactivedateof(RiC-R654)
SeealsoRiC-R316
RiC-R322 Agent(oftypegroup)
hasenddate Date isenddateof(RiC-R656) SeealsoRiC-R319
RiC-R323 Agent isassociatedwith Date isassociatedwith(RiC-R655)
SeealsoRiC-R324
RiC-R324 Agent wasassociatedwith Date wasassociatedwith(RiC-R658)
SeealsoRiC-R323
RiC-R325 Agent(oftypeperson)
hadbirthplace Place wasbirthplaceof(RiC-R730)
RiC-R326 Agent(oftypeperson)
haddeathplace Place wasdeathplaceof(RiC-R731)
RiC-R327 Agent isassociatedwith Place isassociatedwith(RiC-R727)
SeealsoRiC-R330
RiC-R328 Agent(oftypeperson)
iscitizenof Place hascitizen(RiC-R726) SeealsoRiC-R331
RiC-R329 Agent islocatedat Place islocationof(RiC-R728) SeealsoRiC-R332
RiC-R330 Agent wasassociatedwith Place wasassociatedwith(RiC-R729)
SeealsoRiC-R327
RiC-R331 Agent(oftypeperson)
wascitizenof Place hadcitizen(RiC-R725) SeealsoRiC-R328
RiC-R332 Agent waslocatedat Place waslocationof(RiC-R732)
SeealsoRiC-R329
RiC-R333
Agent isassociatedwith Concept/Thing isassociatedwith(RiC-R771)
SeealsoRiC-R334
RiC-CMConsultationDraftv0.1 September2016 61
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R334 Agent wasassociatedwith Concept/Thing wasassociatedwith(RiC-R772)
SeealsoRiC-R333
4.1.5.OccupationRelations
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R335 Occupation isassociatedwith Record isassociatedwith(RiC-R37)
SeealsoRiC-R338
RiC-R336 Occupation issubjectof Record hassubject(RiC-R36)
RiC-R337 Occupation resultedin Record resultedfrom(RiC-R38)
RiC-R338 Occupation wasassociatedwith Record wasassociatedwith(RiC-R39)
SeealsoRiC-R335
RiC-R339 Occupation isassociatedwith RecordComponent isassociatedwith(RiC-R98)
SeealsoRiC-R342
RiC-R340 Occupation issubjectof RecordComponent hassubject(RiC-R97)
RiC-R341 Occupation resultedin RecordComponent resultedfrom(RiC-R99)
RiC-R342 Occupation wasassociatedwith RecordComponent wasassociatedwith(RiC-R100)
SeealsoRiC-R339
RiC-R343 Occupation isassociatedwith RecordSet isassociatedwith(RiC-R167)
SeealsoRiC-R346
RiC-R344 Occupation issubjectof RecordSet hassubject(RiC-R166)
RiC-R345 Occupation resultedin RecordSet resultedfrom(RiC-R168)
RiC-R346 Occupation wasassociatedwith RecordSet wasassociatedwith(RiC-R169)
SeealsoRiC-R343
RiC-CMConsultationDraftv0.1 September2016 62
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R347 Occupation isassociatedwith Agent isassociatedwith(RiC-R292)
SeealsoRiC-R349
RiC-R348 Occupation ispursuedby Agent pursues(RiC-R294) SeealsoRiC-R350
RiC-R349 Occupation wasassociatedwith Agent wasassociatedwith(RiC-R295)
SeealsoRiC-R347
RiC-R350 Occupation waspursuedby Agent pursued(RiC-R293) SeealsoRiC-R348
RiC-R351 Occupation isassociatedwith Occupation isassociatedwith(RiC-R351)
SeealsoRiC-R354
RiC-R352 Occupation ispredecessorof Occupation issuccessorof(RiC-R353)
RiC-R353 Occupation issuccessorof Occupation ispredecessorof(RiC-R352)
RiC-R354 Occupation wasassociatedwith Occupation wasassociatedwith(RiC-R354)
SeealsoRiC-R351
RiC-R355 Occupation isassociatedwith Position isassociatedwith(RiC-R392)
SeealsoRiC-R357
RiC-R356 Occupation isrequiredcompetencyof
Position requirescompetency(RiC-R394)
SeealsoRiC-R358
RiC-R357 Occupation wasassociatedwith Position wasassociatedwith(RiC-R395)
SeealsoRiC-R355
RiC-R358 Occupation wasrequiredcompetencyof
Position requiredcompetency(RiC-R393)
SeealsoRiC-R356
RiC-R359 Occupation isassociatedwith Function isassociatedwith(RiC-R440)
SeealsoRiC-R360
RiC-R360 Occupation wasassociatedwith Function wasassociatedwith(RiC-R441)
SeealsoRiC-R359
RiC-R361 Occupation isassociatedwith Function(Abstract) isassociatedwith(RiC-R488)
SeealsoRiC-R362
RiC-CMConsultationDraftv0.1 September2016 63
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R362 Occupation wasassociatedwith Function(Abstract) wasassociatedwith(RiC-R489)
SeealsoRiC-R361
RiC-R363 Occupation isassociatedwith Activity isassociatedwith(RiC-R525)
SeealsoRiC-R364
RiC-R364 Occupation wasassociatedwith Activity wasassociatedwith(RiC-R526)
SeealsoRiC-R363
RiC-R365 Occupation isassociatedwith Mandate isassociatedwith(RiC-R575)
SeealsoRiC-R366
RiC-R366 Occupation wasassociatedwith Mandate wasassociatedwith(RiC-R576)
SeealsoRiC-R365
RiC-R367 Occupation isassociatedwith DocumentaryForm isassociatedwith(RiC-R624)
SeealsoRiC-R368
RiC-R368 Occupation wasassociatedwith DocumentaryForm wasassociatedwith(RiC-R625)
SeealsoRiC-R367
RiC-R369 Occupation isassociatedwith Date isassociatedwith(RiC-R663)
SeealsoRiC-R370
RiC-R370 Occupation wasassociatedwith Date wasassociatedwith(RiC-R664)
SeealsoRiC-R369
RiC-R371 Occupation isassociatedwith Place isassociatedwith(RiC-R733)
SeealsoRiC-R372
RiC-R372 Occupation wasassociatedwith Place wasassociatedwith(RiC-R734)
SeealsoRiC-R371
RiC-R373 Occupation isassociatedwith Concept/Thing isassociatedwith(RiC-R773)
SeealsoRiC-R374
RiC-R374 Occupation wasassociatedwith Concept/Thing wasassociatedwith(RiC-R774)
SeealsoRiC-R373
RiC-CMConsultationDraftv0.1 September2016 64
4.1.6.PositionRelations
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R375 Position isassociatedwith Record isassociatedwith(RiC-R41) SeealsoRiC-R378
RiC-R376 Position issubjectof Record hassubject(RiC-R40)
RiC-R377 Position resultedin Record resultedfrom(RiC-R42)
RiC-R378 Position wasassociatedwith Record wasassociatedwith(RiC-R43)
SeealsoRiC-R375
RiC-R379 Position isassociatedwith RecordComponent isassociatedwith(RiC-R102)
SeealsoRiC-R382
RiC-R380 Position issubjectof RecordComponent hassubject(RiC-R101)
RiC-R381 Position resultedin RecordComponent resultedfrom(RiC-R103)
RiC-R382 Position wasassociatedwith RecordComponent wasassociatedwith(RiC-R104)
SeealsoRiC-R379
RiC-R383 Position isassociatedwith RecordSet isassociatedwith(RiC-R171)
SeealsoRiC-R386
RiC-R384 Position issubjectof RecordSet hassubject(RiC-R170)
RiC-R385 Position resultedin RecordSet resultedfrom(RiC-R172)
RiC-R386 Position wasassociatedwith RecordSet wasassociatedwith(RiC-R173)
SeealsoRiC-R383
RiC-R387 Position isassociatedwith Agent isassociatedwith(RiC-R297)
SeealsoRiC-R389
RiC-R388
Position isoccupiedby Agent(oftypeperson)
occupies(RiC-R299) SeealsoRiC-R391
RiC-R389 Position wasassociatedwith Agent wasassociatedwith(RiC-R300)
SeealsoRiC-R387
RiC-R390 Position wasestablishedby Agent(oftypegroup)
established(RiC-R296)
RiC-CMConsultationDraftv0.1 September2016 65
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R391 Position wasoccupiedby Agent(oftypeperson)
occupied(RiC-R298) SeealsoRiC-R388
RiC-R392 Position isassociatedwith Occupation isassociatedwith(RiC-R355)
SeealsoRiC-R395
RiC-R393 Position requiredcompetency
Occupation wasrequiredcompetencyof(RiC-R358)
SeealsoRiC-R394
RiC-R394 Position requirescompetency
Occupation isrequiredcompetencyof(RiC-R356)
SeealsoRiC-R393
RiC-R395 Position wasassociatedwith Occupation wasassociatedwith(RiC-R357)
SeealsoRiC-R392
RiC-R396 Position isassociatedwith Position isassociatedwith(RiC-R396)
SeealsoRiC-R399
RiC-R397 Position ispredecessorof Position issuccessorof(RiC-R398)
RiC-R398 Position issuccessorof Position ispredecessorof(RiC-R397)
RiC-R399 Position wasassociatedwith Position wasassociatedwith(RiC-R399)
SeealsoRiC-R396
RiC-R400 Position isassociatedwith Function isassociatedwith(RiC-R442)
SeealsoRiC-R401
RiC-R401 Position wasassociatedwith Function wasassociatedwith(RiC-R443)
SeealsoRiC-R400
RiC-R402 Position isassociatedwith Function(Abstract) isassociatedwith(RiC-R490)
SeealsoRiC-R403
RiC-R403 Position wasassociatedwith Function(Abstract) wasassociatedwith(RiC-R491)
SeealsoRiC-R402
RiC-R404 Position isassociatedwith Activity isassociatedwith(RiC-R527)
SeealsoRiC-R405
RiC-R405
Position wasassociatedwith Activity wasassociatedwith(RiC-R528)
SeealsoRiC-R404
RiC-CMConsultationDraftv0.1 September2016 66
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R406 Position isassociatedwith Mandate isassociatedwith(RiC-R579)
SeealsoRiC-R408
RiC-R407 Position isdefinedby Mandate defines(RiC-R578) SeealsoRiC-R409
RiC-R408 Position wasassociatedwith Mandate wasassociatedwith(RiC-R581)
SeealsoRiC-R406
RiC-R409 Position wasdefinedby Mandate defined(RiC-R577) SeealsoRiC-R407
RiC-R410 Position wasrevisedby Mandate revised(RiC-R580)
RiC-R411 Position isassociatedwith DocumentaryForm isassociatedwith(RiC-R626)
SeealsoRiC-R412
RiC-R412 Position wasassociatedwith DocumentaryForm wasassociatedwith(RiC-R627)
SeealsoRiC-R411
RiC-R413 Position hadenddate Date wasenddateof(RiC-R668) SeealsoRiC-R415
RiC-R414 Position hadstartdate Date wasstartdateof(RiC-R669)
RiC-R415 Position hasenddate Date isenddateof(RiC-R666) SeealsoRiC-R413
RiC-R416 Position isassociatedwith Date isassociatedwith(RiC-R665)
SeealsoRiC-R417
RiC-R417 Position wasassociatedwith Date wasassociatedwith(RiC-R667)
SeealsoRiC-R416
RiC-R418 Position isassociatedwith Place isassociatedwith(RiC-R735)
SeealsoRiC-R420
RiC-R419 Position islocatedin Place islocationof(RiC-R736) SeealsoRiC-R421
RiC-R420 Position wasassociatedwith Place wasassociatedwith(RiC-R737)
SeealsoRiC-R418
RiC-R421 Position waslocatedin Place waslocationof(RiC-R738) SeealsoRiC-R419
RiC-R422 Position isassociatedwith Concept/Thing isassociatedwith(RiC-R775)
SeealsoRiC-R423
RiC-R423 Position wasassociatedwith Concept/Thing wasassociatedwith(RiC-R776)
SeealsoRiC-R422
RiC-CMConsultationDraftv0.1 September2016 67
4.1.7.FunctionRelations
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R424 Function isassociatedwith Record isassociatedwith(RiC-R45)
SeealsoRiC-R427
RiC-R425 Function isevidencedby Record isevidenceof(RiC-R46)
RiC-R426 Function issubjectof Record hassubject(RiC-R44)
RiC-R427 Function wasassociatedwith Record wasassociatedwith(RiC-R47)
SeealsoRiC-R424
RiC-R428 Function isassociatedwith RecordComponent isassociatedwith(RiC-R106)
SeealsoRiC-R431
RiC-R429 Function isevidencedby RecordComponent isevidenceof(RiC-R107)
RiC-R430 Function issubjectof RecordComponent hassubject(RiC-R105)
RiC-R431 Function wasassociatedwith RecordComponent wasassociatedwith(RiC-R108)
SeealsoRiC-R428
RiC-R432 Function isassociatedwith RecordSet isassociatedwith(RiC-R175)
SeealsoRiC-R435
RiC-R433 Function isevidencedby RecordSet isevidenceof(RiC-R176)
RiC-R434 Function issubjectof RecordSet hassubject(RiC-R174)
RiC-R435 Function wasassociatedwith RecordSet wasassociatedwith(RiC-R177)
SeealsoRiC-R432
RiC-R436 Function isassociatedwith Agent isassociatedwith(RiC-R303)
SeealsoRiC-R438
RiC-R437 Function isfulfilledby Agent fulfils(RiC-R302) SeealsoRiC-R439
RiC-R438 Function wasassociatedwith Agent wasassociatedwith(RiC-R304)
SeealsoRiC-R436
RiC-R439 Function wasfulfilledby Agent fulfilled(RiC-R301) SeealsoRiC-R437
RiC-R440 Function isassociatedwith Occupation isassociatedwith(RiC-R359)
SeealsoRiC-R441
RiC-CMConsultationDraftv0.1 September2016 68
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R441 Function wasassociatedwith Occupation wasassociatedwith(RiC-R360)
SeealsoRiC-R440
RiC-R442 Function isassociatedwith Position isassociatedwith(RiC-R400)
SeealsoRiC-R443
RiC-R443 Function wasassociatedwith Position wasassociatedwith(RiC-R401)
SeealsoRiC-R442
RiC-R444 Function hadpart Function waspartof(RiC-R451) SeealsoRiC-R445
RiC-R445 Function haspart Function ispartof(RiC-R447) SeealsoRiC-R444
RiC-R446 Function isassociatedwith Function isassociatedwith(RiC-R446)
SeealsoRiC-R450
RiC-R447 Function ispartof Function haspart(RiC-R445) SeealsoRiC-R451
RiC-R448 Function ispredecessorof Function issuccessorof(RiC-R449)
RiC-R449 Function issuccessorof Function ispredecessorof(RiC-R448)
RiC-R450 Function wasassociatedwith Function wasassociatedwith(RiC-R450)
SeealsoRiC-R446
RiC-R451 Function waspartof Function hadpart(RiC-R444) SeealsoRiC-R447
RiC-R452 Function isassociatedwith Function(Abstract) isassociatedwith(RiC-R493)
SeealsoRiC-R454
RiC-R453 Function isexampleof Function(Abstract) hasexample(RiC-R492)
RiC-R454 Function wasassociatedwith Function(Abstract) wasassociatedwith(RiC-R494)
SeealsoRiC-R452
RiC-R455 Function isassociatedwith Activity isassociatedwith(RiC-R529)
SeealsoRiC-R457
RiC-R456 Function isfulfilledbyperformanceof
Activity isperformedtofulfil(RiC-R530)
SeealsoRiC-R458
RiC-R457 Function wasassociatedwith Activity wasassociatedwith(RiC-R531)
SeealsoRiC-R455
RiC-CMConsultationDraftv0.1 September2016 69
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R458 Function wasfulfilledbyperformanceof
Activity wasperformedtofulfill(RiC-R532)
SeealsoRiC-R456
RiC-R459 Function isassociatedwith Mandate isassociatedwith(RiC-R584)
SeealsoRiC-R461
RiC-R460 Function isdefinedby Mandate defines(RiC-R583) SeealsoRiC-R462
RiC-R461 Function wasassociatedwith Mandate wasassociatedwith(RiC-R586)
SeealsoRiC-R459
RiC-R462 Function wasdefinedby Mandate defined(RiC-R582) SeealsoRiC-R460
RiC-R463 Function wasrevisedby Mandate revised(RiC-R585)
RiC-R464 Function isassociatedwith DocumentaryForm isassociatedwith(RiC-R628)
SeealsoRiC-R465
RiC-R465 Function wasassociatedwith DocumentaryForm wasassociatedwith(RiC-R629)
SeealsoRiC-R464
RiC-R466 Function hadactivedate Date wasactivedateof(RiC-R673)
SeealsoRiC-R469
RiC-R467 Function hadenddate Date wasenddateof(RiC-R675)
SeealsoRiC-R470
RiC-R468 Function hadstartdate Date wasstartdateof(RiC-R676)
RiC-R469 Function hasactivedate Date isactivedateof(RiC-R670)
SeealsoRiC-R466
RiC-R470 Function hasenddate Date isenddateof(RiC-R672) SeealsoRiC-R467
RiC-R471 Function isassociatedwith Date isassociatedwith(RiC-R671)
SeealsoRiC-R472
RiC-R472 Function wasassociatedwith Date wasassociatedwith(RiC-R674)
SeealsoRiC-R471
RiC-R473 Function isassociatedwith Place isassociatedwith(RiC-R739)
SeealsoRiC-R474
RiC-CMConsultationDraftv0.1 September2016 70
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R474 Function wasassociatedwith Place wasassociatedwith(RiC-R740)
SeealsoRiC-R473
RiC-R475 Function isassociatedwith Concept/Thing isassociatedwith(RiC-R777)
SeealsoRiC-R476
RiC-R476 Function wasassociatedwith Concept/Thing wasassociatedwith(RiC-R778)
SeealsoRiC-R475
4.1.8.Function(Abstract)Relations
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R477 Function(Abstract)
isassociatedwith Record isassociatedwith(RiC-R49)
SeealsoRiC-R479
RiC-R478 Function(Abstract)
issubjectof Record hassubject(RiC-R48)
RiC-R479 Function(Abstract)
wasassociatedwith Record wasassociatedwith(RiC-R50)
SeealsoRiC-R477
RiC-R480 Function(Abstract)
isassociatedwith RecordComponent isassociatedwith(RiC-R110)
SeealsoRiC-R482
RiC-R481 Function(Abstract)
issubjectof RecordComponent hassubject(RiC-R109)
RiC-R482 Function(Abstract)
wasassociatedwith RecordComponent wasassociatedwith(RiC-R111)
SeealsoRiC-R480
RiC-R483 Function(Abstract)
isassociatedwith RecordSet isassociatedwith(RiC-R179)
SeealsoRiC-R485
RiC-R484 Function(Abstract)
issubjectof RecordSet hassubject(RiC-R178)
RiC-R485 Function(Abstract)
wasassociatedwith RecordSet wasassociatedwith(RiC-R180)
SeealsoRiC-R483
RiC-CMConsultationDraftv0.1 September2016 71
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R486 Function(Abstract)
isassociatedwith Agent isassociatedwith(RiC-R305)
SeealsoRiC-R487
RiC-R487 Function(Abstract)
wasassociatedwith Agent wasassociatedwith(RiC-R306)
SeealsoRiC-R486
RiC-R488 Function(Abstract)
isassociatedwith Occupation isassociatedwith(RiC-R361)
SeealsoRiC-R489
RiC-R489 Function(Abstract)
wasassociatedwith Occupation wasassociatedwith(RiC-R362)
SeealsoRiC-R488
RiC-R490 Function(Abstract)
isassociatedwith Position isassociatedwith(RiC-R402)
SeealsoRiC-R491
RiC-R491 Function(Abstract)
wasassociatedwith Position wasassociatedwith(RiC-R403)
SeealsoRiC-R490
RiC-R492 Function(Abstract)
hasexample Function isexampleof(RiC-R453)
RiC-R493 Function(Abstract)
isassociatedwith Function isassociatedwith(RiC-R452)
SeealsoRiC-R494
RiC-R494 Function(Abstract)
wasassociatedwith Function wasassociatedwith(RiC-R454)
SeealsoRiC-R493
RiC-R495 Function(Abstract)
isassociatedwith Function(Abstract) isassociatedwith(RiC-R495)
SeealsoRiC-R496
RiC-R496 Function(Abstract)
wasassociatedwith Function(Abstract) wasassociatedwith(RiC-R496)
SeealsoRiC-R495
RiC-R497 Function(Abstract)
isassociatedwith Activity isassociatedwith(RiC-R533)
SeealsoRiC-R498
RiC-R498 Function(Abstract)
wasassociatedwith Activity wasassociatedwith(RiC-R534)
SeealsoRiC-R497
RiC-R499 Function(Abstract)
isassociatedwith Mandate isassociatedwith(RiC-R587)
SeealsoRiC-R500
RiC-R500 Function(Abstract)
wasassociatedwith Mandate wasassociatedwith(RiC-R588)
SeealsoRiC-R499
RiC-CMConsultationDraftv0.1 September2016 72
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R501 Function(Abstract)
isassociatedwith DocumentaryForm isassociatedwith(RiC-R630)
SeealsoRiC-R502
RiC-R502 Function(Abstract)
wasassociatedwith DocumentaryForm wasassociatedwith(RiC-R631)
SeealsoRiC-R501
RiC-R503 Function(Abstract)
isassociatedwith Date isassociatedwith(RiC-R677)
SeealsoRiC-R504
RiC-R504 Function(Abstract)
wasassociatedwith Date wasassociatedwith(RiC-R678)
SeealsoRiC-R503
RiC-R505 Function(Abstract)
isassociatedwith Place isassociatedwith(RiC-R741)
SeealsoRiC-R506
RiC-R506 Function(Abstract)
wasassociatedwith Place wasassociatedwith(RiC-R742)
SeealsoRiC-R505
RiC-R507 Function(Abstract)
isassociatedwith Concept/Thing isassociatedwith(RiC-R779)
SeealsoRiC-R508
RiC-R508 Function(Abstract)
wasassociatedwith Concept/Thing wasassociatedwith(RiC-R780)
SeealsoRiC-R507
4.1.9.ActivityRelations
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R509 Activity isassociatedwith Record isassociatedwith(RiC-R52)
SeealsoRiC-R512
RiC-R510 Activity issubjectof Record hassubject(RiC-R51)
RiC-R511 Activity resultedin Record resultedfrom(RiC-R53)
RiC-R512 Activity wasassociatedwith Record wasassociatedwith(RiC-R54)
SeealsoRiC-R509
RiC-R513 Activity isassociatedwith RecordComponent isassociatedwith(RiC-R113)
SeealsoRiC-R516
RiC-R514 Activity issubjectof RecordComponent hassubject(RiC-R112)
RiC-CMConsultationDraftv0.1 September2016 73
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R515 Activity resultedin RecordComponent resultedfrom(RiC-R114)
RiC-R516 Activity wasassociatedwith RecordComponent wasassociatedwith(RiC-R115)
SeealsoRiC-R513
RiC-R517 Activity isassociatedwith RecordSet isassociatedwith(RiC-R182)
SeealsoRiC-R520
RiC-R518 Activity issubjectof RecordSet hassubject(RiC-R181)
RiC-R519 Activity resultedin RecordSet resultedfrom(RiC-R183)
RiC-R520 Activity wasassociatedwith RecordSet wasassociatedwith(RiC-R184)
SeealsoRiC-R517
RiC-R521 Activity isassociatedwith Agent isassociatedwith(RiC-R307)
SeealsoRiC-R523
RiC-R522 Activity isperformedby Agent performs(RiC-R309) SeealsoRiC-R524
RiC-R523 Activity wasassociatedwith Agent wasassociatedwith(RiC-R310)
SeealsoRiC-R521
RiC-R524 Activity wasperformedby Agent performed(RiC-R308) SeealsoRiC-R522
RiC-R525 Activity isassociatedwith Occupation isassociatedwith(RiC-R363)
SeealsoRiC-R526
RiC-R526 Activity wasassociatedwith Occupation wasassociatedwith(RiC-R364)
SeealsoRiC-R525
RiC-R527 Activity isassociatedwith Position isassociatedwith(RiC-R404)
SeealsoRiC-R528
RiC-R528 Activity wasassociatedwith Position wasassociatedwith(RiC-R405)
SeealsoRiC-R527
RiC-R529 Activity isassociatedwith Function isassociatedwith(RiC-R455)
SeealsoRiC-R531
RiC-R530 Activity isperformedtofulfil Function isfulfilledbyperformanceof(RiC-R456)
SeealsoRiC-R532
RiC-CMConsultationDraftv0.1 September2016 74
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R531 Activity wasassociatedwith Function wasassociatedwith(RiC-R457)
SeealsoRiC-R529
RiC-R532 Activity wasperformedtofulfill Function wasfulfilledbyperformanceof(RiC-R458)
SeealsoRiC-R530
RiC-R533 Activity isassociatedwith Function(Abstract) isassociatedwith(RiC-R497)
SeealsoRiC-R534
RiC-R534 Activity wasassociatedwith Function(Abstract) wasassociatedwith(RiC-R498)
SeealsoRiC-R533
RiC-R535 Activity hadpart Activity waspartof(RiC-R542) SeealsoRiC-R536
RiC-R536 Activity haspart Activity ispartof(RiC-R538) SeealsoRiC-R535
RiC-R537 Activity isassociatedwith Activity isassociatedwith(RiC-R537)
SeealsoRiC-R541
RiC-R538 Activity ispartof Activity haspart(RiC-R536) SeealsoRiC-R542
RiC-R539
Activity ispredecessorof Activity issuccessorof(RiC-R540)
RiC-R540 Activity issuccessorof Activity ispredecessorof(RiC-R539)
RiC-R541 Activity wasassociatedwith Activity wasassociatedwith(RiC-R541)
SeealsoRiC-R537
RiC-R542 Activity waspartof Activity hadpart(RiC-R535) SeealsoRiC-R538
RiC-R543 Activity isassociatedwith Mandate isassociatedwith(RiC-R591)
SeealsoRiC-R545
RiC-R544 Activity isdefinedby Mandate defines(RiC-R590) SeealsoRiC-R546
RiC-R545 Activity wasassociatedwith Mandate wasassociatedwith(RiC-R593)
SeealsoRiC-R543
RiC-R546 Activity wasdefinedby Mandate defined(RiC-R589) SeealsoRiC-R544
RiC-R547 Activity wasrevisedby Mandate revised(RiC-R592)
RiC-CMConsultationDraftv0.1 September2016 75
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R548 Activity isassociatedwith DocumentaryForm isassociatedwith(RiC-R632)
SeealsoRiC-R549
RiC-R549 Activity wasassociatedwith DocumentaryForm wasassociatedwith(RiC-R633)
SeealsoRiC-R548
RiC-R550 Activity hadactivedate Date wasactivedateof(RiC-R682)
SeealsoRiC-R553
RiC-R551 Activity hadenddate Date wasenddateof(RiC-R684)
SeealsoRiC-R554
RiC-R552 Activity hadstartdate Date wasstartdateof(RiC-R685)
RiC-R553 Activity hasactivedate Date isactivedateof(RiC-R679)
SeealsoRiC-R550
RiC-R554 Activity hasenddate Date isenddateof(RiC-R681) SeealsoRiC-R551
RiC-R555 Activity isassociatedwith Date isassociatedwith(RiC-R680)
SeealsoRiC-R556
RiC-R556 Activity wasassociatedwith Date wasassociatedwith(RiC-R683)
SeealsoRiC-R555
RiC-R557
Activity isassociatedwith Place isassociatedwith(RiC-R743)
SeealsoRiC-R558
RiC-R558 Activity wasassociatedwith Place wasassociatedwith(RiC-R744)
SeealsoRiC-R557
RiC-R559 Activity isassociatedwith Concept/Thing isassociatedwith(RiC-R781)
SeealsoRiC-R560
RiC-R560 Activity wasassociatedwith Concept/Thing wasassociatedwith(RiC-R782)
SeealsoRiC-R559
RiC-CMConsultationDraftv0.1 September2016 76
4.1.10.MandateRelations
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R561 Mandate isassociatedwith Record isassociatedwith(RiC-R56) SeealsoRiC-R564
RiC-R562 Mandate isevidencedby Record isevidenceof(RiC-R57)
RiC-R563 Mandate issubjectof Record hassubject(RiC-R55)
RiC-R564 Mandate wasassociatedwith Record wasassociatedwith(RiC-R58)
SeealsoRiC-R561
RiC-R565 Mandate isassociatedwith RecordComponent isassociatedwith(RiC-R117) SeealsoRiC-R567
RiC-R566 Mandate issubjectof RecordComponent hassubject(RiC-R116)
RiC-R567 Mandate wasassociatedwith RecordComponent wasassociatedwith(RiC-R118)
SeealsoRiC-R565
RiC-R568 Mandate isassociatedwith RecordSet isassociatedwith(RiC-R186) SeealsoRiC-R571
RiC-R569 Mandate isevidencedby RecordSet isevidenceof(RiC-R187)
RiC-R570 Mandate issubjectof RecordSet hassubject(RiC-R185)
RiC-R571 Mandate wasassociatedwith RecordSet wasassociatedwith(RiC-R188)
SeealsoRiC-R568
RiC-R572 Mandate authorized Agent wasauthorizedby(RiC-R313)
RiC-R573 Mandate isassociatedwith Agent isassociatedwith(RiC-R311) SeealsoRiC-R574
RiC-R574 Mandate wasassociatedwith Agent wasassociatedwith(RiC-R312)
SeealsoRiC-R573
RiC-R575 Mandate isassociatedwith Occupation isassociatedwith(RiC-R365) SeealsoRiC-R576
RiC-R576 Mandate wasassociatedwith Occupation wasassociatedwith(RiC-R366)
SeealsoRiC-R575
RiC-R577 Mandate defined Position wasdefinedby(RiC-R409) SeealsoRiC-R578
RiC-R578 Mandate defines Position isdefinedby(RiC-R407) SeealsoRiC-R577
RiC-R579 Mandate isassociatedwith Position isassociatedwith(RiC-R406) SeealsoRiC-R581
RiC-CMConsultationDraftv0.1 September2016 77
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R580 Mandate revised Position wasrevisedby(RiC-R410)
RiC-R581 Mandate wasassociatedwith Position wasassociatedwith(RiC-R408)
SeealsoRiC-R579
RiC-R582 Mandate defined Function wasdefinedby(RiC-R462) SeealsoRiC-R583
RiC-R583 Mandate defines Function isdefinedby(RiC-R460) SeealsoRiC-R582
RiC-R584 Mandate isassociatedwith Function isassociatedwith(RiC-R459) SeealsoRiC-R586
RiC-R585 Mandate revised Function wasrevisedby(RiC-R463)
RiC-R586 Mandate wasassociatedwith Function wasassociatedwith(RiC-R461)
SeealsoRiC-R584
RiC-R587 Mandate isassociatedwith Function(Abstract) isassociatedwith(RiC-R499) SeealsoRiC-R588
RiC-R588 Mandate wasassociatedwith Function(Abstract) wasassociatedwith(RiC-R500)
SeealsoRiC-R587
RiC-R589 Mandate defined Activity wasdefinedby(RiC-R546) SeealsoRiC-R590
RiC-R590 Mandate defines Activity isdefinedby(RiC-R544) SeealsoRiC-R589
RiC-R591 Mandate isassociatedwith Activity isassociatedwith(RiC-R543) SeealsoRiC-R593
RiC-R592 Mandate revised Activity wasrevisedby(RiC-R547)
RiC-R593 Mandate wasassociatedwith Activity wasassociatedwith(RiC-R545)
SeealsoRiC-R591
RiC-R594 Mandate isassociatedwith Mandate isassociatedwith(RiC-R594) SeealsoRiC-R597
RiC-R595 Mandate ispredecessorof Mandate issuccessorof(RiC-R596)
RiC-R596 Mandate issuccessorof Mandate ispredecessorof(RiC-R595)
RiC-R597 Mandate wasassociatedwith Mandate wasassociatedwith(RiC-R597)
SeealsoRiC-R594
RiC-R598 Mandate isassociatedwith DocumentaryForm isassociatedwith(RiC-R634) SeealsoRiC-R599
RiC-R599 Mandate wasassociatedwith DocumentaryForm wasassociatedwith(RiC-R635)
SeealsoRiC-R598
RiC-CMConsultationDraftv0.1 September2016 78
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R600 Mandate hadactivedate Date wasactivedateof(RiC-R689)
SeealsoRiC-R604
RiC-R601 Mandate hadenddate Date wasenddateof(RiC-R691) SeealsoRiC-R605
RiC-R602 Mandate hadrevisiondate Date wasrevisiondateof(RiC-R692)
RiC-R603 Mandate hadstartdate Date wasstartdateof(RiC-R693)
RiC-R604 Mandate hasactivedate Date isactivedateof(RiC-R686) SeealsoRiC-R600
RiC-R605 Mandate hasenddate Date isenddateof(RiC-R688) SeealsoRiC-R601
RiC-R606 Mandate isassociatedwith Date isassociatedwith(RiC-R687) SeealsoRiC-R607
RiC-R607 Mandate wasassociatedwith Date wasassociatedwith(RiC-R690)
SeealsoRiC-R606
RiC-R608 Mandate hadjurisdiction Place wasjurisdictionof(RiC-R748)
SeealsoRiC-R609
RiC-R609 Mandate hasjurisdiction Place isjurisdictionof(RiC-R746) SeealsoRiC-R608
RiC-R610 Mandate isassociatedwith Place isassociatedwith(RiC-R745) SeealsoRiC-R611
RiC-R611 Mandate wasassociatedwith Place wasassociatedwith(RiC-R747)
SeealsoRiC-R610
RiC-R612 Mandate isassociatedwith Concept/Thing isassociatedwith(RiC-R783) SeealsoRiC-R613
RiC-R613 Mandate wasassociatedwith Concept/Thing wasassociatedwith(RiC-R784)
SeealsoRiC-R612
4.1.11.DocumentaryFormRelations
RelationNumber
RelationDomain RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R614 DocumentaryForm isassociatedwith Record isassociatedwith(RiC-R60)
SeealsoRiC-R616
RiC-CMConsultationDraftv0.1 September2016 79
RelationNumber
RelationDomain RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R615 DocumentaryForm isdocumentaryformof
Record hasdocumentaryform(RiC-R59)
RiC-R616 DocumentaryForm wasassociatedwith Record wasassociatedwith(RiC-R61)
SeealsoRiC-R614
RiC-R617 DocumentaryForm isassociatedwith RecordComponent isassociatedwith(RiC-R120)
SeealsoRiC-R619
RiC-R618 DocumentaryForm isdocumentaryformof
RecordComponent hasdocumentaryform(RiC-R119)
RiC-R619 DocumentaryForm wasassociatedwith RecordComponent wasassociatedwith(RiC-R121)
SeealsoRiC-R617
RiC-R620 DocumentaryForm isassociatedwith RecordSet isassociatedwith(RiC-R189)
SeealsoRiC-R621
RiC-R621 DocumentaryForm wasassociatedwith RecordSet wasassociatedwith(RiC-R190)
SeealsoRiC-R620
RiC-R622 DocumentaryForm isassociatedwith Agent isassociatedwith(RiC-R314)
SeealsoRiC-R623
RiC-R623 DocumentaryForm wasassociatedwith Agent wasassociatedwith(RiC-R315)
SeealsoRiC-R622
RiC-R624 DocumentaryForm isassociatedwith Occupation isassociatedwith(RiC-R367)
SeealsoRiC-R625
RiC-R625 DocumentaryForm wasassociatedwith Occupation wasassociatedwith(RiC-R368)
SeealsoRiC-R624
RiC-R626 DocumentaryForm isassociatedwith Position isassociatedwith(RiC-R411)
SeealsoRiC-R627
RiC-R627 DocumentaryForm wasassociatedwith Position wasassociatedwith(RiC-R412)
SeealsoRiC-R626
RiC-R628 DocumentaryForm isassociatedwith Function isassociatedwith(RiC-R464)
SeealsoRiC-R629
RiC-R629 DocumentaryForm wasassociatedwith Function wasassociatedwith(RiC-R465)
SeealsoRiC-R628
RiC-CMConsultationDraftv0.1 September2016 80
RelationNumber
RelationDomain RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R630 DocumentaryForm isassociatedwith Function(Abstract) isassociatedwith(RiC-R501)
SeealsoRiC-R631
RiC-R631 DocumentaryForm wasassociatedwith Function(Abstract) wasassociatedwith(RiC-R502)
SeealsoRiC-R630
RiC-R632 DocumentaryForm isassociatedwith Activity isassociatedwith(RiC-R548)
SeealsoRiC-R633
RiC-R633 DocumentaryForm wasassociatedwith Activity wasassociatedwith(RiC-R549)
SeealsoRiC-R632
RiC-R634 DocumentaryForm isassociatedwith Mandate isassociatedwith(RiC-R598)
SeealsoRiC-R635
RiC-R635 DocumentaryForm wasassociatedwith Mandate wasassociatedwith(RiC-R599)
SeealsoRiC-R634
RiC-R636 DocumentaryForm isassociatedwith DocumentaryForm isassociatedwith(RiC-R636)
SeealsoRiC-R637
RiC-R637 DocumentaryForm wasassociatedwith DocumentaryForm wasassociatedwith(RiC-R637)
SeealsoRiC-R636
RiC-R638 DocumentaryForm isassociatedwith Date isassociatedwith(RiC-R694)
SeealsoRiC-R639
RiC-R639 DocumentaryForm wasassociatedwith Date wasassociatedwith(RiC-R695)
SeealsoRiC-R638
RiC-R640 DocumentaryForm isassociatedwith Place isassociatedwith(RiC-R749)
SeealsoRiC-R641
RiC-R641 DocumentaryForm wasassociatedwith Place wasassociatedwith(RiC-R750)
SeealsoRiC-R640
RiC-R642 DocumentaryForm isassociatedwith Concept/Thing isassociatedwith(RiC-R785)
SeealsoRiC-R643
RiC-R643 DocumentaryForm wasassociatedwith Concept/Thing wasassociatedwith(RiC-R786)
SeealsoRiC-R642
RiC-CMConsultationDraftv0.1 September2016 81
4.1.12.DateRelations
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R644 Date isassociatedwith Record isassociatedwith(RiC-R63)
SeealsoRiC-R645
RiC-R645 Date wasassociatedwith Record wasassociatedwith(RiC-R64)
SeealsoRiC-R644
RiC-R646 Date wascreationdateof Record hadcreationdate(RiC-R62)
RiC-R647 Date isassociatedwith RecordComponent isassociatedwith(RiC-R123)
SeealsoRiC-R648
RiC-R648 Date wasassociatedwith RecordComponent wasassociatedwith(RiC-R124)
SeealsoRiC-R647
RiC-R649 Date wascreationdateof RecordComponent hadcreationdate(RiC-R122)
RiC-R650 Date isassociatedwith RecordSet isassociatedwith(RiC-R193)
SeealsoRiC-R652
RiC-R651 Date iscoveragedateof RecordSet hascoveragedate(RiC-R192)
RiC-R652 Date wasassociatedwith RecordSet wasassociatedwith(RiC-R194)
SeealsoRiC-R650
RiC-R653 Date wascreationdateof RecordSet hadcreationdate(RiC-R191)
RiC-R654 Date isactivedateof Agent hasactivedate(RiC-R321) SeealsoRiC-R657
RiC-R655 Date isassociatedwith Agent isassociatedwith(RiC-R323)
SeealsoRiC-R658
RiC-R656 Date isenddateof Agent(oftypegroup) hasenddate(RiC-R322) SeealsoRiC-R661
RiC-R657
Date wasactivedateof Agent hadactivedate(RiC-R316)
SeealsoRiC-R654
RiC-CMConsultationDraftv0.1 September2016 82
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R658 Date wasassociatedwith Agent wasassociatedwith(RiC-R324)
SeealsoRiC-R655
RiC-R659 Date wasbirthdateof Agent(oftypeperson) hadbirthdate(RiC-R317)
RiC-R660 Date wasdeathdateof Agent(oftypeperson) haddeathdate(RiC-R318)
RiC-R661 Date wasenddateof Agent(oftypegroup) hadenddate(RiC-R319) SeealsoRiC-R656
RiC-R662 Date wasstartdateof Agent(oftypegroup) hadstartdate(RiC-R320)
RiC-R663 Date isassociatedwith Occupation isassociatedwith(RiC-R369)
SeealsoRiC-R664
RiC-R664 Date wasassociatedwith Occupation wasassociatedwith(RiC-R370)
SeealsoRiC-R663
RiC-R665 Date isassociatedwith Position isassociatedwith(RiC-R416)
SeealsoRiC-R667
RiC-R666 Date isenddateof Position hasenddate(RiC-R415) SeealsoRiC-R668
RiC-R667 Date wasassociatedwith Position wasassociatedwith(RiC-R417)
SeealsoRiC-R665
RiC-R668 Date wasenddateof Position hadenddate(RiC-R413) SeealsoRiC-R666
RiC-R669 Date wasstartdateof Position hadstartdate(RiC-R414)
RiC-R670 Date isactivedateof Function hasactivedate(RiC-R469) SeealsoRiC-R673
RiC-R671 Date isassociatedwith Function isassociatedwith(RiC-R471)
SeealsoRiC-R674
RiC-R672 Date isenddateof Function hasenddate(RiC-R470) SeealsoRiC-R675
RiC-R673 Date wasactivedateof Function hadactivedate(RiC-R466)
SeealsoRiC-R670
RiC-R674 Date wasassociatedwith Function wasassociatedwith(RiC-R472)
SeealsoRiC-R671
RiC-R675 Date wasenddateof Function hadenddate(RiC-R467) SeealsoRiC-R672
RiC-R676 Date wasstartdateof Function hadstartdate(RiC-R468)
RiC-CMConsultationDraftv0.1 September2016 83
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R677 Date isassociatedwith Function(Abstract) isassociatedwith(RiC-R503)
SeealsoRiC-R678
RiC-R678 Date wasassociatedwith Function(Abstract) wasassociatedwith(RiC-R504)
SeealsoRiC-R677
RiC-R679 Date isactivedateof Activity hasactivedate(RiC-R553) SeealsoRiC-R682
RiC-R680 Date isassociatedwith Activity isassociatedwith(RiC-R555)
SeealsoRiC-R683
RiC-R681 Date isenddateof Activity hasenddate(RiC-R554) SeealsoRiC-R684
RiC-R682 Date wasactivedateof Activity hadactivedate(RiC-R550)
SeealsoRiC-R679
RiC-R683 Date wasassociatedwith Activity wasassociatedwith(RiC-R556)
SeealsoRiC-R680
RiC-R684 Date wasenddateof Activity hadenddate(RiC-R551) SeealsoRiC-R681
RiC-R685 Date wasstartdateof Activity hadstartdate(RiC-R552)
RiC-R686 Date isactivedateof Mandate hasactivedate(RiC-R604) SeealsoRiC-R689
RiC-R687 Date isassociatedwith Mandate isassociatedwith(RiC-R606)
SeealsoRiC-R690
RiC-R688 Date isenddateof Mandate hasenddate(RiC-R605) SeealsoRiC-R691
RiC-R689 Date wasactivedateof Mandate hadactivedate(RiC-R600)
SeealsoRiC-R686
RiC-R690 Date wasassociatedwith Mandate wasassociatedwith(RiC-R607)
SeealsoRiC-R687
RiC-R691 Date wasenddateof Mandate hadenddate(RiC-R601) SeealsoRiC-R688
RiC-R692 Date wasrevisiondateof Mandate hadrevisiondate(RiC-R602)
RiC-R693 Date wasstartdateof Mandate hadstartdate(RiC-R603)
RiC-R694 Date isassociatedwith DocumentaryForm isassociatedwith(RiC-R638)
SeealsoRiC-R695
RiC-CMConsultationDraftv0.1 September2016 84
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R695 Date wasassociatedwith DocumentaryForm wasassociatedwith(RiC-R639)
SeealsoRiC-R694
RiC-R696 Date isassociatedwith Date isassociatedwith(RiC-R696)
SeealsoRiC-R697
RiC-R697 Date wasassociatedwith Date wasassociatedwith(RiC-R697)
SeealsoRiC-R696
RiC-R698 Date isactivedateof Place hasactivedate(RiC-R754) SeealsoRiC-R701
RiC-R699 Date isassociatedwith Place isassociatedwith(RiC-R756)
SeealsoRiC-R702
RiC-R700 Date isenddateof Place hasenddate(RiC-R755) SeealsoRiC-R703
RiC-R701 Date wasactivedateof Place hadactivedate(RiC-R751)
SeealsoRiC-R698
RiC-R702 Date wasassociatedwith Place wasassociatedwith(RiC-R757)
SeealsoRiC-R699
RiC-R703 Date wasenddateof Place hadenddate(RiC-R752) SeealsoRiC-R700
RiC-R704 Date wasstartdateof Place hadstartdate(RiC-R753)
RiC-R705 Date isassociatedwith Concept/Thing isassociatedwith(RiC-R787)
SeealsoRiC-R706
RiC-R706 Date wasassociatedwith Concept/Thing wasassociatedwith(RiC-R788)
SeealsoRiC-R705
4.2.13.PlaceRelations
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R707 Place isassociatedwith Record isassociatedwith(RiC-R68)
SeealsoRiC-R710
RiC-R708 Place isholdinglocationof Record hasholdinglocation(RiC-R66)
SeealsoRiC-R712
RiC-CMConsultationDraftv0.1 September2016 85
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R709 Place issubjectof Record hassubject(RiC-R67)
RiC-R710 Place wasassociatedwith Record wasassociatedwith(RiC-R69)
SeealsoRiC-R707
RiC-R711 Place wascreationlocationof Record wascreatedat(RiC-R70)
RiC-R712 Place washoldinglocationof Record hadholdinglocation(RiC-R65)
SeealsoRiC-R708
RiC-R713 Place isassociatedwith RecordComponent isassociatedwith(RiC-R128)
SeealsoRiC-R716
RiC-R714 Place isholdinglocationof RecordComponent hasholdinglocation(RiC-R126)
SeealsoRiC-R718
RiC-R715 Place issubjectof RecordComponent hassubject(RiC-R127)
RiC-R716 Place wasassociatedwith RecordComponent wasassociatedwith(RiC-R129)
SeealsoRiC-R713
RiC-R717 Place wascreationlocationof RecordComponent wascreatedat(RiC-R130)
RiC-R718 Place washoldinglocationof RecordComponent hadholdinglocation(RiC-R125)
SeealsoRiC-R714
RiC-R719 Place isassociatedwith RecordSet isassociatedwith(RiC-R198)
SeealsoRiC-R722
RiC-R720 Place isholdingplaceof RecordSet hasholdinglocation(RiC-R196)
SeealsoRiC-R724
RiC-R721 Place issubjectof RecordSet hassubject(RiC-R197)
RiC-R722 Place wasassociatedwith RecordSet wasassociatedwith(RiC-R199)
SeealsoRiC-R719
RiC-R723
Place wascreationplaceof RecordSet wascreatedat(RiC-R200)
RiC-CMConsultationDraftv0.1 September2016 86
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R724 Place washoldingplaceof RecordSet hadholdinglocation(RiC-R195)
SeealsoRiC-R720
RiC-R725 Place hadcitizen Agent(oftypeperson) wascitizenof(RiC-R331)
SeealsoRiC-R726
RiC-R726 Place hascitizen Agent(oftypeperson) iscitizenof(RiC-R328)
SeealsoRiC-R725
RiC-R727 Place isassociatedwith Agent isassociatedwith(RiC-R327)
SeealsoRiC-R729
RiC-R728 Place islocationof Agent islocatedat(RiC-R329)
SeealsoRiC-R732
RiC-R729 Place wasassociatedwith Agent wasassociatedwith(RiC-R330)
SeealsoRiC-R727
RiC-R730 Place wasbirthplaceof Agent(oftypeperson) hadbirthplace(RiC-R325)
RiC-R731 Place wasdeathplaceof Agent(oftypeperson) haddeathplace(RiC-R326)
RiC-R732 Place waslocationof Agent waslocatedat(RiC-R332)
SeealsoRiC-R728
RiC-R733 Place isassociatedwith Occupation isassociatedwith(RiC-R371)
SeealsoRiC-R734
RiC-R734 Place wasassociatedwith Occupation wasassociatedwith(RiC-R372)
SeealsoRiC-R733
RiC-R735 Place isassociatedwith Position isassociatedwith(RiC-R418)
SeealsoRiC-R737
RiC-R736 Place islocationof Position islocatedin(RiC-R419)
SeealsoRiC-R738
RiC-R737 Place wasassociatedwith Position wasassociatedwith(RiC-R420)
SeealsoRiC-R735
RiC-R738 Place waslocationof Position waslocatedin(RiC-R421)
SeealsoRiC-R736
RiC-CMConsultationDraftv0.1 September2016 87
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R739 Place isassociatedwith Function isassociatedwith(RiC-R473)
SeealsoRiC-R740
RiC-R740 Place wasassociatedwith Function wasassociatedwith(RiC-R474)
SeealsoRiC-R739
RiC-R741 Place isassociatedwith Function(Abstract) isassociatedwith(RiC-R505)
SeealsoRiC-R742
RiC-R742 Place wasassociatedwith Function(Abstract) wasassociatedwith(RiC-R506)
SeealsoRiC-R741
RiC-R743 Place isassociatedwith Activity isassociatedwith(RiC-R557)
SeealsoRiC-R744
RiC-R744 Place wasassociatedwith Activity wasassociatedwith(RiC-R558)
SeealsoRiC-R743
RiC-R745 Place isassociatedwith Mandate isassociatedwith(RiC-R610)
SeealsoRiC-R747
RiC-R746 Place isjurisdictionof Mandate hasjurisdiction(RiC-R609)
SeealsoRiC-R748
RiC-R747 Place wasassociatedwith Mandate wasassociatedwith(RiC-R611)
SeealsoRiC-R745
RiC-R748 Place wasjurisdictionof Mandate hadjurisdiction(RiC-R608)
SeealsoRiC-R746
RiC-R749 Place isassociatedwith DocumentaryForm isassociatedwith(RiC-R640)
SeealsoRiC-R750
RiC-R750 Place wasassociatedwith DocumentaryForm wasassociatedwith(RiC-R641)
SeealsoRiC-R749
RiC-R751 Place hadactivedate Date wasactivedateof(RiC-R701)
SeealsoRiC-R754
RiC-R752 Place hadenddate Date wasenddateof(RiC-R703)
SeealsoRiC-R755
RiC-R753 Place hadstartdate Date wasstartdateof(RiC-R704)
RiC-CMConsultationDraftv0.1 September2016 88
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R754 Place hasactivedate Date isactivedateof(RiC-R698)
SeealsoRiC-R751
RiC-R755 Place hasenddate Date isenddateof(RiC-R700)
SeealsoRiC-R752
RiC-R756 Place isassociatedwith Date isassociatedwith(RiC-R699)
SeealsoRiC-R757
RiC-R757 Place wasassociatedwith Date wasassociatedwith(RiC-R702)
SeealsoRiC-R756
RiC-R758 Place isassociatedwith Place isassociatedwith(RiC-R758)
SeealsoRiC-R759
RiC-R759 Place wasassociatedwith Place wasassociatedwith(RiC-R759)
SeealsoRiC-R758
RiC-R760 Place isassociatedwith Concept/Thing isassociatedwith(RiC-R789)
SeealsoRiC-R761
RiC-R761 Place wasassociatedwith Concept/Thing wasassociatedwith(RiC-R790)
SeealsoRiC-R760
4.2.14.Concept/ThingRelations
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R762 Concept/Thing isassociatedwith Record isassociatedwith(RiC-R72)
SeealsoRiC-R764
RiC-R763 Concept/Thing issubjectof Record hassubject(RiC-R71)
RiC-R764 Concept/Thing wasassociatedwith Record wasassociatedwith(RiC-R73)
SeealsoRiC-R762
RiC-R765 Concept/Thing isassociatedwith RecordComponent isassociatedwith(RiC-R132)
SeealsoRiC-R767
RiC-R766 Concept/Thing issubjectof RecordComponent hassubject(RiC-R131)
RiC-CMConsultationDraftv0.1 September2016 89
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R767 Concept/Thing wasassociatedwith RecordComponent wasassociatedwith(RiC-R133)
SeealsoRiC-R765
RiC-R768 Concept/Thing isassociatedwith RecordSet isassociatedwith(RiC-R202)
SeealsoRiC-R770
RiC-R769 Concept/Thing issubjectof RecordSet hassubject(RiC-R201)
RiC-R770 Concept/Thing wasassociatedwith RecordSet wasassociatedwith(RiC-R203)
SeealsoRiC-R768
RiC-R771 Concept/Thing isassociatedwith Agent isassociatedwith(RiC-R333)
SeealsoRiC-R772
RiC-R772 Concept/Thing wasassociatedwith Agent wasassociatedwith(RiC-R334)
SeealsoRiC-R771
RiC-R773 Concept/Thing isassociatedwith Occupation isassociatedwith(RiC-R373)
SeealsoRiC-R774
RiC-R774 Concept/Thing wasassociatedwith Occupation wasassociatedwith(RiC-R374)
SeealsoRiC-R773
RiC-R775 Concept/Thing isassociatedwith Position isassociatedwith(RiC-R422)
SeealsoRiC-R776
RiC-R776 Concept/Thing wasassociatedwith Position wasassociatedwith(RiC-R423)
SeealsoRiC-R775
RiC-R777 Concept/Thing isassociatedwith Function isassociatedwith(RiC-R475)
SeealsoRiC-R778
RiC-R778 Concept/Thing wasassociatedwith Function wasassociatedwith(RiC-R476)
SeealsoRiC-R777
RiC-R779 Concept/Thing isassociatedwith Function(Abstract) isassociatedwith(RiC-R507)
SeealsoRiC-R780
RiC-R780 Concept/Thing wasassociatedwith Function(Abstract) wasassociatedwith(RiC-R508)
SeealsoRiC-R779
RiC-R781 Concept/Thing isassociatedwith Activity isassociatedwith(RiC-R559)
SeealsoRiC-R782
RiC-CMConsultationDraftv0.1 September2016 90
RelationNumber
RelationDomain
RelationName RelationRange InverseRelationNameandNumber
Comments
RiC-R782 Concept/Thing wasassociatedwith Activity wasassociatedwith(RiC-R560)
SeealsoRiC-R781
RiC-R783 Concept/Thing isassociatedwith Mandate isassociatedwith(RiC-R612)
SeealsoRiC-R784
RiC-R784 Concept/Thing wasassociatedwith Mandate wasassociatedwith(RiC-R613)
SeealsoRiC-R783
RiC-R785 Concept/Thing isassociatedwith DocumentaryForm isassociatedwith(RiC-R642)
SeealsoRiC-R786
RiC-R786 Concept/Thing wasassociatedwith DocumentaryForm wasassociatedwith(RiC-R643)
SeealsoRiC-R785
RiC-R787 Concept/Thing isassociatedwith Date isassociatedwith(RiC-R705)
SeealsoRiC-R788
RiC-R788 Concept/Thing wasassociatedwith Date wasassociatedwith(RiC-R706)
SeealsoRiC-R787
RiC-R789 Concept/Thing isassociatedwith Place isassociatedwith(RiC-R760)
SeealsoRiC-R790
RiC-R790 Concept/Thing wasassociatedwith Place wasassociatedwith(RiC-R761)
SeealsoRiC-R789
RiC-R791 Concept/Thing isassociatedwith Concept/Thing isassociatedwith(RiC-R791)
SeealsoRiC-R792
RiC-R792 Concept/Thing wasassociatedwith Concept/Thing wasassociatedwith(RiC-R792)
SeealsoRiC-R791
RiCConsultationDraftv0.1 September2016 91
4.2SharedPropertiesofaRelation# Property DefinitionRiC-P68Date Chronologicalinformationassociatedwiththerelationthat
contributestoitsidentificationandcontextualization.
Scope Ifapplicable,includestheDate(rangeortime)whenthereisarelationbetweentwoentities.Willnotapplytoallrelations.Forexample,willnotapplytorelationstoDate.AdditionalexceptionswillbenotedinfutureRiCreleases.
DataType ISO8601TimeandDateFormat
Examples 1792-08-10;1798-10-30;1720/1780
# Property DefinitionRiC-P69Place Jurisdictionsandnamedgeographicalfeatures.
Scope Includessettlementsofanykind(towns,villages,etc.),historical
regions,politicalandadministrativedistricts,andgeographicalfeatures.Ifapplicable,includesthegeographicaloradministrativepointorarea(e.g.district,country,state)wheretherelationbetweentwoentitiesexists.
DataType ControlledTermorPhrase
Examples AmazonRiver;NovaScotia;Paris
RiCConsultationDraftv0.1 September2016 92
RiCConsultationDraftv0.1 September2016 93
AppendixI:ExampleofArchivalDescriptionConformingtoRiC-CMHereisanillustrativeexampleofarchivaldescriptionconformingtoRiC-CMpresentedasadiagram:
ThisexampleshowssomeinformationaboutP.G.F.Léveau,aFrenchpublicnotaryinthe19thcenturyincluding:• datafromtheArchivesnationalesdeFrance(ANF)(inblue);and• datafromalocalarchivalinstitution,theArchivesdépartementalesduCher(inyellow).
QueryinganddisplayingsuchinterrelateddatamayhelpuserswhowanttoresearchLéveauhimself;orstudythehistoryofthenotariesintheFrenchDepartmentofCherinthe19thcentury;orretrievetherecordscreatedbythenotarieswhoworkedinMehunfrom1820to1840,inwhichmuchinformationaboutthelivesofpeoplewholivedinthatareacanbefound.TheentitiesandrelationsusedaredefinedbyRiC-CM.Whiletherelationsareonlyshowninonedirection,theinverserelationsexist.
RiCConsultationDraftv0.1 September2016 94
RiCConsultationDraftv0.1 September2016 95
AppendixII:ExpertsGrouponArchivalDescriptionMembers
CurrentMembers
NilsBrübach,SächsischesStaatsarchiv(Germany)FlorenceClavaud,Archivesnationales(France)AdrianCunningham,QueenslandStateArchives(Australia)BeatrizFrancoEspiño,MinisteriodeEducación,CulturayDeporte(Spain)MiiaHerrala,Arkistolaitos(Finland)PeteJohnston,ArchivesHub(UnitedKingdom)PadréLydieGnessougouBaroan-Dioumency,DirectionGénéraleduTrésoretdelaComptabilitéPublique(IvoryCoast)GavanMcCarthy,UniversityofMelbourneeScholarshipResearchCentre(Australia)VitorManoelMarquesdaFonseca,ArquivoNacional/UniversidadeFederalFluminense(Brazil)VictoriaPeters,UniversityofStrathclyde(UnitedKingdom)DanielPitti(Chair/Président),UniversityofVirginiaInstituteforAdvancedTechnologyintheHumanities(UnitedStates)Bogdan-FlorinPopovici,ArhiveleNaţionalealeRomâniei(Romania)JavierE.RequejoZalama,MinisteriodeEducación,CulturayDeporte(Spain)StéphanieRoussel,ServiceinterministérieldesArchivesdeFrance(France)AaronRubinstein,UniversityofMassachusettsAmherst(UnitedStates)BillStockting,RoyalArchivesandLibrary(UnitedKingdom)MartinStuerzlinger,Archiversum(Austria)KatherineTimms,LibraryandArchivesCanada/BibliothèqueetArchivesCanada(Canada)SalvatoreVassallo,ArchivumRomanumSocietatisIesu(Italy)StefanoVitali,IstitutoCentralepergliArchivi(Italy)PastMembers
JaanaKilkki,NationalArchives(Finland)AliceMotte,ArchivesdépartementalesdesLandes(France)ClaireSibille,ServiceinterministérieldesArchivesdeFrance(France)
RiCConsultationDraftv0.1 September2016 96
RiCConsultationDraftv0.1 September2016 97
AppendixII:Bibliography1.StandardsandModels
ICAStandards
ISAAR(CPF):InternationalStandardArchivalAuthorityRecordforCorporateBodies,PersonsandFamilies,2ndEdition.(2011)(en),ISAAR(CPF):NormeInternationalesurlesnoticesd’autoritéutiliséespourlesArchivesrelativesauxcollectivités,auxpersonnesouauxfamilles,2èmeédition(fr)
ISAD(G):GeneralInternationalStandardArchivalDescription-Secondedition.(2011).ISAD(G):GeneralInternationalStandardArchivalDescription-Secondedition(en),ISAD(G):Normegénéraleetinternationalededescriptionarchivistique-Deuxièmeédition(fr)
ISDF:InternationalStandardforDescribingFunctions.(2011).ISDF:InternationalStandardforDescribingFunctions(en),ISDF:Normeinternationalepourladescriptiondesfonctions(fr)
ISDIAH:InternationalStandardforDescribingInstitutionswithArchivalHoldings.(2011).ISDIAH:InternationalStandardforDescribingInstitutionswithArchivalHoldings(en),ISDIAH:Normeinternationalepourladescriptiondesinstitutionsdeconservationdesarchives(fr)
ArchivalandRecordKeepingConceptualModels
ArchivesNewZealand.TS:TechnicalSpecificationsforElectronicRecordkeepingMetadataStandard.http://archives.govt.nz/ts-technical-specifications-electronic-recordkeeping-metadata-standard(en)
AS/NZSISO5478RecordkeepingMetadataPropertyReferenceSet(RMPRS).
CNEDA.Modeloconceptualdedescripciónarchivísticayrequisitosdedatosbásicosdelasdescripcionesdedocumentosdearchivo,agentesyfunciones.2012.http://www.mcu.es/archivos/docs/NEDA_MCDA_P1_P2_20120618.pdf(es)
⎯⎯⎯⎯⎯.ReportontheworkofCNEDA(2007-2012):towardaconceptualmodelforarchivaldescriptioninSpain(July11,2012).2012.http://www.mcu.es/archivos/docs/MC/CNEDA/ReportCNEDA_11_07_2012.pdf(en)
DLMForum.MoReq2010:ModularRequirementsforRecordsSystems.2016.http://moreq.info/
e-GMS-e-GovernmentMetadataStandardVersion3.029April2004.https://www.oasis-open.org/committees/download.php/7271/eGMS%20version%203.pdf(en)
International Council on Archives and Australasian Digital Records Initiative. Principles and FunctionalRequirements for Records in Electronic Office Environments, Modules 1-3, 2008, published athttp://www.ica.org.(AlsoadoptedasISO16175:2010/2011)
ISO15489:2016–Informationanddocumentation–Recordsmanagement–Part1:General.
ISO23081:2006–Informationanddocumentation–Recordsmanagementprocesses–Metadataforrecords.
Kilkki,Jaana,OutiHupaniittu,andPekkaHenttonen.Towardstheneweraofarchivaldescription-theFinnishApproach.2012.http://www.arkisto.fi/uploads/Arkistolaitos/Teht%C3%A4v%C3%A4t%20ja%20toiminta/Hankkeet/AHAA/The%20Finnish%20Conceptual%20Model%20of%20Archival%20Description_text.pdf(en)
RiCConsultationDraftv0.1 September2016 98
NationalArchivesofAustralia.AustralianGovernmentRecordkeepingMetadataStandard.Version2.2.2015.http://www.naa.gov.au/Images/AGRkMS-Version-2.2-June-2015_tcm16-47131.pdf(en)
SPIRTResearchTeam.AustralianRecordkeepingMetadataSchema.Version1.0.2000.http://www.infotech.monash.edu.au/research/groups/rcrg/projects/spirt/deliverables/rkmsgen-tech-intro.pdf(en)
ArchivalDescriptiveContentStandards
CanadianCouncilofArchives.RulesforArchivalDescription(RAD).Revisedversion.2008.http://www.cdncouncilarchives.ca/RAD/RADComplete_July2008.pdf(en);http://www.cdncouncilarchives.ca/RAD/RDDAComplete_July2008.pdf(fr)
SocietyofAmericanArchivists.DescribingArchives:AContentStandard(DACS).2nded.2013.http://files.archivists.org/pubs/DACS-2007.pdf
ArchivalCommunicationStandards
EncodedArchivalContext-CorporateBodies,Persons,andFamilies(EAC-CPF).http://eac.staatsbibliothek-berlin.de/index.php(en);http://www.archivesdefrance.culture.gouv.fr/gerer/classement/normes-outils/eac/(fr)
EncodedArchivalDescription(EAD).VersionEAD31.0.Schema:https://github.com/SAA-SDT/EAD3/releases/tag/v1.0.0;TagLibrary:http://www.loc.gov/ead/EAD3taglib/index.html
RelatedConceptualModelsandStandards
CIDOCConceptualReferenceModel.Version6.2.2.2016.http://www.cidoc-crm.org/official_release_cidoc.html(en);http://www.cidoc-crm.org/docs/crm_french_version.pdf(fr);officialISOstandardversion:21127:2006Informationanddocumentation–Areferenceontologyfortheinterchangeofculturalheritageinformation.http://www.iso.org/iso/catalogue_detail?csnumber=34424
Europeana.EuropeanaDataModelDocumentation.[2016].http://pro.europeana.eu/page/edm-documentation(en)
IFLA.FunctionalRequirementsforBibliographicRecords.2008.http://www.ifla.org/files/assets/cataloguing/frbr/frbr_2008.pdf(en)http://www.bnf.fr/documents/frbr_rapport_final.pdf(fr)
IFLAWorkingGrouponFRBR/CRM.DraftdefinitionofFRBRoo.http://archive.ifla.org/VII/s13/wgfrbr/FRBRoo_V9.1_PR.pdf(en).
LODE:AnontologyforLinkingOpenDescriptionsofEvents.http://linkedevents.org/ontology/(en)
W3CProv[provenance].http://www.w3.org/TR/2013/WD-prov-overview-20130312/2.ArchivalProfessionalLiterature
Altman,B.,andJ.R.Nemmers.2001.“TheUsabilityofOnlineArchivalResources:ThePolarisProjectFindingAid.”
RiCConsultationDraftv0.1 September2016 99
AmericanArchivist64(1):121-131.
AustralianSocietyofArchivists.2007.DescribingArchivesinContext:AGuidetoAustralasianPractice.Dickson:AustralianSocietyofArchivists.
AustralianSocietyofArchivists,PeterJ.Scott,andAdrianCunningham.2010.TheArrangementandDescriptionofArchivesAmidAdministrativeandTechnologicalChange:EssaysandReflectionsbyandAboutPeterJ.Scott.
Bailey,Jefferson.2013.“DisrespectdesFonds:RethinkingArrangementandDescriptioninBorn-DigitalArchives.”ArchiveJournal3.http://www.archivejournal.net/issue/3/archives-remixed/disrespect-des-fonds-rethinking-arrangement-and-description-in-born-digital-archives/
Barr,Debra.1987-1988.“TheFondsConceptintheWorkingGrouponArchivalDescriptiveStandardsReport.”Archivaria25:163-170.
⎯⎯⎯⎯⎯.1989.“Protectingprovenance:ResponsetotheReportoftheWorkingGrouponDescriptionattheFondsLevel.Archivaria28:141-145.
BartlettNancy.1991.“RespectdesFonds:TheOriginsoftheModernPrincipleofProvenance.”InBibliographicFoundationsofFrenchHistoricalStudies.Vol.1(1-2)ofPrimarySourcesandOriginalWorks.NewYork:HaworthPress.
Bastian,JeanetteAllis.2003-2004.“Ina‘HouseofMemory’:DiscoveringtheProvenanceofPlace.”ArchivalIssues28:9-19.
⎯⎯⎯⎯⎯.2006.“ReadingColonialRecordsthroughanArchivalLens:TheProvenanceofPlace,SpaceandCreation.”ArchivalScience6:267-284.
Bearman,David.1989.ArchivalMethods.Pittsburgh:ArchivesandMuseumInformatics.
⎯⎯⎯⎯⎯.1992.“DocumentingDocumentation.”Archivaria34:33-49.
⎯⎯⎯⎯⎯.1996.“ItemLevelControlandElectronicRecordkeeping.”ArchivesandMuseumInformatics10:195-245.
Bearman,David,andR.H.Lytle.1985-1986.“ThePowerofthePrincipleofProvenance.”Archivaria21:14-27.
Beattie,Heather.2009.“WhereNarrativesMeet:ArchivalDescription,Provenance,andWomen’sDiaries.”PapersfromtheThirdInternationalConferenceontheHistoryofRecordsandArchives.LibrariesandtheCulturalRecord44(1):82-100.
BergerStefan.2013."TheroleofnationalarchivesinconstructingnationalmasternarrativesinEurope",ArchivalScience,13,1:1-22.
Blouin,Jr.,Francis,andWilliamRosenberg.2013.ProcessingthePast.ContestingAuthorityinHistoryandtheArchives.Oxford:OxfordUniversityPress.
Boles,Frank.1982.“DisrespectingOriginalOrder.”AmericanArchivist45(1):26-32.
BoutierRobertHenry,1968."Laphasecrucialedel'histoiredesarchives:laconstitutiondesdépotsd'archivesetlanaissancedel'archivistique(XVI-débutduXIXsiècle).",ArchivumXVIII:139-149.
BrennekeAdolf.1953.Archivkunde.EinBeitragzurThéorieundGeschichtedesEuropäischenArchivwesens,Leipzig:
RiCConsultationDraftv0.1 September2016 100
KœhlerundAmelang.
Brothman,Brien.1991.“OrdersofValue:ProbingtheTheoreticalTermsofArchivalPractice.”Archivaria32:78-100.
⎯⎯⎯⎯⎯.1999.“DecliningDerrida:Integrity,Tensegrity,andthePreservationofArchivesfromDeconstruction.”Archivaria48:64-88.
Bruebach,Nils.2003.“ArchivalScienceinGermany–Traditions,DevelopmentsandPerspectives.”ArchivalScience3:379–399
CookMichael.1993.InformationManagementandArchivalData.London:LibraryAssociationPublishing.
⎯⎯⎯⎯⎯.1996.“TheInternationalDescriptiveStandards:NewDepartures.”Archivi&Computer6:259-266.
Cook,Terry.1992.“TheConceptoftheArchivalFonds:Theory,Description,andProvenanceinthePost-CustodialEra.”InTheArchivalFonds:FromTheorytoPractice,ed.T.Eastwood.Ottawa:BureauofCanadianArchivists.
⎯⎯⎯⎯⎯.1993.“What’sPastisPrologue:AHistoryofArchivalIdeassince1898,andtheFutureParadigmShift.”Archivaria43:17-63.
⎯⎯⎯⎯⎯.2001a.“ArchivalScienceandPostmodernism:NewFormulationsforOldConcepts.”ArchivalScience1:3-24.
⎯⎯⎯⎯⎯.2001b.“FashionableNonsenseorProfessionalRebirth:PostmodernismandthePracticeofArchives.”Archivaria51:14-35.
⎯⎯⎯⎯⎯.2006.“RememberingtheFuture:AppraisalofRecordsandtheRoleofArchivesinConstructingSocialMemory.”InArchives,Documentation,andInstitutionsofSocialMemory:EssaysfromtheSawyerSeminar,ed.F.X.BlouinandW.G.Rosenberg.AnnArbor:UniversityofMichiganPress.
CottaIreneandMannoToluRosaliaeds.1968.Archiviestorianell'EuropadelXIXsecolo:alleradicidell'identitàculturaleeuropea,Roma:MinisteroperiBenieleAttivitàculturali,Direzionegeneralepergliarchivi,2006.
Cox,R.J.2004.NoInnocentDeposits:FormingArchivesbyRethinkingAppraisal.Lanham:ScarecrowPress.
Cunningham,Adrian.2000a.“RecentDevelopmentsinStandardsforArchivalDescriptionandMetadata.”IASAJournal16:14-24.
⎯⎯⎯⎯⎯.2001b.“SixDegreesofSeparation:AustralianMetadataInitiativesandtheirRelationshipswithInternationalStandards.”ArchivalScience1:271-283.
⎯⎯⎯⎯⎯.2012.“PeterJ.ScottandtheAustralian‘Series’System:ItsOrigins,Features,Rationale,ImpactandContinuingRelevance.”InternationalCongressonArchives,Brisbane,Australia,23August2012.
Cunningham,Adrian,LauraMillar,andBarbaraReed.2013."PeterJ.ScottandtheAustralian‘series’system:itsorigins,features,rationale,impactandcontinuingrelevance."Comma2013(1),pp.121–144.
Davis,S.E.2003.“DescriptiveStandardsandtheArchivalProfession.”CatalogingandClassificationQuarterly35:291-308.
Dodge,Bernadine.2002.“AcrosstheGreatDivide:ArchivalDiscourseandRepresentationsofthePastinLate-
RiCConsultationDraftv0.1 September2016 101
ModernSociety.”Archivaria53:16-30.
Douglas,Jennifer.2007.“DigitizationandtheArchivalRecord.”PaperpresentedattheAnnualMeetingoftheAssociationofCanadianArchivists,Kingston,Ontario.
⎯⎯⎯⎯⎯.2010.“Origins:EvolvingIdeasaboutthePrincipleofProvenance.”InCurrentsofArchivalThinking,byHeatherMacNeilandTerryEastwood.SantaBarbara,CA:LibrariesUnlimited.
Duchein,Michel.1977.“Lerespectdes fondsenarchivistique:Principesthéoriquesetproblèmespratiques.".LaGazettedesArchives97:71-96;
⎯⎯⎯⎯⎯.1983.“TheoreticalPrinciplesandPracticalProblemsofRespectdesFondsinArchivalScience.”Archivaria16:64-82.
Duff,Wendy.M.2001.“EvaluatingMetadataonaMetalevel.”ArchivalScience1:285-294.
Duff,Wendy.M.,andK.M.Haworth.1990/1991.“TheReclamationofArchivalDescription:TheCanadianPerspective.”Archivaria31:26-35.
Duff,Wendy.M.,andP.Stoyanova.1998.“TransformingtheCrazyQuilt:ArchivalDisplaysfromaUsers’PointofView.”Archivaria45:44-79.
Duff,Wendy.M.,andV.Harris.2002.“StoriesandNames:ArchivalDescriptionasNarratingRecordsandConstructingMeanings.”ArchivalScience2:263-285.
Duranti,Luciana.1989."TheOdysseyofRecordsManagers."RecordsManagementQuarterly23,3and4(1989):3-11and3-11.
⎯⎯⎯⎯⎯.1993."OriginandDevelopmentoftheConceptofArchivalDescription,"Archivaria35:47-54.
⎯⎯⎯⎯⎯.1997."TheArchivalBond,"ArchivesandMuseumInformatics11,3-4:213-218.
⎯⎯⎯⎯⎯.1998.Diplomatics:NewUsesforanOldScience.Chicago:SAA,ACAandScarecrowPress.
Duranti,Luciana,FranksPatricia,eds.2015.EncyclopediaofArchivalScience.Lanham,MD:Rowman&LittlefieldPublishingGroup.
Eastwood,Terry.1990.“PuttingthePartsoftheWholeTogether:ASystematicApproachtoAccesstoInformationfromtheArchivesofContemporaryAdministration.”PaperdeliveredataSeminaronArrangementandDescriptionofArchives,Weimar.
⎯⎯⎯⎯⎯.1992.“Generalintroduction.”InTheArchivalFonds:FromTheorytoPractice,ed.T.Eastwoood.Ottawa:BureauofCanadianArchivists.
⎯⎯⎯⎯⎯.2000.“PuttingthePartsoftheWholeTogether:SystematicArrangementofArchives.”Archivaria50:93-116.
Evans,Joanne,S.McKemmish,andK.Bhoday.2005.“CreateOnce,UseManyTimes:TheCleverUseofRecordkeepingMetadataforMultipleArchivalPurposes.”ArchivalScience5(1):17-42.
Evans,Max.J.1986.“AuthorityControl:AnAlternativetotheRecordGroupConcept.”AmericanArchivist49(3):249-261.
⎯⎯⎯⎯⎯.2007.“ArchivesofthePeople,BythePeople,ForthePeople.”AmericanArchivist70(2):387-400.
RiCConsultationDraftv0.1 September2016 102
Fenyo,M.D.1966.“TheRecordGroupConcept:ACritique.”AmericanArchivist29(2):229-239.
Fischer,G.L.1973.“LettingtheArchivalDustSettle:SomeRemarksontheRecordGroupConcept.”JournaloftheSocietyofArchivists4:640-645.
Gilliland,Anne,N.Rouche,L.Lindberg,andJ.Evans.2005.“Towardsa21stCenturyMetadataInfrastructureSupportingtheCreation,PreservationandUseofTrustworthyRecords:DevelopingtheInterPARES2MetadataSchemaRegistry.”ArchivalScience5(1):43-78.
Gilliland-Swetland,Anne.J.2001.“PopularizingtheFindingAid:ExploitingEADtoEnhanceOnlineDiscoveryandRetrievalinArchivalInformationSystemsbyDiverseUserGroups.”InEncodedArchivalDescriptionontheInternet,ed.D.V.PittiandW.M.Duff.NewYork:HaworthPress.
⎯⎯⎯⎯⎯.2000.EnduringParadigm,NewOpportunities:TheValueoftheArchivalPerspectiveintheDigitalEnvironment.Washington,D.C.:CouncilonInformationandLibraryResources.
Greene,Mark.A.,andD.Meissner.2005.“MoreProduct,LessProcess:RevampingTraditionalArchivalProcessing.”AmericanArchivist68(2):208-263.
Gueguen, Gretchen, V. M. Marques da Fonseca, D. Pitti, and C. Sibille-de Grimoüard. 2013. “Toward anInternational Conceptual Model for Archival Description: A Preliminary Report from the InternationalCouncilonArchives'ExpertsGrouponArchivalDescription."TheAmericanArchivist76(2):567-584
GuercioMaria.1993.“ArchivalTheoryandthePrincipleofProvenanceforCurrentRecords:TheirImpactonArrangingandInventoryingElectronicRecords,”inSwedishNationalArchives,ThePrincipleofProvenance:ReportfromtheFirstStockholmConferenceonArchivalTheoryandthePrincipleofProvenance,2–3September1993(Stockholm,1994).
Haworth,K.M.1992.“ThePrinciplesSpeakforThemselves:ArticulatingaLanguageofPurposeforArchives.”InTheArchivalImagination:EssaysinHonourofHughA.Taylor,ed.B.L.Craig.Ottawa:AssociationofCanadianArchivists.
⎯⎯⎯⎯⎯.1993.“TheVoyageofRAD:FromtheOldWorldtotheNew.”Archivaria36:5-12.
⎯⎯⎯⎯⎯.2001.“ArchivalDescription:ContentandContextinSearchofStructure.”InEncodedArchivalDescriptionontheInternet,ed.D.V.PittiandW.M.Duff.NewYork:HaworthPress.
Hedstrom,M.1993.“DescriptivePracticesforElectronicRecords:DecidingwhatisEssentialandImaginingwhatisPossible.”Archivaria36:53-63.
⎯⎯⎯⎯⎯.2002.“Archives,Memory,andInterfaceswiththePast.”ArchivalScience2:21-43.
HensenS. L.1989.PersonalPapers,andManuscripts:ACataloguingManual forArchivalRepositories.HistoricalSocieties,andManuscriptLibraries.Chicago:SocietyofAmericanArchivists.
⎯⎯⎯⎯⎯.2001.“ArchivalCatalogingandtheInternet:TheImplicationsandImpactofEAD.”InEncodedarchivaldescriptionontheinternet,ed.D.V.PittiandW.M.Duff.NewYork:HaworthPress.
Holmes,Oliver.W.1964.“ArchivalArrangement:FiveDifferentOperationsatFiveDifferentLevels.”AmericanArchivist27(1):21-41.
Horsman,Peter.1994.“TamingtheElephant:AnOrthodoxApproachtothePrincipleofProvenance.”InThePrincipleofProvenance:ReportfronttheFirstStockholmConferenceonArchivalTheoryandthePrincipleofProvenance,September2-3,1993,ed.K.AbukhanfusaandJ.Sydbeck.Stockholm:Riksarkivet.
RiCConsultationDraftv0.1 September2016 103
⎯⎯⎯⎯⎯.1999a.“ArchivalDescriptionfromaDistantView.”http://www.asap.unimelb.edu.au/asa/stama/conf/WWKHorsman.htm.
⎯⎯⎯⎯⎯.1999b.“DirtyHands:ANewPerspectiveontheOriginalOrder.”ArchivesandManuscripts27:42-53.
⎯⎯⎯⎯⎯.2002.“TheLastDanceofthePhoenix,orTheDe-discoveryoftheArchivalFonds.”Archivaria54:1-23.
HurleyChris.1994.“TheAustralian‘Series’System:AnExposition.”InTheRecordsContinuum:IanMacleanandAustralianArchivesFirstFiftyYears,ed.S.McKemmishandM.Piggott.Clayton:AncoraPress.
⎯⎯⎯⎯⎯.1995.ProblemswithProvenance.ArchivesandManuscripts23:234-259.
⎯⎯⎯⎯⎯.1995."AmbientFunctions-AbandonedChildrentoZoos."Archivaria40:21-39.
⎯⎯⎯⎯⎯.1996.“BeatingtheFrench,”ArchivesandManuscripts24,1:12-18.
⎯⎯⎯⎯⎯.1998.“TheMakingandtheKeepingofRecords:(1)WhatAreFindingAidsfor?”ArchivesandManuscripts26,1:58-77
⎯⎯⎯⎯⎯.2000.“TheMakingandtheKeepingofRecords:(2)TheTyrannyofListing.”ArchivesandManuscripts28:8-23.
⎯⎯⎯⎯⎯.2002.“RelationshipsinRecords.”InNewZealandArchivistSummer,4:6-9.
⎯⎯⎯⎯⎯.2005.“ParallelProvenance[Seriesofparts]:Part1:What,ifanything,isarchivaldescription?”ArchivesandManuscripts33:110-145.
ICA/CBPS.2012a.“CBPS-ProgressReportforRevisingandHarmonisingICADescriptiveStandards.”http://www.ica.org/en/cbps-progress-report-revising-and-harmonising-ica-descriptive-standards
⎯⎯⎯⎯⎯.2012b.“CBPS-RelationshipsinArchivalDescriptiveSystems.”http://www.ica.org/en/cbps-relationship-archival-descriptive-systems
INTERPARESprojectfindings(1:1998-2001;2:2002-2007;3:2007-2012;4:2013-2018).http://www.interpares.org/
Jenkinson,Hilary.1937.AManualofArchiveAdministrationIncludingtheProblemsofWarArchivesandArchiveMaking.2nded.London:P.Lund,Humphries.
JinfangNiu.2013a.“Provenance:CrossingBoundaries.”ArchivesandManuscripts41:2,105-115.
⎯⎯⎯⎯⎯. 2013b. “Recordkeeping Metadata and Archival Description: A Revisit.” Archives and Manuscripts41(3):203-251.
⎯⎯⎯⎯⎯2015.“OriginalOrderintheDigitalWorld.”ArchivesandManuscripts43:1,61-72
KetelaarEric.2001.“TacitNarratives:TheMeaningofArchives.”ArchivalScience1:131-141.
⎯⎯⎯⎯⎯.2002.“ArchivalTemples,ArchivalPrisons:ModesofPowerandProtection.”ArchivalScience2:221-238
⎯⎯⎯⎯⎯.2005.“Sharing:CollectedMemoriesinCommunitiesofRecords.”ArchivesandManuscripts33:44-61.
Koltun,Lily.1999.“ThePromiseandThreatofDigitalOptionsinanArchivalAge.”Archivaria44:114-135.
Kooyman,S.M.1994.“RADandtheResearcher.”Archivaria37:104-110.
RiCConsultationDraftv0.1 September2016 104
KrauseM.G.andE.Yakel.2007."InteractioninVirtualArchives:ThePolarBearExpeditionDigitalCollectionsNextGenerationFindingAid.”TheAmericanArchivist70(2):282-314.
Krawczyk, Bob. 1999. “Cross Reference Heaven: The Abandonment of the Fonds as the Primary Level ofArrangementforOntarioGovernmentRecords.”Archivaria48:131–153.
Lemieux,Victoria.2001.“LettheGhostsSpeak:AnEmpiricalExplorationofthe‘Nature’oftheRecord.”Archivaria51:81-111.
Light,M.2007.“MovingBeyondtheName:DefiningCorporateEntitiestoSupportProvenance-BasedAccess.”JournalofArchivalOrganization5:49-74.
Light,M.andT.Hyry.2002.“ColophonsandAnnotations:NewDirectionsfortheFindingAid.”AmericanArchivist65(2):216-230.
Livelton,Trevor.1996.ArchivalTheory,RecordsandthePublic.Landham,MI:SocietyofAmericanArchivists.
Lodolini,Elio.2005.Archivistica:Principieproblemi.12thed.Milano:F.Angeli.
Lytle,R.H.1980a.“IntellectualAccesstoArchives:I.ProvenanceandContentIndexingMethodsofSubjectRetrieval.”AmericanArchivist43(1):64-75.
⎯⎯⎯⎯⎯.1980b.“IntellectualAccesstoArchives:II.ReportofanExperimentComparingProvenanceandContentIndexingMethodsofSubjectRetrieval.”AmericanArchivist43(2):191-207.
MacNeil, Heather, 1992. “The Context is All: Describing a Fonds and its Parts in Accordancewith the Rules forArchivalDescription,”inTheArchivalFonds:FromTheorytoPractice,TerryEastwood,ed.Ottawa,BureauofCanadianArchivists,PlanningCommitteeonDescriptiveStandards.
⎯⎯⎯⎯⎯.1995.“MetadataStrategiesandArchivalDescription:ComparingApplestoOranges.”Archivaria39:22-32.
⎯⎯⎯⎯⎯.1996.“TheImplicationsoftheUBCResearchResultsforArchivalDescriptioninGeneralandtheCanadianRulesforArchivalDescriptioninParticular.”Archivi&Computer6:239-246.
⎯⎯⎯⎯⎯.2005.“PickingourText:ArchivalDescription,Authenticity,andtheArchivistasEditor.”AmericanArchivist68(2):265-278.
⎯⎯⎯⎯⎯.2006.“Touchstones:ConsideringtheRelationshipbetweenMemoryandArchives.”Archivaria61:105-126.
⎯⎯⎯⎯⎯.2008.“Archivalterity:RethinkingOriginalOrder.”Archivaria66:1-24.
⎯⎯⎯⎯⎯.2009.“TrustingDescription:Authenticity,Accountability,andArchivalDescriptionStandards.”JournalofArchivalOrganization7:89-107.
Malin,G.2002.“DigitizeThis!TheImpactofDigitalCollectionsonArchivalDescription.”JournalofArchivalOrganization1:65-76.
McKemmish,Sue.1994.“AreRecordsEverActual?”InTheRecordsContinuum:IanMacleanandAustralianArchivesFirstFiftyYears,ed.S.McKemmishandM.Piggott.Clayton:AncoraPress.
⎯⎯⎯⎯⎯.2001.“PlacingRecordsContinuumTheoryandPractice.”ArchivalScience1(4):333-359.
McKemmish,Sue,G.Acland,N.Ward,andB.Reed.1999.“DescribingRecordsinContextintheContinuum:The
RiCConsultationDraftv0.1 September2016 105
AustralianRecordkeepingMetadataSchema.”Archivaria48:3-43.
McKemmish,Sue,andD.Parer.1998.“TowardsFrameworksforStandardisingRecordkeepingMetadata.”ArchivesandManuscripts26:24-45.
McKemmish,Sue,A.Gilliland-Swetland,andE.Ketelaar.2005.“‘CommunitiesofMemory’:PluralisingArchivalResearchandEducationAgendas.”ArchivesandManuscripts33:146-175.
Meehan,Jennifer.2009.“MakingtheLeapfromPartstoWhole:EvidenceandInferenceinArchivalArrangementandDescription.”TheAmericanArchivist,72(1):72-90
⎯⎯⎯⎯⎯.2010.“RethinkingOriginalOrderandPersonalRecords.”Archivaria70:27-44.
Menne-Haritz,A.1994.“AppraisalorSelection:CanaContentOrientedAppraisalbeHarmonizedwiththePrincipleofProvenance?”InThePrincipleofProvenance:ReportfromtheFirstStockholmConferenceonArchivalTheoryandthePrincipleofProvenance,September2-3,1993,ed.K.AbukhanfusaandJ.Sydbeck.Stockholm:Riksarkivet.
Michetti,Giovanni.2012.“ArchivesAreNotTrees.HierarchicalRepresentationsinDigitalEnvironment.”TheMemoryoftheWorldintheDigitalAge:DigitizationandPreservation.AnInternationalConferenceonPermanentAccesstoDigitalDocumentaryHeritage.Vancouver,BritishColumbia,Canada.
Millar,Laura.2002.“TheDeathoftheFondsandtheResurrectionofProvenance:ArchivalContextinSpaceandTime.”Archivaria53:1-15.
⎯⎯⎯⎯⎯.2006.“AnObligationofTrust:SpeculationsonAccountabilityandDescription.”AmericanArchivist69(1):60-78.
Muller,Samuel,J.A.Feith,andR.Fruin.2003.TheManualfortheArrangementandDescriptionofArchives.2nded.,trans.byArthurH.Leavitt.Chicago:SocietyofAmericanArchivists.
NesmithTom.1993a.“Introduction,”inCanadianArchivalStudiesandtheRediscoveryofProvenance,ed.byTomNesmith.Metuchen,NJ:SocietyofAmericanArchivists.
⎯⎯⎯⎯⎯.1993b.“ArchivalStudiesinEnglish-SpeakingCanadaandtheNorthAmericanRediscoveryofProvenance.”InCanadianArchivalStudiesandtheRediscoveryofProvenance,ed.T.Nesmith.Metuchen:ScarecrowPress.
⎯⎯⎯⎯⎯.1999.“StillFuzzybutMoreAccurate:SomeThoughtsonthe‘Ghosts’ofArchivalTheory.”Archivaria47:136-150.
⎯⎯⎯⎯⎯.2002.“SeeingArchives:PostmodernismandtheChangingIntellectualPlaceofArchives.”AmericanArchivist65(1):24-41.
⎯⎯⎯⎯⎯.2005.“ReopeningArchives:BringingNewContextualitiesintoArchivalTheoryandPractice.”Archivaria60:259-274.
⎯⎯⎯⎯⎯.2006.“TheConceptofSocietalProvenanceandRecordsofNineteenth-CenturyAboriginal-EuropeanRelationsinWesternCanada:ImplicationsforArchivalTheoryandPractice.”ArchivalScience6(3-4):351-360.
Nordland,LoriPodolski.2001.“TheConceptof‘Secondaryprovenance’:Re-interpretingAckomokki’sMapasEvolvingText.”Archivaria58:147-159.
Ottosson,P.2006.“AuthorityFileInformationinArchives.”InternationalCataloguingandBibliographicControl
RiCConsultationDraftv0.1 September2016 106
35:57-58.
Peters,V.2005.“DevelopingArchivalContextStandardsforFunctionsintheHigherEducationSector.”JournaloftheSocietyofArchivists26:75-85.
Piggot,Michael.2005a.“Archivesandmemory.”InArchives:Recordkeepinginsociety,ed.bySueMcKemmishandBarbaraReed.WaggaWagga,NSW:CentreforInformationStudies,CharlesSturtUniversity.
⎯⎯⎯⎯⎯.2005b.“BuildingCollectiveMemoryArchives.”ArchivesandManuscripts33:62-83.
Piggott,Michael,andS.McKemmish.2002.Recordkeeping,ReconciliationandPoliticalReality,http://www.sims.monash.edu.au/research/rcrg/publications/piggottmckemmish2002.pdf
Pitti,DanielV.1999.“EncodedArchivalDescription:AnIntroductionandOverview.”D-LibMagazine5(11).http://dlib.org/dlib/november99/11pitti.html
Pitti,DanielV.,andW.M.Duff,eds.2001.EncodedArchivalDescriptionontheInternet.NewYork:HaworthPress.
Pohjola,Raimo.1994.“ThePrincipleofProvenanceandtheArrangementofRecords/Archives.”InThePrincipleofProvenance:ReportfromtheFirstStockholmConferenceontheArchivalPrincipleofProvenance,September2-3,1993.Stockholm:SwedishNationalArchives.
Posner,Ernst.2006a.“MaxLehmannandtheGenesisofthePrincipleofProvenance.”InArchivesandthePublicInterest,ed.byKenMunden.Chicago:SocietyofAmericanArchivists.
⎯⎯⎯⎯⎯.2006b.“SomeAspectsofArchivalDevelopmentsincetheFrenchRevolution.”InArchivesandthePublicInterest,ed.byKenMunden.Chicago:SocietyofAmericanArchivists.
Powell,GraemeT.1976.“ArchivalPrinciplesandtheTreatmentofPersonalPapers.”ArchivesandManuscripts6:259-268.
Procter,M.,andM.Cook.2000.AManualofArchivalDescription,3rded.Aldershot:Gower.
Prom,Chris.2004.“UserInteractionswithElectronicFindingAidsinaControlledSetting.”AmericanArchivist67(2):234-268.
Ricci,IsabellaMassabòandM.Carassi,eds.2000.ScrittidiTeoriaArchivisticaItaliana.RassegnaBibliografica.Roma:Ministeroperibenieleattivitaculturali,UfficiocentraleperIbeniarchivistici.
Roper,M.1992.“TheDevelopmentofthePrinciplesofProvenanceandRespectforOriginalOrderinthePublicRecordOffice.”InTheArchivalImagination:EssaysinHonourofHughA.Taylor,ed.B.L.Craig.Ottawa:AssociationofCanadianArchivists.
Savoja,Maurizio,andVitali,Stefano.2007.“AuthorityControlforCreatorsinItaly:TheoryandPractice.”JournalofArchivalOrganization5:121-147.
Schmandt-Besserat,Denise.1996.HowWritingCameAbout.Austin:UniversityofTexasPress.
Scheir,W.2005.“FirstEntry:ReportonaQualitativeExploratoryStudyofNoviceUserExperiencewithOnlineFindingAids.”JournalofArchivalOrganization3:49-85.
Schellenberg,T.R.1956.ModernArchives:PrinciplesandTechniques.Chicago:UniversityofChicagoPress.
RiCConsultationDraftv0.1 September2016 107
⎯⎯⎯⎯⎯.1965.TheManagementofArchives.NewYork:ColumbiaUniversityPress.
Scott,Peter.J.1966.“TheRecordGroupConcept:ACaseforAbandonment.”AmericanArchivist29(4):493-504.
Scott,PeterJ.,G.Finlay,C.D.Smith,H.Rowell.1978-1981.“ArchivesandAdministrativeChange:SomeMethodsandApproaches”,Part1-5,ArchivesandManuscripts.Part1in7:Vol.7,No.3(August1978),pp.115–127;Part2in7:Vol.7,No.4(April1979),pp.151–165.Part3in7:Vol.8,No.1(June1980),pp.41–54.Part4in7:Vol.8,No.2(December1980),pp.51–69.Part5in7:Vol.9,No.1(September1981),pp.3–18.
Sexton,Anna,andC.Turner.2003.“ExpandingtheRoleofEAD:ProvidingAdequateMetadataforDigitalaswellasOriginalArchiveDocuments.”Vine32(4):71-80.
Stibbe,HugoL.P.1992.“ImplementingtheConceptofFonds:PrimaryAccessPoint,MultilevelDescriptionandAuthorityControl.”Archivaria34:109-137.
⎯⎯⎯⎯⎯.1998.“StandardisingDescription:TheExperienceofUsingISAD(G).”Janus1:132-152.
Sweeney,Shelley.2008.“TheAmbiguousOriginsoftheArchivalPrincipleofProvenance.”LibrariesandtheCulturalRecord43:193-213.
Szary,RichardV.1985.“ExpandingtheRoleofAuthorityFilesintheArchivalContext.”Paperpresentedatsemi-annualmeetingofAnnualMeetingofSocietyofAmericanArchivists,November1,1985.
Tamble,Donato.2001.“ArchivalTheoryinItalyToday.”ArchivalScience1:83-100.
Taylor,HughA.1983.“TheCollectiveMemory:ArchivesandLibrariesasHeritage.”Archivaria15:118-130.
⎯⎯⎯⎯⎯.1995.“’Heritage’Revisited:DocumentsasArtifactsintheContextofMuseumsandMaterialCulture,”Archivaria40:8-20.
SwedishNationalArchives.1993.ThePrincipleofProvenance:ReportfromtheFirstStockholmConferenceontheArchivalPrincipleofProvenance,September2-3,1993.Stockholm.
Thomassen,TheoH.P.M.1999.“TheDevelopmentofArchivalScienceanditsEuropeanDimension.”InTheArchivistandtheArchivalScience:SeminarforAnnaChristinaUlfsparreFebruary10-11,1999attheSwedishNationalArchives.Lund:LandsarkivetsILund.
VanCamp,A.2001.“ProvidingUnifiedAccesstoInternationalPrimaryResourcesintheHumanities.”InEncodedArchivalDescriptionontheInternet,ed.D.V.PittiandW.M.Duff.NewYork:HaworthPress.
Vitali,Stefano.1998.“SurfingwithoutGoingoffCourse:AnArchivalDescriptionSystemfortheInternet.”InElectronicAccess:ArchivesintheNewMillennium,ConferenceProceedingsJune1-4,1998.London:PublicRecordOffice.
⎯⎯⎯⎯⎯.2002.“TheArchiveattheTimeofitsInstitution:TheCentralArchiveofFrancescoBonaini.”InTheFlorenceStateArchive:ThirteenCenturiesofHistoricalRecords,ed.byRosalieMannoTuloandAnnaBellinazzi.Florence:NardiniEditore.
⎯⎯⎯⎯⎯.2006.“WhatAretheBoundariesofArchivalContext?TheSIASFIProjectandtheOnlineGuidetotheFlorenceStateArchives,”JournalofArchivalOrganization,3,2-3:243-260.
⎯⎯⎯⎯⎯.2014.“Ladescrizionearchivisticaaltempodeglistandardedeisistemiinformatici”,inArchivistica.Teorie,metodi,pratiche,MariaGuercioandLindaGiuvaeds.Roma:Carocci:179-210
RiCConsultationDraftv0.1 September2016 108
Wallace,D.1995.“ManagingthePresent:MetadataasArchivalDescription.”Archivaria39:11-21.
Westbrook,B.D.2002.“ProspectingVirtualCollections.”JournalofArchivalOrganization1:73-80.
Wurl,Joel.2005.“EthnicityasProvenance:InSearchofValuesandPrinciplesforDocumentingtheImmigrantExperience.”ArchivalIssues29:65-76.
Yakel,Elizabeth.2003.“ArchivalRepresentation.”ArchivalScience3:1-25.
⎯⎯⎯⎯⎯.2004.“EncodedArchivalDescription:AreFindingAidsBoundarySpannersorBarriersforUsers?”JournalofArchivalOrganization2(1):63-77.
Yeo,Geoffrey.2005.“UnderstandingUsersandUse:AMarketSegmentationApproach.”JournaloftheSocietyofArchivists26:25-53.
⎯⎯⎯⎯⎯.2007.“ConceptsofRecord(1):Evidence,Information,andPersistentRepresentations.”AmericanArchivist70(2):315-43.
⎯⎯⎯⎯⎯.2008.“ConceptsofRecord(2):PrototypesandBoundaryObjects.”AmericanArchivist71(1):118-43.
⎯⎯⎯⎯⎯.2009.“CustodialHistory,Provenance,andtheDescriptionofPersonalRecords.”LibrariesandtheCulturalRecord44(1):50-64.
⎯⎯⎯⎯⎯.2010“DebatesaboutDescription.”InCurrentsofArchivalThinking,ed.byHeatherMacNeilandTerryEastwood.SantaBarbara,CA:LibrariesUnlimited.
⎯⎯⎯⎯⎯.2012.“TheConceptualFondsandthePhysicalCollection.”Archivaria73:43-80.