thanks for the clarification 

 30040 and 30041 events aren't expected to have matching titles.  30040 events act as an index of multiple 30041 events, so the name of the index/collection will likely differ from the names of the individual 30041 fragments of which it is composed. 

 are the "e" tag events in 30040 events 30041? they will have to match somehow I think. 

 Yes the e tags in 30040 events reference 30041.  The reference format is kind+pubkey+d-tag, IIRC.  So the e tag references should include a d tag that shows up in some 30041 event. 

 e tags in 30040 can reference any event kind, includind 01 or other 30040. We just defined 30041 as the default kind. 

 Ope I hadn't thought about that yet!  We'll need to add some extra rules for rendering non-30041 events in our viewer. 

 That was the path that was causing so much confusion for @PABLOF7z . He didn't realize that 30040s can contain any event.

We should probably stick to human-written content, for the first run-through. Kind 01, long-form, wikis, 30041s probably enough. What do you think @liminal ? 

 I see other directions, but for now let's stick to the article use cases to render in the Alexandria client. 

 So, plain-text, markdown, asciidoc. 

 Yes, the e tags can include 30041 events or any other event.