#eventmarkup

2024-02-28

@gvogeler
For contested dates that are clearly refering to the same `event` I see the point for having a series of different dating assertions without thinking of these as different related events refering to the same concept…
For person, there’s multiple dates allowed in birth/death (which are special cases for event).
#eventmarkup

2024-02-22

@gvogeler following up on this: The other entity elements (person, place, org etc) do not allow a parentless `date` either. The only kind-of-exception is `birth` and `death`, which are syntactic sugar/special cases of `event`.
The takeaway is that having a `date` without a mandatory `@type` (or other means of specifying the relation between a `date` and its parent element) would result in ambiguities. To sum up, I think the current solution is not that bad. #TEIXML #eventmarkup

2024-02-21

@type (master of events 😀 ) tei-c.org/release/doc/tei-p5-d deliberately does not allow nesting a <date>? #TEIXML #eventmarkup

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst