It's a matter of debate as to whether using <gap> both for (timed) gaps
in a recording and (not timed) gaps on a source is too sharp a swing of
However, it seems perfectly reasonable to me to add gap to att.timed
while we have the debate! I think the class should not be populated
unless you load the spoken module, (that's true for model classes
anyway) but will check. Far preferable to changing or misusing the
datatype of @extent certainly, and less work than adding a completely
new <timedGap> element which seem like the only alternatives.
Thanks for the very helpful suggestion -- keep them rolling in.
Stefan Majewski wrote:
> Dear all,
> as we currently revise our local customisation of P5 to live up to the
> current release of the guidelines, unresolved questions keep popping up.
> I hope some of them are interesting for some of you.
> Now to the issue: Some parts of transcribed audio files may be too noisy
> to be properly transcribed. We currently use <gap>s for this purpose, as
> the sample value 'inaudible' for <gap>'s @reason indicates that it might
> be an appropriate choice. What we are currently not sure of is how to
> indicate the length of the missing stretch. We think of either abusing
> @extent with a time-value and therefore changing the datatype of extent,
> such that to something one would usually find in a @dur attribute, or
> add the <gap> to 'att.duration' or 'att.duration.w3c'. Again, this might
> be something someone could expect anyway, when using the module spoken.
> A brief illustration:
> <gap reason="inaudible" extent="PT01M23S" unit="duration"/>
> <gap reason="inaudible" dur="PT01M23S"/>
> What do you think?