Daniel,
before you step over everything that has been done before, we need to
determine what exactly is the use case for your new specification.
What concerns metadata, we currently have:
* vorbiscomment - this is a header at the beginning of a logical
bitstream which has metadata that refers to the complete file; there
is a specification, which has been public for a long time and is the
de-facto standard that is (or should be) used by all software (see
http://xiph.org/vorbis/doc/v-comment.html)
* cmml - this is a logical bitstream for time-continuous textual
annotations (metadata) for ogg files (see
http://wiki.xiph.org/index.php/CMML)
* skeleton - this is an extension to the ogg bitstream format, which
has all the encapsulation-specific low-level metadata (see
http://wiki.xiph.org/index.php/Ogg_Skeleton)
All of these are supported by xiph and may need further
work/extensions or potentially a replacement if they are not fit to
provide what is required.
Before throwing out more random specifications, could we please look
at what you are trying to achieve with the new format? Can you tell us
where the existing technologies are lacking?
Thanks,
Silvia.
On 9/9/07, Ralph Giles <giles@xiph.org> wrote:> On Sat, Sep 08, 2007 at 07:42:11PM +0200, Daniel Aleksandersen wrote:
>
> > Anyhow, some audio manager software uses Author, some uses Artist, and
many
> > use Creator. It just leaves a mess.
>
> Really? What programs aren't using the recommended artist tag?
>
> -r
> _______________________________________________
> ogg-dev mailing list
> ogg-dev@xiph.org
> http://lists.xiph.org/mailman/listinfo/ogg-dev
>