Uploaded image for project: 'OASIS Open Document Format for Office Applications (OpenDocument) TC'
  1. OASIS Open Document Format for Office Applications (OpenDocument) TC
  2. OFFICE-3458

ODF 1.2 CD05-1 5.4.2 <text:section-source> incompletely defined

    XMLWordPrintable

    Details

    • 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 1 (Schema), Text
    • Labels:
      None
    • Resolution:
      Hide

      Adapt the 2nd paragraph of 5.4.1 <text:section> General to:

      Sections additionally may specify formatting properties for a region of text.**

      The section content may be linked to an external data source.

      Adapt description of 19.863 text:section-name to:

      The text:section-name attribute specifies a section to which a section is linked by its name. The referenced section is looked for either in the document referenced by the xlink:href attribute, or in the same document if the xlink:href attribute is not present.

      If the text:section-name attribute is not present, the section is linked to the entire document referenced by the xlink:href attribute, unless the xlink:href attribute contains a fragment identifier. If neither the xlink:href attribute nor the text:section-name attribute is present, the <text:section-source> element shall be ignored.

      Adapt description of 19.912.37 xlink:href for <text:section-source> to:


      The xlink:href attribute specifies the document or document fragment to which a section is linked. If the IRI contains a fragment identifier, and if the referenced document is an OpenDocument document, the fragment identifier should be interpreted as the name of a section to which a section is linked. A fragment identifier should be ignored if a text:section-source attribute is present.


      Show
      Adapt the 2nd paragraph of 5.4.1 <text:section> General to: Sections additionally may specify formatting properties for a region of text.** The section content may be linked to an external data source. Adapt description of 19.863 text:section-name to: The text:section-name attribute specifies a section to which a section is linked by its name. The referenced section is looked for either in the document referenced by the xlink:href attribute, or in the same document if the xlink:href attribute is not present. If the text:section-name attribute is not present, the section is linked to the entire document referenced by the xlink:href attribute, unless the xlink:href attribute contains a fragment identifier. If neither the xlink:href attribute nor the text:section-name attribute is present, the <text:section-source> element shall be ignored. Adapt description of 19.912.37 xlink:href for <text:section-source> to: The xlink:href attribute specifies the document or document fragment to which a section is linked. If the IRI contains a fragment identifier, and if the referenced document is an OpenDocument document, the fragment identifier should be interpreted as the name of a section to which a section is linked. A fragment identifier should be ignored if a text:section-source attribute is present.

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Patrick Patrick Durusau
              Reporter:
              orcmid Dennis Hamilton (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: