documents

Further elaboration on my answer 

@Lady I mean, SOME of them aren't documents! Depending on their content, and also the context of the collection.

(Also some things can be documents, while also being bad at being documents.)

Further elaboration on my answer 

@Lady Shooting from the hip, and Knowing Nothing, I might think about structuring this as

"The [Object] class representings things which hold a static chunk of data."
With then e.g. "The [Image] class is a subclass of [Object]s representing things which have nonmoving 2D image data."

and "The relation [__ is a document in __] connects [Object]s to [Collection]s which contain them, and carries with it properties of that document in that context."

re: Further elaboration on my answer 

@gaditb what does “static” mean in this context? can objects be edited?

Follow

re: Further elaboration on my answer 

@gaditb in any case i think this vocabulary (FOAF) is trying to characterize “documents” as something more than or different from just “any collection of data” :⁠—

• in allowing for documents which are not backed by data, for example, physical documents

• in allowing for documents to be edited and maintain a stable identity across edits

• in distinguishing documents from constellations of data which do not have “document identity”—for example a single reading from a sensor at a given point of time is a static piece of data, but usually not considered a document, SHA hashes are not documents, ⁊·c

· · Web · 1 · 0 · 0

re: Further elaboration on my answer 

@Lady Yeah I erased and rewrote that word a few times because I was pretty sure I davka didn't want "fixed/unchanging", but I couldn't think of what better.

I was thinking "something that at a particular time has specific information it holds". Not necessarily "unchanging", but not "dynamic".

e.g. something I was considering definitely-not-that was a Stream of events/updates, especially in the sense CRDTs visualize things. (If you're using that to collaborate then you could serialize it into an Object, as a snapshot-view of the shared work, but the shared no-defined-"fully-up-to-date" space isn't one.)

(I don't think the data needs to be digital necessarily. Just.. I dunno, "specific"? "fixed-referant"?)

Sign in to participate in the conversation
📟🐱 GlitchCat

A small, community‐oriented Mastodon‐compatible Fediverse (GlitchSoc) instance managed as a joint venture between the cat and KIBI families.