Y'all I searched and the NIPs repo doesn't formally define the `d` tag anywhere.
That means no one can tell us we can't extend it lol.
I was thinking we use positional values to extend the `d` tag array. Something like:
```json
"tags": [
["d", "war-and-peace", "leo-tolstoy", "penguin-classics-edition"]
]
```
The general format would be `["d", <title>, <author>, <edition>]` where edition is a human-readable edition name (as opposed to just a number).
The event _should_ still be addressable by `#d` and the title, just like other event kinds' d tags, but we can increase address specificity for the Nostr Knowledge Base use case. Then we can bake this specificity into wikilinks (see NIP-54 for an existing wikilinks specification). A document might contain `[[War and Peace. Leo Tolstoy. Penguin Classics Edition.]]` and we can specify that clients should split that at the periods and normalize it into a d tag array reference, so it becomes `["#d", "war-and-peace", "leo-tolstoy", "penguin-classics-edition"]`. The client can then use this tag array to search its relays, find the closest match, and display to the user a hyperlink to the referenced event.
Basically, we define a citation format for NKB events.
Since the event ID is derived from a serialization of the whole event, including tags, increasing identifier specificity will always generate a unique event ID.
We'll have to experiment with how relays index events by d tag, and how they respond to queries for such events. Maybe Stella's PHP utilities can help us with that. Worst case, relays only support searching by the first `d` tag value and return a bunch of matching results, and then we have Alexandria walk through the results and find matches by author and edition.
buttercat1791 / Michael J
npub1wq…cqsyn
2024-09-14 14:36:13
in reply to nevent1q…3hzh
Author Public Key
npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsynPublished at
2024-09-14 14:36:13Event JSON
{
"id": "1b2a607f7d413d9eb0b517c62f3a0bf9690b3b3838a7d1172bdd0e25c187d4e9",
"pubkey": "70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9",
"created_at": 1726324573,
"kind": 1,
"tags": [
[
"e",
"3fbba0ec563849e0904f2d11a908ae89fa6c68e4e41a07ec75b665b532831c8e",
"wss://nostr.thesamecat.io",
"root"
],
[
"e",
"20dc3644f3762de6148a2f94bb1a9b40a11bc36bea465d8cb21f4e57648e67b3",
"wss://nostr.thesamecat.io",
"reply"
],
[
"r",
"2a6cbb5a1636735690493bcc8dcac147a174de45"
],
[
"a",
"30617:fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1:Alexandria"
],
[
"a",
"30617:dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06:Alexandria"
],
[
"a",
"30617:70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9:Alexandria"
],
[
"p",
"fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1",
"wss://theforest.nostr1.com/"
],
[
"p",
"dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06"
]
],
"content": "Y'all I searched and the NIPs repo doesn't formally define the `d` tag anywhere.\n\nThat means no one can tell us we can't extend it lol.\n\nI was thinking we use positional values to extend the `d` tag array. Something like:\n\n```json\n\"tags\": [\n [\"d\", \"war-and-peace\", \"leo-tolstoy\", \"penguin-classics-edition\"]\n]\n```\n\nThe general format would be `[\"d\", \u003ctitle\u003e, \u003cauthor\u003e, \u003cedition\u003e]` where edition is a human-readable edition name (as opposed to just a number).\n\nThe event _should_ still be addressable by `#d` and the title, just like other event kinds' d tags, but we can increase address specificity for the Nostr Knowledge Base use case. Then we can bake this specificity into wikilinks (see NIP-54 for an existing wikilinks specification). A document might contain `[[War and Peace. Leo Tolstoy. Penguin Classics Edition.]]` and we can specify that clients should split that at the periods and normalize it into a d tag array reference, so it becomes `[\"#d\", \"war-and-peace\", \"leo-tolstoy\", \"penguin-classics-edition\"]`. The client can then use this tag array to search its relays, find the closest match, and display to the user a hyperlink to the referenced event.\n\nBasically, we define a citation format for NKB events.\n\nSince the event ID is derived from a serialization of the whole event, including tags, increasing identifier specificity will always generate a unique event ID.\n\nWe'll have to experiment with how relays index events by d tag, and how they respond to queries for such events. Maybe Stella's PHP utilities can help us with that. Worst case, relays only support searching by the first `d` tag value and return a bunch of matching results, and then we have Alexandria walk through the results and find matches by author and edition.",
"sig": "a4fe309b2b2783d046704c6dec12b614d3256b5a8ad5a84ee17bf07e72fa457ec16edc67e60efbda660b1eb4941491d9c86d8022906402152adcba40f2ab7772"
}