User-defined relationships between individuals

18 Dec. 2010, rev. 10 March 2011, rev. 13 May 2012

Introduction

In ISO 15926-2 you will find a number of pre-defined relationships, like connection_of_individual. These will, presumably, be used most often, but they do not cover all situations in real life. So, in order not to get stuck, Part 2 offers a way to use an instance of Other Relationship in combination with with a ClassOfRelationshipWithSignature that can be used to classify the new relationship you have in mind.

WARNING - Do not use this lightly, because it may turn out to be nonsensical and the exchange of information may fail for that reason.

Model

The two attributes of ClassOfRelationshipWithSignature, classOfEnd1 and classOfEnd2, each point at a RoleAndDomain, or in fact at an EXPRESS attribute, or in RDF terms a 'property + object', the relationship being the RDF 'subject'.

To give an example: the relationship CompositionOfIndividual has two attributes: 'part' and 'whole', both pointing at an instance of PossibleIndividual. The instances of RoleAndDomain are here 'PartANDPossibleIndividual' , respectivily 'Whole'ANDPossibleIndividual'.

A heterosexual monogamous marriage relationship as a specialization of OtherRelationship

The conversion of the attribute (property) names, if so required, shall be done with a rule.

Template

From the above analysis diagram we can derive the following templates, first one for the definition of the instance of ClassOfRelationship WithSignature, and then one for the OtherRelationship:

John and Mary Doe have a heterosexual monogamous marriage relationship