W3C home > Mailing lists > Public > public-html-data-tf@w3.org > November 2011

Values of extended (e-*) properties in microformats-2

From: Jeni Tennison <jeni@jenitennison.com>
Date: Thu, 24 Nov 2011 18:45:07 +0000
Message-Id: <FD93BA90-7AD1-485D-8D29-D1CF8ACD18D9@jenitennison.com>
Cc: HTML Data Task Force WG <public-html-data-tf@w3.org>
To: Tantek Çelik <tantek@tantek.com>

A quick question about microformats-2 processing. When you have an e-* property such as e-content, what exactly does the HTML string generated from the content of the appropriate element look like? I can see several options:

  1. the element.innerHTML [1] which will either be HTML or XML depending on whether the document is HTML or XML
  2. the HTML serialisation of the contents of the element [2]
  3. the XML serialisation of the contents of the element [3]
  4. the original characters between the start and end tag of the element (ie no DOM fixup)

Which of these does microformats-2 use or does it do something else? I ask because the RDFa WG are starting to discuss this a bit [4] and it would be great if microformats-2 and RDFa took the same approach if possible.



[1] http://html5.org/specs/dom-parsing.html#innerhtml
[2] http://www.whatwg.org/specs/web-apps/current-work/multipage/the-end.html#html-fragment-serialization-algorithm
[3] http://www.whatwg.org/specs/web-apps/current-work/multipage/the-xhtml-syntax.html#xml-fragment-serialization-algorithm
[4] http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Nov/0177.html
Jeni Tennison
Received on Thursday, 24 November 2011 18:45:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:06 UTC