[Bug 14363] Update the registration mechanisms

https://www.w3.org/Bugs/Public/show_bug.cgi?id=14363

--- Comment #10 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-12-02 18:12:23 UTC ---
(In reply to comment #9)
> > 
> > Well we should definitely have a defined way to determine what the registered
> > types are, sure. I don't see why this is a problem.
> 
> The problem is that currently you *don't* have a defined way to determine what
> the registered types are. If that's a known defect with the specification that
> will be fixed before it's finalised then that's fine.

Yes, this needs to be cleared up.


> > Why would vandalism be an issue? It's not an issue because you say it is,
> > either. :-)
> 
> Because it's trivially easy and could potentially cause significant problems
> for people doing conformance checking (in that their tools will suddenly
> indicate that most websites are invalid).

Tools shouldn't be just scraping the sites automatically (and don't, in
practice).


> > I don't see why. Even if it was dependent on a site that went dark two months
> > from now, it would just be updated to point to another site then.
> 
> Both of these replies tend to indicate that we have a different idea of what a
> "standard" is. Generally speaking, one would expect a standard to be released
> on a certain date and not to change after that, or at least, not to change on a
> daily basis.

HTML will continue to evolve until it is dead. It's a living standard.


> Or rather, it's made a lot worse. Instead of the potential victim of the
> accidental DDoS being a sizeable organisation with the funds and experience to
> cope with the situation, it's just you. No criticism of you personally
> intended, but most people have more limited means in terms of time and money
> than most organisations, and it leaves HTML with a "bus factor" of 1, which is
> somewhat unfortunate.

This is false. If I were to die suddenly, people would just lift up the spec
and wiki and put it elsewhere, assuming they couldn't get the site reassigned
to them, which would be the more likely situation.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 2 December 2011 18:12:25 UTC