Metadata

Motivation

All the Xiph.org codecs have some internal mechanism for including metadata about the current stream. Generally, this is one of the codec headers, and in the words of the vorbis spec, "It is meant for short, text comments...much like someone jotting a quick note on the bottom of a CDR."

This works well enough for most things, and can be overloaded/abused (depending on your point of view) for most other things. But there are three major requirements that point to the design of an external metadata format; one that can be interleaved with the other streams in a container.

Machinability There are a number of items of metadata that a player will want to parse and take action on. While there are usually 'convention' schemes for doing this with the embedded comment headers, this is much easier if there is a separate metadata stream designed for such use, instead of having to do best-effort parsing of natural language comments. For example, a video file with multiple audio tracks can specify the language of each one; a player than can parse these reliably can match them against a language preference list configured by the user to automatically select and begin playback of the best option.

Kitchen Sink There are a minority of people who care passionately about having every detail about a track available. In the sense of conserving such information, and providing an equivalent to liner notes for online distribution, this is a goal worth supporting. However, the simple unstructured key-value pairs offered by the inline metadata are unwieldy for this level of detail. How do you tell the 2nd unit Assistant Director from the USA unit Assistant Director? How do you indicate which artist played tenor sax in the solo?

Addressability The internal comment metadata headers are by necessity attached to a single content stream. This is useful for some appication, but a limitation in others. In a multiplexed stream, which set of comments refers to the collection as a whole? (By convention, in Ogg, it's the first logical bitstream occuring, but we can do better.) A separate metadata stream type must address this issue of collective metadata while still allowing description of individual streams. It should also allow temporal addressability, so that changes can be described. Because the in-stream comment metadata are part of the codec headers, it cannot change over the course of the stream, and allowing additional comment packets elsewhere in the stream presents seeking challenges. In the Ogg container this can be resolved by inserting a chain boundary, but this is a poor option for very-low-bitrate streams and unreliable transports such as RTP.

Proposed Solutions

RDF + dublin core

XML-encoding (generic rdf or CMML?)

binary encoding (three-component length-encoded binary vectors) 呼吸系统槲皮素化肥片化工防腐设备化积口服液化学合成药化学原料药环孢菌素软胶囊环丙氯地孕酮环丙沙星环氧环己烷黄连素黄嘌呤黄体酮肌苷基因工程白细胞介素基因工程干扰素基因工程药品基因重组人白细胞介素加巴喷丁甲醇甲醇催化剂甲肝甲磺酸帕珠沙星甲基多巴甲醛降凝干加剂胶囊清洁剂结核类结晶山梨醇解热镇痛类解热镇痛类药物金钱通淋金银花浸膏精神病类精细化工咖啡因卡马西平坎地沙坦康迈欣康素抗病毒类抗感染类抗过敏类抗生素抗雄激素抗氧剂抗真菌类抗肿瘤类口服固体制剂口服葡萄糖口服液口服制剂矿产无机镁业拉呋替丁兰粒子劳拉西洋雷替曲塞立安利巴韦林利福定利福平利福平片痛血康胶囊利高霉素利眠宁利培酮利血平邻氨基苯甲酰胺临床研究羚羊感冒胶囊硫酸庆大霉素硫酸软骨素硫酸双肼屈嗪硫酸小诺霉素芦丁绿动力氯氮氯氮平中间体氯氮卓氯喹侧链氯霉素罗格列酮罗红霉素罗红霉素侧链洛伐他汀洛索洛芬钠片麻醉药品马杜霉素马来酸依索拉啶马吲哚吗啉梅毒美洛美司美替诺龙米非司酮米托蒽醌免疫移植茉莉花茉莉花净油那琦耐博利尿素牛磺酸农药增效剂诺氟沙星诺氟沙星胶囊诺孕酯潘托拉唑钠培菲康喷昔洛韦皮质激素片剂片剂混悬剂肉桂酸乳酸环丙沙星乳糖酸红霉素乳糖酸钠三甲基氢醌三抗素蒲地蓝消炎片三磷酸腺苷二钠三氯生广谱抗菌剂沙坦主环鲨肝醇山梨醇山楂精降脂片蛇胆川贝胶囊生化药物生物发酵原料药生物工程制品生物农药十一酸睾酮胶丸食品添加剂手性药物手性吲哚生物碱兽药兽药医药原料药输液薯芋皂素双肼呔嗪双嘧达莫双烯醇酮水飞蓟素水杨酸水针四氮唑系列饲料添加剂塑料编织袋钛白粉碳酸氢铵糖尿病治疗类特比萘芬特药类提取液体轻松替勃龙浸膏油茶皂素替米沙坦天然维生素E 天然植物天然植物浸膏油茶皂素田草酮基布洛芬胶囊痛血康胶囊头孢氨苄头孢呋辛酸头孢菌素头孢拉定头孢类头孢曲松头孢三嗪侧链酸头孢他啶头孢他美酸拓扑替康万昔络韦维甲酸类维生素维生素B12 维生素B6 维生素D 维生素D2 维生素D3粉维生素D3油维生素类维生素类衍生物维他命卫生球文拉法辛乌苯美司胶囊乌洛托品无机化工戊肝西力士腺苷腺嘌呤橡胶消毒片硝苯地平缓释片小容量注射剂缬沙坦心可舒胶囊心血管类心血管药物辛伐他汀新戊酸氯中酯干扰素活性剂新鱼腥草素钠信法丁信法丁片信利妥雄激素雄性激素熊去氧胆酸片溴米那畜卫佳血脉宁血压达静樟脑球牙周宁片亚麻酸亚麻酸活力软胶囊亚叶酸钙盐霉素盐酸阿扎司琼盐酸奥昔布宁盐酸蒽诺沙星盐酸伐昔洛韦盐酸氟哌酸盐酸环丙沙星

Metadata

Motivation

Proposed Solutions

Navigation menu