+1 to this suggestion of using clipBegin and clipEnd. It's also coincident with other specifications that do this, most recently to my knowledge the TTML2 <audio><https://www.w3.org/TR/ttml2/#embedded-content-vocabulary-audio> element, which uses the exact same syntax.
Nigel
From: "Xu, Jeff" <zheng.xu@rakuten.com>
Date: Friday, 16 October 2020 at 18:07
To: Marisa DeMeglio <marisa.demeglio@gmail.com>, W3C Synchronized Multimedia for Publications CG <public-sync-media-pub@w3.org>
Subject: Re: Media fragments vs media object attributes
Resent from: <public-sync-media-pub@w3.org>
Resent date: Friday, 16 October 2020 at 18:07
I vote for <audio src="file.mp3" clipBegin="0" clipEnd="30"/>
I don't think web browser(/media player) does support URL like this "file.mp3#t=0,30" if my memory does not mess up 🙂
So, with format of "file.mp3#t=0,30" the consumer will always need to parse src to make sure sending correct URL to media player.
Cheers,
Zheng(Jeff) Xu
Senior Mobile Application Engineer
Toronto, Canada (GMT-5)
[cid:image001.jpg@01D6AB77.55236810]
www.kobo.com<http://www.kobo.com/>
________________________________
From: Marisa DeMeglio <marisa.demeglio@gmail.com>
Sent: Friday, October 16, 2020 12:55 PM
To: W3C Synchronized Multimedia for Publications CG <public-sync-media-pub@w3.org>
Subject: Media fragments vs media object attributes
Hi all,
I would like to hear from you on this issue:
https://github.com/w3c/sync-media-pub/issues/30
Please chime in on the github issue tracker if you have thoughts and opinions about this. It relates to the new draft I sent out last month:
https://raw.githack.com/w3c/sync-media-pub/wip/docs/new/sync-media.html
Thanks
Marisa
