Is the copyright meta tag valid in HTML5?

by

Dublin Core proposes the rightsHolder term (an extension to the <meta> name attribute), which validates using the W3C HTML5 validator:

<meta name="dcterms.rightsHolder" content="Your Copyright-Holder Organization">

This is defined as A person or organization owning or managing rights over the resource.

Additional terms:

For a statement about property rights, we can use the regular rights term:

<meta name="dcterms.rights" content="Statement of copyright">

To add the date of copyright:

<meta name="dcterms.dateCopyrighted" content="2012">

Source: http://wiki.whatwg.org/wiki/MetaExtensions

Nitpick

According to the MetaExtensions document, all these statements must be accompanied by a special <link> element:

<link rel="schema.dcterms" href="http://purl.org/dc/terms/">
<meta name="dcterms.rightsHolder" content="Your Copyright-Holder Organization">

However, the W3C validator does not enforce this.

TL;DR Most of the non standard meta tags are not yet available for HTML5 validators. Until then you should include a small tag if you must have valid code.

Ok, I did a little bit more research into the subject. The issue is that the metatags on the WHATWG wiki are supposed to be used by validators, but in many cases because the tags update so frequently most validators ignore them until they become official parts of the spec.

So the only standard metatags right now are:

  • application-name
  • author
  • description
  • generator
  • keywords

Eventually once the spec gets updated again the rights-standard metatag will validate as well, but until then we need a workaround … which is …

….drumroll….

The <small> tag!

The small element represents side comments such as small print.

Small print typically features disclaimers, caveats, legal
restrictions, or copyrights. Small print is also sometimes used for
attribution, or for satisfying licensing requirements.

Source: http://dev.w3.org/html5/spec/text-level-semantics.html#the-small-element

Also, just a side note. Just because your code doesn’t validate doesn’t mean it isn’t valid. The spec is constantly evolving, so you just need to bear with it until things become more concrete.

More Related Contents:

  1. Is there a W3C valid way to disable autocomplete in a HTML form?
  2. Is it wrong to change a block element to inline with CSS if it contains another block element?
  3. An invalid form control with name=” is not focusable
  4. input type=”submit” Vs button tag are they interchangeable? [duplicate]
  5. Manually Triggering Form Validation using jQuery
  6. How can I change or remove HTML5 form validation default error messages?
  7. Which are the standard W3C meta tags?
  8. Autocomplete off vs false?
  9. Best Way to View Generated Source of Webpage?
  10. HTML5 validation when the input type is not “submit”
  11. How do I get the collection of Model State Errors in ASP.NET MVC?
  12. What values for checked and selected are false?
  13. Fallback for CSS attributes without unit
  14. Delay HTML5 :invalid pseudo-class until the first event
  15. Are nested HTML comments possible?
  16. HTML5 Required input styling
  17. is form enctype “application/json” available?
  18. What elements can be contained within a tag?
  19. Is there a minlength validation attribute in HTML?
  20. How do I make a field required in HTML?
  21. How do I style the HTML form validation error messages with CSS?
  22. How can I change or remove HTML form validation default error messages?
  23. Is div inside list allowed? [duplicate]
  24. Bad value X-UA-Compatible for attribute http-equiv on element meta
  25. When to use line breaks vs CSS positioning?
  26. Using cm/mm on the CSS of a web app that replicates paper interaction is a good practice?
  27. What’s the point of valid CSS/HTML?
  28. How to get the text from the HTML5 input field error message in Selenium?
  29. Is it possible to validate the size and type of input=file in html5
  30. Are void elements and empty elements the same?

Leave a Comment