Just a comment on the tags and their contents as opposed to the data modeling/data base design. I'll use the wiki on ID3 tags as a example (I would guess there are similar definitions for APE and Vorbis);
http://en.wikipedia.org/wiki/ID3 (this refers to ID3.org as the owner of the spec for the contents of the various versions of ID3 tags) This is where I'd say the definition of tag contents is, not the data base modeler/designer that is building a base to accommodate the cataloging of these tags. If the spec for the tags doesn't state that leading/trailing blanks are not allowed in a given tags content then I'd say they are allowed. With that spec in mind then I'd think that it is the job of the data base designer to honor the possibility of having leading and/or trailing blanks. I believe that what we're seeing in the data base is a more strict interpretation of the tag specification. Strictly speaking I'd say that the owner of the file is responsible for the integrity of the data in the file and that the data base designer should honor the data as it is in the file as long as it conforms to the spec of that data type. -- w3wilkes 2 Duets - 1 for upstairs and 1 for downstairs ------------------------------------------------------------------------ w3wilkes's Profile: http://forums.slimdevices.com/member.php?userid=22973 View this thread: http://forums.slimdevices.com/showthread.php?t=88154 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
