It is currently unclear how larger and more complex events should be modelled.
It would be good to improve the Event documentation to cover this.

• http://musicbrainz.org/doc/Event

Questions

• Should the year be included in the title (even if it is also included in the date attribute?)
• How should an event with multiple stages and venues over multiple days be represented (eg Glastonbury: http://www.bbc.co.uk/events/errnc8/performances/lg49mb)
• When creating a complex inter-relationship of lots of separate series and event types, should the names of the ancestors be copied into the children - or should the UI infer this?
  • For example, if you wanted to create a list of events for a single season, it could result in a lot of duplicate text in the view.

Series: https://beta.musicbrainz.org/series/02c9a5b9-6b2c-461e-953d-6d4f6a9cc2d2
One year Festival: https://beta.musicbrainz.org/event/2df30019-64a3-4281-b917-bb35a0563b1c
Single prom event: https://beta.musicbrainz.org/event/e1b75bd6-6a99-40d3-94be-d2c0c509d320

Freso has suggested the following style:
https://www.musicbrainz.org/event/206f9b9d-323d-4cbf-bd9d-95d67507630e

Which looks really good when viewing a single event but does duplicate information, for example an index for all the day events in 1921 might look like this:

• The Proms 1921: Prom 04 (1921-08-18)
• The Proms 1921: Prom 05 (1921-08-19)
• The Proms 1921: Prom 06 (1921-08-20)
• The Proms 1921: Prom 07 (1921-08-21)
• The Proms 1921: Prom 08 (1921-08-22)
• The Proms 1921: Prom 09 (1921-08-23)
• The Proms 1921: Prom 10 (1921-08-24)
• The Proms 1921: Prom 11 (1921-08-25)

However duplicating the information makes searching and disambiguation much easier.