docs: flesh out API and justification for uuid standard library

.travis.yml

@@ -0,0 +1,3 @@
+language: node_js
+node_js:
+  - "node"

README.md

@@ -1,40 +1,73 @@
-# ECMAScript proposal: JavaScript standard library UUID module
+# ECMAScript proposal: JavaScript standard library UUID
 
 Champions: [Benjamin Coe](https://github.com/bcoe)
 
-Status: Stage 0
-
-**_Note to contributors: this template is based on the
-[top-level await proposal](https://github.com/tc39/proposal-top-level-await), use this for
-inspiration while fleshing out document._**
+Status: early draft, never presented to TC39
 
 ## Synopsis
 
-The [JavaScript standard library](https://github.com/tc39/proposal-javascript-standard-library)
-UUID module exposes an API for generating character encoded Universally Unique IDentifiers (UUID),
-based on [IETF RFC 4122](https://tools.ietf.org/html/rfc4122).
+The [JavaScript standard library][standard-library-proposal] UUID describes an API for generating
+character encoded Universally Unique Identifiers (UUID) based on [IETF RFC 4122][rfc-4122],
+available for import in JavaScript engines.
 
 ## Motivation
 
 ### UUID generation is an extremely common software requirement
 
 The [`uuid` module](https://www.npmjs.com/package/uuid) on npm currently receives some
 [64,000,000 monthly downloads](https://npm-stat.com/charts.html?package=uuid) and is relied on by
-over [300,000 repositories](https://libraries.io/npm/uuid).
+over 2,600,000 repositories (as of June 2019).
 
 The ubiquitous nature of the `uuid` module demonstrates that UUID generation is a common
-requirement for JavaScript software applications, making the functionality a good candidate for
-standard library modules.
+requirement for JavaScript software applications, making the functionality a good candidate for the
+standard library.
 
 ### Developers "re-inventing the wheel" is potentially harmful
 
 Developers who have not been exposed to RFC 4122 might naturally opt to invent their own approaches
-to UUID generation, potentially using `Math.random()`.
+to UUID generation, potentially using `Math.random()` (in
+[TIFU by using `Math.random()`][tifu]
+there's an in-depth discussion of why a Cryptographically-Secure-Pseudo-Random-Number-Generator
+(_CSPRNG_) should be used when generating UUIDs).
+
+Introducing a UUID standard library, which dictates that a CSPRNG must be used, helps protect
+developers from security pitfalls.
+
+## Overview
+
+The UUID standard library provides an API for generating RFC 4122 identifiers.
+
+The default export of the UUID library is the
+[Version 4 Algorithm](https://tools.ietf.org/html/rfc4122#section-4.4), and returns the string
+representation _(as described in RFC-4122)_.
+
+```js
+import uuid from "lib:uuid"; // (Note: exact import syntax is TBD).
+uuid(); // 52e6953d-edbe-4953-be2e-65ed3836b2f0
+```
+
+## Out of scope
 
-It's well documented that
-[`Math.random()` is not cryptographically secure](https://v8.dev/blog/math-random), by instead
-exposing users to the standard library UUID module we prevent the pitfalls that go hand in hand
-with home-grown implementations.
+Algorithms described in RFC 4122 other than Version 4 are not initially supported.
+
+Statistics we've collected
+([see issue #4](https://github.com/bcoe/proposal-standard-module-uuid/issues/4)) indicate that the
+Version 4 algorithm is most widely used:
+
+| Algorithm Version | Repo Count | %    |
+| ----------------- | ---------- | ---- |
+| v4                | 18318      | 79.7 |
+| v1                | 4399       | 19.1 |
+| v5                | 231        | 1    |
+| v3                | 29         | .1   |
+
+### Regarding other UUID versions
+
+While there is utility in other UUID versions, we are advocating starting with a minimal API
+surface that supports a large percentage of users _(the string representation of Version 4 UUIDs)._
+
+If research and/or user feedback later indicates that additional functionality, such as versions 1,
+3, and 5 UUIDs, would add value, this proposal does not preclude these additions.
 
 ## Use cases
 
@@ -48,15 +81,33 @@ How do folks in the community use RFC 4122 UUIDs?
 
 ## FAQ
 
-## History
+**what are the advantages to uuid being in the standard library?**
 
-## Specification
+- The `uuid` module is relied on by `> 2,600,000` repos on GitHub (June 2019). Guaranteeing a
+  secure, consistent, well-maintained UUID implementation provides value to millions of developers.
+- The 12 kb `uuid` module is downloaded from npm `> 62,000,000` times a month (June 2019); making
+  it available in the standard library eventually saves TBs of bandwidth globally. If we continue
+  to address user needs, such as `uuid`, with the standard library, bandwidth savings add up.
 
-## Implementations
+## TODO
 
-- none yet.
+- [x] Identify champion to advance addition (stage-1)
+- [ ] Prose outlining the problem or need and general shape of the solution (stage-1)
+- [ ] Illustrative examples of usage (stage-1)
+- [x] High-level API (stage-1)
+- [ ] Initial spec text (stage-2)
+- [ ] Babel plugin (stage-2)
+- [ ] Finalize and reviewer sign-off for spec text (stage-3)
+- [ ] Test262 acceptance tests (stage-4)
+- [ ] tc39/ecma262 pull request with integrated spec text (stage-4)
+- [ ] Reviewer sign-off (stage-4)
 
 ## References
 
-- [IETF RFC 4122](https://tools.ietf.org/html/rfc4122)
-- [JavaScript Standard Library Proposal](https://github.com/tc39/proposal-javascript-standard-library)
+- [IETF RFC 4122][rfc-4122]
+- [JavaScript Standard Library Proposal][standard-library-proposal]
+- [TIFU by using `Math.random()`][tifu]
+
+[rfc-4122]: https://tools.ietf.org/html/rfc4122
+[standard-library-proposal]: https://github.com/tc39/proposal-javascript-standard-library
+[tifu]: https://medium.com/@betable/tifu-by-using-math-random-f1c308c4fd9d

package.json

@@ -1,29 +1,15 @@
 {
   "private": true,
   "scripts": {
-    "test": ":",
+    "test": "prettier --check ./README.md",
     "prebuild": "mkdirp dist",
-    "pretest": "markdownlint -c .markdownlintrc.json README.md",
     "build": "npm test && ecmarkup --verbose spec.html dist/index.html --css dist/ecmarkup.css --js dist/ecmarkup.js",
-    "watch": "npm run build -- --watch"
+    "watch": "npm run build -- --watch",
+    "fix": "prettier --write ./README.md"
   },
   "devDependencies": {
     "ecmarkup": "^3.12.0",
-    "husky": "^2.4.1",
-    "lint-staged": "^8.2.1",
-    "markdownlint-cli": "0.17.0",
     "mkdirp": "^0.5.1",
     "prettier": "^1.18.2"
-  },
-  "husky": {
-    "hooks": {
-      "pre-commit": "lint-staged"
-    }
-  },
-  "lint-staged": {
-    "*.{js,css,json,md}": [
-      "prettier --write",
-      "git add"
-    ]
   }
 }