diff options
Diffstat (limited to '99.md')
| -rw-r--r-- | 99.md | 9 |
1 files changed, 5 insertions, 4 deletions
| @@ -8,9 +8,9 @@ Classified Listings | |||
| 8 | 8 | ||
| 9 | This NIP defines `kind:30402`: a parameterized replaceable event to describe classified listings that list any arbitrary product, service, or other thing for sale or offer and includes enough structured metadata to make them useful. | 9 | This NIP defines `kind:30402`: a parameterized replaceable event to describe classified listings that list any arbitrary product, service, or other thing for sale or offer and includes enough structured metadata to make them useful. |
| 10 | 10 | ||
| 11 | The category of classifieds includes a very broad range of physical goods, services, work opportunities, rentals, free giveaways, personals, etc. and is distinct from the more strictly structured marketplaces defined in [NIP-15](https://github.com/nostr-protocol/nips/blob/master/15.md) that often sell many units of specific products through very specific channels. | 11 | The category of classifieds includes a very broad range of physical goods, services, work opportunities, rentals, free giveaways, personals, etc. and is distinct from the more strictly structured marketplaces defined in [NIP-15](15.md) that often sell many units of specific products through very specific channels. |
| 12 | 12 | ||
| 13 | The structure of these events is very similar to [NIP-23](https://github.com/nostr-protocol/nips/blob/master/23.md) long-form content events. | 13 | The structure of these events is very similar to [NIP-23](23.md) long-form content events. |
| 14 | 14 | ||
| 15 | ### Draft / Inactive Listings | 15 | ### Draft / Inactive Listings |
| 16 | 16 | ||
| @@ -26,8 +26,8 @@ The `.pubkey` field of these events are treated as the party creating the listin | |||
| 26 | 26 | ||
| 27 | ### Metadata | 27 | ### Metadata |
| 28 | 28 | ||
| 29 | - For "tags"/"hashtags" (i.e. categories or keywords of relevance for the listing) the `"t"` event tag should be used, as per [NIP-12](https://github.com/nostr-protocol/nips/blob/master/12.md). | 29 | - For "tags"/"hashtags" (i.e. categories or keywords of relevance for the listing) the `"t"` event tag should be used, as per [NIP-12](12.md). |
| 30 | - For images, whether included in the markdown content or not, clients SHOULD use `image` tags as described in [NIP-58](https://github.com/nostr-protocol/nips/blob/master/58.md). This allows clients to display images in carousel format more easily. | 30 | - For images, whether included in the markdown content or not, clients SHOULD use `image` tags as described in [NIP-58](58.md). This allows clients to display images in carousel format more easily. |
| 31 | 31 | ||
| 32 | The following tags, used for structured metadata, are standardized and SHOULD be included. Other tags may be added as necessary. | 32 | The following tags, used for structured metadata, are standardized and SHOULD be included. Other tags may be added as necessary. |
| 33 | 33 | ||
| @@ -40,6 +40,7 @@ The following tags, used for structured metadata, are standardized and SHOULD be | |||
| 40 | - `"<number>"` is the amount in numeric format (but included in the tag as a string) | 40 | - `"<number>"` is the amount in numeric format (but included in the tag as a string) |
| 41 | - `"<currency>"` is the currency unit in 3-character ISO 4217 format or ISO 4217-like currency code (e.g. `"btc"`, `"eth"`). | 41 | - `"<currency>"` is the currency unit in 3-character ISO 4217 format or ISO 4217-like currency code (e.g. `"btc"`, `"eth"`). |
| 42 | - `"<frequency>"` is optional and can be used to describe recurring payments. SHOULD be in noun format (hour, day, week, month, year, etc.) | 42 | - `"<frequency>"` is optional and can be used to describe recurring payments. SHOULD be in noun format (hour, day, week, month, year, etc.) |
| 43 | - - `"status"` (optional), the status of the listing. SHOULD be either "active" or "sold". | ||
| 43 | 44 | ||
| 44 | #### `price` examples | 45 | #### `price` examples |
| 45 | 46 | ||