Craig Birkmaier wrote: > We told the FCC in 1992 that digital would enable rapid innovation; > that locking down system parameters was a BAD IDEA. That's funny. Craig, what "you told" the FCC back then was basically wrong. You didn't understand the difference between "the service" and "the layered protocol." We've been over this many times. "The service" can and *must* establish standards, to *ensure* interoperability. The problem was, your camp was still uninformed. It was early days of the Internet, though, only 10 years into its existence, and you confused the "extendible" and layered IP suite, with the apps that run over it. > Anyone who studied the embryonic science of entropy coding, could > quickly grasp that this technology would evolve rapidly, And anyone who understood the difference between the service and the digital link KNEW, even back then, that A/53 could easily be updated. That's the point! We've been over this countless times too, way back. You thought that A/53 was a "point solution," which you repeat that in this post, and I kept telling you that it wasn't. The standard can be changed at the stroke of a pen. THE ONLY PROBLEM IS LEGACY. Apple *wants* to obsolete its iToys as soon as possible. Instead, the ATSC does not have the luxury of obsoleting everyone's TVs every couple of years. Not everything in the world has to emulate iToys, Craig. > The "real world experience" is exactly as we predicted. Hardly. The "real world experience" is that TV over the Internet is habitually problematic still (what? Can't get cbs.com and fox.com on your iToys yet?), while ATSC TV is totally reliable. If you have at least -85 or -80 dBm of signal strength, and at least 15 dB of CNR, you get reception. > What rubbish. There were many competitors in the "Office" > applications markets before Microsoft used its monopoly Rubbish. There were many office suites, and MS Office won out. We ourselves used multiple suites, e.g. Smartware, Framemaker, Lotus, but the corporation had to standardize for interoperability. Practically the entire industry, and government, chose WordPerfect at first, and then migrated to MS Office. *That's* why it had to happen. If you're going to collaborate, within the corporation and between the company and the clients, you naturally want to use the digital tools available out there, but the tools have to be compatible. > I never had major issues being a consultant to all of these > enterprises that enforced strict standards, OTHER THAN when > Microsoft purposely kept changing file formats with each new > Office release. Why did they do this? Another funny from Craig. Yes, I admit that upgrading is a nuisance, but hey! Aren't you the same Craig that was extolling the virtues of innovation up above, telling us that the ATSC TV app is "stagnant?" Obviously, Office is updated to offer new features, to keep competition at bay. And yes, competitors are still there, and they might even take MS Office's place. That changes nothing. Enterprises will still want compatible apps. That's the only important point. > Oh wait...the traditional CE vendors are now selling Smart TVs. Who needs > ATSC when the TV can pull bits from the WiFi router connected to your > broadband service. Again, you're getting lost in your rhetoric. In principle, **OF COURSE** one-way broadcast distribution pipes are not mandatory for TV distribution. That's already true today. But the TV app still needs to work reliably, no matter what the distribution medium. The real-world experience is, over ATSC it does. Over the Internet, well, a little bit amateur night still. And it's almost certainly true that "the TV app" will need a two-way medium of distribution, for any significant new features it might want to introduce. So yes, the one-way broadcast pipe is likely to be phased out in due course. That's why I am not waiting with baited breath for ATSC 3.0. SO WHAT? That changes nothing about the need for standards. Bert ---------------------------------------------------------------------- You can UNSUBSCRIBE from the OpenDTV list in two ways: - Using the UNSUBSCRIBE command in your user configuration settings at FreeLists.org - By sending a message to: opendtv-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.