File: development.html

package info (click to toggle)
libjaudiotagger-java 2.0.0-1
  • links: PTS, VCS
  • area: main
  • in suites: squeeze
  • size: 6,380 kB
  • ctags: 8,143
  • sloc: java: 57,670; xml: 371; makefile: 12; sh: 11
file content (30 lines) | stat: -rw-r--r-- 2,273 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
 
<html>
<head>
<title>DevelopmentDetails</title>
</head>
<body>

<h3>Development Goals</h3>
<p>Welcome to JAudiotagger. The aim of this project is to provide a world class Java library for editing tag information in audio files. Most existing solutions are not java based inhibiting the use of java applications with digital files.
<p>This project was branched from the <a href="http://jid3lib.dev.java.net">jid3lib</a> project which provided the basis for an ID3 tagging api, but was incomplete. I wanted to move
away from the ID3 centric nature of the project and provide support for other tagging formats. 
</p>
<h4>Functional Goals</h4>
<ul>
<li>It should support the ID3 Specification accurately and completely,ideally it should provide the reference implementation for ID3.org</li>
<li>It should support other audio and tagging formats in a consistent and flexible manner, it should be possible to provide a level of indirection to end users so they do not have to deal with 
the intricases of the format themselves WITHOUT dumming down the interface and only providing access to basic fields such as Artist/Album...</li>
<li>It should help in the development of an XML/RDF tagging format</li>
<li>It should integrate well with new technologies such as Musicbrainz</li>
<li>It should be possible to convert between tag versions (i.e v23 <-> v 24) and between tagging formats If allowed for the audio format (e.g mp3 supports both ids and ogg)</li>
<li>Scope is limited to reading and writing tags</li>
</ul>

<h4>Non Functional Goals</h4>
<ul>
<li>It should be written the Java way,many low level interfaces take a very old-fashioned approach to design, often they are designed like a C program with vast switch statements/bit manipulation and magic numbers sprinkled everywhere. The code should be self documenting you should not need to know the ID3 specification inside out from another source</li>
<li>It should take advantage of the latest Java releases when they are availble on all major platforms, I have not upgraded to Java 1.5 yet because this has only recently been adopted as the default java platform on MacOS</li>
<li>We should work together with other open source projects to stop the wheel being reinvented</li>
</ul>