docs(NIP-64): change kind from 30 to 64

This commit is contained in:
theborakompanioni 2024-02-28 16:41:40 +01:00
parent 653642205e
commit e735ef9aef
No known key found for this signature in database
GPG Key ID: E8070AF0053AAC0D

10
64.md
View File

@ -6,7 +6,7 @@ Portable Game Notation
`draft` `optional`
This NIP defines `kind:30` notes representing Chess games in [PGN][pgn_specification] format, which can be read by humans and is also supported by most chess software.
This NIP defines `kind:64` notes representing games in [PGN][pgn_specification] format, which can be read by humans and is also supported by most chess software.
## Note
@ -18,7 +18,7 @@ The `.content` of these notes is a string representing a [PGN-database][pgn_form
```json
{
"kind": 30,
"kind": 64,
"content": "1. e4 *",
...
}
@ -26,7 +26,7 @@ The `.content` of these notes is a string representing a [PGN-database][pgn_form
```json
{
"kind": 30,
"kind": 64,
"tags": [
["alt", "Fischer vs. Spassky in Belgrade on 1992-11-04 (F/S Return Match, Round 29)"],
...
@ -38,12 +38,12 @@ The `.content` of these notes is a string representing a [PGN-database][pgn_form
## Client Behavior
Clients SHOULD check whether the formatting is valid and all moves comply with chess rules.
Clients SHOULD display the content represented as chessboard.
Clients SHOULD publish PGN notes in ["export format"][pgn_export_format] ("strict mode", i.e. created by machines) but expect incoming notes to be in ["import format"][pgn_import_format] ("lax mode", i.e. created by humans).
Clients SHOULD check whether the formatting is valid and all moves comply with chess rules.
Clients MAY include additional tags (e.g. like [`"alt"`](https://github.com/nostr-protocol/nips/blob/master/31.md)) in order to represent the note to users of non-supporting clients.
## Relay Behavior