I assume that the author intends // to replace http:// http://, and that all other protocols such as ftp, https, etc. would still be written? If that's the cas

I assume that the author intends // to replace http:// http://, and that all other protocols such as ftp, https, etc. would still be written? If that's the case, why bother with the // at all? Why not just assume, as most browsers already do, that there's an inferred http:// http:// at the beginning of whatever the user types in the address bar? (EDIT - I see that he's talking about how we would refer to URLs in things like print advertisements. Cute idea, but given the ubiquity of web addresses in mass media, and the time it takes for the public to learn anything new, it still sounds like a solution in search of a problem. The average American is still not sure how Twitter works, or what it means when they see a @name or a #tag.)