UserPreferences

PaceContentAsTextOrHtml


Abstract

Limit all such content to text/plain, text/html, and application/xhtml+xml. Eliminate mode attribute (text is escaped, xhtml is inline). At least one of summary and content is required.

Status

Open

Related paces

Rationale

[WWW]Reducing this portion of the spec to stuff that's already been proven to work and be interoperable, and writing it down in a clean clear way.

Proposal

3.1 Content Constructs

A Content construct is an element with arbitrary child content, whose properties are described by the following attribute:

3.1.1 "type" Attribute

Content constructs MAY have a "type" attribute, whose value indicates the media type of the content. When present, this attribute's value MUST be one of the following values: "text/plain", "text/html", or "application/xhtml+xml". If this attribute is not present, processors MUST behave as if it were present with a value of "text/plain".

When the type is "text/plain", the value of this element is to be interpreted as character data without any markup. Entity and character references can both be used to [WWW]escape the left angle bracket, ampersand, and other delimiters. [WWW]CDATA sections may also appear anywhere in this text, and effectively achieves the same result as escaping.

When the type is "text/html", the value of this element is to be interpreted as the contents of the body of an [WWW]HTML document. This means that in addition to the escaping required by HTML, there is a second level of escaping required for all character data, and all HTML markup must be escaped. [WWW]CDATA sections may also appear anywhere in this text, and effectively achieves the same result as escaping.

When the type is "application/xhtml+xml", the value of this element may contain [WWW]mixed content. Immediate child elements must be in the "http://www.w3.org/1999/xhtml" namespace. The set of valid child elements are the same as the set elements permissable as children of the [WWW]xhtml body element.

Examples:

<title type="text/plain">An ode to the
  &lt;blink&gt; tag</title>
<title type="text/plain"><![CDATA[An ode to the
  <blink> tag]]></title>
<title type="text/html">An ode to the
  &lt;code&gt;&amp;lt;blink&amp;gt;&lt;/code;&gt; tag</title>
<title type="text/html"><![CDATA[An ode to the
  &lt;blink&gt; tag]]></title>
<title type="application/xhtml+xml">
  <div xmlns="http://www.w3.org/1999/xhtml">An ode to the
    <code>&lt;blink&gt;</code> tag</div>
</title>
<title type="application/xhtml+xml">
  <div xmlns="http://www.w3.org/1999/xhtml">An ode to the
    <code><![CDATA[<blink>]]></code> tag</div>
</title>

3.1.2 "mode" Attribute

deleted

5.9 "atom:summary" Element

The "atom:summary" element is a Content construct that conveys a short summary, abstract or excerpt of the entry. atom:entry elements MAY contain an atom:summary element, but MUST NOT contain more than one. atom:entry elements that do not have a atom:content element MUST contain an atom:summary element.

5.10 "atom:content" Element

The "atom:content" element is a Content construct that conveys the content of the entry. atom:entry elements MAY contain an atom:content element, but MUST NOT contain more than one. atom:entry elements that do not have a atom:summary element MUST contain an atom:content element.

Impacts

Non textual information will need to be related to the entry by link (either by [WWW]anchor tags in HTML or with atom:link rel="related" elements)

Notes


CategoryProposals