Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pick a spec name #24

Closed
foolip opened this issue Apr 2, 2015 · 11 comments
Closed

Pick a spec name #24

foolip opened this issue Apr 2, 2015 · 11 comments

Comments

@foolip
Copy link
Member

foolip commented Apr 2, 2015

So that I can request https://foo.spec.whatwg.org/ we need a value for foo. Much of the shape of the spec is still unknown, but the concepts involved are known: audio focus and media keys. Options:

  • audio-focus
  • media-keys
  • media-focus (suggested by @mounirlamouri)
  • media-session (as in MediaSession)
  • something else?
@marcoscaceres
Copy link
Member

I like media-session

@foolip
Copy link
Member Author

foolip commented Apr 2, 2015

I am partial to that as well, but would be OK with media-focus too. In the meantime I'll see what's involved in setting up foo.spec.whatwg.org.

@mounirlamouri
Copy link
Member

I would prefer media-focus over media-session given that the latter is about the problem scope and the former the name of an interface used in a proposed solution.

@marcoscaceres
Copy link
Member

yeah, true.... ok, I'm changing my vote to media-focus.

@foolip
Copy link
Member Author

foolip commented Apr 2, 2015

@annevk tells me it won't be much hassle to set up, so we just need to pick a name.

At this point the risk of both media-focus and media-session is that we'll end up with a spec that has none of those terms in its title or in any of the main interfaces. Not sure if richtr/html-media-focus#2 will re-surface if we go with focus, while session is very generic-sounding.

@doomdavve
Copy link
Contributor

Renaming specs wouldn't be the end of the world either? Have seen it multiple time in CSS land (e.g. Backgrounds and borders started out separate, CSSOM sliced and diced, etc.) and nothing too bad seem to come out of it.

I don't think media-focus is easily confused with focusable elements, not as much as |focusable| was at least.

@annevk
Copy link
Member

annevk commented Apr 2, 2015

I recommend starting with a name for the specification. "Media Focus Standard"? "Media Session Standard"? "Media Controls Standard"? Then we can pick a shorthand.

@jzaefferer
Copy link

I like the name of this repo, "media-keys". Makes it obvious enough what it is about, and can then introduce the related concepts like focus and session, which by themselves are much less obvious. So "Media Keys Standard"?

@padenot
Copy link

padenot commented Apr 21, 2015

MediaKeys is kind of taken by EME already: https://w3c.github.io/encrypted-media/#idl-def-MediaKeys.

@foolip
Copy link
Member Author

foolip commented Apr 29, 2015

To get things started, I'm suggesting "Media Session Standard" and have requested https://mediasession.spec.whatwg.org/. This doesn't mean that the end result will look anything like https://github.com/whatwg/media-keys/blob/gh-pages/MediaSession.md but we want to start experimenting and a media session as a core concept is in line with both Android and iOS.

@foolip
Copy link
Member Author

foolip commented Apr 29, 2015

I created a separate whatwg/mediasession repo for that work, but @marcoscaceres suggested in an email to rename this repo instead. I don't want to hijack if someone intends to work on other proposals, but if nobody objects within 12 hours (@richtr has a placeholder ready) I will rename.

@foolip foolip closed this as completed May 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants