![]() The lowest hierarchy found in music or movies When an album or episode has different logical partsĬorresponds to parts of a track for audio (like a movement) The most common grouping level of music and video (equals to an episode for TV series) The high hierarchy consisting of many different lower items Have different meanings depending on where it is (otherwise we would end up with 15 TITLE_ tags). ![]() For now audioĪnd video will have different values & names. (CD title or track title), we also need a set of official TargetType names. The album it comes from and even the CD set even if it’s not found in the file.įor application to know what kind of information (like TITLE) relates to a certain level For example, in an audio file with one song you could have information about The TargetType element allows tagging of different parts that are inside or outside a For instance, you would store “15.59” instead of “$15.59USD”. Only numbers, no letters or symbols other than “.”. For currency amounts, there SHOULD only be a numeric value in the Tag.Also, a thousandths separator SHOULD NOT be used. To display it differently for another local, applications SHOULD support auto Fields that require a Float SHOULD use the “.” mark instead of the “,” mark.To store a specific day such as May 1st, 2003, you would use “”. To store less accuracy, you remove items starting from the right. MM = Month, DD = Days, HH = Hours, mm = Minutes, ss = Seconds, mss = Milliseconds. The fields with dates SHOULD have the following format: YYYY-MM-DD hh:mm:ss.mss YYYY = Year,.TagNames starting with the underscore character ‘_’ are not official tags see (#why-official-tags-matter).The TagName SHOULD NOT contain any space.The TagName SHOULD consists of capital letters, numbers and the underscore character ‘_’.Which tag has the wanted meaning so that other apps could understand the same meaning). ![]() In their own design (if they choose to support a list of meta-information they SHOULD know We also need an official list simply for developers to be able to display relevant information A website would be better for that… It’s hard to define what SHOULDīe in and what doesn’t make sense in a file. ![]() But it doesn’t mean it willīe accepted… Matroska files are not meant the become a whole database of people who madeĬostumes for a film. Official one that fit them and hopefully use it ! If it’s not in the list, this personĬan contact us any time for addition of such a missing tag. So hopefully, when someone wants to put information in one’s file, they will find an But it’s usually a bad idea to use custom/exotic tags because you will probablyīe the only person to use this information even though everyone else could benefit from it. The applications, they usually give you a basic list of tags you can use. If you look at this page you will realize we are in between.Īdvanced-users application might let you put any tag in your file. There is a debate between people who think all tags SHOULD be free and those who thinkĪll tags SHOULD be strict. Than one tag of a certain type to be stored, then more than one SimpleTag SHOULD be used. Multiple items SHOULD never be stored as a list in a single TagString. In this way, it becomes possible to store any Tag as attributes of another tag. Then your tag tree would look something like this: That singer being the lead singer for a track that included multiple bands simultaneously, When a Tag is nested within another Tag, the nested Tag becomes an attribute of the base tag.įor instance, if you wanted to store the dates that a singer used certain addresses for,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |