Re: [apps-discuss] Terry Manderson's Discuss on draft-ietf-appsawg-text-markdown-use-cases-02: (with DISCUSS)

[John C Klensin <[e-mail]>]

--On Tuesday, July 14, 2015 11:53 -0400 Barry Leiba
<[e-mail]> wrote:

>>>> Guidance on Markdown:
>>>> Design Philosophies, Preservation Strategies, and Select
>>>> Registrations
>>> 
>>> That seems reasonable, with a question: What does
>>> "preservation strategies" mean?
>> 
>> It means "how to preserve the text/markdown Content-Type
>> along with its parameters outside of MIME bodies",
>> or, "how to preserve the author's intent when the author
>> wrote the Markdown content in a certain way, so that
>> recipients know what kind of Markdown (variant) the content
>> actually is, along with the charset".
>> 
>> (Covered in Section 2.)
> 
> Yes; I'm questioning whether anyone reading the title will
> have any idea what "preservation strategies" means.  What's
> the point of putting words into the title that don't add to
> (and actually detract from) the understanding of what the
> title means?

Barry and Sean, short of just dropping that clause, how about
"stability strategies" or "interoperability strategies"?  Both
terms are well-known in the community and give much more of a
clue as to what is being discussed than "preservation".  The use
of either in this context is a bit unusual, but it seems to me
that preserving interoperability and original intent as Markdown
documents move through systems is precisely what Sean is talking
about.

    john