Oleksij Rempel <bug-track at fisher-privat.net>> On 05.06.2012 20:41, Martin Leese wrote:...>> On 6/5/12, Oleksij Rempel wrote: >> || We need fallowing tags: >> || creation datetime: seconds and time zone should be included. >> || source host: it can be name or guid. to organise created files by >> sources. >> || keywords,events. >> || date and person ho did transcription of record. >> >> To me, this looks like a job for three or more >> separate VorbisComments. You might want to >> choose keys which typically are not used for >> other things. For example, don't use DATE as >> this typically stores the date the track was >> recorded.> I do not like the idea of using separate VorbisComments, but i'll keep > this option open.Why not? For the small set of metadata elements you describe below, to me this still looks like the way to go.> According to this documentation: > [1] > http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf > > we can use fallowing tags (page 39): > dc:creator > dc:date > dc:description > dc:identifier > dc:source > dc:subject > xmpBJ:JobRefSeveral different technologies are discussed, here. You have previously mentioned XML and XMP. However, all but one of the above elements are Dublin Core (DC). DC can be expressed in many languages, including XML; visit: http://dublincore.org/documents/dc-ds-xml/ I am now puzzled why you want to use XMP. There is no standard for expressing DC in Ogg, but it should be straightforward to define one. However, DC has very limited structure, so such a standard would very likely use separate VorbisComments. Regards, Martin -- Martin J Leese E-mail: martin.leese stanfordalumni.org Web: http://members.tripod.com/martin_leese/
On 07.06.2012 05:06, Martin Leese wrote:> Oleksij Rempel <bug-track at fisher-privat.net> > >> On 05.06.2012 20:41, Martin Leese wrote: > ... >>> On 6/5/12, Oleksij Rempel wrote: >>> || We need fallowing tags: >>> || creation datetime: seconds and time zone should be included. >>> || source host: it can be name or guid. to organise created files by >>> sources. >>> || keywords,events. >>> || date and person ho did transcription of record. >>> >>> To me, this looks like a job for three or more >>> separate VorbisComments. You might want to >>> choose keys which typically are not used for >>> other things. For example, don't use DATE as >>> this typically stores the date the track was >>> recorded. > >> I do not like the idea of using separate VorbisComments, but i'll keep >> this option open. > > Why not? For the small set of metadata > elements you describe below, to me this still > looks like the way to go. > >> According to this documentation: >> [1] >> http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf >> >> we can use fallowing tags (page 39): >> dc:creator >> dc:date >> dc:description >> dc:identifier >> dc:source >> dc:subject >> xmpBJ:JobRef > > Several different technologies are discussed, > here. You have previously mentioned XML > and XMP. However, all but one of the above > elements are Dublin Core (DC). DC can be > expressed in many languages, including XML; > visit: > http://dublincore.org/documents/dc-ds-xml/ > > I am now puzzled why you want to use XMP. > > There is no standard for expressing DC in > Ogg, but it should be straightforward to define > one. However, DC has very limited structure, > so such a standard would very likely use > separate VorbisComments.Ok, you are right, using existing technology will save time :) please correct me if i'm wrong: 1) datetime in different sources i got different description. At the beginning i thought the DATE tag can be used only with DATE=YYYY-MM-DD According to this: http://wiki.xiph.org/VorbisComment#Date_and_time i can use: YYYY-MM-DDTHH:MM:SS+TS is it correct? 2) keywords. it is not the same as DESCRIPTION. What tag should i use for keywords? In case of dc we usually use dc:subject. 3) DECRIPTIO - clear, no problem. 4) LOCATION, i would use computer guid and host name. Is it ok? or is it "Tantalos resource ID" 5) we also need do some kind of booksmarks at record time. it should know only the time where button "bookmark" was pressed. is "Chapter Extension" correct way to do this? Is it possible to use only one time "CHAPTER001=00:10:00.000"? Usually second time is unknown any way. -- Regards, Oleksij
Oleksij Rempel <bug-track at fisher-privat.net> wrote:> Ok, > you are right, using existing technology will save time :)What has not yet been discussed is what you are streaming *to*. That is to say, what software is going to receive the metadata, and what will it do with it. This is important because VorbisComments can contain pretty much anything you want. Suggestions for field names (keys) and field values are just those, suggestions. Whether suggestions make sense for your particular application depend on what your metadata will be used for.> please correct me if i'm wrong: > 1) datetime > in different sources i got different description. At the beginning i > thought the DATE tag can be used only with DATE=YYYY-MM-DD > According to this: > http://wiki.xiph.org/VorbisComment#Date_and_time > i can use: YYYY-MM-DDTHH:MM:SS+TS > is it correct?Correct, the suggestion is to use the ISO scheme. I don't recall which specific ISO standard this is; perhaps somebody else can remember its number.> 2) keywords. > it is not the same as DESCRIPTION. What tag should i use for keywords? > In case of dc we usually use dc:subject.VorbisComment field names (keys) are case insensitive. However, the convention is to use uppercase, so I would stick with DC:SUBJECT, DC:DESCRIPTION, JOBREF, etc. Note that keys cannot contain the tilde character, ~.> 3) DECRIPTIO - clear, no problem. > > 4) LOCATION, i would use computer guid and host name. Is it ok? > or is it "Tantalos resource ID"Use whatever works best for your application. (I have never understood what a "Tantalos resource ID" actually is. It does not seem to be widely used.) Note that field values must contain only UTF-8.> 5) we also need do some kind of booksmarks at record time. > it should know only the time where button "bookmark" was pressed. > is "Chapter Extension" correct way to do this? Is it possible to use > only one time "CHAPTER001=00:10:00.000"? Usually second time is unknown > any way.The Chapter Extension is intended for indexing, and is expected to have a second time. Instead, why not use BOOKMARK=... ? Regards, Martin -- Martin J Leese E-mail: martin.leese stanfordalumni.org Web: http://members.tripod.com/martin_leese/
Hi, On 08.06.2012 19:14, Martin Leese wrote:> Oleksij Rempel<bug-track at fisher-privat.net> wrote: >> Ok, >> you are right, using existing technology will save time :) > > What has not yet been discussed is what you > are streaming *to*. That is to say, what > software is going to receive the metadata, and > what will it do with it.After file was created they can be used everywhere. This is why i wont integrate as match as possible in existing software. At first plays stay gstreamer and little tools called gnome-sound-recorder. This is also the reason why i do not wont to create comments for my own use. I already started pushing patches, your comment are welcome too: This is first one for DATE tag. https://bugzilla.gnome.org/show_bug.cgi?id=677712> This is important because VorbisComments > can contain pretty much anything you want. > Suggestions for field names (keys) and field > values are just those, suggestions. Whether > suggestions make sense for your particular > application depend on what your metadata will > be used for. >> please correct me if i'm wrong: >> 1) datetime >> in different sources i got different description. At the beginning i >> thought the DATE tag can be used only with DATE=YYYY-MM-DD >> According to this: >> http://wiki.xiph.org/VorbisComment#Date_and_time >> i can use: YYYY-MM-DDTHH:MM:SS+TS >> is it correct? > > Correct, the suggestion is to use the ISO > scheme. I don't recall which specific ISO > standard this is; perhaps somebody else can > remember its number.in progress>> 2) keywords. >> it is not the same as DESCRIPTION. What tag should i use for keywords? >> In case of dc we usually use dc:subject. > > VorbisComment field names (keys) are case > insensitive. However, the convention is to use > uppercase, so I would stick with DC:SUBJECT, > DC:DESCRIPTION, JOBREF, etc. Note that > keys cannot contain the tilde character, ~. > >> 3) DECRIPTIO - clear, no problem. >> >> 4) LOCATION, i would use computer guid and host name. Is it ok? >> or is it "Tantalos resource ID" > > Use whatever works best for your application. > (I have never understood what a "Tantalos > resource ID" actually is. It does not seem to > be widely used.) Note that field values must > contain only UTF-8. > >> 5) we also need do some kind of booksmarks at record time. >> it should know only the time where button "bookmark" was pressed. >> is "Chapter Extension" correct way to do this? Is it possible to use >> only one time "CHAPTER001=00:10:00.000"? Usually second time is unknown >> any way. > > The Chapter Extension is intended for indexing, > and is expected to have a second time. > Instead, why not use BOOKMARK=... ? > > Regards, > Martinthank you! I working on patches now, if i have more questions, i'll ask.