[PROPOSAL] Use full asset URLs instead of relative paths.

If you include HTML into a different site w/ a relative path to javascript it won't be loaded (since it doesn't exists on the local server).

I'm up for other options for being able to generate the absolute URL to the javascript assets, but I couldn't find anything that wouldn't necessitate requiring the entire routing framework wholesale into all our viewers.
My concern wrt https is if I have a site under ssl (say a library.stanford.edu blog that somebody is viewing through https) and our Embed representation attempts to load a javascrpt file from our embed service under http, that would throw security messages in the browser (this is all speculative) about trying to load insecure content.

If we default to loading all of our assets through https then there would be no security issues regardless if the consumer was displaying our embed via http or https.