Thank you for the elaborate explanation. I don't understand the need for the negotiation process, but I will read deeper later.
IMO, finding a way to have as much of the logic reside in the Nostr protocol in the form of a data scheme laid over events and profiles is vital.
This will allow the use case you described and many other use cases to run over the data and strengthen each other, like what is happening with the current social media use cases of the Nostr protocol.
These are roughly the changes I think are required at the protocol level to enable this:
In short:
Adding a Product type Nostr event that describes a tradable product.
Adding skills as a possible property list of a user profile.
Adding Rating type Nostr event that rates a product or a skill.
In longer form:
Products
========
Product Event
- High-level type of product - Good, Service, ...
- [categorie1, categorie2, categorie3, ...] categories the products fits into. For an apple, this may be ['food', 'fruit', 'ready to eat food', ...]
- ID: Unique Pubkey Id of this product
- Description in text
- Description media - image or video
- Price value
- Unit of account that the price quotes - Bitcoin, Dollar, ....
- Purchasing process URL. Calling this with the product ID redirects to a purchasing page.
Social rating
==========
Rating event
- Rating value
- Rating range [min max]
- [Skill: skill that is being rated, Profile ID: Profile to which this rating applies]
- Item id: the item that is being rated.
- Rater ID. The ID of the user who gives the rate
- Commen
Division of labor
=============
Add the to set_metadata event. Note that this is only for a user who is a seller of goods or products.
- [skill2, skill2, ] skills that the user proclaims. Skill may be in the service category (marketer, developer) or in the product supplier category (cloths store, electronic device store,... ). Profile skills may be rated by other users who will send rate events
- [product1, product2, produ3] - Ids of products supplied by the use
ofer.elrom / Ofer Elrom
npub13q…lnw8c
2023-02-23 23:01:38
in reply to nevent1q…utvn
Author Public Key
npub13qktwex55g7re2thlp2klcnhm8ry86gex90l6j7w8mz5thq7ywpsvlnw8cPublished at
2023-02-23 23:01:38Event JSON
{
"id": "3321765370372bcefade25c9fd2d7b455b967cf4f90cbe76cb07328560e2727c",
"pubkey": "882cb764d4a23c3ca977f8556fe277d9c643e919315ffd4bce3ec545dc1e2383",
"created_at": 1677193298,
"kind": 1,
"tags": [
[
"e",
"1d74cb1693dad3649814bfabcce6bec75afa23575604f6aa7b647c16a8819312",
"wss://eden.nostr.land",
"root"
],
[
"p",
"88e9326a185488072480e0383d2968f7c2f1bc73ef7ad9999f400459afc053dc"
],
[
"e",
"0f392350bb055241bef4823f4e73fd49e580a0813a035b9c3633d41d11470d3a",
"wss://eden.nostr.land",
"reply"
],
[
"p",
"88e9326a185488072480e0383d2968f7c2f1bc73ef7ad9999f400459afc053dc"
]
],
"content": "Thank you for the elaborate explanation. I don't understand the need for the negotiation process, but I will read deeper later.\nIMO, finding a way to have as much of the logic reside in the Nostr protocol in the form of a data scheme laid over events and profiles is vital.\nThis will allow the use case you described and many other use cases to run over the data and strengthen each other, like what is happening with the current social media use cases of the Nostr protocol.\nThese are roughly the changes I think are required at the protocol level to enable this:\nIn short:\nAdding a Product type Nostr event that describes a tradable product.\nAdding skills as a possible property list of a user profile.\nAdding Rating type Nostr event that rates a product or a skill.\nIn longer form:\n\nProducts\n========\nProduct Event\n- High-level type of product - Good, Service, ...\n- [categorie1, categorie2, categorie3, ...] categories the products fits into. For an apple, this may be ['food', 'fruit', 'ready to eat food', ...]\n- ID: Unique Pubkey Id of this product\n- Description in text\n- Description media - image or video\n- Price value\n- Unit of account that the price quotes - Bitcoin, Dollar, ....\n- Purchasing process URL. Calling this with the product ID redirects to a purchasing page.\n\nSocial rating\n==========\nRating event\n- Rating value\n- Rating range [min max]\n- [Skill: skill that is being rated, Profile ID: Profile to which this rating applies]\n- Item id: the item that is being rated.\n- Rater ID. The ID of the user who gives the rate\n- Commen\n\nDivision of labor \n=============\nAdd the to set_metadata event. Note that this is only for a user who is a seller of goods or products.\n- [skill2, skill2, ] skills that the user proclaims. Skill may be in the service category (marketer, developer) or in the product supplier category (cloths store, electronic device store,... ). Profile skills may be rated by other users who will send rate events\n- [product1, product2, produ3] - Ids of products supplied by the use",
"sig": "4f26a4632e2592494873b15723f560e039247ff35cebe32c5b320f2ebdc73dd15cbe4062aabcbe3d764bf78f836ff5e26ef72dce10cc56da31d19759035a54a5"
}