- From: Philip TAYLOR [PC336/H-XP] <P.Taylor@Rhul.Ac.Uk>
- Date: Mon, 03 Feb 2003 08:46:51 +0000
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- CC: "www-html@w3.org" <www-html@w3.org>
Coming as I do from a typesetting/TeX background, I see exactly the same situation occurring with <object ...> as did with \special in TeX. That is, one clearly needs an extensible mechanism for communication with the agent (be it device driver for TeX or user agent for *ML) but there /has/ to be a central registry to ensure that two different agents don't (accidentally or otherwise) use the same discriminator in order to detect when data is intended for them. That is, one needs something analogous to fully-IANA- registered MIME types as a mandatory parameter to <object ...> to ensure that other optional parameters are correctly and consistently interpreted. I'm copying this one back to the list, since it would seem that this has somehow been overlooked ... ** Phil. -- Philip Taylor, RHBNC -------- Boris Zbarsky wrote: > > > Hmmm, seems to leave rather a lot to chance, then! > > Yeah, well.... I feel, personally, that the <object> definition in HTML 4.01 is > very poorly thought-out. > > Boris > -- > Under the most rigorously controlled conditions of pressure, > temperature, volume, humidity, and other variables, the > organism will do as it damn well pleases.
Received on Monday, 3 February 2003 03:46:45 UTC