[sXBL] Various issues in the sXBL draft -- section 1

The definition of the term "in error" says that error handling is defined by 
"SVG" (and references SVG 1.1).  It's not clear to me how SVG's error-handling 
rules should be applied to sXBL.  In particular, would partial bindings end up 
being attached?  Would an error in a binding make all bindings coming after it 
in the file not be attached, while those before it are attached?

It's not quite obvious, at first glance, whether the namespace URI for sXBL 
includes the trailing '.' character.  I recomment placing the URI in appropriate 
delimiters recommended for URIs in plaintext (eg '<' and '>') to make this clearer.

The definition of "unless it has already been loaded" presumes a certain amount 
of control over the HTTP implementation used by the sXBL implemenation (for 
example, it presumes that sXBL implementation is able to get the post-redirect 
URI for HTTP redirects).  Furthermore, this definition means that any time a 
reference is made to a resource via an HTTP URI and the server prevents caching 
(fairly common for all sorts of script-generated and CMS-generated things) the 
sXBL implementation MUST make an HTTP request to determine whether the URI might 
now result in a redirect.  This seems rather undesirable.  I'm not quite sure 
what this section is trying to accomplish, but the proposed solution has some 
unpleasant side effects; perhaps there is a better solution?

-Boris