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) 维生素D3 叶酸伊特安伊维菌素医疗服务结晶山梨醇医药原料药医药制剂医药中间体消毒药剂依立替康依普瑞丰依托红霉素片依维菌素依西美坦乙胺丁醇乙肝乙酰吉他霉素颗粒剂异烟肼异烟酸益比奥因特芬吲达帕胺片吲哚生物碱茚满酮英路因营养强化剂硬胶囊硬脂酸硬脂酸红霉素原料药右旋糖酐铁玉米淀粉愈创木酚愈创木酚甘油醚愈创木酚磺酸钾原料药洗衣粉孕激素甾体激素激素甾体激素类樟脑丸针剂芝麻酚植物药原料药止痛灵成品药制药心血管中成药中间体中枢神经片剂模具中西药制剂中药种植肿瘤标志物重组人红细胞生成素重组人粒细胞重组人粒细胞集落刺激因子朱砂莲胶囊注射剂注射葡萄糖左西孟旦左西替利嗪聚合物驱油剂睾丸素格列美脲葛根芩连片更昔洛韦庚肝谷维素片光敏剂广谱抗菌剂国家二类新药过氧乙酸合成药物核酸恒欣红霉素肟葡甲胺葡萄糖葡乙胺奇净康祺泰GINA 蕲蛇酶注射液强化戊二醛强力霉素强盛羟基氯喹侧链青霉素类曲克芦丁驱蚊片剂去氧氟尿苷全灭长效驱虫注射液全球性原料药乙胺盐酸盐盐酸洛美沙星盐酸谱萘洛尔盐酸头孢他美酯盐酸头孢他美酯片盐酸小檗碱盐酸盐盐酸左氧氟沙星颜料氧氟沙星氧雄诺龙药品流通药品注册服务药物药物中间体感光高分子破伤风抗毒素盐酸环丙沙星胶囊甘油 CIPROFLOXACIN VE烟酸酯胶囊阿苯达唑阿卡明阿拉肽阿那曲唑阿奇霉阿司匹林阿替洛尔阿维菌素阿昔洛韦艾滋病安宫黄体酮安普罗列安普罗林氨基酸保护剂氨基酸类衍生物氨基酸衍生物奥卡西平奥拉米特奥洛他定奥美拉唑白花油白藜芦百士欣半合成抗生素半合成原料药棒酸包装容器胞苷保健品保肾康倍灵高效广谱抗体外寄生虫药倍他米松苯磺阿曲库胺苯甲酰甲酸甲酯天门冬氨酸苯乙酮甲酯冬氨酸吡嗪酰胺扁桃酸表雄酮丙肝丙基硫氧嘧啶参茸蛤蚧保肾丸藏成药牙膏茶碱肠胃病治疗类橙皮甙雌二醇环戊丙酸酯雌三醇醋酸甲地孕酮醋酸美伦孕酮醋酸钠醋酸坦勃龙软胶囊蛋白同化激素迪克拉苏地蒽粉地克珠利地舍平碘伏消毒液电池模具淀粉糖叠氮钠丁洛地尔注射液东莨菪醇杜球对甲苯磺酸氟乙酯对羟基苯甲醇对异丙基苯甲酸多非利特多索茶碱片多肽多肽缩合剂多西环素鹅去氧胆酸胶囊厄贝沙坦恶霉灵水剂吡啶醇酯二氧化碳法莫替丁注射液泛昔洛韦芳香球放射性药物专用消毒剂非诺洛芬钙酚磺乙胺粉针剂风疹病毒呋喃胺盐敷克酰基化氟宝注射液氟达拉滨磷酸盐氟康唑氟康唑片氟罗沙星粗品氟哌酸氟西汀氟孕酮福美司坦甘氨酸苄酯对甲苯磺酸盐甘氨酸苄酯盐酸盐甘草次酸甘草酸单铵盐甘草酸单钾盐甘草酸二铵甘草酸二铵盐甘草酸二钾盐甘草酸二钠盐甘草酸三钾盐甘草酸三钠盐甘草酸锌甘草甜味素片剂胶

Metadata

Motivation

Proposed Solutions

Navigation menu