Comment 3 for bug 776505

The (Published)Application.tos_url now simply references the tos_url from it's published json representation - so it is no longer tied to devportal itself. It is also rendered by an sca url/view now. That said, other aspects are. If I were to work on this today for a /api/2.1/ I'd check the following:

 * The exported tos_url includes a devportal-specific application id - this should be switched to depend only on the sca published app id (currently sca needs to look up devportal.Application objects to serve the request).
 * When a devportal app is published to sca, the license text should be included, so that sca can render the license without devportal.
 * The embedded video urls point at devportal - these should instead point at sca so that USC isn't requesting data from devportal at all, just published app data from sca - this includes the app-id in that url, which currently refers to a devportal app object, rather than the published sca object.
 * Finally, the available apps json should use the "id" attribute of the sca.published application, rather than the devportal app id.

With those done, the sca api would be completely independent of devportal data, allowing the service to run separately (ie. we don't have the same server serving high-volume available app urls, as well as servicing uploads from devs uploading packages) with devportal to publish data via an API call to sca.