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-3465

ODF CD05-1 10.4.4 <draw:image> use of <office:binary-data> unimplementable

    XMLWordPrintable

    Details

    • Resolution:
      Hide

      From 10.4.4 <draw:image> remove:

      If a user chooses to embed the image in the document with the <office:binary-data> element, the only attribute available is: draw:filter-name.
      Note: The method chosen to represent the image changes the attributes available for this element.

      Update of 10/11:

      Add this note to 10.4.5

      Note: The image data may be in an arbitrary data format. Consumers have to analyze the image data to determine the data format that is used.

      Show
      From 10.4.4 <draw:image> remove: If a user chooses to embed the image in the document with the <office:binary-data> element, the only attribute available is: draw:filter-name. Note: The method chosen to represent the image changes the attributes available for this element. Update of 10/11: Add this note to 10.4.5 Note: The image data may be in an arbitrary data format. Consumers have to analyze the image data to determine the data format that is used.

      Description

      See similar issue OFFICE-3463

      In 10.4.4, the image (however obtained) is apparently parked in the <office:binary-data> and the only allowed attribute on <draw:image> is the <draw:filter-name>. (There can be no xlink:href and the defaults for the other xlink attributes are apparently not relevant.)

      All that 10.4.5 <office:binary-data> provides base64binary of the image, but we are given no clue what the represented image format is.

      Although there is a "should" about [SVG] and [PNG] but no indication how to tell what the <office:binary-data> represents (and if this case is relevant to [SVG], but if not, how is the SVG included in the element, or is that not provided for?)

      It is unclear how there is a choice to represent the image any other way than in binary data, unless the alternative is always with xlink:href and it is not permitted to cache the retrieved image in the <draw:image> element (because it would then not be refreshable).

      This is seriously underspecified as well as not being interoperably implementable from the information provided.

      Although ODF 1.1:9.3.2 is not much more specific. There, the XLink information is described as not necessary when the <office:binary-data> is present, but it is not described as forbidden.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: