Re: Manifesto: Rules for standards-makers by Dave Winer

Dont disagree with any of it.

Having spent time on some standards committees that think they must first
design a detailed specification then software builders will implement it, I
especially like the part about working software driving (fixing) the
standard.  If you don't test what you are writing then you can be sure
it'll be full of bugs and make it virtually un-implementable.

On Tue, 15 Dec 2020 at 09:58, Heather Vescent <heathervescent@gmail.com>
wrote:

> Interesting piece by Dave Winer. What do you agree with? What do you
> disagree with?
> http://scripting.com/2017/05/09/rulesForStandardsmakers.html
>
> -H
>
> --
> Heather Vescent <http://www.heathervescent.com/>
> Co-Chair, Credentials Community Group @W3C
> <https://www.w3.org/community/credentials/>
> President, The Purple Tornado, Inc <https://thepurpletornado.com/>
> Author, The Secret of Spies <https://amzn.to/2GfJpXH> (Available Oct 2020)
> Author, The Cyber Attack Survival Manual
> <https://www.amazon.com/Cyber-Attack-Survival-Manual-Apocalypse/dp/1681886545/> (revised,
> Dec 2020)
> Author, A Comprehensive Guide to Self Sovereign Identity
> <https://ssiscoop.com/>
>
> @heathervescent <https://twitter.com/heathervescent> | Film Futures
> <https://vimeo.com/heathervescent> | Medium
> <https://medium.com/@heathervescent/> | LinkedIn
> <https://www.linkedin.com/in/heathervescent/> | Future of Security Updates
> <https://app.convertkit.com/landing_pages/325779/>
>


-- 
Steve Capell

Received on Tuesday, 15 December 2020 00:26:37 UTC