- From: marbux <marbux@gmail.com>
- Date: Thu, 22 Nov 2012 14:39:40 -0800
- To: Markdown List <public-markdown@w3.org>
On Thu, Nov 22, 2012 at 9:37 AM, Dave Pawson <dave.pawson@gmail.com> wrote:
> On 22 November 2012 17:06, Shane McCarron <ahby@aptest.com> wrote:
>> Let me put it another way. If one of the goals of this work is that we
>> codify current behavior,
>
> Not sure what you mean Shane?
> I'd certainly not say that. Current behaviour is in current multiple
> (different) implementations,
> which is the source and cause behind this work.
>
> Do you agree with http://www.w3.org/community/markdown/wiki/Deliverables ?
>
> If not, what would you change?
I'll just toss this out for discussion. A somewhat different approach
when implementations' markup differs is to specify one method as a
recommendation ("should") ("must" for new implementations of the
feature) but indicate that the other methods are optional deprecated
methods ("should not")?
W3C QA Glossary: "Deprecated feature --- An existing feature that has
become outdated and is in the process of being phased out, usually in
favor of a specified replacement. Deprecated features are no longer
recommended for use and may cease to exist in future versions of the
specification." <http://www.w3.org/QA/glossary>.
Paul
Received on Thursday, 22 November 2012 22:40:11 UTC