[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (OFFICE-3465) ODF CD05-1 10.4.4<draw:image> use of <office:binary-data> unimplementable
[ http://tools.oasis-open.org/issues/browse/OFFICE-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21957#action_21957 ] Dennis Hamilton commented on OFFICE-3465: ----------------------------------------- I want to come back to the specific ase of a <draw:image> with an <office:binary-data> element, the subject of this issue. 1. I assume that if a consumer does not give preference to this <draw:image> element, then it is expected to choose from a later one in the sequence of <draw:frame> children. 2. If the consumer does give preference, or has no choice but to use the <draw:image> element, assuming it is able to accomplish that is some mannery, my next question is: 3. What is the purpose of any draw-text markup following the <office:binary-data> element in the <draw:image> element, and what is a consumer expected to do with it? (this is a general question about draw-text markup in drawing elements, but I wonder specifically what does it have to do with the image? > ODF CD05-1 10.4.4 <draw:image> use of <office:binary-data> unimplementable > -------------------------------------------------------------------------- > > Key: OFFICE-3465 > URL: http://tools.oasis-open.org/issues/browse/OFFICE-3465 > Project: OASIS Open Document Format for Office Applications (OpenDocument) TC > Issue Type: Bug > Components: Graphics, Part 1 (Schema) > Affects Versions: ODF 1.2 CD 05 > Reporter: Dennis Hamilton > Assignee: Patrick Durusau > Priority: Blocker > Fix For: ODF 1.2 CD 06 > > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]