- From: David Bruchmann via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Jun 2017 09:28:43 +0000
- To: public-svg-issues@w3.org
The latter proposition would eventually require notation of the mime-type in the svg-element if the code is embedded directly in the html as file-extensions never exist to separate the mime-type. There could be automatic recognition in browsers to omit this requirement but this would show that the new file-extensions are constructions only to satisfy outer (server-, security-)needs and not related to inner functionality. A clear concept here would be nice as the multimedia-files show already that it can be a big mess and a file-extension like avi is just a container and never allows to see any details about the used codex or required software. So even your player / editor can handle those files it doesn't mean that it can handle each of those files, So changing file-extensions or mime-types is quite a big effort and impact and should be considered thoughtfully. Therefore the suggestion from @nikosandronikos is perhaps still the best even it needs a bit more explanation to understand how dynamic and static svgs can be treated different. -- GitHub Notification of comment by DavidBruchmann Please view or discuss this issue at https://github.com/w3c/svgwg/issues/266#issuecomment-310618970 using your GitHub account
Received on Friday, 23 June 2017 09:28:49 UTC