Why no "audio" type?

Open
#21 15 comments 13 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
html
Domain
documentation

Research direction

Start with the oEmbed specification and compare the existing video, photo, link, and rich types. Review how an audio type would fit the stated HTML5 player use case; done means the specification clearly resolves whether and how audio is a first-class type.

Written by the indexing model from the issue text.

Description

Postpone

Why is there no 'audio' type in the spec?

We only have video, photo, link and rich - which can all return html, be it for an image or an iframe with an HTML5 video player in it or some Flash.

So, seeing as we can easily put HTML5 audio players in iframes, I think that we should be able to define them as such. As 'audio'.

Sure, 'rich' could be a document PDF or something, arbitrary. But why is audio not a 'first class type'?

It's the most easily created and consumed media type in most of the world, yet constantly overlooked (because we can't 'see' it? ;) )

thanks.
Kosso

Dominant language
PHP
Stars
1.4k
Forks
772
Avg merge
12h 54m
Merged PRs (30d)
16

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from iamcal/oembed

All issues in iamcal/oembed

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.