Introduction
RiC-O (Records in Contexts-Ontology) is an OWL ontology for describing
archival record resources. As the third part of Records in Contexts standard, it
is a formal representation of Records in Contexts Conceptual Model (RiC-CM).
This version, which is v1.0.2, is the latest official release. It is compliant
with RiC-CM v1.0.
The following diagram shows the main RiC-CM 1.0 entities and a few relations
between them:
RiC-O design principles
The following design principles were followed when developing
RiC-O.
1. RiC-O is a domain and reference
ontology.
RiC-O provides a generic vocabulary and formal rules for
creating RDF datasets (or generating them from existing archival
metadata) that describe in a consistent way any kind of archival record
resource. It supports publishing RDF datasets as Linked
Data, querying them using SPARQL, and making inferences using the logic of
the ontology.
While some projects have built some specific ontologies for describing
archives, in 2013 no generic domain ontology existed for the specific needs
of the archival community. This is why EGAD decided to develop RiC-O as a
part of RiC standard.
Apart from this first, main target, RiC-O, as a technical
implementation of RiC-CM that also extends and refines it and that
includes formal logic, can guide or inspire, in many ways, the
development of any tool or system that manages (i.e. stores, enables to
edit or processes) and publishes descriptive archival
metadata.. Of course, other technical implementations of
RiC-CM may be developed later on. Also, the current technical
implementations of the former ICA standards, e.g. EAD and EAC-CPF XML
schemas, should be made closer to RiC-CM in the future; on this topic, see
the news and announcements of the Technical Subcommittee on Encoded
Archival Standards (TS-EAS) of the Society of American
Archivists.
As RiC-O is a generic, domain ontology, it does not address
by itself every specific need or expectation that may
occur in every archival institution or project. It is rather a
high level framework and an institution or project
implementing RiC-O can apply only such a subset of properties as meets their
needs, or extend the specification according to their particular
requirements, or do both.
As a domain ontology, RiC-O, at this stage, does not borrow from other
existing ontologies (such as the cultural heritage models – IFLA-LRM and
CIDOC-CRM, PREMIS, or PROV-O). It should therefore be easier, for an
archival institution or archival project, to understand, implement and
maintain RiC-O within its system.
Alignment with those and other models, where possible, will be
undertaken in a future revision cycle to support the interconnected nature
of resource description across the domains. This is of course essential for
interconnecting RDF datasets conforming to RiC-O with other datasets, or for
using parts of RiC-O in other contexts than the archival or records
management realm.
2. RiC-O is immediately usable.
This is a key feature. Metadata
conforming to superseded ICA standards can be transformed to RiC-O
successfully. Converting existing archival metadata
created or generated in current information systems and compliant with ICA
standards to RDF/RiC-O is possible without losing data or
structure.
During the ongoing development process of RiC-O, intensive conversion
testing, either by hand or using scripts, was conducted on XML/EAD finding
aids and XML/EAC-CPF authority records to ensure that RiC-O is usable with
existing descriptive metadata. An open
source conversion software was also developed and made
available in April 2020.
While some existing metadata sets may have a very fine level of
granularity and accuracy, already using, for example, controlled
vocabularies, or describing curation events separately, often these metadata
don’t have the very precise structure that RiC-CM recommends. Even then,
such a conversion process remains possible. In order to allow this, RiC-O
sometimes provides several methods for representing information (as
described below). From this point of view, RiC-O v1.0 may be considered a
transitional ontology, in which some components may be deprecated later
on.
The usability of a model also depends on its documentation. RiC-O is
documented extensively. The documentation will be reviewed and updated on a
continuing basis.
3. RiC-O provides a flexible framework.
This is a very important principle too. It is
related with the usability principle quoted above. Moreover,
archival description is flexible by essence.
It is quite commonly noted that today the level of granularity of
information varies from one finding aid to another (or from one authority
record to another), or even within the same finding aid. Some series or
agents are described summarily because little is known about them and there
is little time for extensive research, while other series, even records, or
agents are described in detail; some relations (e.g. that relating to
provenance) may be described without any detail while others may be
thoroughly documented, as ISAAR(CPF) and EAC-CPF allow it.
Being generally flexible, for an OWL ontology, depends first on the
polyhierarchical systems of classes and properties it provides. A
superproperty or superclass, more general or generic than its subproperties
or subclasses, must exist and be available for handling information, while
at the same time more accurate subcomponents must be there for handling more
accurate description. Also, RiC-O provides methods for describing relations
as full entities, as well as direct and short paths between
entities.
4. RiC-O opens new potential for archival
description.
Linked Data tools and interfaces enable end users to go
through RDF/RiC-O graphs, query them using SPARQL, and make inferences.
This means a completely new way of consulting archival metadata and
their multiple contexts. An end user should be able to ask
of any given data set, for example, “What are (according to your dataset)
the corporate bodies that succeeded a given entity from its end of existence
to now (as concerns this given activity)?”, or “what instantiations of this
photograph exist?”, or “what are the existing copies of this original
charter?”, and get a list of these entities. This means that institutions or
projects that invest in the implementation of RiC-O will be able to query
their data in ways not possible with the previous ICA standards, and will
get new insight into the content and context of their archives that wasn’t
visible with the existing ICA-standards. What is more, repositories using
RiC-O may infer new assertions from the RDF datasets and link them to other
resources outside their institution, thereby amplifying the query and
inferencing possibilities manifold.
5. RiC-O is extensible.
Institutions with descriptive needs beyond what RiC-O provides
out-of-the-box have the option of extending the ontology by adding new
subclasses or subproperties as needed. Also, the concepts defined in
existing SKOS vocabularies (e.g. a list of documentary form types) can also
be connected to RiC-O based graphs (using the *Type classes, and properties
which are in the domain or range of these classes).
RiC-O has also the potential to be usable in other contexts than purely
archival ones. It can be used to “hook” archival description to descriptive
metadata in other domains (e.g. bibliographic or museum metadata). As said
above, alignment with other models will be undertaken by EGAD in a future
revision cycle, facilitating such connections.
Back to the table of contents | Back to top
Understanding RiC-O: a quick overview of some features
From RiC-CM to RiC-O
1. From RiC-CM components to RiC-O classes
Each RiC-CM entity has a corresponding class in
RiC-O. These classes are organized according to
the same hierarchy as in RiC-CM. Some projects may need very few of
them (e.g. Agent, Record Resource and Activity only), while others
may need more (e.g. Corporate Body and Person; Record; Place;
Organic Provenance Relation).
Many classes only exist in RiC-O and not in
RiC-CM. These additional classes address special
needs:
-
some correspond to RiC-CM
attributes, when it may be considered
necessary to handle them as full entities. This is the case for
Type and its subclasses,
that correspond to RiC-CM attributes that contain controlled
values, and that can help to articulate RiC-O with external RDF
resources like SKOS vocabularies; and also for Language, Name and Identifier, that can be
considered as full entities and as key linking nodes in a RDF
graph. All these classes have been grouped under a Concept class.
-
some classes have been added in order to
provide a more accurate definition and model for some
entities. Place thus comes along with a Physical Location
class, and with a Coordinates class. A Place is considered both a
geographical and historical entity. As a historical entity,
among other features, it has a history, and may be preceded or
succeeded by other Places. A Place also may have zero to many
Physical Location through time (for instance, its boundaries, if
it is an administrative area or a country, may change). Each
Physical Location may be connected to zero to many Coordinates.
This model is quite close to the Linked Places Format (https://github.com/LinkedPasts/linked-places).
Another example of such an addition is the Proxy class, that represents
(stands for) a Record Resource as it exists in a specific Record
Set.
-
finally, a system of n-ary classes helps to
implement the Relations section of RiC-CM.
While these relations also are represented as simple, binary
object properties (e.g. hasOrganicProvenance that corresponds to RiC-R026
relation), you may need to assign different attributes to a
relation, e.g. a date, certainty or description, as it is
already possible, and quite often done, in a XML/EAC-CPF file.
One of the standard available methods for representing such a
documented relation in RDF for now is to use a class. The
RDF-star specification, which is being developed by the W3C
RDF-DEV Community Group, provides a far simpler method (allowing
to consider a triple as the subject or object of another triple;
see https://w3c.github.io/rdf-star/) and is already
being used by some tools; however it is not yet a complete W3C
standard. Thus, for example, in RiC-O a OrganicProvenanceRelation class exists. This class
may connect one to many Agents to one to many created or
accumulated Record Resources or Instantiations, and has some
specific object properties (certainty, date, description,
source). Back to the hasOrganicProvenance object property, let us add
that it is formally defined in RiC-O, using OWL 2 property chain
axiom (see https://www.w3.org/TR/owl2-new-features/#F8:_Property_Chain_Inclusion),
as a ‘shortcut’ for the longer path
‘thingIsSourceOfRelation/organicProvenanceRelation_role/relationHasTarget’,
where the intermediate node is an instance of OrganicProvenanceRelation:
A triplestore, with the appropriate configuration, may
thus infer the direct ‘hasOrganicProvenance’ assertion from this
long path.
Back to the table of contents | Back to top
2. About RiC-O datatype properties (relations whose object is a
litteral)
Most of the datatype properties in RiC-O correspond
to RiC-CM attributes that contain free, plain
text. See for example rico:generalDescription, rico:history and rico:scopeAndContent.
In many simple usecases it’s sufficent to just use the rico:identifier or rico:name datatype properties.
However, in addition to these datatype properties, the Name and
Identifier RiC-CM attributes also have corresponding classes
(subclasses of rico:Appellation). A resource may have several
Identifiers (e.g. archival reference code, system number, digital
object identifier) or Names and each comes with different
attributes; in this case instances of classes are needed.
The Location RiC-CM attribute also has a rico:PhysicalLocation
corresponding class (for users who want to use Place, Physical
Location and Coordinates for handling places).
As already said too, every RiC-CM attribute that has ‘controlled
value’ or ‘rule-based’ as a schema value, has a class as
corresponding component in RiC-O. However, for these CM
attributes that correspond to a RiC-O class, as it is necessary
to provide an immediately usable ontology, two supplementary
datatype properties exist that allow not to use the classes, at
least for a while, if you want to implement RiC-O and create
RiC-O/RDF datasets from existing archival metadata without being
able to handle URIs for the information you
have.
For example, you may not be able to handle and maintain URIs for
some controlled values you use in EAD finding aids for carrier
types: maybe your information system does not use a vocabulary for
this, and you cannot for a while consider these carrier types as
full entities. Nevertheless you want to produce RiC-O datasets where
every piece of information is kept, and you want to avoid blank
nodes. If RiC-O would only provide the Carrier Type class, it would
be an issue for you.
So RiC-O provides a rico:type
datatype property, with range rdfs:literal, which allows you to move
forward. For RiC-CM Coordinates attribute, you also have the rico:geographicalCoordinates datatype
property.
These datatype properties have a skos:scopeNote which says (for
example) "Provided for usability reasons. May be made deprecated or
removed later on. Use only if you don’t use Physical Location and
Coordinates classes with Place."
The same key design principle (RiC-O must be
immediately usable) led us to define some datatype properties
that would enable users to use RiC-O in simple usecases where
they do not want to consider dates and rules as full
entities. Thus, there of course is Date and Rule
classes in RiC-O (since there are Date and Rule entities in RiC-CM).
And you also have a rico:date datatype property, which has several
subproperties; plus a rico:ruleFollowed datatype property.
The same analysis led us to keep the rico:history datatype property in RiC-O (same as
RiC-CM history attribute), while RiC-CM and RiC-O also provide the
Event class, and using a
series of Events may of course be a better method, easier to query,
link and display, than simply using a history prose discourse. The
two methods may be used in parallel within the same dataset by an
institution that, for example, would decide to emphasize only the
accession, appraisal and description events among the whole history
of Record Resources.
These datatype properties have the same kind of skos:scopeNote
as above.
Finally, we have introduced a few datatype
properties that do not correspond to any RiC-CM
attribute.
Some are superproperties, and thus group datatype properties:
rico:physicalOrLogicalExtent, with rico:carrierExtent,
rico:instantiationExtent and rico:recordResourceExtent as
subproperties; rico:textualValue, with rico:expressedDate,
rico:normalizedValue and rico:quantity as subproperties; rico:measure; rico:referenceSystem.
Some are simply more specific properties: rico:accrualsStatus;
rico:recordResourceStructure and rico:instantiationStructure, subproperties of
rico:structure; rico:title
(subproperty of rico:name); rico:altitude, rico:height,
rico:latitude, rico:length, rico:longitude, rico:width
(subproperties of rico:measure), rico:geodesicSystem and
rico:altimetricSystem (subproperties of rico:referenceSystem).
Back to the table of contents | Back to top
3. About RiC-O object properties (relations between two
entities)
In order to connect all the classes created, a
significant number of object properties have been defined, in
addition to the 85 relations defined in RiC-CM
1.0.
While the 'flat' list of object properties is a long one,
the object properties are grouped
hierarchically, so that one can use the upper to
intermediate level ones for simplicity sake, or choose the most
accurate and expressive ones, or extend the system adding a
subproperty easily. It is expected that, in most use cases, a subset
of these properties only will be needed.
Below we just give a few details on certain specific sets of
properties.
While in RiC-CM it was not possible to achieve such a level of
precision with simple attributes, RiC-O includes object
properties to assert that a rico:RecordSet has or had members (either all of
them, or some of them) that share some
characteristics, i.e. Language, ContentType,
DocumentaryFormType, LegalStatus, or RecordState. See for example
rico:hasOrHadAllMembersWithCategory, and its
subproperties.
Some of the object properties are formally defined
as shortcuts: they can be inferred if you create
triples that include instances of the Relation classes. See the
example explained above in the section
dedicated to classes.
Many properties, new in RiC-O 1.0, are
transitive, as explained in the history note above.
Back to the table of contents | Back to top
4. Named Individuals
RiC-O adds six individuals to address current and frequent
needs:
-
FindingAid and AuthorityRecord, which are
instances of both RiC-O Documentary Form Type and SKOS Concept.
They can be used for categorizing Records, finding aids and
authority records being considered as Records. For example, a
Record with Documentary Form Type ‘Finding Aid’ may be connected
to one to many Record Resources using the 'rico:describes’
object property.
-
Fonds, Series, File, and Collection are instances of both Record Set Type
class and skos:Concept. Their definition is taken from the
ISAD(G) glossary. They can be used for categorizing Record
Sets.
We expect other categories to be defined by the archival
community as RiC-O matures, forming rich, hopefully multilingual,
SKOS vocabularies that support rich description (for example,
allowing an instance of the Documentary Form Type class to have a history and
temporal relations to other documentary form types).
Back to the table of contents | Back to top
RiC-O documentation and annotation properties
Each class or property has an English, a French and a Spanish label
(rdfs:label), and a description (rdfs:comment). Some also have a
skos:scopeNote or a skos:example.
When a RiC-O class or property corresponds to a RiC-CM component in
any way, its description and scope note are either the same as or
derived from their RiC-CM definition and scope note.
RiC-O provides two annotation properties (subproperties of
rdfs:comment) for handling:
- information about the corresponding RiC-CM component when
applicable (rico:RiCCMCorrespondingComponent). Various phrasings
are used in this property depending on the rule applied for defining
the RiC-CM component.
- information about possible mappings with other models or
ontologies (rico:closeTo,
rarely used in this 1.0.2 version)).
Any change in the definition of a class or property made since
December 2019 is documented using a skos:changeNote.
Back to the table of contents | Back to top
Next steps
The following is a non exhaustive list of known issues, topics or tasks
on which EGAD has begun to work and will continue to work in the next
months.
- articulate the Event and Activity classes, and the Relation system
of classes
- add suggestions of mappings (in rico:closeTo) and OWL equivalences
between some classes or properties and components in other models (among
which - this is not an exhaustive list- PREMIS, Schema.org, PROV-O,
IFLA-LRM and RDA, CIDOC-CRM), or document how these models can be used
together.
Back to the table of contents | Back to top
Classes
rico:AccumulationRelation | rico:Activity | rico:ActivityDocumentationRelation | rico:ActivityType | rico:Agent | rico:AgentControlRelation | rico:AgentHierarchicalRelation | rico:AgentName | rico:AgentTemporalRelation | rico:AgentToAgentRelation | rico:Appellation | rico:AppellationRelation | rico:AuthorityRelation | rico:AuthorshipRelation | rico:CarrierExtent | rico:CarrierType | rico:ChildRelation | rico:Concept | rico:ContentType | rico:Coordinates | rico:CorporateBody | rico:CorporateBodyType | rico:CorrespondenceRelation | rico:CreationRelation | rico:Date | rico:DateType | rico:DemographicGroup | rico:DerivationRelation | rico:DescendanceRelation | rico:DocumentaryFormType | rico:Event | rico:EventRelation | rico:EventType | rico:Extent | rico:ExtentType | rico:Family | rico:FamilyRelation | rico:FamilyType | rico:FunctionalEquivalenceRelation | rico:Group | rico:GroupSubdivisionRelation | rico:Identifier | rico:IdentifierType | rico:Instantiation | rico:InstantiationExtent | rico:InstantiationToInstantiationRelation | rico:IntellectualPropertyRightsRelation | rico:KnowingOfRelation | rico:KnowingRelation | rico:Language | rico:LeadershipRelation | rico:LegalStatus | rico:ManagementRelation | rico:Mandate | rico:MandateRelation | rico:MandateType | rico:Mechanism | rico:MembershipRelation | rico:MigrationRelation | rico:Name | rico:OccupationType | rico:OrganicOrFunctionalProvenanceRelation | rico:OrganicProvenanceRelation | rico:OwnershipRelation | rico:PerformanceRelation | rico:Person | rico:PhysicalLocation | rico:Place | rico:PlaceName | rico:PlaceRelation | rico:PlaceType | rico:Position | rico:PositionHoldingRelation | rico:PositionToGroupRelation | rico:ProductionTechniqueType | rico:Proxy | rico:Record | rico:RecordPart | rico:RecordResource | rico:RecordResourceExtent | rico:RecordResourceGeneticRelation | rico:RecordResourceHoldingRelation | rico:RecordResourceToInstantiationRelation | rico:RecordResourceToRecordResourceRelation | rico:RecordSet | rico:RecordSetType | rico:RecordState | rico:Relation | rico:RepresentationType | rico:RoleType | rico:Rule | rico:RuleRelation | rico:RuleType | rico:SequentialRelation | rico:SiblingRelation | rico:SpouseRelation | rico:TeachingRelation | rico:TemporalRelation | rico:Thing | rico:Title | rico:Type | rico:TypeRelation | rico:UnitOfMeasurement | rico:WholePartRelation | rico:WorkRelation
Class: rico:AccumulationRelation
IRI:
https://www.ica.org/standards/RiC/ontology#AccumulationRelation
- Label(s)
- Accumulation Relation [en]; Relation d’accumulation [fr]; Relación de acumulación [es]
- Definition
- Connects at least one Record Resource or Instantiation to at
least one Agent, when the Record Resource or Instantiation is or was accumulated by the
Agent, be it intentionally (collecting it) or not (receiving it in the course of its
activities). The Record Resource(s) or Instantiation(s) is the source of the Relation,
and the Agent(s) is the target.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R028 and RiC-R028i
relations
- Has super-classes
-
rico:OrganicProvenanceRelation
-
relationHasSource
min 1 (Instantiation
or
RecordResource)
-
relationHasTarget
min 1 Agent
- Is equivalent of
-
rico:accumulationRelation_role Self
- Is in domain of
-
rico:accumulationRelation_role
- Is in range of
-
rico:accumulationRelation_role
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment).
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:Activity
IRI:
https://www.ica.org/standards/RiC/ontology#Activity
- Label(s)
- Activity [en]; Activité [fr]; Actividad [es]
- Definition
- The doing of something for some human purpose.
- Scope note
- Activity is a kind of Event. Activity is specifically used to
designate purposeful human activity. Activity may be understood from two perspectives.
First it can be understood as leading to an end. The end is the purpose of the Activity,
or why the Activity is performed. Second, it can be understood in terms of the processes
that lead to achieving the end, how the end is realized through coordinated actions.
Purpose and process are complementary understandings of Activity. Together the two
perspectives address why the Activity is performed, the expected ends or outcomes; and
how the Activity fulfills the purpose. While activity has an intended end, it also has
unintended consequences and results, or side-effects. By and large, these may not be the
focus of the description, but they are, unquestionably, context. |In a corporate or
government context an Activity may also be called a 'function'. An Activity exists in a
specific social and cultural context, and within that context is subject to change over
time. An Activity may be composed of other Activities.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-E15 (Activity
entity)
- Has super-classes
-
rico:Event
- Is in domain of
-
rico:activityIsContextOfRelation; rico:documentedBy; rico:hasActivityType; rico:isOrWasPerformedBy; rico:isOrganicOrFunctionalProvenanceOf
- Is in range of
-
rico:asConcernsActivity; rico:documents; rico:hasOrganicOrFunctionalProvenance; rico:isActivityTypeOf; rico:performsOrPerformed
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-23: Scope note: made separate paragraphs and updated.
Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:ActivityType
IRI:
https://www.ica.org/standards/RiC/ontology#ActivityType
- Label(s)
- Activity Type [en]; Type d’activité [fr]; Tipo de actividad [es]
- Definition
- Categorization of an Activity.
- Scope note
- Can be extended with any number of subclasses, e.g.
“function/action” and “activity domain”. This allows for a faceted approach that enables
an Activity to be categorized using a combination of components, general or more
specific. For example, “monitoring” can be used in combination with “election polls” or
“water resources”.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A02 (Activity Type
attribute)
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isActivityTypeOf
- Is in range of
-
rico:hasActivityType
- Has sub-classes
-
rico:OccupationType
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-23: Scope note: updated (different from RiC-CM scope note).
Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:Agent
IRI:
https://www.ica.org/standards/RiC/ontology#Agent
- Label(s)
- Agent [en]; Agent [fr]; Agente [es]
- Definition
- A Person, or Group, or an entity created by a Person or Group
(Mechanism), or a Position, that acts in the world.
- Scope note
- An Agent may have one or more identities; an identity is a
constellation of properties or relations that together “identify” the Agent. A Person or
Group commonly has one identity, though each also may have one or more alternative
identities. Such alternative identities may be shared by more than one Person or Group.
Alternative identities include but are not limited to pseudonyms, heteronyms, DBA (Doing
Business As), and trade identities. An alternative identity should not be confused with
a Position in a Group, for example, presidents, prime ministers, governors, popes,
royalty, or bishops. Nor should an alternative identity be confused with a variant name
or identifier of the same identity. Agent also includes entities created by a Person or
Group that act on behalf of the creating Agent in an autonomous or semi-autonomous
manner. Examples of a Mechanism include software agents, robots, and space and
underwater probes that generate data (records) in the course of Activity assigned to and
in conformance with the instructions given to them by the creating Person or
Group.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-E07 (Agent
entity)
- Has super-classes
-
rico:Thing
- Is in domain of
-
rico:agentHasOrHadLocation; rico:authorizedBy; rico:authorizingMandate; rico:hadSubordinate; rico:hasDirectSubordinate; rico:hasOrHadAgentName; rico:hasOrHadAuthorityOver; rico:hasOrHadController; rico:hasOrHadJurisdiction; rico:hasOrHadLanguage; rico:hasOrHadLegalStatus; rico:hasOrHadSubordinate; rico:hasOrHadWorkRelationWith; rico:hasSubordinateTransitive; rico:hasSuccessor; rico:history; rico:isAccumulatorOf; rico:isAddresseeOf; rico:isAgentAssociatedWithAgent; rico:isAgentAssociatedWithPlace; rico:isAuthorizingAgentInMandateRelation; rico:isCollectorOf; rico:isCreatorOf; rico:isDirectSubordinateTo; rico:isOrWasControllerOf; rico:isOrWasHolderOf; rico:isOrWasManagerOf; rico:isOrWasResponsibleForEnforcing; rico:isOrWasSubordinateTo; rico:isOrganicOrFunctionalProvenanceOf; rico:isOrganicProvenanceOf; rico:isPublisherOf; rico:isReceiverOf; rico:isResponsibleForIssuing; rico:isSenderOf; rico:isSubordinateToTransitive; rico:isSuccessorOf; rico:performsOrPerformed; rico:wasSubordinateTo
- Is in range of
-
rico:authorizes; rico:authorizingAgent; rico:hadSubordinate; rico:hasAccumulator; rico:hasAddressee; rico:hasCollector; rico:hasCreator; rico:hasDirectSubordinate; rico:hasOrHadController; rico:hasOrHadHolder; rico:hasOrHadManager; rico:hasOrHadSubordinate; rico:hasOrHadWorkRelationWith; rico:hasOrganicOrFunctionalProvenance; rico:hasOrganicProvenance; rico:hasPublisher; rico:hasReceiver; rico:hasSender; rico:hasSubordinateTransitive; rico:hasSuccessor; rico:isAgentAssociatedWithAgent; rico:isDirectSubordinateTo; rico:isOrWasAgentNameOf; rico:isOrWasControllerOf; rico:isOrWasEnforcedBy; rico:isOrWasJurisdictionOf; rico:isOrWasLanguageOf; rico:isOrWasLegalStatusOf; rico:isOrWasLocationOfAgent; rico:isOrWasPerformedBy; rico:isOrWasSubordinateTo; rico:isOrWasUnderAuthorityOf; rico:isPlaceAssociatedWithAgent; rico:isSubordinateToTransitive; rico:isSuccessorOf; rico:issuedBy; rico:wasSubordinateTo
- Has sub-classes
-
rico:Group; rico:Mechanism; rico:Person; rico:Position
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2021-02-08: removed the Restrictions
- 2020-10-23: Comment: updated. Scope note: updated and made several
paragraphs. Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:AuthorshipRelation
IRI:
https://www.ica.org/standards/RiC/ontology#AuthorshipRelation
- Label(s)
- Authorship Relation [en]; Relation de responsabilité intellectuelle [fr]; Relación de autoría [es]
- Definition
- Connects at least one Record to at least one Person, Group or
Position that is or was responsible for conceiving and formulating the information
contained in the Record. The Record is the source of the Relation and the Person(s),
Group(s) or Position(s) is the target.
- Scope note
- To be used for a person, group or position that makes any
contribution to the content of a record. Includes the person, group or position in whose
name or by whose command the content may have been formulated and first instantiated
(for example the person who signed the record).
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R079 and RiC-R079i
relations
- Has super-classes
-
rico:CreationRelation
-
relationHasSource
min 1 Record
-
relationHasTarget
min 1 (Group
or
Person
or
Position)
- Is equivalent of
-
rico:authorshipRelation_role Self
- Is in domain of
-
rico:authorshipRelation_role
- Is in range of
-
rico:authorshipRelation_role
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-12-29: Created following the addition of RiC-R079 relation in
RiC-CM 0.2
Back to the table of contents | Back to top
Class: rico:CarrierExtent
IRI:
https://www.ica.org/standards/RiC/ontology#CarrierExtent
- Label(s)
- Carrier Extent [en]; Mesure d’un support [fr]; Extensión del soporte [es]
- Definition
- Number of physical units and/or physical dimensions of the
carrier of an Instantiation.
- Scope note
- In order to manage an instantiation of a record resource it is
necessary to note the extent of the carrier as well as that of the instantiation itself.
Whether it is necessary to note dimensions, the number of relevant units or both depends
on the nature of the carrier and particular business needs.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-A04 (Carrier Extent)
attribute
- Has super-classes
-
rico:Extent
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-21: Changed a bit the definition and added change
notes.
- 2020-10-28: Class added in order to handle an accurate description of a
carrier extent
Back to the table of contents | Back to top
Class: rico:CarrierType
IRI:
https://www.ica.org/standards/RiC/ontology#CarrierType
- Label(s)
- Carrier Type [en]; Type de support [fr]; Tipo de soporte [es]
- Definition
- Categorization of physical material on which information is
represented.
- Scope note
- In order to manage an instantiation of a record resource, it
is necessary to note the type of carrier on which the record resource is instantiated as
its nature will determine the environmental storage conditions and the prerequisites for
and possible ways of accessing and using the record resource.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A05 (Carrier Type
attribute)
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isCarrierTypeOf
- Is in range of
-
rico:hasCarrierType
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-23: Scope note: updated (quite the same as RiC-CM definition).
Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:ChildRelation
IRI:
https://www.ica.org/standards/RiC/ontology#ChildRelation
- Label(s)
- Child Relation [en]; Relation de filiation [fr]; Relación de filiación [es]
- Definition
- Connects at least one Person to at least another Person, when
the first has(ave) child(s) the second one(s). The Relation is oriented from the parent
to the child: the parent is the source of the relation, and the child(ren) is the
target.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R018 and RiC-R018i
relations
- Has super-classes
-
rico:DescendanceRelation
-
relationHasSource
min 1 Person
-
relationHasTarget
min 1 Person
- Is equivalent of
-
rico:childRelation_role Self
- Is in domain of
-
rico:childRelation_role
- Is in range of
-
rico:childRelation_role
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment).
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:ContentType
IRI:
https://www.ica.org/standards/RiC/ontology#ContentType
- Label(s)
- Content Type [en]; Type de contenu [fr]; Tipo de contenido [es]
- Definition
- The fundamental form of communication in which a Record or
Record Part is expressed.
- Scope note
- Content Type should not be confused with Representation Type
or Carrier Type that would concern a related Instantiation since the form of
communication can be independent of the representation or carrier, for example a map
(content type "cartographic image") may be represented as a sketch (representation type
"visual") recorded as a physical document (carrier type "paper"). It also should not be
confused with the Documentary Form Type of a Record, or Record Part, which describes a
specific document form (for example a deed of sale).
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A10 (Content Type
attribute)
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isContentTypeOf; rico:isOrWasContentTypeOfAllMembersOf; rico:isOrWasContentTypeOfSomeMembersOf
- Is in range of
-
rico:hasContentOfType; rico:hasOrHadAllMembersWithContentType; rico:hasOrHadSomeMembersWithContentType
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-23: Scope note: added (quite the same as RiC-CM
definition).
Back to the table of contents | Back to top
Class: rico:CorporateBody
IRI:
https://www.ica.org/standards/RiC/ontology#CorporateBody
- Label(s)
- Corporate Body [en]; Collectivité [fr]; Institución [es]
- Definition
- An organized group of persons that act together as an Agent, and
that has a recognized legal or social status.
- Scope note
- Corporate body is a kind of Group (RiC-E09). By exception,
within some legal contexts, a sole trader or sole proprietor may be recognized as a
corporate body, even when the economic enterprise does not have additional members.
Corporate bodies often have a mandate giving them the authority to act within their
area(s) of competence. They will also usually act within a particular jurisdiction being
governed by legal and other rule-based frameworks. A corporate body though may be
constituted in a more informal manner and exist as an entity by virtue of its
recognition as such by its members.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-E11 (Corporate Body
entity)
- Has super-classes
-
rico:Group
- Is in domain of
-
rico:hasOrHadCorporateBodyType; rico:isOrWasEmployerOf; rico:resultedFromTheMergerOf; rico:resultedFromTheSplitOf; rico:wasMergedInto; rico:wasSplitInto
- Is in range of
-
rico:hasOrHadEmployer; rico:isOrWasCorporateBodyTypeOf; rico:resultedFromTheMergerOf; rico:resultedFromTheSplitOf; rico:wasMergedInto; rico:wasSplitInto
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-10-23: scope note: updated. Objective: to make RiC-O compliant
with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:CorporateBodyType
IRI:
https://www.ica.org/standards/RiC/ontology#CorporateBodyType
- Label(s)
- Corporate Body Type [en]; Type de collectivité [fr]; Tipo de institución [es]
- Definition
- Categorization of a Corporate Body.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A12 (Corporate Body Type
attribute)
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isOrWasCorporateBodyTypeOf
- Is in range of
-
rico:hasOrHadCorporateBodyType
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
Back to the table of contents | Back to top
Class: rico:CreationRelation
IRI:
https://www.ica.org/standards/RiC/ontology#CreationRelation
- Label(s)
- Creation Relation [en]; Relation de création [fr]; Relación de creación [es]
- Definition
- Connects at least one Record Resource or Instantiation to at
least one Agent, when the Agent is either responsible for all or some of the content of
the Record Resource, or is a contributor to the genesis or production of the
Instantiation. The Record Resource or Instantiation is the source of the Relation, and
the Agent(s) is the target.
- Scope note
- Covers the definition of "author" in diplomatics, and any
agent that makes a contribution to the intellectual content of a record resource. Can
also be used for any agent that was involved in the genesis (e.g. with the role of
witness, representative of the author etc.) or in the production (e.g. with the role of
scribe, secretary, notary, printer etc.) of the record resource or
instantiation.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R027 and RiC-R027i
relations
- Has super-classes
-
rico:OrganicProvenanceRelation
-
relationHasSource
min 1 (Instantiation
or
RecordResource)
-
relationHasTarget
min 1 Agent
- Is equivalent of
-
rico:creationRelation_role Self
- Is in domain of
-
rico:creationRelation_role; rico:creationWithRole
- Is in range of
-
rico:creationRelation_role; rico:roleIsContextOfCreationRelation
- Has sub-classes
-
rico:AuthorshipRelation
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the
skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed a 0.2 existing unnecessary restriction.
Back to the table of contents | Back to top
Class: rico:DateType
IRI:
https://www.ica.org/standards/RiC/ontology#DateType
- Label(s)
- Date Type [en]; Type de date [fr]; Tipo de fecha [es]
- Definition
- Categorization of a Date.
- Scope note
- May be used to categorize a Date as a single date, a date
range or a date set or sub-categories of these broad types. This attribute should not be
confused with the date relations defined to connect a Date entity and any other entity
(such as RiC-R069 ‘is beginning date of’).
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A42 (Date Type attribute) (new
in RiC-CM 1.0).
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isDateTypeOf
- Is in range of
-
rico:hasDateType
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote. Added a label in Spanish.
- 2023-10-10: Added the rdfs:comment, a French rdfs:label, and adjusted
the rico:RiCCMCorrespondingComponent annotation.
- 2023-09-22: Added in RiC-O 1.0.
Back to the table of contents | Back to top
Class: rico:DemographicGroup
IRI:
https://www.ica.org/standards/RiC/ontology#DemographicGroup
- Label(s)
- Demographic Group [en]; Catégorie démographique [fr]; Categoría demográfica [es]
- Definition
- Categorization of a Person or Group based on shared
characteristics.
- Scope note
- Can be extended with any number of specific subclasses. Among
possible specific demographic groups are gender, (biological) sex, education, identity,
place, ancestry, ethnic/cultural identification, and religion.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A15 (Demographic Group
attribute)
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isOrWasDemographicGroupOf
- Is in range of
-
rico:hasOrHadDemographicGroup
- Has sub-classes
-
rico:OccupationType
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2021-02-08: Removed the Restriction.
- 2020-10-23: Comment: updated. Scope note: updated and made several
paragraphs. Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:DerivationRelation
IRI:
https://www.ica.org/standards/RiC/ontology#DerivationRelation
- Label(s)
- Derivation Relation [en]; Relation de dérivation [fr]; Relación de derivación [es]
- Definition
- Connects an Instantiation to at least one Instantiation that is
derived from it, whether it exists or has been lost or destroyed. The Relation is
oriented chronologically, from the first Instantiation in time to the derived
Instantiation: the first Instantiation is the source of the Relation, and the derived
Instantiation(s) is the target.
- Scope note
- In some situations, it may be useful or necessary to connect
an instantiation to an instantiation that was derived from it but no longer exists or
has been lost.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R014 and RiR014i
relations
- Has super-classes
-
rico:InstantiationToInstantiationRelation
-
rico:TemporalRelation
-
relationHasSource 1 Instantiation
-
relationHasTarget
min 1 Instantiation
- Is equivalent of
-
rico:derivationRelation_role Self
- Is in domain of
-
rico:derivationRelation_role
- Is in range of
-
rico:derivationRelation_role
- Has sub-classes
-
rico:MigrationRelation
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:EventRelation
IRI:
https://www.ica.org/standards/RiC/ontology#EventRelation
- Label(s)
- Event Relation [en]; Relation impliquant un événement [fr]; Relación con un evento [es]
- Definition
- Connects at least one Event to at least one Thing, when the
first is associated with the existence and lifecycle of the second one. The Event(s) is
the source of the Relation, and the Thing(s) is the target.
- Scope note
- Use to connect an event and an entity only if it is not
possible to specify a narrower event relation, for example a
PerformanceRelation.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R057 and RiC-R057i
relations
- Has super-classes
-
rico:Relation
-
relationHasSource
min 1 Event
-
relationHasTarget
min 1 Thing
- Is equivalent of
-
rico:eventRelation_role Self
- Is in domain of
-
rico:eventRelation_role
- Is in range of
-
rico:eventRelation_role
- Has sub-classes
-
rico:ActivityDocumentationRelation; rico:PerformanceRelation
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the
skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:EventType
IRI:
https://www.ica.org/standards/RiC/ontology#EventType
- Label(s)
- Event Type [en]; Type d’événement [fr]; Tipo de evento [es]
- Definition
- Categorization of an Event.
- Scope note
- Events of all kinds can be categorized. Curation event types
include creation; acquisition; transfer; arrangement; description; digitization, etc.
Biographical event types include birth, marriage, death, etc.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A18 (Event Type
attribute)
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isEventTypeOf
- Is in range of
-
rico:hasEventType
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the
skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-23: Scope note: updated and made several paragraphs. Objective:
to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:Family
IRI:
https://www.ica.org/standards/RiC/ontology#Family
- Label(s)
- Family [en]; Famille [fr]; Familia [es]
- Definition
- Two or more persons related by birth, or through marriage,
adoption, civil union, or other social conventions that bind them together as a socially
recognized familial group.
- Scope note
- Family is a kind of Group. “Family” is used here as a general
term that encompasses a wide variety of familial groups. Other types of familial groups
include Dynasty, Clan, House, Tribe and others. Though family may be a recognized legal
group in specific contexts, the term may also be used for groups that are socially
recognized as families. A family may be a group of persons related either by
consanguinity or affinity or cohabitation or other social conventions. In some context,
a Family may be legally recognized as Corporate Body. For example, certain North
American peoples (tribes) retain self-government rights and have jurisdiction over
defined tribal lands.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-E10 (Family
entity)
- Has super-classes
-
rico:Group
- Is in domain of
-
rico:hasFamilyType
- Is in range of
-
rico:isFamilyTypeOf
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-10-23: Scope note: made separate paragraphs and some
changes.
Back to the table of contents | Back to top
Class: rico:FamilyType
IRI:
https://www.ica.org/standards/RiC/ontology#FamilyType
- Label(s)
- Family Type [en]; Type de famille [fr]; Tipo de familia [es]
- Definition
- Categorization of a Family.
- Scope note
- Encompasses a wide variety of familial groups related by
consanguinity, affinity, cohabitation, or other social conventions.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A20 (Family Type
attribute)
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isFamilyTypeOf
- Is in range of
-
rico:hasFamilyType
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the
skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-23: Comment: slighty changed.
Back to the table of contents | Back to top
Class: rico:FunctionalEquivalenceRelation
IRI:
https://www.ica.org/standards/RiC/ontology#FunctionalEquivalenceRelation
- Label(s)
- Functional Equivalence Relation [en]; Relation d’équivalence fonctionnelle [fr]; Relación de equivalencia funcional [es]
- Definition
- Connects at least two Instantiations which may be considered as
equivalent. This Relation is not oriented.
- Scope note
- Two instantiations, from some point of view, may be considered
as equivalent. This equivalence is usually based upon the fact that the instantiations
have at least the same intellectual content (they instantiate the same record
resource).
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R035 and RiC-R035i
relations
- Has super-classes
-
rico:InstantiationToInstantiationRelation
-
relationConnects
min 2 Instantiation
- Is equivalent of
-
rico:functionalEquivalenceRelation_role Self
- Is in domain of
-
rico:functionalEquivalenceRelation_role
- Is in range of
-
rico:functionalEquivalenceRelation_role
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the
skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:Identifier
IRI:
https://www.ica.org/standards/RiC/ontology#Identifier
- Label(s)
- Identifier [en]; Identifiant [fr]; Identificador [es]
- Definition
- A word, number, letter, symbol, or any combination of these used
to uniquely identify or reference an individual instance of an entity within a specific
information domain.
- Scope note
- Can include Global Persistent Identifiers (globally unique and
persistently resolvable identifier for the entity) and/or Local Identifiers. Both the
domain within which the identifier is unique, and the rules used in forming the
identifier value should be provided with the identifier value.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-A22 (Identifier
attribute) (see also the identifier datatype property)
- Has super-classes
-
rico:Appellation
- Is in domain of
-
rico:hasIdentifierType; rico:isOrWasIdentifierOf
- Is in range of
-
rico:hasOrHadIdentifier; rico:isIdentifierTypeOf
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the
skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
Back to the table of contents | Back to top
Class: rico:Instantiation
IRI:
https://www.ica.org/standards/RiC/ontology#Instantiation
- Label(s)
- Instantiation [en]; Instanciation [fr]; Instanciación [es]
- Definition
- The inscription of information made by an Agent on a physical
carrier in any persistent, recoverable form as a means of communicating information
through time and space.
- Scope note
- A Record or Record Part must have been instantiated at least
once, though this instantiation may no longer exist at the moment of description. An
instantiation might also exist at the moment of description, but be destroyed at a later
moment in time, when, for example, a derived instantiation might become the only
remaining instantiation. A Record Set may have an instantiation, which is to say that it
is not a necessary condition. An Instantiation may be derived from another
Instantiation. A Record Resource may have many Instantiations simultaneously (for
instance, a record printed and saved in the same time as DOCX and PDF/A would have 3
concurrent instantiations) or through time (for example, copy of a record). Depending on
the context, a new instantiation may be seen as a new or as the same record resource.
During in the process of re-instantiation something is lost and something is preserved,
but it is up to the context and the Agent that produces or uses that Instantiation to
assess whether the two instantiations are functionally equivalent or not. For instance,
a postcard representing a town map from 1874 (Instantiation 1) is digitized and kept as
a JPEG file (Instantiation 2). The digital copy may be considered as instantiating the
"same" Record by an Agent considering the information transmitted by the Record (e.g.,
the urban landscape displayed), but as a" different" Record by an antiquarian more
focused on the materiality of the carrier. Successive instantiations may change the
perceivable boundaries of a Record Resource. For instance, a case file comprising many
records may be digitized and saved as one single PDF file, which, from management
perspective, may be treated as one Record. Similarly, a large Record Set (a fonds or a
series) may be maintained as one database. On the other hand, one record (main document
and its annexes) may be digitized in separate files and each one may be managed as a
discrete “physical” item. Instantiations may require mediation to communicate the
information in the Record Resource. While a traditional Record on paper can simply be
read by an Agent in order to understand the information, a vinyl recording, a video
cassette or a digital file needs a device (mediator) to codify or decodify the
information conveyed. This mediator may imply simple physical components (a turntable
needle, for example), or a complex gallery of software and hardware elements.
Instantiations are more than the mere informational content of Record Resource and may
be the focus of preservation and physical management of records. The use of particular
document types for records, such as a medieval charter, may have implications for the
authenticity of the records. Hence, the way a Record Resource is instantiated
contributes to the contextualizing of the content.record resource is instantiated
contributes to the contextualizing the content. Distinguishing the message conveyed
(Record Resource) and its physical representations (Instantiation) allows for the
efficient management of their descriptions, and preserve information about a Record
Resource even when no physical representation of it exists or is known to exist anymore.
The relations between distinct instantiations can then be expressed wherever they
coexist, and they can be related to the Record Resource they
instantiate.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-E06 (Instantiation
entity)
- Possible mapping(s) with other external resources
- PREMIS Representation
- Has super-classes
-
rico:Thing
- Is in domain of
-
rico:authenticityNote; rico:carrierExtent; rico:conditionsOfAccess; rico:conditionsOfUse; rico:documents; rico:hadComponent; rico:hasAccumulator; rico:hasAddressee; rico:hasCarrierType; rico:hasCollector; rico:hasComponentTransitive; rico:hasCreationDate; rico:hasCreator; rico:hasDirectComponent; rico:hasOrHadComponent; rico:hasOrHadDerivedInstantiation; rico:hasOrHadHolder; rico:hasOrHadIntellectualPropertyRightsHolder; rico:hasOrHadManager; rico:hasOrHadTitle; rico:hasOrganicOrFunctionalProvenance; rico:hasOrganicProvenance; rico:hasProductionTechniqueType; rico:hasReceiver; rico:hasRepresentationType; rico:hasSender; rico:history; rico:instantiationExtent; rico:instantiationStructure; rico:isComponentOfTransitive; rico:isDirectComponentOf; rico:isFunctionallyEquivalentTo; rico:isInstantiationAssociatedWithInstantiation; rico:isOrWasAnalogueInstantiationOf; rico:isOrWasComponentOf; rico:isOrWasDerivedFromInstantiation; rico:isOrWasDigitalInstantiationOf; rico:isOrWasInstantiationOf; rico:migratedFrom; rico:migratedInto; rico:physicalCharacteristicsNote; rico:physicalOrLogicalExtent; rico:productionTechnique; rico:qualityOfRepresentationNote; rico:structure; rico:title; rico:wasComponentOf
- Is in range of
-
rico:documentedBy; rico:hadComponent; rico:hasComponentTransitive; rico:hasDirectComponent; rico:hasOrHadAnalogueInstantiation; rico:hasOrHadComponent; rico:hasOrHadDerivedInstantiation; rico:hasOrHadDigitalInstantiation; rico:hasOrHadInstantiation; rico:isAccumulatorOf; rico:isAddresseeOf; rico:isCarrierTypeOf; rico:isCollectorOf; rico:isComponentOfTransitive; rico:isCreationDateOf; rico:isCreatorOf; rico:isDirectComponentOf; rico:isFunctionallyEquivalentTo; rico:isInstantiationAssociatedWithInstantiation; rico:isOrWasComponentOf; rico:isOrWasDerivedFromInstantiation; rico:isOrWasHolderOf; rico:isOrWasHolderOfIntellectualPropertyRightsOf; rico:isOrWasManagerOf; rico:isOrWasTitleOf; rico:isOrganicOrFunctionalProvenanceOf; rico:isOrganicProvenanceOf; rico:isProductionTechniqueTypeOf; rico:isReceiverOf; rico:isRepresentationTypeOf; rico:isSenderOf; rico:migratedFrom; rico:migratedInto; rico:wasComponentOf
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restrictions.
- 2020-10-23: Comment: updated. Scope note: updated and made several
paragraphs. Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:InstantiationExtent
IRI:
https://www.ica.org/standards/RiC/ontology#InstantiationExtent
- Label(s)
- Instantiation Extent [en]; Mesure d’une instanciation [fr]; Extensión de la instanciación [es]
- Definition
- Countable characteristics of an Instantiation expressed as a
quantity.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-A23 (Instantiation
Extent attribute)
- Has super-classes
-
rico:Extent
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-21: Changed a bit the definition and added change
notes.
- 2020-10-28: Class added in order to handle an accurate description of
an instantiation extent
Back to the table of contents | Back to top
Class: rico:KnowingRelation
IRI:
https://www.ica.org/standards/RiC/ontology#KnowingRelation
- Label(s)
- Knowing Relation [en]; Relation de connaissance entre personnes [fr]; Relación de conocimiento directo entre personas [es]
- Definition
- Connects at least two Persons who directly know each other
during their existence. This Relation is not oriented.
- Scope note
- The relation implies that the two persons met or at least
corresponded with each other.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R051 and RiC—R051i
relations
- Has super-classes
-
rico:AgentToAgentRelation
-
relationConnects
min 2 Person
- Is equivalent of
-
rico:knowingRelation_role Self
- Is in domain of
-
rico:knowingRelation_role
- Is in range of
-
rico:knowingRelation_role
- Has sub-classes
-
rico:CorrespondenceRelation; rico:TeachingRelation
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:Mandate
IRI:
https://www.ica.org/standards/RiC/ontology#Mandate
- Label(s)
- Mandate [en]; Mandat [fr]; Norma [es]
- Definition
- Delegation of responsibility or authority by an Agent to another
Agent to perform an Activity.
- Scope note
- Mandate is a kind of Rule. A mandate confers the
responsibility or authority of an agent to perform a specified activity. In addition to
assigning an activity and delegating responsibility or authority to perform the activity
to an agent, a mandate commonly limits the place (jurisdiction) and date (time period)
within which an agent may perform the activity (where and when). Mandates exist in a
specific social and cultural context, and within that context are subject to change over
time. While a mandate may be tacit, in whole or part, it may be explicitly expressed in
a variety of documentary sources (for example, constitutions, legislation, (legal) acts,
statutes, legal codes, ordinances, charges, charters, or mission statements). The
evidence for identifying a mandate may be found in its entirety in one documentary
source (for example, a law or regulation), or may be found in two or more sources. A
mandate should not be confused with the one or more documentary sources that serve as
evidence of its identity. A documentary source is a record.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-E17 (Mandate
entity)
- Has super-classes
-
rico:Rule
- Is in domain of
-
rico:authorizes; rico:hasOrHadMandateType
- Is in range of
-
rico:authorizedBy; rico:isOrWasMandateTypeOf
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-21: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-23: Scope note: made separate paragraphs and updated.
Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:MandateType
IRI:
https://www.ica.org/standards/RiC/ontology#MandateType
- Label(s)
- Mandate Type [en]; Type de mandat [fr]; Tipo de norma [es]
- Definition
- Categorization of a Mandate.
- Scope note
- For example : charter, treaty, contract, letter of
appointment, papal mandate, episcopal mandate, ciurt mandate, election mandate, popular
mandate, federal mandate, etc.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A44 (Mandate Type
attribute).
- Has super-classes
-
rico:RuleType
- Is in domain of
-
rico:isOrWasMandateTypeOf
- Is in range of
-
rico:hasOrHadMandateType
- Change note(s)
- 2023-11-12: Added in RiC-0 1.0 as it has been added to RiC-CM
1.0.
Back to the table of contents | Back to top
Class: rico:Mechanism
IRI:
https://www.ica.org/standards/RiC/ontology#Mechanism
- Label(s)
- Mechanism [en]; Système [fr]; Mecanismo [es]
- Definition
- A process or system created by a Person or Group that performs
an Activity.
- Scope note
- Mechanism is a kind of Agent. A mechanism may have both
mechanical and software components or may be exclusively software. A mechanism acts in
the world producing physical or social effects and may generate or modify records. A
mechanism performs activities based on rules determined by the agent that designed and
created it. A mechanism has an essential, derivative relation with the designing and
creating agent.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-E13 (Mechanism
entity)
- Has super-classes
-
rico:Agent
- Disjoint with
-
rico:Person; rico:Position
- Is in domain of
-
rico:technicalCharacteristics
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the
skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-10-23: scope note: made separate paragraphs. Disjoint with:
enriched.
Back to the table of contents | Back to top
Class: rico:MigrationRelation
IRI:
https://www.ica.org/standards/RiC/ontology#MigrationRelation
- Label(s)
- Migration Relation [en]; Relation de migration [fr]; Relación de migración entre instanciaciones [es]
- Definition
- Connects an Instantiation and at least another Instantiation it
has been migrated into. The Relation is oriented chronologically, from the first
Instantiation in time (the migrated one) to the one which results from its migration:
the first Instantiation in time is the source of the Relation, and the resulting
Instantiation is the target.
- Scope note
- Use for digital instantiations.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R015 and RiC-R015i
relations
- Has super-classes
-
rico:DerivationRelation
-
relationHasSource 1 Instantiation
-
relationHasTarget
min 1 Instantiation
- Is equivalent of
-
rico:migrationRelation_role Self
- Is in domain of
-
rico:migrationRelation_role
- Is in range of
-
rico:migrationRelation_role
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:Name
IRI:
https://www.ica.org/standards/RiC/ontology#Name
- Label(s)
- Name [en]; Nom [fr]; Nombre [es]
- Definition
- A label, title or term designating an entity in order to make it
distinguishable from other similar entities.
- Scope note
- Provides brief information about the content or other
individual characteristics of the entity being described, necessary to distinguish it
from other perhaps similar entities.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-A28 (Name attribute)
(see also the name datatype property)
- Has super-classes
-
rico:Appellation
- Is in domain of
-
rico:isOrWasNameOf
- Is in range of
-
rico:hasOrHadName
- Has sub-classes
-
rico:AgentName; rico:PlaceName; rico:Title
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:OccupationType
IRI:
https://www.ica.org/standards/RiC/ontology#OccupationType
- Label(s)
- Occupation Type [en]; Type d’occupation [fr]; Tipo de ocupación [es]
- Definition
- Categorization of a profession, trade, or craft pursued by a
Person in fulfilment of an Activity.
- Scope note
- The pursuit of an occupation involves the performance of an
Activity. Successful performance of the Activity is based on the ability to perform
related competencies successfully. Such competencies may be acquired through education
or experience, or a combination of both. The authority of the Person to pursue the
occupation may be derived tacitly or explicitly from an external Agent, based on a
demonstrated mastery of the competency. An occupation may be pursued independently by a
Person or a Group, thereby contributing to the fulfilment of the function (activity) of
the group. Should not be confused with Position where, for example, an agent with the
occupation type "lawyer" holds the position of "legal counsel" in an agency. Related to
but should not be confused with the domain or field of activity, such as an archivist
who works in the domain of archival science.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A30 (Occupation Type
attribute)
- Has super-classes
-
rico:ActivityType
-
rico:DemographicGroup
- Is in domain of
-
rico:isOrWasOccupationTypeOf
- Is in range of
-
rico:hasOrHadOccupationOfType
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-23: scope note: added.
Back to the table of contents | Back to top
Class: rico:OrganicProvenanceRelation
IRI:
https://www.ica.org/standards/RiC/ontology#OrganicProvenanceRelation
- Label(s)
- Organic Provenance Relation [en]; Relation de provenance organique [fr]; Relación de procedencia orgánica [es]
- Definition
- Connects at least one Record Resource or an Instantiation to at
least one Agent that creates or accumulates the Record Resource, receives it, or sends
it. The Record Resource(s) or Instantiation(s) is the source of the Relation, and the
Agent(s) is the target.
- Scope note
- This is the most general organic provenance relation. Use it
to connect a record resource or instantiation with an agent only if it is not possible
to use a narrower, more specific relation, for example Creation
Relation.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R026 and RiC-R026i
relations
- Has super-classes
-
rico:OrganicOrFunctionalProvenanceRelation
-
relationHasSource
min 1 (Instantiation
or
RecordResource)
-
relationHasTarget
min 1 Agent
- Is equivalent of
-
rico:organicProvenanceRelation_role Self
- Is in domain of
-
rico:organicProvenanceRelation_role
- Is in range of
-
rico:organicProvenanceRelation_role
- Has sub-classes
-
rico:AccumulationRelation; rico:CreationRelation
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-07: Renamed the relation in order to make it clearer (its name
was AgentOriginationRelation).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:OwnershipRelation
IRI:
https://www.ica.org/standards/RiC/ontology#OwnershipRelation
- Label(s)
- Ownership Relation [en]; Relation de propriété [fr]; Relación de posesión [es]
- Definition
- Connects at least one Group, Person or Position and at least a
Thing that these Agent(s) own(s) or owned. The Group(s), Person(s) or Position(s) is the
source of the Relation, and the Agent(s) is the target.
- Scope note
- Among other probably more rare use cases for archival
description, can be used between agents (a person owns a corporate body, a corporate
body owns a mechanism), or between agents and record resources.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R037 and RiC-R037i
relations
- Has super-classes
-
rico:AuthorityRelation
-
relationHasSource
min 1 (Group
or
Person
or
Position)
-
relationHasTarget
min 1 Thing
- Is equivalent of
-
rico:ownershipRelation_role Self
- Is in domain of
-
rico:ownershipRelation_role
- Is in range of
-
rico:ownershipRelation_role
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:Person
IRI:
https://www.ica.org/standards/RiC/ontology#Person
- Label(s)
- Person [en]; Personne [fr]; Persona [es]
- Definition
- An individual human being.
- Scope note
- Person is a kind of Agent. Most commonly, a human being
(biological person) has a single socially constructed identity or persona. Less common
though not rare, one or more personae in addition to the original persona which emerges
at or near birth may be associated with the human being over the course of that human
being’s lifetime. Such "alternative personae" are most often created by the original
person for specific purposes. The original persona may, in everyday discourse, be
regarded as “the real person”. Under some circumstances, an alternative persona might
eclipse or replace the original person (Mark Twain eclipsing Samuel Clemens; John Wayne
eclipsing Marion Mitchell Morrison), that is, the alternative identity becomes the
predominant identity. Less common is when two or more persons collaborate to create a
shared persona. A persona shared by two or more persons constitutes a kind of group.
Within the archival context, the description of a person commonly will focus on the
original associated persona, with alternative personae noted. Exceptionally, an
alternative persona may displace the original persona as the focus of the description.
Under some circumstances, for example, when record resources are associated with two or
more different personae of one person, describing the different personae as separate
though related persons may be desirable. Alternatively, a person may change their
identity over the course of their lifetime.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-E08 (Person
entity)
- Has super-classes
-
rico:Agent
- Disjoint with
-
rico:Position
- Is in domain of
-
rico:birthDate; rico:deathDate; rico:hasAncestor; rico:hasBirthDate; rico:hasBirthPlace; rico:hasChild; rico:hasDeathDate; rico:hasDeathPlace; rico:hasDescendant; rico:hasFamilyAssociationWith; rico:hasOrHadCorrespondent; rico:hasOrHadDemographicGroup; rico:hasOrHadEmployer; rico:hasOrHadOccupationOfType; rico:hasOrHadSpouse; rico:hasOrHadStudent; rico:hasOrHadTeacher; rico:hasSibling; rico:isAuthorOf; rico:isChildOf; rico:isOrWasEmployerOf; rico:isOrWasHolderOfIntellectualPropertyRightsOf; rico:isOrWasLeaderOf; rico:isOrWasMemberOf; rico:isOrWasOwnerOf; rico:knownBy; rico:knows; rico:knowsOf; rico:occupiesOrOccupied
- Is in range of
-
rico:hasAncestor; rico:hasAuthor; rico:hasChild; rico:hasDescendant; rico:hasFamilyAssociationWith; rico:hasOrHadCorrespondent; rico:hasOrHadEmployer; rico:hasOrHadIntellectualPropertyRightsHolder; rico:hasOrHadLeader; rico:hasOrHadMember; rico:hasOrHadOwner; rico:hasOrHadSpouse; rico:hasOrHadStudent; rico:hasOrHadTeacher; rico:hasSibling; rico:isBirthDateOf; rico:isBirthPlaceOf; rico:isChildOf; rico:isDeathDateOf; rico:isDeathPlaceOf; rico:isOrWasDemographicGroupOf; rico:isOrWasEmployerOf; rico:isOrWasOccupationTypeOf; rico:isOrWasOccupiedBy; rico:knownBy; rico:knows; rico:knowsOf
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2021-02-08: Removed one Restriction.
- 2020-10-23: Scope note: made separate paragraphs and updated. Disjoint
with: enriched. Objective: to make RiC-O compliant with RiC-CM v0.2.
- 2020-10-23: Scope note: made separate paragraphs and updated. Disjoint
with: enriched. Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:PhysicalLocation
IRI:
https://www.ica.org/standards/RiC/ontology#PhysicalLocation
- Label(s)
- Physical Location [en]; Localisation physique [fr]; Localización física de lugar [es]
- Definition
- A delimitation of the physical territory of a
Place.
- Scope note
- Used to describe basic human-readable text such as an address,
a cadastral reference, or less precise information found in a record. Use the
coordinates datatype property, or the Coordinates class to capture the geographical
coordinates of the Place. Use spatial relations (particularly 'has or had location') to
capture a relation between two places.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-A27 (Location
attribute)
- Has super-classes
-
rico:Thing
- Is in domain of
-
rico:hasOrHadCoordinates; rico:isOrWasPhysicalLocationOf
- Is in range of
-
rico:hasOrHadPhysicalLocation; rico:isOrWasCoordinatesOf
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the
skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the two 0.2 existing unnecessary
restrictions.
Back to the table of contents | Back to top
Class: rico:PlaceRelation
IRI:
https://www.ica.org/standards/RiC/ontology#PlaceRelation
- Label(s)
- Place Relation [en]; Relation impliquant un lieu [fr]; Relación con lugar [es]
- Definition
- Connects a Place and at least one Thing when the first is
associated with the existence and lifecycle of the second one. The Place is the source
of the Relation and the Thing(s) is the target.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R074 and RiC-R074i
relations
- Has super-classes
-
rico:Relation
-
relationHasSource 1 Place
-
relationHasTarget
min 1 Thing
- Is equivalent of
-
rico:placeRelation_role Self
- Is in domain of
-
rico:placeRelation_role
- Is in range of
-
rico:placeRelation_role
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:PlaceType
IRI:
https://www.ica.org/standards/RiC/ontology#PlaceType
- Label(s)
- Place Type [en]; Type de lieu [fr]; Tipo de lugar [es]
- Definition
- Categorization of a Place.
- Scope note
- Broadly, a Place may be a member of three broad categories:
jurisdiction, manmade structure, or a natural feature. Each of these three categories
can subdivided into narrower categories.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A32 (Place Type
attribute)
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isOrWasPlaceTypeOf
- Is in range of
-
rico:hasOrHadPlaceType
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
Back to the table of contents | Back to top
Class: rico:ProductionTechniqueType
IRI:
https://www.ica.org/standards/RiC/ontology#ProductionTechniqueType
- Label(s)
- Production Technique Type [en]; Type de technique de production [fr]; Tipo de técnica de producción [es]
- Definition
- The method used in the representation of information on an
instantiation.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-A33 (Production
Technique attribute)
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isProductionTechniqueTypeOf
- Is in range of
-
rico:hasProductionTechniqueType
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-23: Comment: updated. Objective: to make RiC-O compliant with
RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:Proxy
IRI:
https://www.ica.org/standards/RiC/ontology#Proxy
- Label(s)
- Proxy [en]; Proxy [fr]; Proxy [es]
- Definition
- A Proxy represents (stands for) a Record Resource as it exists
in a specific Record Set.
- Scope note
- Useful for handling in RDF the sequencing of records or
records sets in the context of a Record set. A Record Resource has only one Proxy in the
context of one specific Record Set. It may have many Proxies simultaneously or through
time.
- Possible mapping(s) with other external resources
- ORE Proxy (http://www.openarchives.org/ore/terms/Proxy)
- Has super-classes
-
rico:Concept
-
proxyFor 1 RecordResource
-
proxyIn 1 RecordSet
- Is in domain of
-
rico:proxyFor; rico:proxyIn
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:RecordResource
IRI:
https://www.ica.org/standards/RiC/ontology#RecordResource
- Label(s)
- Record Resource [en]; Ressource archivistique [fr]; Recurso documental [es]
- Definition
- Information produced or acquired and retained by an Agent in the
course of life or work activity.
- Scope note
- Record resource is a kind of Thing. Producing a record
resource may imply either its initial creation or a reuse of previous existing
information by combination, rearrangement, selecting, reformatting, etc. Record set,
record, and record part are kinds of record resource. A record resource is evidence of
the activity of an agent. More than one agent may be involved in the creation of a
record resource. The role of the agent in creating the record resource may take
different forms, for example, authoring of an individual record, accumulating a record
set, or arranging a record set. Though a record, record set, and record part, under most
circumstances, may be easily distinguished from one another, identifying the boundary of
each may frequently present particular challenges. Documentary forms provide the rules
governing the structure of many types of records, providing criteria for identifying a
record's boundary, and identifying its essential parts. Many records, though, do not
have well-established documentary forms, particularly in the case of digital records,
where it may be difficult to determine whether individual elements represented in
separate bitstreams are record parts, records, or record sets. For example, is
photographic information represented independently in a bitstream embedded in a text
document a record or a record part? Or is the same photographic information attached to
an email that maintains its independent representation, a record or a record part?
Information grouped for some purpose, for example, ZIP or TAR "file compression" for
saving storage space, presents a further challenge. One file comprises multiple
bitstreams subjected to techniques that remove bits that can be losslessly recovered
when decompressed. Under what circumstances is such a compressed bitstream a record or a
record set? Determining when an information object is a record, record set, or record
part is based on perspective and judgement exercised in a particular context. In one
context, the agent describing an information object may designate it a record, while
another agent in a different context may designate it a record part. Both designations
are supported by RiC-CM, and the significance of the difference for users of the records
is ameliorated by the fact that all of the attributes and relations employed in
describing record and record part are shared, as are many of the attributes and
relations employed in describing a record set.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-E02 (Record Resource
entity)
- Has super-classes
-
rico:Thing
- Is in domain of
-
rico:authenticityNote; rico:classification; rico:conditionsOfAccess; rico:conditionsOfUse; rico:describesOrDescribed; rico:documents; rico:evidences; rico:expressesOrExpressed; rico:hasAccumulator; rico:hasAddressee; rico:hasCollector; rico:hasCopy; rico:hasCreationDate; rico:hasCreator; rico:hasGeneticLinkToRecordResource; rico:hasOrHadAnalogueInstantiation; rico:hasOrHadDigitalInstantiation; rico:hasOrHadHolder; rico:hasOrHadInstantiation; rico:hasOrHadIntellectualPropertyRightsHolder; rico:hasOrHadMainSubject; rico:hasOrHadManager; rico:hasOrHadSubject; rico:hasOrHadTitle; rico:hasOrganicOrFunctionalProvenance; rico:hasOrganicProvenance; rico:hasPublicationDate; rico:hasPublisher; rico:hasReceiver; rico:hasReply; rico:hasSender; rico:history; rico:integrityNote; rico:isCopyOf; rico:isRecordResourceAssociatedWithRecordResource; rico:isReplyTo; rico:physicalOrLogicalExtent; rico:publicationDate; rico:recordResourceExtent; rico:recordResourceStructure; rico:scopeAndContent; rico:structure; rico:title
- Is in range of
-
rico:documentedBy; rico:hasCopy; rico:hasGeneticLinkToRecordResource; rico:hasReply; rico:isAccumulatorOf; rico:isAddresseeOf; rico:isCollectorOf; rico:isCopyOf; rico:isCreationDateOf; rico:isCreatorOf; rico:isEvidencedBy; rico:isOrWasAnalogueInstantiationOf; rico:isOrWasDescribedBy; rico:isOrWasDigitalInstantiationOf; rico:isOrWasExpressedBy; rico:isOrWasHolderOf; rico:isOrWasHolderOfIntellectualPropertyRightsOf; rico:isOrWasInstantiationOf; rico:isOrWasMainSubjectOf; rico:isOrWasManagerOf; rico:isOrWasSubjectOf; rico:isOrWasTitleOf; rico:isOrganicOrFunctionalProvenanceOf; rico:isOrganicProvenanceOf; rico:isPublicationDateOf; rico:isPublisherOf; rico:isReceiverOf; rico:isRecordResourceAssociatedWithRecordResource; rico:isReplyTo; rico:isSenderOf; rico:proxyFor
- Has sub-classes
-
rico:Record; rico:RecordPart; rico:RecordSet
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2021-02-08: Removed one Restriction.
- 2020-10-23: Scope note: made separate paragraphs plus very few
changes.
Back to the table of contents | Back to top
Class: rico:RecordResourceExtent
IRI:
https://www.ica.org/standards/RiC/ontology#RecordResourceExtent
- Label(s)
- Record Resource Extent [en]; Mesure d’une ressource archivistique [fr]; Extensión de recurso documental [es]
- Definition
- The quantity of information content, as human experienced,
contained in a Record Resource.
- Scope note
- The method and precision of expressing the quantity of
information represented in a Record Resource will vary according to the kind of record
resource being described, processing economy constraints, etc. For Record Sets, quantity
may be expressed as number of records, or, for analogue records in particular, by the
physical storage dimensions of the members of the Record Set. For individual Records or
Record Parts, quantity may be expressed in more precise terms.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-A35 (Record Resource
extent attribute)
- Has super-classes
-
rico:Extent
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-21: Changed a bit the definition and added change
notes.
- 2020-10-28: Class added in order to handle an accurate description of a
record resource extent
Back to the table of contents | Back to top
Class: rico:RecordResourceToInstantiationRelation
IRI:
https://www.ica.org/standards/RiC/ontology#RecordResourceToInstantiationRelation
- Label(s)
- Record Resource to Instantiation Relation [en]; Relation d’instanciation [fr]; Relación de recurso documental a instanciación [es]
- Definition
- Connects a Record Resource to one or more Instantiations that
instantiate it, and which either may exist or may have been lost or destroyed. The
Record Resource is the source of the Relation and the Instantiation(s) is the
target.
- Scope note
- In some situations, it may be useful or necessary to connect a
record resource to an instantiation that no longer exists or has been lost, when some of
its characteristics are known from a source, such as an old finding
aid.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R025 and RiC-R025i
relations
- Has super-classes
-
rico:Relation
-
relationHasSource 1 RecordResource
-
relationHasTarget
min 1 Instantiation
- Is equivalent of
-
rico:recordResourceToInstantiationRelation_role Self
- Is in domain of
-
rico:recordResourceToInstantiationRelation_role
- Is in range of
-
rico:recordResourceToInstantiationRelation_role
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:RecordSet
IRI:
https://www.ica.org/standards/RiC/ontology#RecordSet
- Label(s)
- Record Set [en]; Ensemble d’objets informationnels [fr]; Agrupación documental [es]
- Definition
- One or more records that are grouped together by an Agent based
on the records sharing one or more attributes or relations.
- Scope note
- Record set is a kind of Record Resource. The member records in
a Record Set may physically reside together, though physical proximity is not essential.
In a particular context, an Agent (for example, administrator, records manager,
archivist, end-user, etc.) may select the member records of a Record Set based on any
shared attribute or attributes, or any shared relation or relations. The grouping of the
records serves a purpose or purposes specific to the context of the Agent. For example,
all member records of a Record Set have been accumulated by the same Agent; have the
same Documentary Form Type; or are related to and document the same Activity. A Record
Set may represent the act of classifying the records in accordance with a formal
classification scheme that may be based on activity, subject, organizational structure,
or other criteria; an act of archival arrangement (for example, based on common
provenance); or some other selection and grouping that fulfils a particular purpose or
purposes (for example, a classification that reflects or supports the purposes of a
researcher). By exception, some records are brought together based on their not
belonging in the context of selection to other designated groups: a 'Miscellaneous'
series, for example. A Record Sset accumulated by an Agent in the course of life or work
activity should be described in a manner that preserves context and evidential value.
Record Sets may also contain other Record Sets. A Record Set or Record may
simultaneously be a member of more than one Record Set, and over the course of its
existence, a Record Set or Record may be a member of an indeterminate number of Record
Sets in an indeterminate number of contexts. Record Sets and Records contained within a
Record Set may be ordered into a sequence based on a common property or relation, or
common properties or relations (for example, alphabetical by agent or related place);
chronological order by creation date; or some other criterion (for example, an imposed
order by relevance).
- Mapping to RiC-CM 1.0
- Corresponds to RiC-E03 (Record Set
entity)
- Has super-classes
-
rico:RecordResource
- Is in domain of
-
rico:accruals; rico:accrualsStatus; rico:directlyIncludes; rico:hasOrHadAllMembersWithCategory; rico:hasOrHadAllMembersWithContentType; rico:hasOrHadAllMembersWithCreationDate; rico:hasOrHadAllMembersWithDocumentaryFormType; rico:hasOrHadAllMembersWithLanguage; rico:hasOrHadAllMembersWithLegalStatus; rico:hasOrHadAllMembersWithRecordState; rico:hasOrHadMostMembersWithCreationDate; rico:hasOrHadSomeMembersWithCategory; rico:hasOrHadSomeMembersWithContentType; rico:hasOrHadSomeMembersWithCreationDate; rico:hasOrHadSomeMembersWithDocumentaryFormType; rico:hasOrHadSomeMembersWithLanguage; rico:hasOrHadSomeMembersWithLegalStatus; rico:hasOrHadSomeMembersWithRecordState; rico:hasRecordSetType; rico:included; rico:includesOrIncluded; rico:includesTransitive; rico:isDirectlyIncludedIn; rico:isIncludedInTransitive; rico:isOrWasIncludedIn; rico:wasIncludedIn
- Is in range of
-
rico:directlyIncludes; rico:included; rico:includesOrIncluded; rico:includesTransitive; rico:isDirectlyIncludedIn; rico:isIncludedInTransitive; rico:isOrWasCategoryOfAllMembersOf; rico:isOrWasCategoryOfSomeMembersOf; rico:isOrWasContentTypeOfAllMembersOf; rico:isOrWasContentTypeOfSomeMembersOf; rico:isOrWasCreationDateOfAllMembersOf; rico:isOrWasCreationDateOfMostMembersOf; rico:isOrWasCreationDateOfSomeMembersOf; rico:isOrWasDocumentaryFormTypeOfAllMembersOf; rico:isOrWasDocumentaryFormTypeOfSomeMembersOf; rico:isOrWasIncludedIn; rico:isOrWasLanguageOfAllMembersOf; rico:isOrWasLanguageOfSomeMembersOf; rico:isOrWasLegalStatusOfAllMembersOf; rico:isOrWasLegalStatusOfSomeMembersOf; rico:isOrWasRecordStateOfAllMembersOf; rico:isOrWasRecordStateOfSomeMembersOf; rico:isRecordSetTypeOf; rico:proxyIn; rico:wasIncludedIn
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-23: comment: updated. Scope note: updated and made several
paragraphs. Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:RecordSetType
IRI:
https://www.ica.org/standards/RiC/ontology#RecordSetType
- Label(s)
- Record Set Type [en]; Type d’ensemble d’objets informationnels [fr]; Tipo de agrupación documental [es]
- Definition
- A broad categorization of the type of Record Set.
- Scope note
- Four instances of Record Set Type are included for now in
RiC-O; they also are instances of skos:Concept and, as such, part of a SKOS vocabulary.
Record Set Type may also be used (or extended) to categorize types of Record Set that
have not traditionally been considered archival, e.g. search result
list.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A36 (Record Set Type
attribute)
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isRecordSetTypeOf
- Is in range of
-
rico:hasRecordSetType
- Has members
-
ric-rst:Collection; ric-rst:File; ric-rst:Fonds; ric-rst:Series
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the
skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-23: scope note: updated. Objective: to make RiC-O compliant
with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:RepresentationType
IRI:
https://www.ica.org/standards/RiC/ontology#RepresentationType
- Label(s)
- Representation Type [en]; Type de représentation [fr]; Tipo de grabación [es]
- Definition
- Method of recording the content type of an
Instantiation
- Scope note
- Can be unmediated (which allows humans to receive the message
communicated without an intermediation of a device) and mediated (which needs a device
to decode the message). A lot of contemporary mediated types are digital. Each
representation type may present specific features: bit rate for audio, resolution for
digital images, encoding format for video etc. Depending on the type, specific
attributes may be added to describe their characteristics.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A37 (Representation Type
attribute)
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isRepresentationTypeOf
- Is in range of
-
rico:hasRepresentationType
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-23: Comment and scope note: updated. Objective: to make RiC-O
compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:Rule
IRI:
https://www.ica.org/standards/RiC/ontology#Rule
- Label(s)
- Rule [en]; Règle [fr]; Regla [es]
- Definition
- Conditions that govern the existence, responsibility, or
authority of an Agent; or the performance of an Activity by an Agent; or that contribute
to the distinct characteristics of things created or managed by an Agent.
- Scope note
- Rule is a kind of Thing. Rule can be related directly to
agent, activity, or anything created or managed by agents, such as a record resource or
instantiation. A rule may be unwritten or written or otherwise documented. Unwritten
rules may include though are not limited to the following: social mores, customs, or
community expectations. Written rules may include though are not limited to the
following: constitutions, legislation, acts (legal), statutes, legal codes, ordinances,
charters, mission statements, regulations, policies, procedures, instructions, codes of
conduct or ethics, professional standards, work assignments, or work plans. The source
or sources of some rules governing the existence or activity of an agent may be external
(for example, expressed in elections, social mores, customs, community expectations,
laws, regulations, standards, and best practice codes), while others may be expressed
within the immediate context of an agent (for example, policies, or written or verbal
instructions). The evidence for identifying rules may be found in their entirety in one
documentary source (for example, a law or regulation) or may be found in two or more
sources. Rule should not be confused with the one or more documentary sources that serve
as evidence of its identity. A documentary source is a record.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-E16 (Rule
entity)
- Has super-classes
-
rico:Thing
- Is in domain of
-
rico:hasOrHadRuleType; rico:hasOrHadTitle; rico:history; rico:isOrWasEnforcedBy; rico:isOrWasExpressedBy; rico:isRuleAssociatedWith; rico:issuedBy; rico:regulatesOrRegulated; rico:title
- Is in range of
-
rico:expressesOrExpressed; rico:isAssociatedWithRule; rico:isOrWasRegulatedBy; rico:isOrWasResponsibleForEnforcing; rico:isOrWasRuleTypeOf; rico:isOrWasTitleOf; rico:isResponsibleForIssuing
- Has sub-classes
-
rico:Mandate
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2021-02-11: Updated the definition (rdfs:comment) and scope note, as
they were recently changed in RiC-CM 0.2 full draft.
- 2020-10-23: Scope note: made separate paragraphs and updated.
Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Class: rico:RuleType
IRI:
https://www.ica.org/standards/RiC/ontology#RuleType
- Label(s)
- Rule Type [en]; Type de règle [fr]; Tipo de regla [es]
- Definition
- Categorization of a Rule.
- Scope note
- For example, for rules that can be applied to record resources
: access rule, use rule, etc.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A45 (Rule Type
attribute).
- Has super-classes
-
rico:Type
- Is in domain of
-
rico:isOrWasRuleTypeOf
- Is in range of
-
rico:hasOrHadRuleType
- Has sub-classes
-
rico:MandateType
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: added a
rico:RiCCMCorrespondingComponent.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-04-19: Removed the 0.2 existing unnecessary
restriction.
- 2020-10-19: Class added along with hasRuleType and isRuleTypeOf object
properties.
Back to the table of contents | Back to top
Class: rico:SequentialRelation
IRI:
https://www.ica.org/standards/RiC/ontology#SequentialRelation
- Label(s)
- Sequential Relation [en]; Relation séquentielle [fr]; Relación secuencial [es]
- Definition
- Connects at least one Thing to at least one other Thing that
follows or followed it in some sequence. The Relation is oriented from the first
Thing(s) in the sequence to the following one(s): the first Thing(s) is the source, and
the following Thing(s) is the target.
- Scope note
- The relation does not specify the criteria used for ordering
the sequence. There may be zero to many intermediate entities, ignored or unknown, in
the sequence between the two connected things. Can be used, for example, for specifying
that a record "has next" another record within a record set.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R008 and RiC-R008i
relations
- Has super-classes
-
rico:Relation
-
relationHasSource
min 1 Thing
-
relationHasTarget
min 1 Thing
- Is equivalent of
-
rico:sequentialRelation_role Self
- Is in domain of
-
rico:sequentialRelation_role
- Is in range of
-
rico:sequentialRelation_role
- Has sub-classes
-
rico:TemporalRelation
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:TeachingRelation
IRI:
https://www.ica.org/standards/RiC/ontology#TeachingRelation
- Label(s)
- Teaching Relation [en]; Relation entre enseignants et étudiants [fr]; Relación académica entre profesor y alumno [es]
- Definition
- Connects at least one Person to at least another Person who is
or was their student. The Relation is oriented from the teacher(s) to the student(s):
the teacher Person(s) is the source of the Relation, and the student Person(s) is the
target.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R053 and RiC-R053i
relations
- Has super-classes
-
rico:KnowingRelation
-
relationHasSource
min 1 Person
-
relationHasTarget
min 1 Person
- Is equivalent of
-
rico:teachingRelation_role Self
- Is in domain of
-
rico:teachingRelation_role
- Is in range of
-
rico:teachingRelation_role
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment).
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:TemporalRelation
IRI:
https://www.ica.org/standards/RiC/ontology#TemporalRelation
- Label(s)
- Temporal Relation [en]; Relation temporelle [fr]; Relación temporal [es]
- Definition
- Connects at least one Thing to at least one other Thing that
follows it in chronological order. The Relation is oriented chronologically: the
preceding Thing(s) is the source of the Relation, the following Thing(s) is the
target.
- Scope note
- There may be zero to many intermediate entities, ignored or
unknown, in the chronological sequence between the connected entities.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R009 and RiC-R009i
relations
- Has super-classes
-
rico:SequentialRelation
-
relationHasSource
min 1 Thing
-
relationHasTarget
min 1 Thing
- Is equivalent of
-
rico:temporalRelation_role Self
- Is in domain of
-
rico:temporalRelation_role
- Is in range of
-
rico:temporalRelation_role
- Has sub-classes
-
rico:AgentTemporalRelation; rico:DerivationRelation
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the
skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:TypeRelation
IRI:
https://www.ica.org/standards/RiC/ontology#TypeRelation
- Label(s)
- Type Relation [en]; Relation de catégorisation [fr]; Tipo de relación [es]
- Definition
- Connects a category (a Type) and at least one Thing that belongs
to this category. The Type(s) is the source of the Relation, and the Thing(s) is the
target.
- Scope note
- may be useful at least for some types (e.g. demographic
group)
- Has super-classes
-
rico:Relation
-
relationHasSource 1 Type
-
relationHasTarget
min 1 Thing
- Is equivalent of
-
rico:typeRelation_role Self
- Is in domain of
-
rico:typeRelation_role
- Is in range of
-
rico:typeRelation_role
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Class: rico:UnitOfMeasurement
IRI:
https://www.ica.org/standards/RiC/ontology#UnitOfMeasurement
- Label(s)
- Unit Of Measurement [en]; Unité de mesure [fr]; Unidad de medida [es]
- Definition
- A definite magnitude of a quantity, defined and adopted by
convention or by law, that is used as a standard for measurement of the same kind of
quantity. Can be spacial units (cm, m), weight (g, kg), time (s, h), storage (MB, TB) or
more informal units used in the archival context like number of boxes, pages or
words.
- Has super-classes
-
rico:Concept
- Is in domain of
-
rico:isUnitOfMeasurementOf
- Is in range of
-
rico:hasUnitOfMeasurement
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added an xml:lang attribute to the
rdfs:comment.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-10-28: Class added in order to be able to handle units of
measurement as full entities.
Back to the table of contents | Back to top
Class: rico:WorkRelation
IRI:
https://www.ica.org/standards/RiC/ontology#WorkRelation
- Label(s)
- Work Relation [en]; Relation de travail [fr]; Relación profesional [es]
- Definition
- Connects at least two Agents that have or had some type of work
relation in the course of their activities. This Relation is not
oriented.
- Mapping to RiC-CM 1.0
- Class implementation of RiC-R046 and RiR046i
relations
- Has super-classes
-
rico:AgentToAgentRelation
-
relationConnects
min 2 Agent
- Is equivalent of
-
rico:workRelation_role Self
- Is in domain of
-
rico:workRelation_role
- Is in range of
-
rico:workRelation_role
- Change note(s)
- 2023-12-06: Improved the description of the Relation class
(rdfs:comment) by clearly specifying how it is directed.
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment).
- 2023-11-08: In order to get a system of rolified Relation classes:
added an equivalentClass object property; replaced the specific object
properties by the generic ones in the subClassOf declarations.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype properties
rico:accruals | rico:accrualsStatus | rico:altimetricSystem | rico:altitude | rico:authenticityNote | rico:authorizingMandate | rico:beginningDate | rico:birthDate | rico:carrierExtent | rico:classification | rico:conditionsOfAccess | rico:conditionsOfUse | rico:creationDate | rico:date | rico:dateQualifier | rico:deathDate | rico:destructionDate | rico:endDate | rico:expressedDate | rico:generalDescription | rico:geodesicSystem | rico:geographicalCoordinates | rico:height | rico:history | rico:identifier | rico:instantiationExtent | rico:instantiationStructure | rico:integrityNote | rico:lastModificationDate | rico:latitude | rico:length | rico:location | rico:longitude | rico:measure | rico:modificationDate | rico:name | rico:normalizedDateValue | rico:normalizedValue | rico:physicalCharacteristicsNote | rico:physicalOrLogicalExtent | rico:productionTechnique | rico:publicationDate | rico:qualityOfRepresentationNote | rico:quantity | rico:recordResourceExtent | rico:recordResourceStructure | rico:referenceSystem | rico:relationCertainty | rico:relationSource | rico:relationState | rico:ruleFollowed | rico:scopeAndContent | rico:structure | rico:technicalCharacteristics | rico:textualValue | rico:title | rico:type | rico:unitOfMeasurement | rico:usedFromDate | rico:usedToDate | rico:width
Datatype property: rico:accruals
IRI:
https://www.ica.org/standards/RiC/ontology#accruals
- Label(s)
- accruals [en]; accroissements [fr]; ingresos [es]
- Definition
- Information on the anticipated accession(s) to the Record
Set.
- Scope note
- See also accrualsStatus
- Mapping to RiC-CM 1.0
- corresponds to RiC-A01 (Accruals
attribute)
- Example(s)
-
"Accruing - there is an agreement with the creator that additional snapshots of their email directory will be accessioned at yearly intervals" [en]
-
"Non-accruing" [en]
-
"Unknown" [en]
- Has domain
-
rico:RecordSet
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the IRI, mapping to RiC-CM
(rico:RiCCMCorrespondingComponent), labels, skos:scopeNote, examples
(skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:accrualsStatus
IRI:
https://www.ica.org/standards/RiC/ontology#accrualsStatus
- Label(s)
- accruals status [en]; statut des accroissements [fr]; estado de los ingresos [es]
- Definition
- Information on the status of possible accruals
- Scope note
- A text statement or single words such as “Closed” to indicate
that no additional Record Resource will (or is anticipated to) be added to the Record
Set; “Open” to indicate that additional records or record sets will (or are expected to)
be added to the Record Set; or “Unknown” to indicate that this information is not
available, for example. See also accruals
- Mapping to RiC-CM 1.0
- specialization of RiC-A01 (Accruals
attribute)
- Has domain
-
rico:RecordSet
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the IRI, mapping to RiC-CM
(rico:RiCCMCorrespondingComponent), labels, description (rdfs:comment),
skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: scope note : updated. Objective: to make RiC-O compliant
with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:altitude
IRI:
https://www.ica.org/standards/RiC/ontology#altitude
- Label(s)
- altitude [en]; altitude [fr]; altitud [es]
- Definition
- The height of a Place above a reference level, especially above
sea level.
- Scope note
- Property of the Coordinates class. If you don't use this
class, use geographicalCoordinates property, a property of Place class.
- Has super-properties
-
rico:measure
- Has domain
-
rico:Coordinates
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:authenticityNote
IRI:
https://www.ica.org/standards/RiC/ontology#authenticityNote
- Label(s)
- authenticity note [en]; note sur l’authenticité [fr]; nota de autenticidad [es]
- Definition
- Description of the evidence that a Record Resource or
Instantiation is what it purports to be, was created or sent by the said Agent at the
said time, and has not been tampered with, corrupted, or forged.
- Scope note
- May be used in a Record Set description when its value is
shared by some or all members of the Record Set. For digital records, it may include
results from automated means of checking the validity of signatures and timestamp. In
particular cases it may be contextually related to the state attribute, for example, a
document can be an original or a copy, either of which can be authentic or a forgery.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A03 (Authenticity Note
attribute)
- Example(s)
-
"The letter is unsigned." [en]
-
"The deed is digitally signed by the Notary. The electronic signature validity cannot be assessed, but the content was not modified from the moment of signing." [en]
-
"The timestamp exists but cannot be verified." [en]
-
"The record bears signatures." [en]
- Has domain
-
rico:Instantiation
or
rico:RecordResource
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: examples added. Objective: to make RiC-O compliant with
RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:authorizingMandate
IRI:
https://www.ica.org/standards/RiC/ontology#authorizingMandate
- Label(s)
- authorizing mandate [en]; mandat [fr]; norma de control [es]
- Definition
- Information on a Mandate that authorizes an Agent to perform an
Activity.
- Scope note
- Provided for usability reasons. May be deprecated and removed
later on. Use only if you don't use the Mandate class for handling
mandates.
- Has super-properties
-
rico:ruleFollowed
- Has domain
-
rico:Agent
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:birthDate
IRI:
https://www.ica.org/standards/RiC/ontology#birthDate
- Label(s)
- birth date [en]; date de naissance [fr]; fecha de nacimiento [es]
- Definition
- Date at which a Person was born.
- Scope note
- Provided for usability reasons. May be deprecated and removed
later on. Use only if you don't use Date classes for handling dates.
- Mapping to RiC-CM 1.0
- Datatype property specialized implementation of
RiC-E18 (Date entity)
- Has super-properties
-
rico:beginningDate
- Has domain
-
rico:Person
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:carrierExtent
IRI:
https://www.ica.org/standards/RiC/ontology#carrierExtent
- Label(s)
- carrier extent [en]; mesure du support [fr]; extensión del soporte [es]
- Definition
- Number of physical units and/or physical dimensions of the
carrier of an Instantiation. In order to manage an Instantiation of a record resource it
is necessary to note the extent of the carrier as well as that of the Instantiation
itself. Whether it is necessary to note dimensions, the number of relevant units, or
both, depends on the nature of the carrier and particular business needs.
- Scope note
- For digital resources, it may be used to indicate the size of
storage capacity (disk, tape, film, etc.). Carrier extent should not be confused with
instantiation extent or record resource extent. For a given Record Resource, the
instantiation extent may vary, based on format, density of information on the carrier,
etc. For example, a CD with a storage capacity of 700 MB (carrier extent) might hold a
record of 1500 words (record resource extent) represented in two versions, one a Word
document with an instantiation extent of 3 KB and the other a PDF file with an
instantiation extent of 5 KB.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A04 (Carrier Extent
attribute)
- Example(s)
-
"1 page" [en]
-
"32.5 x 49 cm (piece of parchment)" [en]
-
"3 GB (1 USB key)" [en]
- Has super-properties
-
rico:physicalOrLogicalExtent
- Has domain
-
rico:Instantiation
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition and scope note updated. Examples added.
Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:classification
IRI:
https://www.ica.org/standards/RiC/ontology#classification
- Label(s)
- classification [en]; classification [fr]; clasificación [es]
- Definition
- A term, number or alphanumeric string that is usually taken from
an external classification vocabulary or scheme that qualifies a Record Resource.
- Scope note
- May be used in a Record Set description when its value is
shared by some or all members of the record set. This datatype property is not to be
confused with Identifier although, in some cases, the information may be the
same.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A07 (Classification
attribute)
- Example(s)
-
"BUD-01-F002 (classification number from a corporate file plan)" [en]
-
"human resource management" [en]
-
"student registration" [en]
-
"financial affairs" [en]
-
"digitized items" [en]
- Has domain
-
rico:RecordResource
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition and scope note updated. Examples added.
Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:conditionsOfAccess
IRI:
https://www.ica.org/standards/RiC/ontology#conditionsOfAccess
- Label(s)
- conditions of access [en]; conditions d’accès [fr]; condiciones de acceso [es]
- Definition
- Terms and circumstances affecting the availability of a Record
Resource or an Instantiation for consultation.
- Scope note
- May be used in a Record Set description when its value is
shared by some or all members of the Record Set. The attribute provides information
about the accessibility of a Record Resource, as well as the physical, technical or
legal limitations that exist for providing access to it.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A08 (Conditions of Access
attribute)
- Example(s)
-
"Open" [en]
-
"Closed under data protection legislation" [en]
-
"Closed as awaiting conservation treatment" [en]
-
"Acceso libre a través de los terminales de consulta" [es]
-
"The Archives cannot provide VHS reader to access the content of the tape" [en]
-
"Recognita software, min. version 3.0, is needed in order to open the file" [en]
-
"Closed for 30 years" [en]
- Has domain
-
rico:Instantiation
or
rico:RecordResource
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition and scope note updated. Examples added.
Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:conditionsOfUse
IRI:
https://www.ica.org/standards/RiC/ontology#conditionsOfUse
- Label(s)
- conditions of use [en]; conditions d’utilisation [fr]; condiciones de uso [es]
- Definition
- Terms and circumstances affecting the use of a Record Resource
or an Instantiation after access has been provided. Includes conditions governing
reproduction of the Record Resource under applicable copyright (intellectual property)
and/or property legislation or due to conservation status.
- Scope note
- May be used in a Record Set description when its value is
shared by some or all members of the Record Set.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A09 (Conditions of Use
attribute)
- Example(s)
-
"Permission of the copyright owner must be obtained before use" [en]
-
"Cannot be copied using warm light copying machines or photographed using flashlight" [en]
- Has domain
-
rico:Instantiation
or
rico:RecordResource
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition updated. Examples added. Objective: to make
RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:creationDate
IRI:
https://www.ica.org/standards/RiC/ontology#creationDate
- Label(s)
- creation date [en]; date de création [fr]; fecha de creación [es]
- Definition
- Date at which an entity was created.
- Scope note
- Provided for usability reasons. May be deprecated and removed
later on. Use only if you don't use Date classes for handling dates.
- Mapping to RiC-CM 1.0
- Datatype property specialized implementation of
RiC-E18 (Date entity)
- Has super-properties
-
rico:beginningDate
- Has domain
-
rico:Thing
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:dateQualifier
IRI:
https://www.ica.org/standards/RiC/ontology#dateQualifier
- Label(s)
- date qualifier [en]; qualificatif de la date [fr]; calificador de fecha [es]
- Definition
- A human readable qualification of a Date to indicate the level
of precision or certainty.
- Scope note
- Most often, this human readable expression of the accuracy of
the date is used along with an ISO 8601 representation of the date. The qualifier can
also be expressed as a machine-readable value, using the EDTF standard (thus, a
specialization of the normalizedDateValue datatype property).
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A13 (Date Qualifier
attribute)
- Example(s)
-
"approximate" [en]
-
"circa" [en]
-
"end unknown" [en]
- Has domain
-
rico:Date
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-10-10: Updated the rdfs:comment, skos:scopeNote and examples, in
order to make this datatype property fully compliant with RiC-CM 1.0
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: examples added. Objective: to make RiC-O compliant with
RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:deathDate
IRI:
https://www.ica.org/standards/RiC/ontology#deathDate
- Label(s)
- death date [en]; date de décès [fr]; fecha de muerte [es]
- Definition
- Date at which a Person died.
- Scope note
- Provided for usability reasons. May be deprecated and removed
later on. Use only if you don't use Date classes for handling dates.
- Mapping to RiC-CM 1.0
- Datatype property specialized implementation of
RiC-E18 (Date entity)
- Has super-properties
-
rico:endDate
- Has domain
-
rico:Person
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:destructionDate
IRI:
https://www.ica.org/standards/RiC/ontology#destructionDate
- Label(s)
- destruction date [en]; date de destruction [fr]; fecha de destrucción [es]
- Definition
- Date at which an entity was deleted.
- Scope note
- Provided for usability reasons. May be deprecated and removed
later on. Use only if you don't use Date classes for handling dates.
- Mapping to RiC-CM 1.0
- Datatype property specialized implementation of
RiC-E18 (Date entity)
- Has super-properties
-
rico:endDate
- Has domain
-
rico:Thing
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-12: Added a new rdfs:label in Spanish.
- 2023-10-12: Renamed deletion into destruction.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:expressedDate
IRI:
https://www.ica.org/standards/RiC/ontology#expressedDate
- Label(s)
- expressed date [en]; date en langage naturel [fr]; fecha expresada [es]
- Definition
- Natural language expression of a date. This property is a
specialization of the name property. In order that the precise meaning of the date can
be understood, information such as the calendar used or other specific context should be
included.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A19 (Expressed Date
attribute)
- Example(s)
-
"October 24, 1999 (month day, year)" [en]
-
"1925-1966 (date range)" [en]
-
"15 thermidor an IV (calendrier révolutionnaire français)" [fr]
-
"8 avril 1258 (a. st., style de Pâques)" [fr]
-
"XVIIe siècle" [fr]
-
"The Middle Ages" [en]
-
"Die jovis ultima mensis martii anno domini millesimo quingentesimo quadragesimo ante Pascha" [la]
-
"1550-1553, 1555 (date range)" [en]
-
"One of the years 1550, 1551, 1553, 1555" [en]
-
"All of the years 1550, 1551, 1553, 1555" [en]
-
"The second semester of 1951 to 1952 (academic reference system)" [en]
- Has super-properties
-
rico:name; rico:textualValue
- Has domain
-
rico:Date
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-10-10: Updated the rdfs:comment and skos:examples in order to make
this property fully compliant with RiC-CM 1.0. Made it a subproperty of
rico:name.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: examples added. Objective: to make RiC-O compliant with
RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:generalDescription
IRI:
https://www.ica.org/standards/RiC/ontology#generalDescription
- Label(s)
- general description [en]; description générale [fr]; descripción general [es]
- Definition
- General information about an entity. General description may be
used to describe any entity. There are different appropriate uses for general
description. First, while it is recommended that more specific properties be used in
describing an entity, it may be desirable, for economic or other reasons, to describe
two or more specific properties together. Second, general description may be used to
describe one or more characteristics that are not otherwise accommodated in RiC-O.
Third, it may be used to provide a succinct summary or abstract description in addition
to more detailed specific description.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A43 (General Description
attribute)
- Example(s)
-
"Le massif du Mont-Blanc est un massif des Alpes partagé entre la France, l'Italie et la Suisse. Il abrite le mont Blanc, plus haut sommet d'Europe occidentale qui culmine à 4 809 mètres (altitude relevée en 2015). Il est traversé par le tunnel du Mont-Blanc, entre Chamonix dans la vallée de l'Arve et Courmayeur dans la vallée d'Aoste." [fr]
-
"Thomas Blaikie (1750-1838) est un botaniste et jardinier écossais. Il a dessiné notamment les jardins de Malmaison et Bagatelle." [fr]
-
"The Senate is the academic governing body of the University of Strathclyde and is responsible for all academic matters including academic standards and quality. Meetings of the Senate are chaired by the Principal and the membership is drawn entirely from within the University, comprising academic and research staff. (about a corporate body, University of Strathclyde Senate)" [en]
-
"This activity involves regulating the nursing profession by conducting examinations and on-going education for nurses, maintaining rolls of those qualified as enrolled or registered nurses, midwives, psychiatric, and other specialised nurses. It also covers hearing disciplinary charges against nurses (and where necessary, removing them temporarily or permanently from the registers), as well as promoting the nursing profession. (about an activity, Nursing Profession Regulation)" [en]
- Has domain
-
rico:Thing
- Has range
- rdfs:Literal
- Has sub-properties
-
rico:scopeAndContent
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the IRI, mapping to RiC-CM
(rico:RiCCMCorrespondingComponent), labels, description (rdfs:comment), examples
(skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:geographicalCoordinates
IRI:
https://www.ica.org/standards/RiC/ontology#geographicalCoordinates
- Label(s)
- geographical coordinates [en]; coordonnées géographiques [fr]; coordenadas geográficas [es]
- Definition
- Longitudinal and latitudinal information about a Place.
- Scope note
- Provided for usability reasons. May be deprecated and removed
later on. Use only if you don't use PhysicalLocation and Coordinates classes with Place.
Coordinates may be based on ISO 6709 Standard representation of geographic point
location by coordinates.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A11 (Coordinates
attribute)
- Example(s)
-
"Latitude 50°40′46,461″N, Longitude 95°48′26,533″W, Height 123,45m (ISO 6709/D)" [en]
-
"Latitude 35.89421911, Longitude 139.94637467 (ISO 6709/F)" [en]
- Has domain
-
rico:Place
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition and scope note updated. Examples added.
Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:history
IRI:
https://www.ica.org/standards/RiC/ontology#history
- Label(s)
- history [en]; histoire [fr]; historia [es]
- Definition
- Summary of the development of an entity throughout its
existence.
- Scope note
- For a record set, may be used to summarize the history of the
Record Set itself, or additionally to summarize the history of some or all members of
the Record Set. Should not be confused with the scope and content
property.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A21 (History
attribute)
- Example(s)
-
"The manuscripts are part of the collections of Robert Harley (d 1724) and Edward Harley (d 1741), 1st and 2nd Earls of Oxford, that were brought by Parliament and transferred to the British Museum in 1753. Those materials were then separated into this collection and those for Harley Charters and Harley Rolls and became part of the collections of the British Library in 1972. (about a Record Set)" [en]
-
"Nacido en Barbastro en 1892, donde realizó sus primeros estudios con los escolapios. Licenciado en Derecho por la Universidad de Zaragoza, aprobó las oposiciones al cuerpo nacional de notarios… (sobre una persona)" [es]
-
"El primer sorteo de lotería se celebró el 13 de mayo de 1771, siendo desarrollado por la Real Lotería General de Nueva España… (sobre una actividad)" [es]
- Has domain
-
rico:Agent
or
rico:Event
or
rico:Instantiation
or
rico:Place
or
rico:RecordResource
or
rico:Rule
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote, domain, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Domains updated. Examples added. Objective: to make RiC-O
compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:identifier
IRI:
https://www.ica.org/standards/RiC/ontology#identifier
- Label(s)
- identifier [en]; identifiant [fr]; identificador [es]
- Definition
- A word, number, letter, symbol, or any combination of these used
to uniquely identify or reference an individual instance of an entity within a specific
information domain. Can include Global Persistent Identifiers (globally unique and
persistently resolvable identifier for the entity) and/or Local Identifiers. Both the
domain within which the identifier is unique, and the rules used in forming the
identifier value should be provided with the identifier value.
- Scope note
- Use only if you don't use Identifier class for handling
identifiers. Within a given domain (a closed system), identifiers are used to uniquely
reference instances of an entity. Identifiers are instruments of control that facilitate
management of the entities within the domain. The formulation of identifiers commonly is
based on rules. In addition to an identifier needing to be unique within a domain, it is
also highly desirable that it be persistent, that is, that the identifier uniquely
identifies the entity over time. A variety of organizations provide rules for the
formation of identifiers, and services designed to facilitate the persistence of
identifiers. Such identifiers are commonly referred to as Persistent Identifiers (or
PIDs). PIDs conform to RFC 3986, but impose additional rules. Common examples are
Archival Resource Keys (ARKs) and Digital Object Identifiers (DOIs). Within the global
environment of the Internet, there are special rules for the formation of identifiers to
ensure that they are unique within the domain of the Internet. Such identifiers must
conform to the Internet Engineering Task Force (IETF) Uniform Resource Identifier rules
(RFC 3986).
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A22 (Identifier
attribute)
- Example(s)
-
"http://n2t.net/ark:/99166/w6v1266v (example of an Archival Resource Key for a record)" [en]
-
"http://n2t.net/ark:/99166/w6tz44ht (example of an Archival Resource Key for a person)" [en]
-
"http://isni.org/0000000073572182 (example of a persistent International Standard Name Identifier for a person)" [en]
-
"BUD-01-F002 (example of a classification number from a corporate file plan)" [en]
-
"NAS1/A/1.1 (example of a local identifier for a record)" [en]
-
"F 1204 (example of a local identifier for a record set assigned by a repository)" [en]
-
"B-000091 (example of a unique identifier for an instantiation assigned by a repository)" [en]
- Has domain
-
rico:Thing
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition and scope note updated. Examples added.
Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:instantiationExtent
IRI:
https://www.ica.org/standards/RiC/ontology#instantiationExtent
- Label(s)
- Instantiation extent [en]; mesure de l’instanciation [fr]; soporte de instanciación [es]
- Definition
- Countable characteristics of an Instantiation expressed as a
quantity.
- Scope note
- Instantiation extent should not be confused with record
resource extent or carrier extent. For a given Record Resource, the instantiation extent
may vary, based on format, density of information on the carrier, etc. For example, a CD
with a storage capacity of 700 MB (carrier extent) might hold a record of 1500 words
(record resource extent) represented in two versions, one a Word document with an
instantiation extent of 3 KB and the other a PDF file with an instantiation extent of 5
KB.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A23 (Instantiation Extent
attribute)
- Example(s)
-
"The register has 345 written folios" [en]
-
"Size of PDF file: 1.5 MB" [en]
-
"234 linear metres" [en]
- Has super-properties
-
rico:physicalOrLogicalExtent
- Has domain
-
rico:Instantiation
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Scope note updated. Examples added. Objective: to make
RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:instantiationStructure
IRI:
https://www.ica.org/standards/RiC/ontology#instantiationStructure
- Label(s)
- Instantiation structure [en]; structure de l’instanciation [fr]; estructura de la instanciación [es]
- Definition
- Information about the physical arrangement and composition of an
Instantiation.
- Mapping to RiC-CM 1.0
- Specialization of RiC-A40 (Structure
attribute)
- Has super-properties
-
rico:structure
- Has domain
-
rico:Instantiation
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition fixed. Objective: to make RiC-O compliant
with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:integrityNote
IRI:
https://www.ica.org/standards/RiC/ontology#integrityNote
- Label(s)
- integrity note [en]; note sur l'intégrité [fr]; nota de integridad [es]
- Definition
- Information about the known intellectual completeness of a
Record Resource.
- Scope note
- May be used in a Record Set description when its value is
shared by some or all members of the Record Set. The information about integrity may be
generated manually or automatically. Not to be confused with the physical completeness
of the instantiation, which is covered by the physical characteristics note attribute.
The integrity of a Record Resource and the physical characteristics note of an
Instantiation may be complementary. This attribute also covers any additions to or
removal of original information.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A24 (Integrity Note
attribute)
- Example(s)
-
"For record set: series of letters, one is missing so the integrity is compromised." [en]
-
"A web page (HTML, 15 images, 2 CSS, 1 javascript), with 5 images missing." [en]
-
"Part of the text is missing (because a corner on the instantiation was cut out, which is a physical characteristic). See also the examples of physicalCharacteristics." [en]
-
"Line three of a hand-written letter was cut out and a replacement text was inserted by an unknown person." [en]
- Has domain
-
rico:RecordResource
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the IRI, mapping to RiC-CM
(rico:RiCCMCorrespondingComponent), labels, description (rdfs:comment),
skos:scopeNote, domain, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Scope note and examples added. Objective: to make RiC-O
compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:lastModificationDate
IRI:
https://www.ica.org/standards/RiC/ontology#lastModificationDate
- Label(s)
- last modification date [en]; date de dernière modification [fr]; fecha de última modificación [es]
- Definition
- Date at which an entity was last updated.
- Scope note
- Provided for usability reasons. May be deprecated and removed
later on. Use only if you don't use Date classes for handling dates.
- Mapping to RiC-CM 1.0
- Datatype property specialized implementation of
RiC-E18 (Date entity)
- Has super-properties
-
rico:modificationDate
- Has domain
-
rico:Thing
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:location
IRI:
https://www.ica.org/standards/RiC/ontology#location
- Label(s)
- location [en]; localisation [fr]; localización [es]
- Definition
- A delimitation of the physical territory of a Place. Used to
describe basic human-readable text such as an address, a cadastral reference, or less
precise information found in a Record.
- Scope note
- Use only if you don't use PhysicalLocation class with Place.
Use the geographicalCoordinates property, or the Coordinates class, to record the
geographical coordinates of the Place. Use the spatial relations (particularly 'has or
had location') to capture a relation between two places.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A27 (Location
attribute)
- Example(s)
-
"25 rue Saint-Denis à Paris" [fr]
-
"Montreal (city in Canada)" [en]
- Has domain
-
rico:Place
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition and scope note updated. Examples added.
Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:modificationDate
IRI:
https://www.ica.org/standards/RiC/ontology#modificationDate
- Label(s)
- modification date [en]; date de modification [fr]; fecha de modificación [es]
- Definition
- Date of the modification of an entity.
- Scope note
- Provided for usability reasons. May be deprecated and removed
later on. Use only if you don't use Date classes for handling dates.
- Mapping to RiC-CM 1.0
- Datatype property specialized implementation of
RiC-E18 (Date entity)
- Has super-properties
-
rico:date
- Has domain
-
rico:Thing
- Has range
- rdfs:Literal
- Has sub-properties
-
rico:lastModificationDate
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:name
IRI:
https://www.ica.org/standards/RiC/ontology#name
- Label(s)
- name [en]; nom [fr]; nombre [es]
- Definition
- A label, title or term designating an entity in order to make it
distinguishable from other similar entities.
- Scope note
- Use only if you don't use Name class for handling names.
Provides brief information about the content or other individual characteristics of the
entity being described, necessary to distinguish it from other perhaps similar
entities.
- Mapping to RiC-CM 1.0
- Corrresponds to RiC-A28 (Name
attribute)
- Example(s)
-
"The Letter of Neacsu from Campulung to the Mayor of Brasov (about a Record)" [en]
-
"Digital copy of the Pomarius archival inventory from 1575 (about an Instantiation)" [en]
-
"D-Day (about a Date or Event)" [en]
-
"Halloween 2016 (about a Date)" [en]
-
"Fundraising, University of Glasgow (about an Activity)" [en]
-
"Providing hearing services (about an Activity)" [en]
-
"Nelson Mandela (about a Person)" [en]
-
"Papers of the Earls of Liverpool (about a Record Set)" [en]
-
"Paris (about a Place)" [en]
-
"Prime Minister (about a Position)" [en]
-
"Sketch Map of the Qatar Peninsula (about a Record)" [en]
- Has domain
-
rico:Thing
- Has range
- rdfs:Literal
- Has sub-properties
-
rico:expressedDate; rico:title
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition updated. Examples added. Objective: to make
RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:normalizedDateValue
IRI:
https://www.ica.org/standards/RiC/ontology#normalizedDateValue
- Label(s)
- normalized date value [en]; valeur normalisée de la date [fr]; valor normalizado de fecha [es]
- Definition
- Machine readable representation of the date based on a public
technical standard.
- Scope note
- Used to represent the date in a standardized format that can
be processed programmatically. The main standard used today is ISO 8601, which is based
on the Gregorian calendar. See also the Extended Date Time Format (EDTF), which is an
extension of ISO 8601, and enables, among other features, to represent a date set, and
to indicate the date is approximate.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A29 (Normalized Date
attribute)
- Example(s)
-
"2012-02-14/2015-03-08 (an ISO 8601 form of a date range)" [en]
-
"2012/2015-03 (an ISO 8601 form of a date range)" [en]
-
"1948-03 (an ISO 8601 form of a single date)" [en]
-
"1948-03-08 (an ISO 8601 form of a single date)" [en]
-
"1948-03~ (a single date in ETDF, meaning March 1948 approximately)" [en]
-
"1948/.. (an open date range in EDTF, starting in 1948)" [en]
-
"1948/ (a date range in EDTF, starting in 1948, end unknown)" [en]
-
"1550,1551,1553,1555 (a date set in EDTF, meaning one of the years 1550, 1551, 1553, 1555)" [en]
-
"{1550,1551,1553,1555} (a date set in EDTF, meaning all of the years 1550, 1551, 1553, 1555)" [en]
-
"{1805,1815..1820} (a date set in EDTF, meaning all of the years 1805, 1815, 1816, 1817, 1818, 1819, 1820)" [en]
- Has super-properties
-
rico:normalizedValue
- Has domain
-
rico:Date
- Has range
- rdfs:Literal
- Change note(s)
- 2024-09-02: Fixed a typo in two of the EDTF examples.
- 2023-11-11: Aligned with RiC-CM 1.0: updated the examples
(skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-10-10: Updated the rdfs:comment and examples, and added a
scopeNote, in order to make this property fully compliant with RiC-CM
1.0.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Examples added. Objective: to make RiC-O compliant with
RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:physicalCharacteristicsNote
IRI:
https://www.ica.org/standards/RiC/ontology#physicalCharacteristicsNote
- Label(s)
- physical characteristics note [en]; note sur les caractéristiques physiques [fr]; nota sobre las características físicas [es]
- Definition
- Information about the physical features, completeness, or
conservation status of an Instantiation. Includes information about the physical nature
and condition such as conservation status or the deterioration of an Instantiation (for
example its carrier) affecting the ability to recover information.
- Scope note
- Not to be confused with the intellectual completeness of a
Record Resource and its sub-entities, which is covered by the Integrity attribute. May
include digital file fixity.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A31 (Physical
Characteristics Note attribute)
- Example(s)
-
"carrier heavily foxed" [en]
-
"some loss of text due to rodent damage" [en]
-
"The charter is missing the seal." [en]
-
"Letter physical characteristics: corner without text missing – the carrier is damaged, but no information of the content is missing" [en]
-
"British Library binding" [en]
-
"Watermarked" [en]
-
"A web page (HTML, 15 images, 2 CSS, 1 JavaScript), with 1 CSS missing." [en]
-
"For carrier: hard drives on which the author wrote physically (using a pen)." [en]
-
"Digital file format: JPEG-2000" [en]
- Has domain
-
rico:Instantiation
- Has range
- rdfs:Literal
- Has sub-properties
-
rico:qualityOfRepresentationNote
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the IRI, mapping to RiC-CM
(rico:RiCCMCorrespondingComponent), labels, description (rdfs:comment),
skos:scopeNote, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition updated. Examples added. Objective: to make
RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:productionTechnique
IRI:
https://www.ica.org/standards/RiC/ontology#productionTechnique
- Label(s)
- production technique [en]; technique de production [fr]; técnica de produccióon [es]
- Definition
- The method used in the representation of information on an
Instantiation.
- Scope note
- Use only if you have free text or don't have a controlled
vocabulary for production techniques (in this case, use the ProductionTechniqueType
class)
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A33 (Production Technique
attribute)
- Example(s)
-
"engraving" [en]
-
"handwriting" [en]
-
"magnetic recording" [en]
-
"optical recording" [en]
- Has domain
-
rico:Instantiation
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Examples added. Objective: to make RiC-O compliant with
RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:publicationDate
IRI:
https://www.ica.org/standards/RiC/ontology#publicationDate
- Label(s)
- publication date [en]; date de publication [fr]; fecha de publicación [es]
- Definition
- Date of the publication of a Record Resource.
- Scope note
- Provided for usability reasons. May be deprecated and removed
later on. Use only if you don't use Date classes for handling dates.
- Mapping to RiC-CM 1.0
- Datatype property specialized implementation of
RiC-E18 (Date entity)
- Has super-properties
-
rico:date
- Has domain
-
rico:RecordResource
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:qualityOfRepresentationNote
IRI:
https://www.ica.org/standards/RiC/ontology#qualityOfRepresentationNote
- Label(s)
- quality of representation note [en]; note sur la qualité de la représentation [fr]; nota sobre la calidad de representación [es]
- Definition
- Characteristics of an Instantiation that affect the ability to
recover the intellectual content. Such characteristics may be related to the methods
used in creating the Instantiation or introduced subsequent to the creation through
accident.
- Scope note
- Quality of representation note is a specialization of physical
characteristics note. Quality of representation note should be used in conjunction with
physical characteristics note when the physical characteristics impact the ability to
recover the intellectual content.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A34 (Quality of
Representation Note attribute)
- Example(s)
-
"Black and white digitization may have led to loss of some information." [en]
-
"some loss of information due to poor quality of image capture" [en]
-
"some loss of text due to rodent damage" [en]
- Has super-properties
-
rico:physicalCharacteristicsNote
- Has domain
-
rico:Instantiation
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the IRI, mapping to RiC-CM
(rico:RiCCMCorrespondingComponent), labels, description (rdfs:comment),
skos:scopeNote, rdfs:subpropertyOf.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition updated. Examples added. Objective: to make
RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:quantity
IRI:
https://www.ica.org/standards/RiC/ontology#quantity
- Label(s)
- quantity [en]; quantité [fr]; cantidad [es]
- Definition
- Machine-readable quantity.
- Scope note
- Use if you use the Extent class and its properties for
handling an accurate description of the extent of a resource.
- Has super-properties
-
rico:textualValue
- Has domain
-
rico:Extent
- Has range
- xsd:decimal
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added an xml:lang attribute to the
rdfs:comment.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-21: Added a scope note.
- 2020-10-28: Datatype property created along with unitOfMeasurement,
Extent and UnitOfMeasurement classes, in order to provide methods for handling
extent accurately.
Back to the table of contents | Back to top
Datatype property: rico:recordResourceExtent
IRI:
https://www.ica.org/standards/RiC/ontology#recordResourceExtent
- Label(s)
- Record Resource Extent [en]; mesure de la ressource archivistique [fr]; soporte de recurso documental [es]
- Definition
- The quantity of information content, as human experienced,
contained in a Record Resource. The method and precision of expressing the quantity of
information represented in a Record Resource will vary according to the kind of Record
Resource being described, processing economy constraints, etc. For record sets, quantity
may be expressed as number of records, or, for analogue records in particular, by the
physical storage dimensions of the members of the Record Set. For individual records or
record parts, quantity may be expressed in more precise terms.
- Scope note
- Use if you don't use RecordResourceExtent class and its
properties for handling such information. Record resource extent should not be confused
with instantiation extent or carrier extent. The number, size or duration of the
information content unit(s) remains the same even if the information is instantiated in
various carriers. For example, a CD with a storage capacity of 700 MB (carrier extent)
might hold a record of 1,500 words (record resource extent) represented in two versions,
one a Word document with an instantiation extent of 3 KB and the other a PDF file with
an instantiation extent of 5 KB.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A35 (Record Resource Extent
attribute)
- Example(s)
-
"3 minutes and 24 seconds" [en]
-
"6 maps" [en]
-
"6 photographs" [en]
-
"2 films" [en]
-
"1,500 words" [en]
-
"2.065.735 characters" [en]
- Has super-properties
-
rico:physicalOrLogicalExtent
- Has domain
-
rico:RecordResource
- Has range
- rdfs:Literal
- Change note(s)
- 2024-03-15: Fix capitalisation in English label.
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote, examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-21: Updated the scope note, as a RecordResourceExtent class has
been created.
- 2020-11-01: Text definition and scope note updated. Examples added.
Objective: to make RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:recordResourceStructure
IRI:
https://www.ica.org/standards/RiC/ontology#recordResourceStructure
- Label(s)
- Record Resource structure [en]; structure de la ressource archivistique [fr]; estructura de recurso documental [es]
- Definition
- Information about the intellectual arrangement and composition
of a Record Resource. For Record and Record Part, it encompasses information about the
intellectual composition of the record, the presence of record parts and their
functions. For Record Set, it encompasses information about the methodology or criteria
used for arranging the Record Set members or Record members within the containing Record
Set
- Mapping to RiC-CM 1.0
- Specialization of RiC-A40 (Structure
attribute)
- Example(s)
-
"Inside each file, the records are arranged chronologically." [en]
-
"The database has 3 related tables: names, addresses, and passport numbers." [en]
-
"The record has 2 appendixes, comprising a full account of the income from car taxes and real estate taxes." [en]
-
"The series have the files arranged according to the alphabetical order of the places concerned." [en]
- Has super-properties
-
rico:structure
- Has domain
-
rico:RecordResource
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition updated. Examples added. Objective: to make
RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:relationCertainty
IRI:
https://www.ica.org/standards/RiC/ontology#relationCertainty
- Label(s)
- relation certainty [en]; degré de certitude de la relation [fr]; certeza de la relación [es]
- Definition
- Qualifies the level of certitude of the accuracy of a
Relation.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-RA01 (Certainty of Relation
attribute)
- Example(s)
-
"certain" [en]
-
"uncertain" [en]
-
"unknown" [en]
- Has domain
-
rico:Relation
- Has range
- rdfs:Literal
- Change note(s)
- 2023-12-27: Renamed the datatype property (was 'certainty') and reduced
its domain to Relation (the dmain was the union of Event and Relation).
Consequently updated the labels.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-10-14: Reintroduced this datatype property, with the definition
assigned to it in RiC-CM 1.0, apart from its domain that also includes
Event.
Back to the table of contents | Back to top
Datatype property: rico:relationSource
IRI:
https://www.ica.org/standards/RiC/ontology#relationSource
- Label(s)
- relation source [en]; source de la relation [fr]; fuente de la relación [es]
- Definition
- A source of information used for identifying and describing a
Relation.
- Scope note
- Use only if you don't use the 'isEvidencedBy' object
property.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-RA05 (Source of Relation
attribute).
- Has domain
-
rico:Relation
- Has range
- rdfs:Literal
- Change note(s)
- 2023-12-27: Renamed the datatype property (was 'source') and reduced
its domain to Relation (the domain was the union of Record Resource and
Relation). Consequently updated the rdfs:comment, labels and scope note. Added a
rico:RiCCMCorrespondingComponent annotation.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:scopeAndContent
IRI:
https://www.ica.org/standards/RiC/ontology#scopeAndContent
- Label(s)
- scope and content [en]; portée et contenu [fr]; alcance y contenido [es]
- Definition
- Summary of the scope (such as time periods, geography) and
content (such as subject matter, administrative processes) of a Record Resource.
Provides a more complete summary of the informational content of the Record Resource
highlighting the information conveyed in the Record Resource, why it was created,
received, and/or maintained, and the agents connected to it. It may include description
of relations with agents, activities, dates and places, or with other record
resources.
- Scope note
- Scope and content is a specialization of general description.
For a Record Set, may be used to summarize the scope and content of the Record Set
itself, or additionally to summarize the scope and content of some or all members of the
Record Set. It is not to be confused with the history dataytpe property which focuses on
the origination and subsequent changes to a Record Resource.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A38 (Scope and Content
attribute)
- Example(s)
-
"Includes a detailed list of the lands and villages given by the King to the Abbey." [en]
-
"Among the witnesses, the Duke of Normandy." [en]
-
"The author explains why he does not agree with the decision made and adds that it cannot be applied." [en]
-
"Letter from Vlad the Impaler (Dracula) to the Council of Kronstadt asking them to send military support against the Ottomans, within the framework of their alliance treaty." [en]
-
"Se hace referencia a construcción del Gran Hotel, iniciada en 1899 bajo el nombre de Casa Celestino. Tras su interrupción en 1902, continuó la obra ya con su nombre actual." [es]
- Has super-properties
-
rico:generalDescription
- Has domain
-
rico:RecordResource
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote, rdfs:subpropertyOf, examples
(skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition updated. Examples added. Objective: to make
RiC-O compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:structure
IRI:
https://www.ica.org/standards/RiC/ontology#structure
- Label(s)
- structure [en]; structure [fr]; estructura [es]
- Definition
- Information about the intellectual arrangement and composition
of a Record Resource or the physical arrangement and composition of an Instantiation.
For Record and Record Part, it encompasses information about the intellectual
composition of the record, the presence of record parts and their functions. For Record
Set, it encompasses information about the methodology or criteria used for arranging the
Record Set members or Record members within the containing Record Set. For
Instantiation, it may comprise information about the composition of the physical
elements of the instantiation
- Scope note
- Use only if you cannot use the subproperties (particularly if
the same free text is being used in your current metadata for describing the record
resource and the instantiation structure). For a Record Set, may be used to summarize
the structure of the Record Set itself, or additionally to summarize the structure of
some or all members of the Record Set. Should not be confused with the classification
datatype property, which provides information about the category which the Record Set
belongs to within a classification scheme.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A40 (Structure
attribute)
- Example(s)
-
"The record has two appendices, comprising a full account of the income from car taxes and real estate taxes" [en]
-
"The series have the files arranged according to the alphabetical order of the places concerned" [en]
-
"Inside each file, the records are arranged chronologically (about a record set)" [en]
-
"The database has three related tables: names, addresses, and passport numbers (about a record)" [en]
- Has domain
-
rico:Instantiation
or
rico:RecordResource
- Has range
- rdfs:Literal
- Has sub-properties
-
rico:instantiationStructure; rico:recordResourceStructure
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the skos:scopeNote,
examples (skos:example).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Text definition updated. Objective: to make RiC-O compliant
with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:technicalCharacteristics
IRI:
https://www.ica.org/standards/RiC/ontology#technicalCharacteristics
- Label(s)
- technical characteristics [en]; caractéristiques techniques [fr]; características técnicas [es]
- Definition
- Describes any relevant physical or software feature of any
device involved in the creation or management of a Record Resource.
- Scope note
- Does not include references to the workflow that the Mechanism
is involved in, which is described under the Activity entity. It emphasizes those
features that provide a better understanding of the impact of the Mechanism on the
records.
- Mapping to RiC-CM 1.0
- Corresponds to RiC-A41 (Technical Characteristics
attribute)
- Example(s)
-
"Hubble Space Telescope had until 2002 a flawed mirror that introduced severe spherical aberration for the images." [en]
- Has domain
-
rico:Mechanism
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-11: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment), skos:scopeNote.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-01: Scope note and examples added. Objective: to make RiC-O
compliant with RiC-CM v0.2.
Back to the table of contents | Back to top
Datatype property: rico:textualValue
IRI:
https://www.ica.org/standards/RiC/ontology#textualValue
- Label(s)
- textual value [en]; valeur textuelle [fr]; valor textual [es]
- Definition
- A textual expression of an Appellation or Date.
- Has domain
-
rico:Appellation
or
rico:Date
or
rico:Extent
- Has range
- rdfs:Literal
- Has sub-properties
-
rico:expressedDate; rico:normalizedValue; rico:quantity
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:type
IRI:
https://www.ica.org/standards/RiC/ontology#type
- Label(s)
- type [en]; type [fr]; tipo [es]
- Definition
- A term used to characterize an entity.
- Scope note
- Provided for usability reasons. May be deprecated and removed
later on. Use only if you don't use Type subclasses for handling
categories.
- Has domain
-
rico:Thing
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:unitOfMeasurement
IRI:
https://www.ica.org/standards/RiC/ontology#unitOfMeasurement
- Label(s)
- unit of measurement [en]; unité de mesure [fr]; unidad de medida [es]
- Definition
- A definite magnitude of a quantity, defined and adopted by
convention or by law, that is used as a standard for measurement of the same kind of
quantity. Can be spacial units (cm, m), weight (g, kg), time (s, h), storage (MB, TB) or
more informal units used in the archival context like number of boxes, pages or
words.
- Scope note
- Use if you do not use the UnitOfMeasurement class for handling
units of measurement along with Extent.
- Has domain
-
rico:Extent
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added an xml:lang attribute to the
rdfs:comment.
- 2023-08-25: Added a new rdfs:label in French.
- 2020-11-21: Added a scope note.
- 2020-10-28: Datatype property created along with quantity, Extent and
UnitOfMeasurement classes, in order to provide methods for handling extent
accurately.
Back to the table of contents | Back to top
Datatype property: rico:usedFromDate
IRI:
https://www.ica.org/standards/RiC/ontology#usedFromDate
- Label(s)
- used from date [en]; utilisé à partir de [fr]; usado desde la fecha [es]
- Definition
- Date at which an Appellation was first used.
- Scope note
- Provided for usability reasons. May be deprecated and removed
later on. Use only if you don't use Date classes for handling dates.
- Mapping to RiC-CM 1.0
- Datatype property specialized implementation of
RiC-E18 (Date entity)
- Has super-properties
-
rico:beginningDate
- Has domain
-
rico:Appellation
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-12: Made this property a subproperty of
beginningDate.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Datatype property: rico:usedToDate
IRI:
https://www.ica.org/standards/RiC/ontology#usedToDate
- Label(s)
- used to date [en]; utilisé jusqu’à [fr]; usado hasta la fecha [es]
- Definition
- Date until an Appellation was used.
- Scope note
- Provided for usability reasons. May be deprecated and removed
later on. Use only if you don't use Date classes for handling dates.
- Mapping to RiC-CM 1.0
- Datatype property specialized implementation of
RiC-E18 (Date entity)
- Has super-properties
-
rico:endDate
- Has domain
-
rico:Appellation
- Has range
- rdfs:Literal
- Change note(s)
- 2023-11-12: Made this property a subproperty of endDate.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-25: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Object properties
Object property: rico:accumulationRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#accumulationRelation_role
- Label(s)
- has the role of the Accumulation Relation [en] | a le rôle de la Relation d’accumulation [fr] | desempeña el papel de la Relación de Acumulación [es]
- Definition
- Connects an AccumulationRelation to itself. It is a property
that can stand for an instance of the class when necessary, e.g. when you explore a
knowledge graph.
- Scope note
- This property "rolifies" the AccumulationRelation class. It
should be used only when you have to manage instances of the AccumulationRelation class,
to connect each instance to itself, in order to be able to infer, using OWL-RL and
property paths, the two shortcuts corresponding to this n-ary class.
- Has super-properties
-
rico:organicProvenanceRelation_role
- Has domain
-
rico:AccumulationRelation
- Has range
-
rico:AccumulationRelation
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the AccumulationRelation
rolified class. Declared it as reflexive. Declared it(s)
superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:activityDocumentationRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#activityDocumentationRelation_role
- Label(s)
- has the role of the Activity Documentation Relation [en] | a le rôle de la Relation entre activités et ressources
archivistiques [fr] | desempeña el papel de la Relación de procedencia
funcional [es]
- Definition
- Connects an ActivityDocumentationRelation to itself. It is a
property that can stand for an instance of the class when necessary, e.g. when you
explore a knowledge graph.
- Scope note
- This property "rolifies" the ActivityDocumentationRelation
class. It should be used only when you have to manage instances of the
ActivityDocumentationRelation class, to connect each instance to itself, in order to be
able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this
n-ary class.
- Has super-properties
-
rico:eventRelation_role; rico:organicOrFunctionalProvenanceRelation_role
- Has domain
-
rico:ActivityDocumentationRelation
- Has range
-
rico:ActivityDocumentationRelation
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the
ActivityDocumentationRelation rolified class. Declared it as reflexive. Declared
it(s) superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:activityIsContextOfRelation
IRI:
https://www.ica.org/standards/RiC/ontology#activityIsContextOfRelation
- Label(s)
- activity is context of relation [en] | activité est le contexte de la relation [fr] | actividad es contexto de relación [es]
- Definition
- Connects an Activity to an Agent Temporal Relation (when the
Activity is transferred from an Agent to another one) or a Mandate Relation (the Mandate
assigns the Activity to the Agent or defines it).
- Has super-properties
-
rico:thingIsContextOfRelation
- Has domain
-
rico:Activity
- Has range
-
rico:AgentTemporalRelation
or
rico:MandateRelation
Has inverse:
rico:asConcernsActivity
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Object property: rico:affectsOrAffected
IRI:
https://www.ica.org/standards/RiC/ontology#affectsOrAffected
- Label(s)
- affects or affected [en] | affecte ou a affecté [fr] | afecta o afectaba a [es]
- Definition
- Connects an Event to a Thing on which the Event has or had some
significant impact.
- Mapping to RiC-CM 1.0
- RiC-R059 ('affects or affected'
relation)
- Has super-properties
-
rico:hasOrHadParticipant
- Has domain
-
rico:Event
- Has range
-
rico:Thing
Has inverse:
rico:isOrWasAffectedBy
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
- 2021-01-22: changed the IRI, label, inverse property IRI, text
definition and corresponding CM component (changed made in order to make RiC-O
compliant with RiC-CM 0.2; the name of this property in RiC-O 0.1 was
"affects").
Back to the table of contents | Back to top
Object property: rico:agentControlRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#agentControlRelation_role
- Label(s)
- has the role of the Agent Control Relation [en] | a le rôle de la Relation de contrôle entre agents [fr] | desempeña el papel de la Relación de control entre
agentes [es]
- Definition
- Connects an AgentControlRelation to itself. It is a property
that can stand for an instance of the class when necessary, e.g. when you explore a
knowledge graph.
- Scope note
- This property "rolifies" the AgentControlRelation class. It
should be used only when you have to manage instances of the AgentControlRelation class,
to connect each instance to itself, in order to be able to infer, using OWL-RL and
property paths, the two shortcuts corresponding to this n-ary class.
- Has super-properties
-
rico:agentHierarchicalRelation_role; rico:authorityRelation_role
- Has domain
-
rico:AgentControlRelation
- Has range
-
rico:AgentControlRelation
- Has sub-properties
-
rico:leadershipRelation_role
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the AgentControlRelation
rolified class. Declared it as reflexive. Declared it(s)
superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:agentHierarchicalRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#agentHierarchicalRelation_role
- Label(s)
- has the role of the Agent Hierarchical Relation [en] | a le rôle de la Relation hiérarchique entre agents [fr] | desempeña el papel de la Relación jerárquica entre
agentes [es]
- Definition
- Connects an AgentHierarchicalRelation to itself. It is a
property that can stand for an instance of the class when necessary, e.g. when you
explore a knowledge graph.
- Scope note
- This property "rolifies" the AgentHierarchicalRelation class.
It should be used only when you have to manage instances of the
AgentHierarchicalRelation class, to connect each instance to itself, in order to be able
to infer, using OWL-RL and property paths, the two shortcuts corresponding to this n-ary
class.
- Has super-properties
-
rico:agentToAgentRelation_role
- Has domain
-
rico:AgentHierarchicalRelation
- Has range
-
rico:AgentHierarchicalRelation
- Has sub-properties
-
rico:agentControlRelation_role; rico:groupSubdivisionRelation_role
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the AgentHierarchicalRelation
rolified class. Declared it as reflexive. Declared it(s)
superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:agentTemporalRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#agentTemporalRelation_role
- Label(s)
- has the role of the Agent Temporal Relation [en] | a le rôle de la Relation temporelle entre agents [fr] | desempeña el papel de la Relación temporal entre
agentes [es]
- Definition
- Connects an AgentTemporalRelation to itself. It is a property
that can stand for an instance of the class when necessary, e.g. when you explore a
knowledge graph.
- Scope note
- This property "rolifies" the AgentTemporalRelation class. It
should be used only when you have to manage instances of the AgentTemporalRelation
class, to connect each instance to itself, in order to be able to infer, using OWL-RL
and property paths, the two shortcuts corresponding to this n-ary
class.
- Has super-properties
-
rico:agentToAgentRelation_role; rico:temporalRelation_role
- Has domain
-
rico:AgentTemporalRelation
- Has range
-
rico:AgentTemporalRelation
- Has sub-properties
-
rico:descendanceRelation_role
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the AgentTemporalRelation
rolified class. Declared it as reflexive. Declared it(s)
superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:appellationRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#appellationRelation_role
- Label(s)
- has the role of the Appellation Relation [en] | a le rôle de la Relation d’appellation [fr] | desempeña el papel de la Relación de denominación [es]
- Definition
- Connects an AppellationRelation to itself. It is a property that
can stand for an instance of the class when necessary, e.g. when you explore a knowledge
graph.
- Scope note
- This property "rolifies" the AppellationRelation class. It
should be used only when you have to manage instances of the AppellationRelation class,
to connect each instance to itself, in order to be able to infer, using OWL-RL and
property paths, the two shortcuts corresponding to this n-ary class.
- Has super-properties
-
rico:relation_role
- Has domain
-
rico:AppellationRelation
- Has range
-
rico:AppellationRelation
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the AppellationRelation
rolified class. Declared it as reflexive. Declared it(s)
superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:authorshipRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#authorshipRelation_role
- Label(s)
- has the role of the Authorship Relation [en] | a le rôle de la Relation de responsabilité
intellectuelle [fr] | desempeña el papel de la Relación de autoría [es]
- Definition
- Connects an AuthorshipRelation to itself. It is a property that
can stand for an instance of the class when necessary, e.g. when you explore a knowledge
graph.
- Scope note
- This property "rolifies" the AuthorshipRelation class. It
should be used only when you have to manage instances of the AuthorshipRelation class,
to connect each instance to itself, in order to be able to infer, using OWL-RL and
property paths, the two shortcuts corresponding to this n-ary class.
- Has super-properties
-
rico:creationRelation_role
- Has domain
-
rico:AuthorshipRelation
- Has range
-
rico:AuthorshipRelation
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the AuthorshipRelation
rolified class. Declared it as reflexive. Declared it(s)
superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:childRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#childRelation_role
- Label(s)
- has the role of the Child Relation [en] | a le rôle de la Relation de filiation [fr] | desempeña el papel de la Relación de filiación [es]
- Definition
- Connects a ChildRelation to itself. It is a property that can
stand for an instance of the class when necessary, e.g. when you explore a knowledge
graph.
- Scope note
- This property "rolifies" the ChildRelation class. It should be
used only when you have to manage instances of the ChildRelation class, to connect each
instance to itself, in order to be able to infer, using OWL-RL and property paths, the
two shortcuts corresponding to this n-ary class.
- Has super-properties
-
rico:descendanceRelation_role
- Has domain
-
rico:ChildRelation
- Has range
-
rico:ChildRelation
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the ChildRelation rolified
class. Declared it as reflexive. Declared it(s) superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:correspondenceRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#correspondenceRelation_role
- Label(s)
- has the role of the Correspondence Relation [en] | a le rôle de la Relation épistolaire [fr] | desempeña el papel de la Relación entre personas por
correspondencia [es]
- Definition
- Connects a CorrespondenceRelation to itself. It is a property
that can stand for an instance of the class when necessary, e.g. when you explore a
knowledge graph.
- Scope note
- This property "rolifies" the CorrespondenceRelation class. It
should be used only when you have to manage instances of the CorrespondenceRelation
class, to connect each instance to itself, in order to be able to infer, using OWL-RL
and property paths, the two shortcuts corresponding to this n-ary
class.
- Has super-properties
-
rico:knowingRelation_role
- Has domain
-
rico:CorrespondenceRelation
- Has range
-
rico:CorrespondenceRelation
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the CorrespondenceRelation
rolified class. Declared it as reflexive. Declared it(s)
superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:creationRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#creationRelation_role
- Label(s)
- has the role of the Creation Relation [en] | a le rôle de la Relation de création [fr] | desempeña el papel de la Relación de creación [es]
- Definition
- Connects a CreationRelation to itself. It is a property that can
stand for an instance of the class when necessary, e.g. when you explore a knowledge
graph.
- Scope note
- This property "rolifies" the CreationRelation class. It should
be used only when you have to manage instances of the CreationRelation class, to connect
each instance to itself, in order to be able to infer, using OWL-RL and property paths,
the two shortcuts corresponding to this n-ary class.
- Has super-properties
-
rico:organicProvenanceRelation_role
- Has domain
-
rico:CreationRelation
- Has range
-
rico:CreationRelation
- Has sub-properties
-
rico:authorshipRelation_role
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the CreationRelation rolified
class. Declared it as reflexive. Declared it(s) superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:derivationRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#derivationRelation_role
- Label(s)
- has the role of the Derivation Relation [en] | a le rôle de la Relation de dérivation [fr] | desempeña el papel de la Relación de derivación [es]
- Definition
- Connects a DerivationRelation to itself. It is a property that
can stand for an instance of the class when necessary, e.g. when you explore a knowledge
graph.
- Scope note
- This property "rolifies" the DerivationRelation class. It
should be used only when you have to manage instances of the DerivationRelation class,
to connect each instance to itself, in order to be able to infer, using OWL-RL and
property paths, the two shortcuts corresponding to this n-ary class.
- Has super-properties
-
rico:instantiationToInstantiationRelation_role; rico:temporalRelation_role
- Has domain
-
rico:DerivationRelation
- Has range
-
rico:DerivationRelation
- Has sub-properties
-
rico:migrationRelation_role
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the DerivationRelation
rolified class. Declared it as reflexive. Declared it(s)
superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:descendanceRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#descendanceRelation_role
- Label(s)
- has the role of the Descendance Relation [en] | a le rôle de la Relation de descendance [fr] | desempeña el papel de la Relación de descendencia [es]
- Definition
- Connects a DescendanceRelation to itself. It is a property that
can stand for an instance of the class when necessary, e.g. when you explore a knowledge
graph.
- Scope note
- This property "rolifies" the DescendanceRelation class. It
should be used only when you have to manage instances of the DescendanceRelation class,
to connect each instance to itself, in order to be able to infer, using OWL-RL and
property paths, the two shortcuts corresponding to this n-ary class.
- Has super-properties
-
rico:agentTemporalRelation_role; rico:familyRelation_role
- Has domain
-
rico:DescendanceRelation
- Has range
-
rico:DescendanceRelation
- Has sub-properties
-
rico:childRelation_role
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the DescendanceRelation
rolified class. Declared it as reflexive. Declared it(s)
superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:describesOrDescribed
IRI:
https://www.ica.org/standards/RiC/ontology#describesOrDescribed
- Label(s)
- describes or described [en] | décrit ou a décrit [fr] | describe o describía [es]
- Definition
- Connects a Record Resource to a Thing that it describes or
described.
- Scope note
- Can be used, among other situations, for specifying that some
finding aid (a Record that has Documentary Form Type Finding Aid) describes some Record
Set.
- Mapping to RiC-CM 1.0
- RiC-R021 ('describes or described'
relation)
- Has super-properties
-
rico:hasOrHadSubject
- Has domain
-
rico:RecordResource
- Has range
-
rico:Thing
Has inverse:
rico:isOrWasDescribedBy
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
- 2021-01-22: changed the IRI, label, inverse property IRI, text
definition, corresponding CM component name (changed made in order to make RiC-O
compliant with RiC-CM 0.2; the name of this property in RiC-O 0.1 was
"describes").
Back to the table of contents | Back to top
Object property: rico:directlyPrecedesInSequence
IRI:
https://www.ica.org/standards/RiC/ontology#directlyPrecedesInSequence
- Label(s)
- directly precedes in sequence [en] | précède directement dans la séquence [fr] | precede directamente en la secuencia [es]
- Definition
- Connects a Thing to a Thing that it precedes directly in some
non chronological sequence.
- Has super-properties
-
rico:precedesInSequenceTransitive
- Has domain
-
rico:Thing
- Has range
-
rico:Thing
Has inverse:
rico:directlyFollowsInSequence
- Change note(s)
- 2023-11-27: Added a new rdfs:label in Spanish.
- 2023-11-12: Updated the description (rdfs:comment) and
labels.
- 2023-09-22: Renamed the property and modified its definition
(rdfs:comment) in order to better distinguish it from
precedesInTime.
- 2023-09-08: Object property added, along with its inverse property, in
order to enable to express current, direct, sequential relations between things
(the possibly indirect, transitive relation, superproperty of this one, being
also added).
Back to the table of contents | Back to top
Object property: rico:eventRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#eventRelation_role
- Label(s)
- has the role of the Event Relation [en] | a le rôle de la Relation impliquant un événement [fr] | desempeña el papel de la Relación con un evento [es]
- Definition
- Connects an EventRelation to itself. It is a property that can
stand for an instance of the class when necessary, e.g. when you explore a knowledge
graph.
- Scope note
- This property "rolifies" the EventRelation class. It should be
used only when you have to manage instances of the EventRelation class, to connect each
instance to itself, in order to be able to infer, using OWL-RL and property paths, the
two shortcuts corresponding to this n-ary class.
- Has super-properties
-
rico:relation_role
- Has domain
-
rico:EventRelation
- Has range
-
rico:EventRelation
- Has sub-properties
-
rico:activityDocumentationRelation_role; rico:performanceRelation_role
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the EventRelation rolified
class. Declared it as reflexive. Declared it(s) superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:evidences
IRI:
https://www.ica.org/standards/RiC/ontology#evidences
- Label(s)
- evidences [en] | atteste de [fr] | evidencia [es]
- Definition
- Connects a Record Resource to a Relation, when the first is used
for proving the existence of the second one, or for describing it.
- Mapping to RiC-CM 1.0
- Inverse of 'is evidenced by' object
property.
- Has super-properties
-
rico:thingIsConnectedToRelation
- Has domain
-
rico:RecordResource
- Has range
-
rico:Relation
Has inverse:
rico:isEvidencedBy
- Change note(s)
- 2023-12-27: Renamed the object property (was 'is source of') and
reduced its domain to Record Resource (the domain was the union of Record
Resource and Agent) and its range to Relation (the range was the union of Record
Resource and Relation). Consequently updated the superproperty, the labels, and
added a rico:RiCCMCorrespondingComponent. Same for the inverse object
property.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
Back to the table of contents | Back to top
Object property: rico:familyRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#familyRelation_role
- Label(s)
- has the role of the Family Relation [en] | a le rôle de la Relation familiale [fr] | desempeña el papel de la Relación familiar [es]
- Definition
- Connects a FamilyRelation to itself. It is a property that can
stand for an instance of the class when necessary, e.g. when you explore a knowledge
graph.
- Scope note
- This property "rolifies" the FamilyRelation class. It should
be used only when you have to manage instances of the FamilyRelation class, to connect
each instance to itself, in order to be able to infer, using OWL-RL and property paths,
the two shortcuts corresponding to this n-ary class.
- Has super-properties
-
rico:agentToAgentRelation_role
- Has domain
-
rico:FamilyRelation
- Has range
-
rico:FamilyRelation
- Has sub-properties
-
rico:descendanceRelation_role; rico:siblingRelation_role; rico:spouseRelation_role
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2024-03-15: Corrected unparseable symbol in rdfs:comment
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the FamilyRelation rolified
class. Declared it as reflexive. Declared it(s) superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:followedInSequence
IRI:
https://www.ica.org/standards/RiC/ontology#followedInSequence
- Label(s)
- followed in sequence [en] | a suivi dans la séquence [fr] | seguía en la secuencia transitivo [es]
- Definition
- Connects a Thing to a Thing that it followed in some non
chronological sequence in the past.
- Has super-properties
-
rico:followsOrFollowed
- Has domain
-
rico:Thing
- Has range
-
rico:Thing
Has inverse:
rico:precededInSequence
- Change note(s)
- 2023-11-27: Added a new rdfs:label in Spanish.
- 2023-11-12: Updated the description (rdfs:comment) and
labels.
- 2023-09-22: Renamed the property and modified its definition
(rdfs:comment) in order to better distinguish it from followsInTime.
- 2023-09-08: Added transitive super-property and both present direct and
past sequential relations as well as their respective inverse
relations.
Back to the table of contents | Back to top
Object property: rico:functionalEquivalenceRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#functionalEquivalenceRelation_role
- Label(s)
- has the role of the Functional Equivalence Relation [en] | a le rôle de la Relation d’équivalence fonctionnelle [fr] | desempeña el papel de la Relación de equivalencia
funcional [es]
- Definition
- Connects a FunctionalEquivalenceRelation to itself. It is a
property that can stand for an instance of the class when necessary, e.g. when you
explore a knowledge graph.
- Scope note
- This property "rolifies" the FunctionalEquivalenceRelation
class. It should be used only when you have to manage instances of the
FunctionalEquivalenceRelation class, to connect each instance to itself, in order to be
able to infer, using OWL-RL and property paths, the two shortcuts corresponding to this
n-ary class.
- Has super-properties
-
rico:instantiationToInstantiationRelation_role
- Has domain
-
rico:FunctionalEquivalenceRelation
- Has range
-
rico:FunctionalEquivalenceRelation
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the
FunctionalEquivalenceRelation rolified class. Declared it as reflexive. Declared
it(s) superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:groupSubdivisionRelation_role
IRI:
https://www.ica.org/standards/RiC/ontology#groupSubdivisionRelation_role
- Label(s)
- has the role of the Group Subdivision Relation [en] | a le rôle de la Relation de subdivision entre groupes
d’agents [fr] | desempeña el papel de la Relación de subdivisión entre grupos de
agentes [es]
- Definition
- Connects a GroupSubdivisionRelation to itself. It is a property
that can stand for an instance of the class when necessary, e.g. when you explore a
knowledge graph.
- Scope note
- This property "rolifies" the GroupSubdivisionRelation class.
It should be used only when you have to manage instances of the GroupSubdivisionRelation
class, to connect each instance to itself, in order to be able to infer, using OWL-RL
and property paths, the two shortcuts corresponding to this n-ary
class.
- Has super-properties
-
rico:agentHierarchicalRelation_role; rico:wholePartRelation_role
- Has domain
-
rico:GroupSubdivisionRelation
- Has range
-
rico:GroupSubdivisionRelation
- Change note(s)
- 2024-08-02: Removed global reflexivity (leads to
inconsistency).
- 2023-11-08: In order to get a system of rolified Relation classes:
created the object property, with domain and range the GroupSubdivisionRelation
rolified class. Declared it as reflexive. Declared it(s)
superproperty(ies).
Back to the table of contents | Back to top
Object property: rico:hasAuthor
IRI:
https://www.ica.org/standards/RiC/ontology#hasAuthor
- Label(s)
- has author [en] | a pour responsable intellectuel [fr] | tiene como autor a [es]
- Definition
- Connects a Record to the Group, Person or Position that is
responsible for conceiving and formulating the information contained in the
Record.
- Scope note
- To be used for a Person, Group or Position that makes any
contribution to the content of a record. Includes the Person, Group or Position in whose
name or by whose command the content may have been formulated and first instantiated
(for example the Person who signed the Record).
- Mapping to RiC-CM 1.0
- RiC-R079 ('has author'
relation)
- Has super-properties
-
rico:hasCreator
- Has domain
-
rico:Record
- Has range
-
rico:Group
or
rico:Person
or
rico:Position
Has inverse:
rico:isAuthorOf
Has sub-properties chains: rico:thingIsSourceOfRelation
o
rico:authorshipRelation_role
o
rico:relationHasTarget
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the
skos:scopeNote.
- 2023-11-08: In order to get a system of rolified Relation classes:
modified the property chain axiom so that it now involves the new
authorshipRelation_role object property.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
- 2020-12-29: Created following the addition of RiC-R079 relation in
RiC-CM 0.2
Back to the table of contents | Back to top
Object property: rico:hasCollector
IRI:
https://www.ica.org/standards/RiC/ontology#hasCollector
- Label(s)
- has collector [en] | est collecté par [fr] | tiene como coleccionista a [es]
- Definition
- Connects a Record Resource or an Instantiation to the Agent that
collects it intentionally, i.e., the Agent is a collector.
- Mapping to RiC-CM 1.0
- RiC-R030 ('has collector'
relation)
- Has super-properties
-
rico:hasAccumulator
- Has domain
-
rico:Instantiation
or
rico:RecordResource
- Has range
-
rico:Agent
Has inverse:
rico:isCollectorOf
- Change note(s)
- 2023-11-12: Aligned with RiC-CM 1.0: updated the description
(rdfs:comment).
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
- 2021-01-22: changed the IRI, label, inverse property and super property
IRI, text definition, domain (changed made in order to make RiC-O compliant with
RiC-CM 0.2; the name of this property in RiC-O 0.1 was
"collectedBy").
Back to the table of contents | Back to top
Object property: rico:hasContentOfType
IRI:
https://www.ica.org/standards/RiC/ontology#hasContentOfType
- Label(s)
- has content of type [en] | a pour type de contenu [fr] | tiene como tipo de contenido [es]
- Definition
- Connects a Record or a Record Part to a Content Type which
categorizes its content.
- Has super-properties
-
rico:hasOrHadCategory
- Has domain
-
rico:Record
or
rico:RecordPart
- Has range
-
rico:ContentType
Has inverse:
rico:isContentTypeOf
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
- 2021-01-22: changed the text definition and superproperty
IRI.
Back to the table of contents | Back to top
Object property: rico:hasExtent
IRI:
https://www.ica.org/standards/RiC/ontology#hasExtent
- Label(s)
- has extent [en] | a pour mesure [fr] | tiene como extensión [es]
- Definition
- Connects a Record Resource or Instantiation to an
Extent
- Has super-properties
-
rico:isRelatedTo
- Has domain
-
rico:Thing
- Has range
-
rico:Extent
Has inverse:
rico:isExtentOf
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Changed the domain (was Instantiation or RecordResource) to
Thing; changed the definition accordingly.
- 2023-08-28: Added a new rdfs:label in French; added an xml:lang
attribute to the rdfs:comment.
- 2020-10-28: Object property created along with the Extent class and its
subclasses, in order to provide methods for handling extent
accurately.
Back to the table of contents | Back to top
Object property: rico:hasOrHadAllMembersWithContentType
IRI:
https://www.ica.org/standards/RiC/ontology#hasOrHadAllMembersWithContentType
- Label(s)
- has or had all members with content type [en] | inclut ou a inclus des membres ayant tous pour type de
contenu [fr] | tienen o tenían todos sus miembros como tipo de
contenido [es]
- Definition
- Connects a Record Set and a Content Type that categorizes all
the Records or Record Parts that are or were included in the Record Set.
- Has super-properties
-
rico:hasOrHadAllMembersWithCategory
- Has domain
-
rico:RecordSet
- Has range
-
rico:ContentType
Has inverse:
rico:isOrWasContentTypeOfAllMembersOf
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
- 2020-12-28: Object property added for handling the case where a Record
Set is described as having all or some members that belong to some category (see
RiC-CM 0.2 attributes section, #4.4 on Record Set, Record and Record Part
attributes).
Back to the table of contents | Back to top
Object property: rico:hasOrHadAllMembersWithLanguage
IRI:
https://www.ica.org/standards/RiC/ontology#hasOrHadAllMembersWithLanguage
- Label(s)
- has or had all members with language [en] | inclut ou a inclus des membres ayant tous pour langue [fr] | tienen o tenían todos sus miembros como lengua [es]
- Definition
- Connects a Record Set and a Language used by all the Records or
Record Parts that are or were included in the Record Set.
- Has super-properties
-
rico:isRelatedTo
- Has domain
-
rico:RecordSet
- Has range
-
rico:Language
Has inverse:
rico:isOrWasLanguageOfAllMembersOf
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
- 2020-12-28: Object property added for handling the case where a Record
Set is described as having all or some members that belong to some category (see
RiC-CM 0.2 attributes section, #4.4 on Record Set, Record and Record Part
attributes).
Back to the table of contents | Back to top
Object property: rico:hasOrHadCorporateBodyType
IRI:
https://www.ica.org/standards/RiC/ontology#hasOrHadCorporateBodyType
- Label(s)
- has or had corporate body type [en] | a ou a eu pour type de collectivité [fr] | tiene o tenía como tipo de institucion [es]
- Definition
- Connects a Corporate Body to a Corporate Body Type which
categorizes or categorized it.
- Has super-properties
-
rico:hasOrHadCategory
- Has domain
-
rico:CorporateBody
- Has range
-
rico:CorporateBodyType
Has inverse:
rico:isOrWasCorporateBodyTypeOf
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
- 2021-01-22: changed the IRI, label, inverse property IRI, textual
definition (the name of this property in RiC-O 0.1 was
"hasCorporateBodyType").
Back to the table of contents | Back to top
Object property: rico:hasOrHadCorrespondent
IRI:
https://www.ica.org/standards/RiC/ontology#hasOrHadCorrespondent
- Label(s)
- has or had correspondent [en] | a ou a eu pour correspondant [fr] | tiene o tenía como correspondiente [es]
- Definition
- Connects two Persons that correspond or have corresponded with
each other. This relation is symmetric.
- Mapping to RiC-CM 1.0
- RiC-R052 ('has or had correspondent'
relation)
- Has super-properties
-
rico:knows
- Has domain
-
rico:Person
- Has range
-
rico:Person
Type: symmetric property
Has sub-properties chains: rico:thingIsConnectedToRelation
o
rico:correspondenceRelation_role
o
rico:relationConnects
- Change note(s)
- 2023-11-08: In order to get a system of rolified Relation classes:
modified the property chain axiom so that it now involves the new
correspondenceRelation_role object property.
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
- 2021-01-22: changed the IRI, label, textual definition (changed made in
order to make RiC-O compliant with RiC-CM 0.2; the name of this property in
RiC-O 0.1 was "hasCorrespondent").
Back to the table of contents | Back to top
Object property: rico:hasOrHadDigitalInstantiation
IRI:
https://www.ica.org/standards/RiC/ontology#hasOrHadDigitalInstantiation
- Label(s)
- has or had digital instantiation [en] | a ou a eu pour instanciation numérique [fr] | tiene o tenía como instanciación digital [es]
- Definition
- Connects a record resource to one of its digital instantiations,
whether it exists or has been lost or destroyed.
- Scope note
- This property can be used, among other cases, when you want to
convert findings aids encoded in EAD/XML and need a simple and accurate migration path
to process dao or daogrp EAD elements. Also, in some situations, it may be useful or
necessary to connect a record resource to a digital instantiation that no longer exists
or or has been lost.
- Has super-properties
-
rico:hasOrHadInstantiation
- Has domain
-
rico:RecordResource
- Has range
-
rico:Instantiation
Has inverse:
rico:isOrWasDigitalInstantiationOf
- Change note(s)
- 2023-11-27: Added a new rdfs:label in Spanish.
- 2023-08-29: Added the property.
Back to the table of contents | Back to top
Object property: rico:hasOrHadJurisdiction
IRI:
https://www.ica.org/standards/RiC/ontology#hasOrHadJurisdiction
- Label(s)
- has or had jurisdiction [en] | a ou a eu pour ressort [fr] | tiene o tenía como jurisdicción [es]
- Definition
- Inverse of 'is or was jurisdiction of' object
property.
- Mapping to RiC-CM 1.0
- RiC-R076i ('has or had jurisdiction'
relation)
- Has super-properties
-
rico:isAgentAssociatedWithPlace
- Has domain
-
rico:Agent
- Has range
-
rico:Place
Has inverse:
rico:isOrWasJurisdictionOf
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-10-19: Made subproperty of new property isAgentAssociatedWithPlace
instead of its parent isAssociatedWithPlace.
- 2023-08-28: Added a new rdfs:label in French.
- 2021-01-22: changed the IRI, label, inverse property IRI and textual
definition (changed made in order to make RiC-O compliant with RiC-CM 0.2; the
name of this property in RiC-O 0.1 was "hasJurisdiction").
Back to the table of contents | Back to top
Object property: rico:hasOrHadMainSubject
IRI:
https://www.ica.org/standards/RiC/ontology#hasOrHadMainSubject
- Label(s)
- has or had main subject [en] | a ou a eu pour sujet principal [fr] | tiene o tenía como matería principal [es]
- Definition
- Connects a Record Resource to a Thing that is or was its main
subject.
- Scope note
- Use for specifying, for example, that a Record Set of type
personal file has main subject some person, which would help end users to retrieve the
main archival resources about this person.
- Mapping to RiC-CM 1.0
- RiC-R020 ('has or had main subject'
relation)
- Has super-properties
-
rico:hasOrHadSubject
- Has domain
-
rico:RecordResource
- Has range
-
rico:Thing
Has inverse:
rico:isOrWasMainSubjectOf
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
- 2021-01-22: changed the IRI, label, inverse property IRI and textual
definition (changed made in order to make RiC-O compliant with RiC-CM 0.2; the
name of this property in RiC-O 0.1 was "hasMainSubject").
Back to the table of contents | Back to top
Object property: rico:hasOrHadSomeMembersWithContentType
IRI:
https://www.ica.org/standards/RiC/ontology#hasOrHadSomeMembersWithContentType
- Label(s)
- has or had some members with content type [en] | inclut ou a inclus des membres ayant pour type de
contenu [fr] | tienen o tenían algunos de sus miembros como tipo de
contenido [es]
- Definition
- Connects a Record Set and a Content Type that categorizes some
of the Records or Record Parts that are or were included in the Record
Set.
- Has super-properties
-
rico:hasOrHadSomeMembersWithCategory
- Has domain
-
rico:RecordSet
- Has range
-
rico:ContentType
Has inverse:
rico:isOrWasContentTypeOfSomeMembersOf
- Change note(s)
- 2023-11-02: Added a new rdfs:label in Spanish.
- 2023-08-28: Added a new rdfs:label in French.
- 2020-12-28: Object property added for handling the case where a Record
Set is described as having all or some members that belong to some category (see
RiC-CM 0.2 attributes section, #4.4 on Record Set, Record and Record Part
attributes).
Back to the table of contents | Back to top
