[ID3 Dev] Suggestion - uniform 'Element ID' creation]

[Michal Vician]

> I can see the merit of your "uniform Element ID"
> concept in terms of simplicity for parsers. However, I'm concerned that
it would block one of the useful capabilities of the current scheme -
the ability to reference chapters from more than one table of contents.
>
> For example, for the recording of a rock festival you could create a
CHAP frame for each song and then index these frames in three ways using
different CTOCs to provide:
>  - a full, temporally ordered table of contents
>  - a table providing an index of band names or genres
>  - a table listing highlights
>
> I think it's important to maintain this kind of flexibility because it
opens up all kinds of interesting opportunities for content developers.

Oh yes. I had forgotten that there may be more than one table of contents
in each tag. Therefore I have adjusted my "uniform Element ID" concept so
that there may be more than one table of contents. How?
Just by adding the "X#" at the very beggining of each Element ID.
X - the unigue number identifier of each table of contents.
Here is example of 2 tables of contents written in one ID3 tag (there are
also some CHAP frames which are not referenced by any CTOC frame):

{THIS IS TABLE OF CONTENTS #1}
1#0 (root - zero level)
	  1#1 (1st level)
	  1#2
	  1#3
	    1#3.1 (2nd level)
	    1#3.2
	    1#3.3
	      1#3.3.1 (3rd level)
	      1#3.3.2
	      1#3.3.3
	        1#3.3.3.1 (4th level)
	        1#3.3.3.2
	        ...
	  1#4
	    1#4.1 (2nd level)
	    1#4.2
	    1#4.3
	      1#4.3.1
	      1#4.3.2
              ...

{THIS IS TABLE OF CONTENTS #2}
2#0 (root - zero level)
	  2#1 (1st level)
	  2#2
	  2#3
	    2#3.1 (2nd level)
	    2#3.2
	    2#3.3
	      2#3.3.1 (3rd level)
	      2#3.3.2
	      2#3.3.3
	        2#3.3.3.1 (4th level)
	        2#3.3.3.2
	        ...
	  2#4
	    2#4.1 (2nd level)
	    2#4.2
	    2#4.3
	      2#4.3.1
	      2#4.3.2
              ...

{CHAP FRAMES NOT REFERENCED BY ANY CTOC FRAME}
*1
*2
*3
...

I think that now there is nothing what would block the capability of
current chap/ctoc scheme. I also think that this way of creating "element
ids" will make it much easier for parsers.
Consider revising the current chapter scheme in this way please.

> Thanks also for the example content. I'm having problems with this
because my chapter tool application is based on the Jens Vonderheide API
and this doesn't currently support ID3v2.4. Does anyone have a fix for
this?

Just tell me and I can generate ID3 tag in whatever version.
See attachment. There is example content in ID3v2.3.

Cau
Miso

-- 
Michal Vician
id3v2 at audiott.com
http://www.audiott.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: example content.zip
Type: application/zip
Size: 1853 bytes
Desc: not available
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20051111/355a3348/attachment.zip>
-------------- next part --------------
---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org