Re: Safari is moving to Windows!!!

In article <GTqbi.161$vi5.141@xxxxxxxxxxxxxxxxxxxxxxxxxx>,
"ed" <news@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

"ZnU" <znu@xxxxxxxxxxxx> wrote in message
news:znu-0EC3C3.01581012062007@xxxxxxxxxxxxxxxxx
In article <466e30b3$0$27164$742ec2ed@xxxxxxxxxxxxxx>,
SMS <scharf.steven@xxxxxxxxxxx> wrote:

ZnU wrote:

There is no such tag. Microsoft might think there is, but they're
wrong.

Well it's an IE tag anyway, and many sites use it.

There are plenty of standards-compliant ways to play background audio on
web sites, should one wish to commit such heinous crimes against
humanity. I'd prefer that Apple not support ill-conceived proprietary
tags.

but of course you're probably ok w/ apple supporting proprietary elements
that you think are NOT ill-conceived, right? that's the problem with
proprietary elemens, no?- some people think they're ill conceived, some
think they're not, but they DO have a relatively decent history of driving
forward the standards (see xmlhttprequest from microsoft, and canvas from
apple, as two examples that i think show how proprietary tags drive the
standard forward).

It depends.

The truth is there are degrees between proprietary and formally
standardized by the W3C. A lot of the interesting new work is happening
in this space. There's nothing wrong, IMO, with creating new tags or JS
functions, as long as they're actually doing something significant (e.g.
they're not just proprietary alternatives to standard tags or
functions), and as long as companies make an attempt to be open about
it. A browser vendor inventing a new tag or function should document it
thoroughly, implement things in ways that make sense for other vendors,
participate in organizations designed to facilitate collaboration
between browser vendors, and ideally provide an open-source reference
implementation.

Sometimes a vendor that doesn't follow these rules comes up with a
decent idea. What tends to happen then is that some other party takes
the idea and runs with it, creating a more open version.

This is essentially what happened with XMLHttpRequest. For which an
object is instantiated with 'new ActiveXObject("MSXML2.XMLHTTP.3.0")' in
IE. You can tell they were totally thinking of what would make sense
other other browsers. Not.

--
"That's George Washington, the first president, of course. The interesting thing
about him is that I read three--three or four books about him last year. Isn't
that interesting?"
- George W. Bush to reporter Kai Diekmann, May 5, 2006
.

Relevant Pages

  • Re: Jumping ship from Cumberland Family Tree
    ... I've already tried importing the GEDCOM to Legacy 7, ... The GEDCOM standard accommodates events that are beyond the prescribed ... Any other style of export, particularly creating special non-standard tags, ...
    (soc.genealogy.computing)
  • Re: Safari is moving to Windows!!!
    ... web sites, should one wish to commit such heinous crimes against ... I'd prefer that Apple not support ill-conceived proprietary ... as two examples that i think show how proprietary tags drive the ... defiantely wasn't a STANDARD way. ...
    (comp.sys.mac.advocacy)
  • Re: high performance hyperlink extraction
    ... The single or double quote delimiters are optional in some cases ... To follow the standard, one would have to acquire the SGML standard, which costs money. ... Writing a Python RE to match all and only legal anchor tags may ...
    (comp.lang.python)
  • Re: Beyond GEDCOM
    ... An example of this is Cumberland Family Tree's export of a non-standard "ADOP" tag instead of a standard "PEDI Adoption". ... can be accommodated within the current GEDCOM standard via the ASSO/RELA + NOTE/SOUR tags. ... I'd like for it to allow a SOUR to be at any level. ...
    (soc.genealogy.computing)
  • [Full-disclosure] RFID access control tokens widely open to cloning
    ... these tokens are based on 125kHz or 134.2kHz standard tags, ... to the reader, but also to the human eye. ... Trovan 'Unique', aka EM4x02 ...
    (Full-Disclosure)