#751 <event> not allowed in <org>

[Syd Bauman]

<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.

[Martin Holmes]

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.html

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.

[Peter Stadler]

I was just working on a schema for corporate bodies and tried to add something like <event type="foundation"> for encoding the foundation date. So +1 from me for fixing this bug!
For the record, there is an open feature request to rationalize content models of org and place (etc) [feature-requests:#366]

[Syd Bauman]

On 2015-05-25 I created a branch of P5 for addressing this bug (https://svn.code.sf.net/p/tei/code/branches/P5/for-bug-751). The fix was checked into that branch for Council to take a look at and concur or object.

[Syd Bauman]

Fixed in 13301 by merging the for-bug-751 branch into the trunk, as Council said this repair was fine in our last conference call.