Microsoft Hatred FAQ

Mike Schilling mscottschilling at hotmail.com
Tue Oct 18 01:36:49 EDT 2005


"John Bokma" <john at castleamber.com> wrote in message 
news:Xns96F2D6EAAC3BBcastleamber at 130.133.1.4...
> "Mike Schilling" <mscottschilling at hotmail.com> wrote:
>
>>
>> "John Bokma" <john at castleamber.com> wrote in message
>> news:Xns96F1E574E6873castleamber at 130.133.1.4...
>>> Roedy Green <my_email_is_posted_on_my_website at munged.invalid> wrote:
>>>
>>>> On 16 Oct 2005 05:22:47 GMT, John Bokma <john at castleamber.com> wrote
>>>> or quoted :
>>>>
>>>>>No, it's a recommendation, an advise, nothing else. Otherwise they
>>>>>would call it a standard. Why do you think W3C calls it
>>>>>recommendations? Because it are no standards. There is an ISO HTML
>>>>>standard though, but when people babble about HTML standards they
>>>>>talk about W3C *recommendations*.
>>>>
>>>> What do you think the Internet is based on?  RFCs.
>>>
>>> Yup, I know. Hence no standards.
>>>
>>> Like I said: there is ISO HTML, and there is a w3c HTML 4.01
>>> recommendation. The former is a standard, the latter is a defacto
>>> standard.
>>> For some the difference does matter.
>>
>> What matters in generating HTML is which browsers you want to support
>> and what they understand.  Standards and recommendations are both
>> irrelevant.
>
> So how do you develop a browser? I assume you have some experience with
> programming, or is that trial and error programming? Hack until it
> works?
>

A browser that's perfectly compliant but can't render the pages actually 
found would be of only academic interest.  So, yes, the standards (and 
recommendations) are one source of requirements, but the actual contents of 
the internet is another. 





More information about the Python-list mailing list