JS - inside or out?

Following up on a comment from the meeting on Monday:

>Ivan: "There is one big choice to be made - and this is whether the javascript that does the heavy lifting
> - is it something deployed as part of the publication, or external to a publication.
>

I feel very strongly that this isn’t something we should be mandating either way.

If a given author wishes to include JS inside their publication to handle pagination or navigation – they should be able to do so.  However, we certainly don’t want to require that, so we need a model that also allows for UA-provided navigation.

Leonard