12.1.134. <trait>

<trait> (trait) contains a description of some status or quality attributed to a person, place, or organization typically, but not necessarily, independent of the volition or action of the holder and usually not at some specific time or for a specific date range. [14.3.1. Basic Principles 14.3.2.1. Personal Characteristics]
Module	namesdates — Specification
Attributes	att.global @xml:id @n @xml:lang @xml:base att.global.analytic @ana att.global.change @change att.global.facs @facs att.global.linking @corresp @synch @sameAs @copyOf @next @prev @exclude @select att.global.rendition @rend @style @rendition att.global.responsibility @cert @resp att.global.source @source att.cmc @generatedBy att.datable @period att.datable.custom @when-custom @notBefore-custom @notAfter-custom @from-custom @to-custom @datingPoint @datingMethod att.datable.iso @when-iso @notBefore-iso @notAfter-iso @from-iso @to-iso att.datable.w3c @when @notBefore @notAfter @from @to att.dimensions @unit @quantity @extent @precision @scope att.ranging @atLeast @atMost @min @max @confidence att.editLike @evidence @instant att.naming @role @nymRef att.canonical @key @ref att.typed @type @subtype
Member of	model.persStateLike model.placeStateLike
Contained by	core: abbr author bibl biblScope citedRange date desc editor email expan gloss head hi item name p pubPlace publisher rb resp rt term corpus: channel domain interaction purpose figures: figDesc header: authority change edition licence principal rendition tagUsage namesdates: affiliation age education faith floruit forename gender langKnown nationality occupation orgName persName persPronouns person personGrp persona place placeName residence sex socecStatus surname trait
May contain	core: bibl biblStruct desc head listBibl note p namesdates: trait
Note	Where there is confusion between <trait> and <state> the more general purpose element <state> should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The <state> element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.
Example	`<trait type="physical"> <label>Eye colour</label> <desc>Blue</desc> </trait>`
Content model	<content> <sequence> <elementRef key="precision" minOccurs="0" maxOccurs="unbounded"/> <alternate> <elementRef key="trait" minOccurs="1" maxOccurs="unbounded"/> <sequence> <classRef key="model.headLike" minOccurs="0" maxOccurs="unbounded"/> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.noteLike"/> <classRef key="model.biblLike"/> </alternate> </sequence> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.labelLike"/> <classRef key="model.noteLike"/> <classRef key="model.biblLike"/> </alternate> </alternate> </sequence> </content> ⚓
Schema Declaration	`element trait { att.global.attributes, att.cmc.attributes, att.datable.attributes, att.dimensions.attributes, att.editLike.attributes, att.naming.attributes, att.typed.attributes, ( precision, ( trait+ \| ( model.headLike, model.pLike+, ( model.noteLike \| model.biblLike )* ) \| ( model.labelLike \| model.noteLike \| model.biblLike )* ) ) }`⚓