Re: WebVMT: TPAC Document Review & Breakout Session

Nigel,

Thanks for your comments.

The MAP block partially initialises the metadata rendering area and has a strong parallel with WebVTT's REGION block, though it's different in many ways.

The drawing primitives are based on SVG, as you rightly say, but there are significant differences. For instance, WebVMT includes the ‘path’ concept to handle the distance travelled by a moving object, which is integrated with the move and line primitives, so these are related to real-world events.

I believe that the inclusion of the whole of SVG verbatim would be unwise, as it was designed for a different purpose. My approach is to cherry-pick components for inclusion, which allows scope to modify them without being hampered by legacy issues, and also keeps the format very lightweight. There will certainly be more elements included over time, and section 6.1 aims to identify those missing elements. 

I’d be interested to see an example of what you think is missing from section 4, so I can address this.

Rob Smith

Away Team
www.awayteam.co.uk <http://www.awayteam.co.uk/>
> On 16 Oct 2018, at 09:05, Nigel Megitt <nigel.megitt@bbc.co.uk> wrote:
> 
> Hi Rob,
> 
> Thanks for forwarding this. It looks as though there is a set of metadata with some kind of schema; I see that you have things like MAP with [lat, lng] and rad data, then things like panto, zoom, moveto, lineto, circle, animate, and maybe others. Some of those are described in §4 but others look a lot like drawing primitives and are not listed – would it make sense to be able to specify SVG within the file format?
> 
> Kind regards,
> 
> Nigel
> 
> 
> From: Rob Smith <rob.smith@awayteam.co.uk <mailto:rob.smith@awayteam.co.uk>>
> Date: Monday, 15 October 2018 at 17:22
> To: "public-web-and-tv@w3.org <mailto:public-web-and-tv@w3.org>" <public-web-and-tv@w3.org <mailto:public-web-and-tv@w3.org>>
> Subject: WebVMT: TPAC Document Review & Breakout Session
> Resent-From: <public-web-and-tv@w3.org <mailto:public-web-and-tv@w3.org>>
> Resent-Date: Monday, 15 October 2018 at 17:22
> 
>> Following up on the Media Timed Events telecon today:
>> 
>> 1. The Web Video Map Tracks (WebVMT) Editor’s Draft was updated last week with new data model [1] and syntax [2] sections to enable implementation by early adopters, and input from Media Timed Events TF is welcomed. This document will be reviewed in the Spatial Data on the Web IG meeting [3] at TPAC Lyon on Monday 22 October.
>> 
>> 2. As previously posted, a breakout session [4] has been proposed at the TPAC Plenary on Wednesday 24 October entitled ‘Video Metadata Cue Support Including Geolocation (WebVMT)' to discuss how best to handle video metadata cues for maps, e.g. threaded through VTTCue or using a new VMTCue.
>> 
>> Many thanks, and I look forward to meeting up with you in Lyons.
>> 
>> Rob Smith
>> 
>> Away Team
>> www.awayteam.co.uk <http://www.awayteam.co.uk/>
>> 
>> [1] https://w3c.github.io/sdw/proposals/geotagging/webvmt/#datamodel <https://w3c.github.io/sdw/proposals/geotagging/webvmt/#datamodel>
>> [2] https://w3c.github.io/sdw/proposals/geotagging/webvmt/#syntax <https://w3c.github.io/sdw/proposals/geotagging/webvmt/#syntax>
>> [3] https://www.w3.org/2017/sdwig/meetings/f2f-3.html <https://www.w3.org/2017/sdwig/meetings/f2f-3.html>
>> [4] https://www.w3.org/wiki/TPAC/2018/SessionIdeas#Video_Metadata_Cue_Support_Including_Geolocation_.28WebVMT.29 <https://www.w3.org/wiki/TPAC/2018/SessionIdeas#Video_Metadata_Cue_Support_Including_Geolocation_.28WebVMT.29>
>> 
> 
> 
>  
> ----------------------------
> 
> http://www.bbc.co.uk <http://www.bbc.co.uk/>
> This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
> ---------------------