-
Type:
Bug
-
Status: Applied
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: ODF 1.2 CD 05
-
Fix Version/s: ODF 1.2 CD 06
-
Component/s: Part 3 (Schema) [1.2: 1], Text
-
Labels:None
-
Resolution:
The schema shows all.
The definition of 5.4.2 is as follows:
"""
The <text:section-source> element indicates that an enclosed section is a linked section.
"""
But all <text:section> elements are linked sections and/or the presence of the DDE element also shows that.
WHAT I THINK AND NEEDS TO BE CONFIRMED:
The difference with <text:section-source> is that if it has a text:section-name attribute, that is the name of a section that is a source for the <text:section> that is the parent of the <text:section-source> element.
Now, because the xlink:href can beused instead of the text:section-name to to a fragment having an xml:id that matches, this is not the only way to gain section text from the same XML document and from a different XML document in the package. So there is no actual requirement that the link is to an "external" document or one that is not very close by.
ABOUT xlink:show="embed" PROBLEMS
My understanding of that default/only value is that this means the included content is to be rendered as if it were there in place of the <text:section-source> element – that is how [XLink] defines the xlink:show="embed" case.
What we really want, here, is that it is rendered in place of the <text:section> element. Or, put differently, it is cached in the <text:section> element and it is the cache that is rendered.
IS THAT IT? WE NEED TO SAY SO.
Then section 5.4.1 needs to be adjusted to be more clear about what the cases are, perhaps via OFFICE-3386. This should be discussed along with OFFICE-3386.