Christian: > 1. Introduction > 1.1. Project/Component Working Name: > id3lib > > 1.2. Name of Document Author/Supplier: > Christian Kelly > > 1.3. Date of This Document: > 02/04/08 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > 1.4.1. The Community you expect to review your project: > 1.4.2. The ARC(s) you expect to review your project:
Probably LSARC > 1.4.3. The Director/VP who is "Sponsoring" this project: > robert.odea at sun.com > 1.4.4. The name of your business unit: > OPG/OpenSource > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: > Tom.Garland at Sun.Com > 1.5.2. Responsible Engineer: > Christian.Kelly at Sun.Com Where is 1.5.3? > 1.5.4. Interest List: > jds-dev at sun.com > > 4. Technical Description: > 4.1. Details: > id3lib is a library for handling ID3v1 and ID3v2 tags added > to digital media files. While the format allows for tagging > any media format, it is used exclusively with MP3s. The tags > hold information about the file such as artist, title, year > of production, etc.. > > The ID3 tagging standard is independant of the media format Independent is misspelled. > of the file that they are applied to, they are merely appended > or pre-pended to the file. > > This proposal adds version 3.4.3, the latest stable release. > > The use of the ID3v1 standard has dwindled due to the fact > that it is now twelve years old and the obvious limitations > compared to ID3v2 - i.e. fixed lenth fields of thirty characters. > For these reasons it is extremely unlikely that we will see > compatability breaks in the API. length and compatibility are misspelled. I don't think it adds value to have the same "For these reasons it is unlikely to have compatibility braeks" at the end of the above and the below paragraphs. Why not just say this once after talking about both ID3v1 and ID3v2? > The last revision of the ID3v2 standard was eight years ago. Also, > the standard allows for adding tag fields in a backwarrds > compatible way. For these reasons, it is unlikely we will see > compatability breaksin the API. Has the libid3tag interfaces remained stable for a long time also? Just because the specs are stable doesn't necessarily mean that the library has been stable. > 4.2. Bug/RFE Number(s): > None > > 4.3. In Scope: > See Above > > 4.4. Out of Scope: > See Above > > 4.5. Interfaces: > > -------------------------------------------------------------------- > Exported Stability Comments > > -------------------------------------------------------------------- > SUNWid3lib Uncommitted > Package name > libid3.so Uncommitted C library > /usr/bin/id3info Uncommitted CLI > /usr/bin/id3convert Uncommitted CLI > /usr/bin/id3tag Uncommitted CLI > /usr/bin/id3cp Uncommitted CLI > /usr/include/id3 Not an Interface *NEW* > Folder > /usr/include/id3.h Uncommitted > Where are questions 4.6 to 4.8? Brian
