mleku the disregarded @mleku - 6d
do these event kinds include a label and label namespace by default? probably would be a useful way to add category data and enable the kind to become a general purpose grouping operator (they could be stacked hierarchically too)
Silberengel @Silberengel - 6d
30040s? That's what they're used for, yes. For creating note collections and hierarchies. We allow for optional tags, including labels. Already listed a bunch in the spec, but you could add labels. #Alexandria just ignores whatever additional tags it doesn't utilize. We didn't bother including labels, as we're going for embeddings, with the 1987 kinds. https://wikistr.com/nkbip-01*70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9 https://wikistr.com/nkbip-02*dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06
well, just a thought... aggregating things into groups is a general purpose that cuts across many use cases
Yeah, that's why we didn't limit 30040s to 30041s. You could aggregate any event kind and use any tags, so long as you have the mandatory ones. If your 30040 doesn't include any other 30040s, then it's an ordered list of whatever events. If it does, then it's a nested hierarchy of indexes, like for a ToC. ``` Kind 30040 MUST have events listed in e tags in the order that they appear in the article. The events may be any already-existing event (including nested kind 30040s). ```
eBooks are just our first use case because we want to start off with the Bible, but obviously, I can think of a gazillion different types of collections. A photo collage, or a playlist, or an audiobook, a "best of" grouping of someone's long-form articles, related wiki pages, or etc.