search for: oggserial

...But I will be the first to admit I have no idea how Oggs work. (!!) I figured that multiple elements can be described using URIs. > A URI/URL scheme for referencing streams would be a generally useful > thing. Should we override the query mechanism like the time fragment > draft? "?oggserial=0x15323421" ? Please explain how oggserials works. If all items (audio, text, images, ...) in an Ogg stream can be described using oggserials; than a oggserial attribute should be used instead of a more generic URI attribute. A quick an dirty example describing the relation between an imag...

Daniel Aleksandersen wrote: > On Saturday 08. September 2007 11:40:05 Ian Malone wrote: >> Daniel Aleksandersen wrote: >>> Hi again list, >>> >>> Attached is a much improved version of yesterday's draft. Introducing >>> the audio:collection:artwork element to deal with album cover graphics >>> and such. >>> >>> After

Ralph Giles wrote: > > A URI/URL scheme for referencing streams would be a generally useful > thing. Should we override the query mechanism like the time fragment > draft? "?oggserial=0x15323421" ? > This is roughly what was suggested the last time around. A possible refinement is to provide a mapping from identifiers to IDs so you could say "?oggid=myvideo". The mapping could maybe be handled by a fishbone packet. -- imalone

...ppear on audio, video, text, image elements. Though there is no limit to how many audio elements you have and how many rights children those elements have. So I guess this example would explain everyting better: <?xml ...><metadata ...> <audio type="audio/flac+lossless" oggserial="somethingsomething"> ????????<rights date="2019">? 2019 Harvey the Wonder Hamster</rights></audio> <audio type="audio/flac+lossless" oggserial="somethingelse"> ????????<rights date="2020">? 2020 Your Mother</rig...

...; text, image elements. Though there is no limit to how many audio elements > you have and how many rights children those elements have. So I guess this > example would explain everyting better: > > <?xml ...><metadata ...> > <audio type="audio/flac+lossless" oggserial="somethingsomething"> > <rights date="2019">? 2019 Harvey the Wonder Hamster</rights></audio> > <audio type="audio/flac+lossless" oggserial="somethingelse"> > <rights date="2020">? 2020 Your...

Hi Daniel,, > I really have to ask you: Have you even tried to describe media using the > excising solutions? I don't mean adding subtitles and editing stuff. I mean > really say what a Ogg file contins. There is no working wheels for this. > Vorbis comments--used in FLAC too--can describe content with a very limited > field names (and badly enforced standards). I have and I

...hough there is no limit to how many audio > > elements you have and how many rights children those elements have. So > > I guess this example would explain everyting better: > > > > <?xml ...><metadata ...> > > <audio type="audio/flac+lossless" oggserial="somethingsomething"> > > ? ? ? ? <rights date="2019">? 2019 Harvey the Wonder > > Hamster</rights></audio> <audio type="audio/flac+lossless" > > oggserial="somethingelse"> > > ? ? ? ? <rights date="2...

...in our application, and even a video/theora stream since it's an internal reference. But what if there are multiple multiplexed video streams. A URI/URL scheme for referencing streams would be a generally useful thing. Should we override the query mechanism like the time fragment draft? "?oggserial=0x15323421" ? -r

...ss. Cheers, Silvia. On 9/9/07, Ian Malone <ibmalone@gmail.com> wrote: > Ralph Giles wrote: > > > > > A URI/URL scheme for referencing streams would be a generally useful > > thing. Should we override the query mechanism like the time fragment > > draft? "?oggserial=0x15323421" ? > > > > This is roughly what was suggested the last time around. > A possible refinement is to provide a mapping from identifiers > to IDs so you could say "?oggid=myvideo". The mapping could > maybe be handled by a fishbone packet. > > -- &g...

Daniel, these are all good ideas and worth progressing. However, it may be better not to merge too many goals in one format (MPEG-7 did that and ended up as a big mess). So, I suggest to start by structuring the types of things you want - then finding out which parts belong where into existing formats such as vorbis comment, Skeleton and CMML, and only then start to develop a new format. For