3 ms·
It's too specific, too lightweight, and there's no existing precedent. The purpose of the HTML specification is to standardize and formalize how pages are struc
by scott_s 17y ago
It's too specific, too lightweight, and there's no existing precedent. The purpose of the HTML specification is to standardize and formalize how pages are structure, not predict every corner case.
For example, many sites are now embedding videos, which is a heavyweight activity. So HTML is being extended to be able to say "This is an embedded video" so that browsers can handle the nitty-gritty details, not people who make webpages.
Disclaimers are not heavyweight. They're usually a single sentence. That's what I mean by "too lightweight." It's too specific because very few people have to put up disclaimers - yes, few people have to, say, embed video, but embedding video has more performance implications on the browser, and many people will view such pages. It's not worth the corner case for something as small and specific as a disclaimer. Lastly, the trend in HTML standardization seems to be "formalize existing practices." I don't think there's an existing practice for disclaimers beyond just putting a sentence or two at the beginning or the end.
Finally, I think that re-postings of a review could cause legal trouble beyond the original posting is a weak argument. And in the case of a re-posting, I don't see how adding a semantically tagged disclaimer would help - the HTML probably wouldn't be copied over, so the semantic tagging would be lost, and if the copier picked up the semantically tagged disclaimer, they'd pick up a plain text disclaimer, too.
- rriepe 17y agoThanks. That's the kind of reply I was looking for. I guess it will depend a lot on how people implement disclosures over the next few years. When HTML6 comes around, hopefully I'll get a chance to dust off this article.