Okay, it's all a bit fuzzy. The spec assumes 30040 is always an article and each linked element is a section of the article. But we also allowed for 30040 to be a book and each linked element is then a chapter. And we allowed for 30040 to be a collection and each linked element is then an article, in it's own right. I made a 30040 that was an audiobook list and each 30041 contained an audiobook episode.

I actually prefer 30040 index and 30041 section, as we don't presume to know the content of the events, we're just describing what the "do": one contains a list of events, the other contains a portion of the content. 

 Yeah, bit fuzzy but that's why in some earlier conversations i made analogues to 30040s being some type of container event. They also got inspiration from lists and how you can have a top level note with other comments chained under it.

Containers can hold other containers, but collectively the pairing of 30040s with a sequence of various events constructs a modular article, not that 30040s are the modular article event. 

 Recording here what we discussed in Slack:

- 'Zettel' is the term we're using specifically for kind 30041 events.  They are intended to be bite-sized notes.
- 'Index' is the term we're using for kind 30040 events.
- 'Event' is the generic term.  Wiki entries, long-form articles, indices, and zettels are all 'events.'  If we don't have a specific term for an event kind in a given instance, we'll call it an 'event.'

Terms like 'node,' 'block,' and 'section' are specific to Asciidoctor.  I can add details in the code comments explaining how we are using different terms throughout the parser logic. 

 In terms of feed based implementation, maybe some 30040s should have an explicit 'top level' indicator. That way chapters won't be seen in the feed.