Stay on the world when transforming coords.

Instead of a transform that results in +/- Infinity northing, we can constrain the results to be within the world bounds.
Fix DOM API call to setAttributeNS()
Gets the right url (#608 / 3)
Merge pull request #683 from sbrunner/wmtscapabilities-right-url

Gets the right url (#608 / 3)
call stopObserving before setting img.src to blank image as well
Merge pull request #660 from m-click/fix-setAttributeNS

Fix DOM API call to setAttributeNS()
Merge pull request #690 from pgiraud/client_zoom

call stopObserving before setting img.src to blank image as well
Support for multiple resource urls

With this change, createLayer generates url arrays for both KVP and REST
encoding if multiple resource urls are provided. To make this work, the
WMTSCapabilities format got a new resourceUrls property, because
previously only the first resourceUrl for a format was stored.
Multiple URLs also for unconstrained GetTile resources
Fixing typo

Thanks @sbrunner for catching this. That's what I got from making
last-minute changes before committing without testing again.
Addressing @sbrunner's review comment
Merge pull request #695 from ahocevar/wmts

Support for multiple resource urls for WMTS. r=@sbrunner
Declaring undeclared variable
Applying VersionedOGC pattern to WMSDescribeLayer format

The WMSDescribeLayer format currently differs from other formats that
inhreit from VersionedOGC by having an array instead of an object as return
type. This especially bad since the VersionedOGC superclass sets a version
property on the array. With this change, the WMSDescribeLayer format will
also be compatible with GeoServer's new JSON response type for
DescribeLayer - see
http://sourceforge.net/mailarchive/message.php?msg_id=29912776.

Another change included here is the removal of the WMSDescribeLayer
format's getVersion hack, which was replaced by a generic fallback to less
generic parsers, e.g. from a v1_1_1 parser to a v1_1 parser if v1_1_1 is
not implemented.
Adding TODO, as suggested by @bartvde
Less intrusive version fallback
Testing backwards compatibility
Do not provide an 1.1 parser
Merge pull request #697 from ahocevar/describelayer

Applying VersionedOGC pattern to WMSDescribeLayer format. r=@bartvde
Use protocol-relative URL for Bing metadata.

The [URI standard](http://tools.ietf.org/html/rfc3986#section-4.2) allows for URI without a scheme.  Where http is used to load the app, using a schemeless URL for the Bing metadata loads a script using http - and the same goes for https.