domain names, web standards, etc

> Registration has nothing to do with this. It's a simply a matter of
> creating an A record or CNAME within DNS for domainname.tld that points at
> your web server. This is purely a function of DNS, and is wholly
> independant of NIC registration and *should* be independant of web server
> platform.

I figured it was some sort of setting that can be controlled. As I said, I
just never looked into it myself


> Absolutely, unless Doc G was being facetious here. W3C compliance should
> be the holy grail of achievements for any site, because those are the
> standards browsers are *supposed* to be developed against.
>
> Yes, I know different browsers do things differently. Is it possible? Yes.
> Is it *feasible*? Not always. Marketing people may not lean as far toward
> the technical side as some of us, and may not simply understand that even
> though there are things all browsers will do, some will do things
> differently.
>
> What sacrifices you have to make (Site Design vs Browser Compatibility vs
> Cost to Deploy) depend on your product, your target market, and your
> budget. Usually, standards compliance is the first factor to get tossed
> out as sites target a specific browser and then pursue basic compatibility
> across the board.

Yes but what he asked is whether or not you can satisfy marketing AND be W3C
compliant. Most marketing people always want something cool and flashy and
will grab the users attention. Most of the time this includes stuff that is
NOT compliant (or not yet) or it has to be done a certain way so that IE
(which is what they use, lets face it, most marketing people wouldnt know
their ass from a real browser) can supply what they need. We all know IE is
FAR from compliant, and does it's own thing, which means you wouldn't really
have a compliant page.