This NIP defines the minimum specification for collections - ordered, optionally-hierarchical assemblies of nostr events. Collections provide a standard way to organize and present related content, similar to how books organize chapters or journals organize articles.
## Event Kinds
This NIP defines two primary event kinds:
-`30040`: Collection Index
-`30041`: Collection Section
## kind 30040: Collection Index
A collection index defines the structure and metadata of a collection. It serves as a table of contents that references the actual content sections.
### Requirements
- The `content` field MUST be empty
- MUST include a `title` tag containing the full title of the collection
- MUST be uniquely identifiable by the combination of:
"content": "== The Farmer and The Snake\nA [[fable]], by Aesop.\nONE WINTER a Farmer found a Snake stiff and frozen with cold. He had compassion on it, and taking it up, placed it in his bosom. The Snake was quickly revived by the warmth, and resuming its natural instincts, bit its benefactor, inflicting on him a mortal wound. 'Oh,' cried the Farmer with his last breath, 'I am rightly served for pitying a scoundrel.'\nThe greatest kindness will not bind the ungrateful.",
"sig": "49cab8c75fb35cec71d07258..."
}
```
## Extensions
Collections are flexible and can be extended for different types of content. Examples include:
- Books
- Academic journals
- Course materials
- Documentation
Additional tags relevant to the specific content type MAY be included in both index and section events.