nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 08:55:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update 211.md

Browse Source
This commit is contained in:
unostr 2023-11-18 22:54:15 +03:00 committed by GitHub
parent 1d5ae28be8
commit 6e49c2cb55
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
211.md
View File

@ -7,7 +7,7 @@ Info Triple Note
`draft` `optional` `draft` `optional`
TLDR: Info Triples can be used when creating micro apps as an alternative to adding new meta data to the NOSTR Note's JSON document. TLDR: Info Triples can be used when creating micro apps as an alternative to adding new meta data to the NOSTR Note's JSON document.
Because of that we will no longer have to write a new NIP for each type of micro app created and thus the JSON structure can be kept simple. Because of that we will no longer have to write a new NIP for each type of micro app created and thus the JSON structure can be kept simpler.
I propose a new event type "211" which is a note meant to describe relationships between "stuff" in a machine friendly way using Info Triples. I propose a new event type "211" which is a note meant to describe relationships between "stuff" in a machine friendly way using Info Triples.
"Stuff" here are represented by large numbers, as identifiers, and would most likely be SHA256 hashes of data objects. "Stuff" here are represented by large numbers, as identifiers, and would most likely be SHA256 hashes of data objects.
@ -49,15 +49,14 @@ Encoding
-------- --------
Simple hex values works, as they do for other fields in the NOSTR note. Simple hex values works, as they do for other fields in the NOSTR note.
However there are some size benefits to gain from using, for example, Base64 or Base58 encoding. However there are some size benefits to gain from using, for example, Base64 or Base58 encoding.
To tell clients and relays what form of encoding is used self-reporting, as described in Nip 32 and 56, can be used. To tell clients and relays what form of encoding is used self-reporting, as described in Nip 32, can be used.
Nip 32 Labeling (and NIP 56 Reporting) Nip 32 Labeling (and NIP 56 Reporting)
---------------------------------- ----------------------------------
Nostr have another way of classifying content already in the form defined in Nip 32 and Nip 56. Nostr have another way of classifying content already in the form defined in Nip 32 and Nip 56.
Some differences between NIP 211 Info Triples and NIP32 Labeling: Some differences between NIP 211 Info Triples and NIP32 Labeling:
- Info Triples are meant to model complex data as well and are therefore more comparable to Knowledge Graphs. - Info Triples are meant to model complex data as well and are therefore more comparable to Knowledge Graphs.
- Info Triples are meant for modeling information in general (not just NOSTR notes) and hence the NOSTR note can seen as a carrier/envelope. - Info Triples are meant for modeling information in general (not just NOSTR notes) and hence the NOSTR note can seen as a carrier/envelope. In comparison the NIP32 are specifically targeting everything NOSTR: events, people, relays, topics...
In comparison the NIP32 are specifically targeting everything NOSTR: events, people, relays, topics...
- NIP 32 is meant to create human readable tags, Info Triples are meant for machine readable meta data, which can then be augmented with human readble Descriptor Notes (NIP101) - NIP 32 is meant to create human readable tags, Info Triples are meant for machine readable meta data, which can then be augmented with human readble Descriptor Notes (NIP101)
- NIP 32 is meant to keep everything within the scope of NOSTR. Info Triples let the developer abstract from the NOSTR layer and build new micro protocols on top of NOSTR. - NIP 32 is meant to keep everything within the scope of NOSTR. Info Triples let the developer abstract from the NOSTR layer and build new micro protocols on top of NOSTR.
- It is not a priority for Info Triple data to be recognizable by relays (or everybody). For the NIP 32 labeling namespaces "should" be well-defined. - It is not a priority for Info Triple data to be recognizable by relays (or everybody). For the NIP 32 labeling namespaces "should" be well-defined.