<relation>

<relation> (relationship) describes any kind of relationship or linkage amongst a specified group of participants. 15.2.2 The Participant Description
Modulenamesdates — 13 Names, Dates, People, and Places
Attributes att.datableatt.datable.w3c (@period, @when, @notBefore, @notAfter, @from, @to) att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso) att.editLike (@cert, @resp, @evidence, @source, @precision) att.naming (@key, @ref, @nymRef)
typecategorizes the relationship in some respect, e.g. as social, personal or other.
Status Optional
Datatype 

<rng:ref name="data.enumerated"/>
data.enumerated
Suggested values include:
social
relationship concerned with social roles
personal
relationship concerned with personal roles, e.g. kinship, marriage, etc. [Default]
other
other kinds of relationship
namesupplies a name for the kind of relationship of which this is an instance.
Status Required
Datatype 

<rng:ref name="data.enumerated"/>
data.enumerated
Values an open list of application-dependent keywords
activeidentifies the ‘active’ participants in a non-mutual relationship, or all the participants in a mutual one.
Status Optional
Datatype 1–∞ occurrences of 

<rng:ref name="data.pointer"/>
data.pointer
separated by whitespace
Values a list of identifier values for participant or participant groups
mutualsupplies a list of participants amongst all of whom the relationship holds equally.
Status Mandatory when applicable
Datatype 1–∞ occurrences of 

<rng:ref name="data.pointer"/>
data.pointer
separated by whitespace
Values a list of identifier values for participant or participant groups
passiveidentifies the ‘passive’ participants in a non-mutual relationship.
Status Optional
Datatype 1–∞ occurrences of 

<rng:ref name="data.pointer"/>
data.pointer
separated by whitespace
Values a list of identifier values for participant or participant groups
Used bylistNym listOrg listPerson listPlace relationGrp
May contain
core: desc
Declaration

<rng:element name="relation">
<rng:ref name="att.global.attributes"/>
<rng:ref name="att.datable.w3c.attributes"/>
<rng:ref name="att.datable.iso.attributes"/>
<rng:ref name="att.editLike.attributes"/>
<rng:ref name="att.naming.attributes"/>
<rng:optional>
 <rng:attribute name="type" a:defaultValue="personal">
  <rng:choice>
   <rng:value>social</rng:value>
   <rng:value>personal</rng:value>
   <rng:value>other</rng:value>
   <rng:data type="Name"/>
  </rng:choice>
 </rng:attribute>
</rng:optional>
<rng:attribute name="name">
 <rng:ref name="data.enumerated"/>
</rng:attribute>
<rng:choice>
 <rng:optional>
  <rng:attribute name="active">
   <rng:list>
    <rng:oneOrMore>
     <rng:ref name="data.pointer"/>
    </rng:oneOrMore>
   </rng:list>
  </rng:attribute>
 </rng:optional>
 <rng:optional>
  <rng:attribute name="mutual">
   <rng:list>
    <rng:oneOrMore>
     <rng:ref name="data.pointer"/>
    </rng:oneOrMore>
   </rng:list>
  </rng:attribute>
 </rng:optional>
</rng:choice>
<rng:optional>
 <rng:attribute name="passive">
  <rng:list>
   <rng:oneOrMore>
    <rng:ref name="data.pointer"/>
   </rng:oneOrMore>
  </rng:list>
 </rng:attribute>
</rng:optional>
<rng:optional>
 <rng:ref name="desc"/>
</rng:optional>
</rng:element>
element relation
{
   att.global.attributes,
   att.datable.w3c.attributes,
   att.datable.iso.attributes,
   att.editLike.attributes,
   att.naming.attributes,
   attribute type { "social" | "personal" | "other" | xsd:Name }?,
   attribute name { data.enumerated },
   (
      attribute active { list { data.pointer+ } }?
    | attribute mutual { list { data.pointer+ } }?
   ),
   attribute passive { list { data.pointer+ } }?,
   desc?
}
Example
<relation
  type="social"
  name="supervisor"
  active="#p1"
  passive="#p2 #p3 #p4"/>

This indicates that the person with identifier p1 is supervisor of persons p2, p3, and p4.

Example
<relation type="personal" name="friends" mutual="#p2 #p3 #p4"/>

This indicates that p2, p3, and p4 are all friends.

Note
Only one of the attributes active and mutual may be supplied; the attribute passive may be supplied only if the attribute active is supplied. Not all of these constraints can be enforced in all schema languages.