Soon it becomes apparent that, wait, that same electrode group collects multiple timeseries, so it should probably be its own thing that I can reference in multiple places. So the ability to create references is added, and the ability to create anonymous sub-things is also retained, because not everything is reused.
so electrode is its own thing, but it too has its own anonymous untyped things, and I want to reference those. So now I need to create a reference with subselection - "this electrode within electrode group x." This is often done by creating another anonymous subthing within the referring thing - "a table that contains indices with which I select from the thing I'm referring to." When you un-nest the schema, these kinds of references are actually most of the anonymous classes.
This is a pretty tight analogical map to blank nodes, this tension in #RDF where "everything should be uniquely, globally identifiable" but "actually not literally everything because that would be ridiculous." And blank nodes have caused a ton of work to be needed to eg. canonicalize graphs so you can automatically assign unique names to things.
See also #IPLD which makes some different choices, notably being to treat every subgraph as ordered even though graphs don't have an intrinsic ordering: https://ipld.io/design/tricky-choices/ordering/
(Side note every project should have a "tricky choices" section in the docs. Props to protocol labs for that)
Dr. jonny phd /
npub1ny…dxmrh
2023-08-27 00:30:02
in reply to nevent1q…5ak0
Author Public Key
npub1nyn0d3f3vgefljenfq0schd55q2mm43a2errd6sncdw5jawpwm3s3dxmrhPublished at
2023-08-27 00:30:02Event JSON
{
"id": "d0b07a0615a391c8312fd27ceab814922d066dcd07d98f4eda4d08e2b54d01ee",
"pubkey": "9926f6c53162329fcb33481f0c5db4a015bdd63d564636ea13c35d4975c176e3",
"created_at": 1693096202,
"kind": 1,
"tags": [
[
"e",
"6f7e4a3a8696803c5187daecfbab43fe2b2c16f85faa7da7df20d8c90da9245c",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"rdf"
],
[
"t",
"ipld"
],
[
"proxy",
"https://neuromatch.social/users/jonny/statuses/110958752712180828",
"activitypub"
]
],
"content": "Soon it becomes apparent that, wait, that same electrode group collects multiple timeseries, so it should probably be its own thing that I can reference in multiple places. So the ability to create references is added, and the ability to create anonymous sub-things is also retained, because not everything is reused.\n\nso electrode is its own thing, but it too has its own anonymous untyped things, and I want to reference those. So now I need to create a reference with subselection - \"this electrode within electrode group x.\" This is often done by creating another anonymous subthing within the referring thing - \"a table that contains indices with which I select from the thing I'm referring to.\" When you un-nest the schema, these kinds of references are actually most of the anonymous classes.\n\nThis is a pretty tight analogical map to blank nodes, this tension in #RDF where \"everything should be uniquely, globally identifiable\" but \"actually not literally everything because that would be ridiculous.\" And blank nodes have caused a ton of work to be needed to eg. canonicalize graphs so you can automatically assign unique names to things.\n\nSee also #IPLD which makes some different choices, notably being to treat every subgraph as ordered even though graphs don't have an intrinsic ordering: https://ipld.io/design/tricky-choices/ordering/\n(Side note every project should have a \"tricky choices\" section in the docs. Props to protocol labs for that)",
"sig": "b87a11e0d125e12f8f1187385a8ee594a096f9c4aa8f162449118843a0a38847214c166a4432ea4e26723b32bb9d0742f328556b63047b95c027be3814ba3799"
}