<br><br><div class="gmail_quote">On Jan 16, 2008 9:58 PM, <a href="mailto:ogg.k.ogg.k@googlemail.com">ogg.k.ogg.k@googlemail.com</a> <<a href="mailto:ogg.k.ogg.k@googlemail.com">ogg.k.ogg.k@googlemail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">> I also disagree that CMML is complex, but I may be mistaken. In terms<br>
> of complexity, I see it as about 10% of the way between using<br>> zero-markup and using HTML.<br><br></div>When I looked at it, it seemed to be that CMML could contain things like<br>URLs, and other "non-text" markup. While complex may not be the right<br>
word for it (maybe "too much of a superset for most uses of text" would be<br>more appropriate), a program using a stream to get, say, video subtitles,<br>would have to expect those and deal with them (probably by discarding<br>
them as they parse them).<br><br>This is what I meant by complex, that is, in the context of what I was trying<br>to do, which is certainly a rather narrow goal compared to the expressivity<br>that CMML can give due to its being XML based, making it more suited to<br>
meta description of accompanying streams, for which it seemed (from what<br>I've seen) to have been designed.</blockquote><div><br>Hyperlinks are optional - as is just about all other markup.<br><br>The simplest CMML markup you can create is in principle identical to your example on the wiki page:<br>
<br><cmml><br> <clip start="00:00:05" end="00:00:10:><br> <desc>This is a text</desc><br> </clip><br></cmml><br><br></div><br>Cheers,<br>Silvia.<br></div>