[w3c/FileAPI] Use valid UUID in blob: URL example (#151)

The algorithm for creating a blob URL references RFC4122 to generate a UUID. However the example contains an _invalid_ UUID (according to RFC4122): `9115d58c-bcda-ff47-86e5-083e9a215304`

This given string is not a valid UUID because it does not contain a meaningful version field (the first character after the second dash).

It could be worthwhile to consider specifying the specific UUID algorithm to be used ([Version 4 UUIDs](https://tools.ietf.org/html/rfc4122#section-4.4)) however that might be an actual change in the spec, not just an editorial change like the one I propose here.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/FileAPI/pull/151

-- Commit Summary --

  * Use valid UUID in blob: URL example

-- File Changes --

    M index.bs (2)

-- Patch Links --

https://github.com/w3c/FileAPI/pull/151.patch
https://github.com/w3c/FileAPI/pull/151.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/pull/151