Re: [encoding] The title of the document needs to be more than one (commonly used) word (#11)

I think we want people to be aware of this spec and what it’s about, if they see it referenced, if they see its title somewhere, if they see a ‘request for review’ and so on. The title should be good enough to alert people that they might be interested, might need to read and use it, should review it, and so on.

I really think that helpful is better than ‘cool’ (and cool is in the eye of the beholder).

We’re not writing specs for ourselves, we’re writing specs to try to help the entire industry.

> On Nov 9, 2015, at 9:58 , Domenic Denicola <notifications@github.com> wrote:
> 
> @nigelmett can you give links to this observed confusion? Note that we're not worried about causing confusion to drive-by reviewers, but instead substantive cases like someone writing a video processing spec and accidentally referencing the Encoding Standard because they thought it would contain algorithms for H264.
> 
> —
> Reply to this email directly or view it on GitHub.
> 

David Singer
Manager, Software Standards, Apple Inc.



---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/11#issuecomment-155874422