Re: [draft-freed-sieve-in-xml-02] Emphasis Whitespace Preservation

[Aaron Stone <aaron@xxxxxxxxxxxxxx>]

On Fri, 30 Jan 2009 17:27:44 +0000, Robert Burrell Donkin
<robertburrelldonkin@xxxxxxxxx> wrote:
> Issue
> -----
> Implicit whitespace preservation.
> 
> Original
> --------
> In "4. XML Representation of Sieve"
> 
>   String, number, and tag arguments are represented as str, num, and
>   tag elements respectively.  The actual string, number, or tag
>   identifier appears as text inside the element.  None of these
>   elements have any defined attributes.  Several examples of arguments
>   have already appeared in the preceding control, action and test
>   examples.
> 
> Proposal
> --------
>   String, number, and tag arguments are represented as str, num, and
>   tag elements respectively.  The actual string, number, or tag
>   identifier appears as text inside the element.  None of these
>   elements have any defined attributes.  Several examples of arguments
>   have already appeared in the preceding control, action and test
>   examples. Any whitespace in the str body content MUST be preserved
>   by the processor.
> 
> 
> Rationale
> ---------
> This isn't a major issue but based on experience with HTML, developers
> too often assume that whitespace should be trimmed. It is therefore
> worthwhile emphasizing explicitly that whitespace is expected to be
> preserved.

+1, whitespace should be preserved for string arguments.

Also, the RFC Editor will want to add Oxford commas and quotes around
"str", "num", and "tag" for clarity :-)

Aaron