Re: [apps-discuss] On the markdown documents

[Dave Crocker <[e-mail]>]

On 11/10/2014 6:33 PM, Murray S. Kucherawy wrote:
> Colleagues,
> 
> Alexey and I have discussed it, and we recommend that the WG not adopt
> draft-seantek-text-markdown-use-cases at this time.  We would like the
> WG to focus on developing draft-ietf-appsawg-text-markdown with Sean
> until it's ready to go at least to WGLC, or preferably to the IESG, and
> then we can adopt draft-seantek-text-markdown-use-cases if there's still
> the energy and desire to publish it at that time.


Use cases can serve two different purposes.  I think the intent of the
use case document, here, could affect whether it should come before or
after the actual spec.  So I think we should be clear about that intent.

One purpose is to guide design of the solution.  The other is to explain
what has been designed, to those who might use it, specifically by
giving them likely scenarios to use it in.

If the current spec document is far enough along, in purpose and detail,
then I assume the use case document is for educating the mass of
potential adopters.

However from the discussions about markdown, I really can't tell how
settled design issues are.

So I'll reduce to a simple question:

     Could/Should having a use case document make it easier to resolve
disagreements about the choices in the text-markdown document?

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net