I would like to construct a template for recording historical
information about a person. Such records might be used for a
According to section 13.3.1 of the P5 Guidelines, information about
people essentially comprises a series of statements about traits,
states, and events. This seems like a good way to describe people so I
would like to organize the template accordingly:
<!-- Traits: things that rarely change. -->
<!-- States: things that hold for a time. -->
<!-- Events: things which may change states or even traits. -->
I may be committing tag abuse by filling <residence> with a number of
<placeName>s and <education> with a number of <orgName>s, but this seems
to be a nice way to organise things.
And this is where I hit a problem. By analogy with my possible abuse of
<residence> and <education>, I would like to have an element that can be
a child of <person> and parent of multiple <occupation>s. E.g.
There is already a <listEvent>. Why not have a <listState> and
<listTrait> too? And why not let them be children of <person>?
(As things stand, <listEvent> is not allowed to be a child of <person>
even though <event> is.)
I'd also like <relationGrp> to be allowed as a child of <person> because
that would be a handy place to put a person's <relation>s. (One end of
each relation could then be deduced from, say, the ancestor [log in to unmask])
I fear that it would be impolite (or revealing-of-ignorance) to ask for
<person> to be allowed as a direct child of elements like <particDesc>,
<body>, and <div>.