DIF Recommended did methods: Slide Presentation for DID Method Deep Dives

[ottomorac]

As discussed in the wg call on 21-May it might be a good idea to require a brief slide presentation for the deep dives.

The proposed content of the slide deck would be the following:

1. Cover Page - indicate did method name, name(s) of champion/sponsor along with professional titles
2. DID method description 3 paragraphs max about did method background and objectives
3. DID Method info: Spec version and information on when it was registered in the W3C did methods registry, standardization target organization (if any)
4. Information of coverage of W3C test suite and support for universal resolver
5. Evaluation against did traits and highlight of specific traits featured in the did method that sponsor would like to highlight
6. Information on multiple implementations on different coding languages
7. Information on live production clients and traction of the did method
8. Closing comments and contact information of the sponsor(s)

[ankurdotb]

This feels like the existing proposal template, but in a different form factor.

So two questions:

1. Is it worth having two separate form factors: one that's a Markdown proposal file, and second a Google Slides template?
2. If the answer is yes, then at the very least the two should be synchronised so that there's extra information in the proposal that's not in the slide and vice versa.

One thought/tip! There are a LOT of services that can convert from Markdown to slides, so maybe using that to convert the proposal to slides could be a way of reducing the work necessary.

[bumblefudge]

1. Well, what I was proposing was yes, 2 very distinct templates. i think running through the proposal line by line is a bad structure for a presi, and most of the template might not even need to come up in the slide. The proposal is the "homework" for evaluators to read beforehand, the presi is scaffolding for a well timeboxed deepdive 😄
2. Synchronised? In this economy?

https://docs.google.com/presentation/d/1fHwwIyC9cQnPVGQotDXjYi8-ydrJeNsijJN_gzWGpCA

[bumblefudge]

sent to next week's dogfooder as-is in the interest of time, feel free to change though and the next deep-diver will have a better template to work from!

[jrayback]

@bumblefudge , thank you so much for putting together this slide template. I'm worried that we're accumulating too many summary-type artifacts. The fact that we've had this proposal to create a new one probably means that what we have today is not passing muster for some (many?). But rather than just add, I'd feel better about reworking the full set of summary-type docs (the proposal template, the table, and what's being suggested in these slides). Also, I kind of hate that this core element of our process would need to live outside of GitHub.

[bumblefudge]

yeah on or before the call monday i'll strip out references to "pdf mode" so it doesn't come across as a deliverable or as one more form to fill out, and frame it more explicitly as an optional template than a requirement of giving a deep dive!