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.

<content>
 <sequence>
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate>
   <elementRef key="state" 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>

element state
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   tei_att.naming.attributes,
   tei_att.dimensions.attributes,
   (
      tei_precision*,
      (
         tei_state+
       | (
            tei_model.headLike*,
            tei_model.pLike+,
            ( tei_model.noteLike | tei_model.biblLike )*
         )
       | ( tei_model.labelLike | tei_model.noteLike | tei_model.biblLike )*
      )
   )
}