[ID3 Dev] Why is footer not included in total size?

[Jim]

Even if a comprehensive test suite was not created, I think it would still
be better to have more example tags/files to use for testing a particular
app.  Perhaps someone could be in charge of compiling submissions from
developers or other people that submit tags for use in testing?  (That
person would have to have a thorough knowledge of the spec/standards.
Perhaps someone that has developed or is developing a fully compliant ID3v2
application?)  If this project was started now, eventually it could claim to
be a comprehensive set of example tags once enough submissions were
received.

And if the order that the frames are written is carefully controlled, is
there something else that would cause a written tag to not be bit-for-bit
identical to an example tag?  (That's assuming it followed the model of the
example tag, like having/not having an extended header, using
unsynchronization, etc.)

Jim


----- Original Message ----- 
From: "Scott Wheeler" <wheeler at kde.org>
To: <id3v2 at id3.org>
Sent: Tuesday, November 21, 2006 7:53 AM
Subject: Re: [ID3 Dev] Why is footer not included in total size?


> Ray Manning wrote:
> > Is Martin Nilsson active on this list?
> >
>
> I've not seen anything ID3 related from him in years.
>
> > Example tags
> > A comprehensive test suite for all versions of ID3 tags are currently
under
> > development. The test suite includes both conforming tags and
non-conforming
> > tags so that both standards coformance and software robustness can be
> > tested. Part of these will be released as example tags while the rest
will
> > be sold to cover development and running expenses. If you are
interested,
> > contact Martin Nilsson.
> >
> > While waiting for the ID3v2 test suite, feel free to try the
ID3v1/ID3v1.1
> > test suite.
> >
> > --------------------------------------
> >
> > That seems to imply to me that people have been waiting for example tags
> > since v1.
> >
>
> And they'll keep waiting until someone takes up the not-terribly-fun
> task of creating such a suite.  It being a good idea won't make it happen.
>
> Even from there you've got a lot of obstacles:
>
> - It's going to be hard to get together multiple people that know the
> spec well to do bit-for-bit compliance checks.
> - Most implementations don't even claim to do the whole spec.
> - Writing is much more interesting than reading compliance-wise and
> it's very difficult to set things up to get bit-for-bit output matches
> even with compliant implementations.
>
> -Scott
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org