This seems completely uncontroversial to me. If <listEvent> can be a child of <person>, it should also be available as a child of <org>. If events happen to people they must happen to organizations too. The mechanics of it are not quite the same; <person> gets <listOrg> through model.personEventLike: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-model.persEventLike.... which includes <birth>, <death> and <event> as well as <listEvent>. The little invisible horned thing standing on my shoulder is whispering to me that organizations are also born, and also die, and we use the same vocabulary to describe those events as we do for people. But probably it would be better to use <event type="incorporation">, <event type="foundation"> and so on, to be more precise about what is intended. Cheers, Martin On 15-04-24 01:42 PM, Syd Bauman wrote:
Julia just reminded me that <event> still is not allowed as a child or grandchild of <org>. Off the top of my head, I don't see why <listEvent> is not a member of model.orgPart. Not quite so obvious how to make <event> an eligible direct child of <org>, but it seems like a reasonable request.
I plan to submit a bug report shortly, with hopes that we can tackle this and solve it for next release.
(Although I have my suspicions that this will bring up other thorny issues.)