Re: [manifest] camelCase more suitable to JSON and JS API (#72)

We haven't _really_ eff'ed up until this reaches CR status. As a Working Draft, breaking changes should be expected by both implementers and users. The draft stage is there for little mix-ups like this to be found by reviewers and get corrected so future users don't have to live with it... Which is why it doesn't demand backwards-compatibility between versions of the draft.

Also, I'm not suggesting that we support both naming forms in the spec - I'm saying that vendors could support both for a short period (perhaps with a deprecation notice), giving users time to switch over.

Lastly, I'd be happy to update all the documentation & articles for you. I'm not sure how much I can do for the various implementations, but for the ones that are open-source - I can probably help with those too.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/72#issuecomment-113986038