11.07.2015 Views

acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSIONo The second in<strong>for</strong>mation item (segment identifier / SID) is mandatory in eachsubfield and uniquely numbers the segment to which the following items in thesubfield apply. There is no requirement that the segments be numberedsequentially in sequential subfields. The SID may contain up to 6 digits, but thenumber of segments identified in the field (the total number of recurringsubfields) is limited to 600,000.o The third in<strong>for</strong>mation item (track number list / TRK) is mandatory if TRC inField 11.012: Physical media object / PMO or CHC of Field 11.014: Codec /CDCis greater than one and lists all tracks or channels on the recording to whichthe segment identifier applies. No value in this list should be greater than thevalue of PMO_TRC or CDC_CHC, whichever applies. For example, in thecase of a two-track stereo recording where both tracks contain a segment at thesame start and end times, this list will be “1” and “2”o The fourth in<strong>for</strong>mation item (relative start time / RST) is a mandatory integer <strong>for</strong>every segment identified and indicates in microseconds the time of the start ofthe segment relative to the absolute beginning of the voice recording. The itemcan contain up to 11 digits, meaning that the segment can start at any time withinthe 28 hour voice recording. Because each segment is expected to be dominatedby the primary subject of this Type-11 record, it is expected that segments fromthe same track of the audio object identified in Field 11.003: Audio objectdescriptor code /AOD not will overlap, meaning that the RST of a segment isnot expected to occur earlier than the end of a previous segment from the sametrack, although this is not prohibited. In multiple ANSI/<strong>NIST</strong>-ITL transactionsinvolving multiple speakers using the same voice data record, segments on thesame track across the transactions may overlap during periods of voice collision.If the Type-11 record refers to an analog recording, the method of determiningthe start time shall be given in the comment item of this subfield. See Section7.7.2.6 Time measured in microseconds.o The fifth in<strong>for</strong>mation item (relative end time / RET) is mandatory <strong>for</strong> everysegment and indicates in microseconds the time of the end of the segmentrelative to the absolute beginning of the voice recording. The item can contain upto 11 digits, meaning that the segment can end at any time within the 28 hourvoice recording. As with the RST, it is expected that segments from the subjectof this Type-11 record will not overlap, although this is not prohibited. SeeSection 7.7.2.6 Time measured in microseconds.o The sixth in<strong>for</strong>mation item (comments / COM) is an optional unrestricted textstring of a maximum of 10,000 characters in length that allows <strong>for</strong> comments ofany type to be made on a segment. This comment item could contain word- orphonic level transcriptions, language translations or security classificationmarkings, as specified in exchange agreements.8.11.21 Field 11.031: Segment recording time stamp / TMEThis optional field contains subfields, each referring to a segment identified in either theMay, 2013 DRAFT VERSION UPDATE 2013 Page 255

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!