(part of the InLOC Information Model > InLOC properties)
InLOC specified relationships
The relationships that InLOC specifies are designed to cover the most common and useful set of relationships between parts of frameworks or other LOC structures. The information about relationships is split into three tables:
- the names of the relationships with their intended interpretations
- URIs and labels
- information relevant to an ontology, about the nature of the relationships
In the table below, "subject" and "object" are to be interpreted as they are in linked data triples. That is, if we have a triple "concept A" "relationship" "concept B" then concept A is the "subject" of the triple, and concept B is the "object" of the triple. "Object" here has nothing to do with the "object" as in "object-oriented".
Name and interpretation
| name | interpretation |
|---|---|
| closeMatch | links two concepts that are sufficiently similar that they can be used interchangeably in some information retrieval applications [SKOS] |
| exactMatch | links two concepts, indicating a high degree of confidence that the concepts can be used interchangeably across a wide range of information retrieval applications [SKOS] |
| hasDefinedLevel | the object concept represents a level of the subject concept |
| hasExample | the object concept is an example or illustration of the subject concept |
| hasLOCpart | the object concept is in some way covered by the subject concept |
| hasNecessaryPart | the object concept is a necessary, essential, required, or mandatory part of the subject concept |
| hasOptionalPart | the object concept is an optional part of the subject concept |
| hasPreRequisite | attaining the object concept is required before proceeding to attain the subject concept |
| isDefinedLevelOf | the subject concept represents a level of the object concept |
| isExampleOf | the subject concept is an example or illustration of the object concept |
| isLOCpartOf | the subject concept is in some way covered by the object concept |
| isNecessaryPartOf | the subject concept is a necessary, essential, required, or mandatory part of the object concept |
| isOptionalPartOf | the subject concept is an optional part of the object concept |
| isPreRequisiteOf | attaining the subject concept is required before proceeding to attain the object concept |
| isReplacedBy | the subject resource is supplanted, displaced, or superseded by the object resource (adapted from [DCMI]) |
| related | the subject and object resources are related in an unspecified way |
| replaces | the object resource is supplanted, displaced, or superseded by the subject resource (adapted from [DCMI]) |
| name | interpretation |
URIs and labels
Ontology
These relationships are represented in LOCassociations. The subject and object are each a LOCstructure or LOCdefinition, while the scheme is one of the above list of relationships. The scheme appears rather like a RDF "predicate" linking the subject and object resources. Possible subjects and objects are given below along with other information concerning the nature of these relationships.