Summary

The idea is a part of the Web 2.0 wave. The main concept is to tag the contents of an audio, may it be a podcast, song, audio book or audio clip.

A tag should be readable/writable on a specific timestamp in the track. Which is then searchable by the software.

There are two ways in implementing the tags, [1] embedding in the metadata of the audio or [2] storing them in a database.

[1] The tags will be encoded in the comments field in the ID3v2 or APEv2 for MP3 files and Vorbis Comment for Vorbis and FLAC files. The tags will then be parsed when read.

Pros:- No other place needed for the storage of the tags also modifiable "by hand".- Plugins could be made for mainstream media players to parse and code the tags.

Cons:- I don't know. Metadata corruption perhaps? Or the tags are not that "secured"?

[2] The tags and their respective timestamps are stored in a database then the audio file could be track in a certain way, some that came up with:

- A hash of the track will be stored in the database which will then be matched to a hash calculation done by the client computer.- Placing an ID on the metadata of the track which should match in the database.

Pros:- Centralized server

Cons:- Centralized server- Requires an Internet connection

Tools/References:ID3APEv2Vorbis CommentPHP PEAR MP3_ID packagePHP PEAR File_Ogg package

What do you think of this idea or comment?
(You can change your vote at any time)

I agree

No opinion

I disagree