- • lucasgonze clears throat
- [6:21pm] lucasgonze: I have this thought –
- [6:22pm] lucasgonze: apply http://www.w3.org/wiki/LinkHeader to audio files on the web, as a method to annotate pcm data.
- [6:22pm] lucasgonze: as an alternative to id3
- [6:22pm] lucasgonze: so let’s say there is http://example.com/example.wav
- [6:22pm] lucasgonze: wav has no metadata support
- [6:23pm] lucasgonze: GET on http://example.com/example.wav would return a response header pointing to a metadata file
- [6:23pm] lucasgonze: Link: example-metadata.json; rel=meta
- [6:25pm] lucasgonze: GET http://example.com/stairwaytoheaven.wav
- [6:25pm] lucasgonze: Link: http://musicbrainz.org/ws/2/recording/ccfdd180-22e1-49b9-bd81-b5fcf2c6474e?inc=artist-credits%2Breleases; rel=meta
- [6:35pm] lucasgonze: use CORS on the metadata resource http://www.w3.org/TR/cors/ to enable cross site requests from ajax
- [6:37pm] lucasgonze: the metadata technology is factored out of the codec.
- [6:37pm] lucasgonze: the http request becomes the envelope for waveform data and metadata together.
- [6:37pm] lucasgonze: metadata technology and audio signal processing technology can evolve independently
See also the Web Audio API and jsmad.
2 thoughts on “Link: header for audio metadata”
Seems very cool. The one advantage of meta in file is that it travels everywhere with the file, including offline. In the above scenario, seems easy for the file to travel places where the client has no idea how to check for the meta header.
Maybe a backup could be to also install meta link inside id3 as a fallback?
I’d think of it as a caching thing.
You have an audio resource at some URL. It’s just PCM bytes, no metadata. A wav file would match this description. But I’m thinking about next-generation audio formats that have real compression, are accessible to CORS, and can be fed into web audio APIs.
For the most part the file would be kept with its URL. The bytes returned by the URL and the URL itself wouldn’t be decoupled, so that one could travel without the other. Given that the client has the URL and the URL is enough to get a metadata file, the metadata and audio do travel together.
The concept for metadata in this post is a sibling to the web audio API. It’s a web metadata API.