Ownership and portability of a book is one thing that becomes relevant when price includes mark up to be paid to own it.
What's different about the stream of bits on a disk that represents a "book" compared to the stream of bits that represents a "file"?
But from a consumer point of view, which is extremely important, files and books in the real world are poles apart. So why not treat them such online?
Specifics?
I'm actually still digging this one but "active internet" connection - yes - that's again doable. Localstorage() /something probably? Or wait for a future to be more online.
Because technically I agree with you that it's only the presentation and nature of 'binding' that makes for all the difference.
If it's being transferred over the internet, it's a file.
Electronic books are a subset of files, not a disjoint set, just as paper books are a subset of "paper with ink on it".
> Electronic books are a subset of files
follow from
> paper books are a subset of "paper with ink on it"
?
I'd argue that paper books are not a subset of paper files, therefore, in online realm also electronic books should NOT be a subset of electronic files. It is a disjoint set by your logic.