I propose that we also standardize exposing the Graphics Data Definition on the window object, as this will allow the greatest level of re-usability of the templates, including online, SaaS-type applications.
While it would probably be possible for the host application to do the parsing of the meta-tag themselves, I see one scenario, where - if the referenced URL is absolute and the CORS settings are not set correctly, the host application may not be able to download the referenced GDD file, while the hosted template will be able to do so. Because of that, I believe it should be up to the template to establish the API, much in the same way as we expect it to handle calls to play(), stop() or setData().
I propose that we also standardize exposing the Graphics Data Definition on the window object, as this will allow the greatest level of re-usability of the templates, including online, SaaS-type applications.
While it would probably be possible for the host application to do the parsing of the meta-tag themselves, I see one scenario, where - if the referenced URL is absolute and the CORS settings are not set correctly, the host application may not be able to download the referenced GDD file, while the hosted template will be able to do so. Because of that, I believe it should be up to the template to establish the API, much in the same way as we expect it to handle calls to
play()
,stop()
orsetData()
.