- From: Rob Smith via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Jan 2019 14:39:09 +0000
- To: public-sdwig@w3.org
Thanks for your clarification. If I've understood correctly, your concerns are: 1. Errors in the [WebVMT media url]( http://w3c.github.io/sdw/proposals/geotagging/webvmt/#dfn-webvmt-media-url-setting) cannot be easily identified, so this information may be unreliable. 1. Web links should not be bidirectional, e.g. the image should not contain a link to the HTML. Firstly, warnings could be displayed by the WebVMT engine in the rendered webpage, e.g. by displaying text in the map element instead of the rendered map. Is there a precedent for displaying errors or warnings within the browser, e.g. broken image link? Secondly, to clarify my webpage-image analogy, the VMT file contains a URL to the media file in the same way as an HTML file contains a URL to the image file. I can't see a bidirectional link - there's no link from the VMT to the HTML. Have I misunderstood? `HTML -> image` `VMT -> media` While the HTML use case is important for WebVMT, it's not the _only_ use case. The VMT file should contain sufficient data for all use cases, and the purpose of the WebVMT media block is to identify the linked media - particularly in non-HTML use cases, e.g. for the [mobile demo](http://webvmt.org/demos#mobile). In the HTML use case, some of the data can be _duplicated_ into the HTML file, which is a _product_ of the VMT source data, e.g. by a PHP script. If the linked media URL is not in the VMT file, where would that information be recorded? -- GitHub Notification of comment by rjksmith Please view or discuss this issue at https://github.com/w3c/sdw/issues/1107#issuecomment-451955256 using your GitHub account
Received on Monday, 7 January 2019 14:39:12 UTC