Introduction problem #34

Open
opened 2023-06-18 16:51:47 +02:00 by thm · 0 comments

Sometimes, it may be beneficial to only mark a certain address as existing within a vault, even though no information is associated with it.

For example, when a data blob is present, but nameless; or an URL, which is entered into the vault (for possible later annotation).

(From a more wishy-washy perspective, the moment something is entered into e.g. the pile has unique meaning, which is also the secondary purpose of numeric document IDs. What's the equivalent in content-addressable systems?)

Possible resolutions:

  • ADDED attribute (current quasi-workaround)
  • Entity Attribute="" Value=Invalid triplet (ugly?)
  • "God-object" to which these free-floating entities are related to (implications?)
Sometimes, it may be beneficial to only mark a certain address as existing within a vault, even though no information is associated with it. For example, when a data blob is present, but nameless; or an URL, which is entered into the vault (for possible later annotation). (From a more wishy-washy perspective, the moment something is entered into e.g. [the pile](https://pile.sdbs.cz) has unique meaning, which is also the secondary purpose of numeric document IDs. What's the equivalent in content-addressable systems?) Possible resolutions: - `ADDED` attribute (current quasi-workaround) - `Entity Attribute="" Value=Invalid` triplet (ugly?) - "God-object" to which these free-floating entities are related to (implications?)
thm added the
structure
label 2023-06-18 16:51:47 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: thm/upend#34
There is no content yet.