Robert Sayre wrote:
Bill de h�ra wrote:
No, the thing is these two are similar problems structurally insofar as processing directives from the Atom layer are bleeding into the content.
No. xml:base doesn't mean anything in (x)html, ever, so there is no need for a structural measure. Additional spec text wouldn't be adding requirements, just spelling out what's implied by our references.
Aside from what Anne said, I just scanned the XML Base spec and can't find anything scope wrt to child elements and attributes. In particular this (quoted previously here):
[[[
The deployment of XML Base is through normative reference by new specifications, for example XLink and the XML Infoset. Applications and specifications built upon these new technologies will natively support XML Base. The behavior of xml:base attributes in applications based on specifications that do not have direct or indirect normative reference to XML Base is undefined.
]]]
had nothing to say about scope. What is implied by our references appears to be it xml:base either evaluates to all the children under which it's declared or the behavior is undefined because the spec didn't define xml:base usage.
So I guess my question is - how is scoping xml:base to not apply within atom:content where type is xhtml not profiling XML Base?
cheers Bill
