54 lines
1.1 KiB
Markdown
54 lines
1.1 KiB
Markdown
%%
|
|
Title: Datastore tuples
|
|
Created: 2022-03-08 01:45
|
|
Status:
|
|
Parent: [[Archive/Computing/KExocortex/KnowledgeGraph]]
|
|
Tags: #MissingContext
|
|
Source:
|
|
%%
|
|
|
|
# Datastore tuples
|
|
|
|
- [[202203080152 Entity Attribute Value]]
|
|
- [[zk/202203080153 Transactional Entity Attribute Value]]
|
|
|
|
#### What's the context?
|
|
|
|
I think where I was going with this is that each cell that gets entered into the knowledge graph is a tuple. I'm not sure that still makes sense.
|
|
|
|
## n-tuple
|
|
|
|
* Entity
|
|
* Does a single string serve to identify this?
|
|
* Maybe a "Name": {common name, id}
|
|
* Can the ID be a UUID?
|
|
* What about documents with a DOI? Does this matter?
|
|
* Attribute
|
|
* Tempted to make this a string
|
|
* What if every attribute is a Name?
|
|
|
|
|
|
```protobuf
|
|
message Name {
|
|
string id = 1; // e.g. a UUID
|
|
string common = 2;
|
|
};
|
|
|
|
message Attribute {
|
|
Name name = 1;
|
|
Value value = 2;
|
|
}
|
|
|
|
message Transaction {
|
|
int64 timestamp = 1;
|
|
};
|
|
|
|
message Fact {
|
|
Name entity = 1;
|
|
Attribute attribute =2;
|
|
Value value = 3;
|
|
Transaction transaction = 4;
|
|
boolean retraction = 5;
|
|
};
|
|
```
|