4 ms·
The consistency of PDF rendering has nothing to do with it being an ISO standard. It's based on a completely different model that made different tradeoffs with
by bct 13y ago
The consistency of PDF rendering has nothing to do with it being an ISO standard. It's based on a completely different model that made different tradeoffs with respect to user-end flexibility. It was also controlled by a single company for 15 years.
TimBL and the W3C were pushing for new payment models 15 years ago (and probably earlier). This is why HTTP has 402 Payment Required. There was a W3C micropayments working group back in 1998: http://www.w3.org/ECommerce/Micropayments/ http://www.w3.org/ECommerce/Micropayments/ .
This stuff would be hard to get right in a vacuum. It's even harder when you're trying to get groups with competing interests to agree on something, especially when you have as little leverage as standards organizations tend to have. The view put forward in the last half of this essay is naive.
- minikites 13y agoXanadu had it even earlier: http://en.wikipedia.org/wiki/Project_Xanadu http://en.wikipedia.org/wiki/Project_Xanadu > Every document can contain a royalty mechanism at any desired degree of granularity to ensure payment on any portion accessed, including virtual copies ("transclusions") of all or part of the document.