W3C home > Mailing lists > Public > www-html-editor@w3.org > July to September 2006

[xhtml2] Metadata as Content is a gem

From: <karl@w3.org>
Date: Thu, 17 Aug 2006 03:28:15 -0000
To: www-html-editor@w3.org
Message-Id: <20060817032820.2D34E4F5E7@homer.w3.org>

This is a QA Review comment for "XHTML 2.0"
8th WD

About http://www.w3.org/TR/2006/WD-xhtml2-20060726/mod-meta.html

The document focuses on meta (and link) used in the head of an XHTML 2.0 document. It should be the other way around. Remove the head/body dichotomy which would lead to more flexibility for authors.
	See Mail "html/head/body and Document module"

The MetaInformation Attributes module is also making this point in "24.3. Metadata as Content"

	"One use of the metadata attributes is with elements 
	that represent document content, since the same string 
	literal can be used to specify both document content, 
	and metadata."

There is one of the direct benefit for authors. When hidden metadata are needed for one reason or the other it can be a lot easier to edit them where the actual content is, more than having to jump back and forward to two sections of the document.

Another benefit could be in some case to have the meta at the end of the document more than at the begining. So the author can open a template document where meta are at the bottom and then start editing the content at the top.

There might be indeed benefits to have some of them at the begining of the document in progressive rendering when for example link for CSS is specified or encoding. That would be more a question of good practice, like it's already the case. (Often manual recommends to put the encoding instruction in the first lines.)

Emphasize the use of meta in-situ.

Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***
Received on Thursday, 17 August 2006 03:29:26 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:08:55 UTC