Hi Ian,

Ian Hickson a écrit :
On Wed, 6 Dec 2006, Cyril Concolato wrote:
  
In Section 3.1, "Loading External Resources", the specification says:

"Such resource sharing is limited to resources loaded by a document, its 
binding documents, its scripts, and its style sheets."

Make this sentence a normative statement
    

Done.


  
The sentence from the XBL specification "Nested documents and images do 
not share resources with each other or with their container document." 
is in conflict with the notion of primary document in SVG see 
"Externally referenced documents" 
[http://www.w3.org/TR/SVGMobile12/linking.html#externalReferences] This 
means that an SVG player would have to behave differently if it is also 
XBL-compliant.
    

As far as I can tell, the statement in the XBL spec is the same as in the 
SVG spec. 
The second sentence is wrong for SVG documents. The SVG specification explains the opposite in http://www.w3.org/TR/SVGMobile12/linking.html#externalReferences.
"The conceptual model is that each resource document is loaded only once; if the same resource document is referenced multiple times directly or indirectly by the same primary document, that resource document is only retrieved and processed one time."
But in any case, the XBL spec's negative statement is not 
normative, it's just descriptive 
If it is just descriptive, since it is wrong, please remove it.
(and a consequence of the previous 
statement, which, as requested above, is now normative).
  
Actually, I think I was wrong when I asked that. I'll explain why. The term "already been loaded" appears three times in the specification and every time about "binding documents". This is correct because the XBL spec cannot specify how resources are handled (shared or not) by other languages. So I would propose to not use the word 'resource' but instead use 'binding document' in that whole section and remove the sentence "Such resource sharing must be limited to resources loaded by a document, its binding documents, its scripts, and its style sheets."

  
The XBL specification should not impose constraints on how 
documents/resources used by other non-XBL documents should be handled.  
The example with 'iframe' seems contradictory with the general rule. Is 
this an exception? What are the other exceptions? What about 
<xhtml:object> elements in CDF cases ?
    

I don't understand why the <iframe> example looks like an exception. It 
isn't intended to look like one.

  
The specification says: "For example, if a document uses a binding document, and its style sheets use that binding document, the same binding document instance will be used for both cases. However, if that document contains an iframe whose document uses the same binding document, a new instance will be used: the binding document instance from the outer document is not reused."
So in the general case (used in style sheets, referenced with PI, ...) the Document is reused but when it is referenced inside an iframe it is not. That looks like an exception. But I may understand that you mean that when a presentation is made of multiple documents being rendered independently (like in Compound Document by Reference (html:iframe, svg:foreignObject, html:object)), then they do not share the same set of bindings. Am I correct ?

Cyril


Reply via email to