Things I consider "a document" and that I would like to manipulate as files in my filesystem:<p>* A Facebook post.<p>* An email I receive.<p>* A form I fill in online.<p>* A chat session on WhatsApp.<p>* An SMS.<p>* An X-ray of my wrist.<p>* A video "voicemail" left by the caller when I don't pick up a Meet call.<p>* My electricity consumption as measured by the smart meter in my house.<p>* (the list goes on)<p>The fact that none of them appear in my filesystem* by default is, to me, the biggest failure of consumer IT since the Internet exists.<p>*Or at least in some standardized, interchangeable, mostly uniform container format.
Buckland and Lynch are still doing the Friday seminar <a href="https://www.ischool.berkeley.edu/events/ias" rel="nofollow noreferrer">https://www.ischool.berkeley.edu/events/ias</a>
Reminds me of the discussion around what is "content". Recent criticism of the word suggests that "content" is how art and creative expression gets processed into commodity, entertainment and consumption. With machine learning, "content mills" are hoping to generate endless amount of content without a (human) creator.<p>I also wonder what a "document" means in the context of a web browser. It includes HTML, CSS, JavaScript, as well as any media files like audio, video. The Pandora's box was to include dynamic scripting, so a document is run as an application, a kind of "hyper document" for multimedia communication and interaction.
> discussed whether, for example, sculpture, museum objects, and live animals, could be considered ‘documents.’<p>big "what are birds" energy <a href="https://www.youtube.com/watch?v=Kh0Y2hVe_bw">https://www.youtube.com/watch?v=Kh0Y2hVe_bw</a>
@dang - this is actually pretty interesting, particularly because of when it was written (1997). I'd suggest you add the date in the tile, it's of most interest (to me at least) as a view of where we were all at in the '90s thinking about digital records.