Event JSON
{
"id": "0cd705221fc683d5f53a2a02ff5968c541ff1dd88b2e28f74c77f9e5386252dc",
"pubkey": "277c6a290699ff0dd3474ade6851305ae20f5bdf2f15e1400c21d870b0475426",
"created_at": 1689500955,
"kind": 1,
"tags": [
[
"p",
"d4ef978919acbc1c641db1b3392fa19fc786a1070e0d14897709d5893f019816",
"wss://relay.mostr.pub"
],
[
"p",
"d4e0623c6b6a5b0911b013e1e242fc477ec8d689f8e38c14e2742fe0120b4cf9",
"wss://relay.mostr.pub"
],
[
"e",
"a618da1a851ae92654a4fa54d7342cc61f2af68e7461d9bb833ed18ec87c609b",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"logseq"
],
[
"t",
"class"
],
[
"mostr",
"https://pkm.social/users/alexl/statuses/110723134605343568"
]
],
"content": "nostr:npub16nhe0zge4j7pceqakxenjtapnlrcdgg8pcx3fzthp82cj0cpnqtqzvtnnq \n\nI don't know if this is what you mean but in Logseq you can use namespaces in tags to differenciate their meaning, for example #Logseq tag would mean \"this is ABOUT Logseq\" while #class/person/author would mean \"this IS a person and in particular an author\".\n\nIn queries you can filter out the whole \"class\" namespace for example.\n\nBut you can also use properties like class:: [[person/author]] that have the advantages of being columns in the queries' table view.",
"sig": "05bbed0b4c2b4c2a4e753a75a418cc55cc4e342abdbd7a1e427b571059e7fd8d0c2d5a01701ef6a898460baac79d7fe26b68c3f6a3848c73f354e13c54d827b6"
}