OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (OFFICE-1538) Editor Note: Section17.913.38 <text:section-source> (xlink:href)



    [ http://tools.oasis-open.org/issues/browse/OFFICE-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486#action_13486 ] 

Patrick Durusau commented on OFFICE-1538:
-----------------------------------------

Michael, since we have been back and forth on this one, here is a clean copy of the complete suggested text for <draw:obect> and <draw:object-ole>. I will apply it my Weds and ship the file to you.

9.4.5.2 <draw:object>

The <draw:object> element represents objects that have an OpenDocument representation.

Objects with an OpenDocument representation can be: 

1) Contained in the same package as a document, in which case it is contained in folder within the package rather than in the package root. The xlink:href attribute of this element references that folder. 

2) Contained in a separate OpenDocument document instance. The xlink:href attribute of this element references that document's package. 

3) Contained in a child <office:document> element of this element. 

4) Contained in a child <math:math> element of this element. 

A <draw:object> shall use only one method of containment for any instance of that element. 

Note: Objects with OpenDocument representations can appear in an OpenDocument document instance or be embedded in such documents. Embedding results in the object being stored in a folder in the package rather than as part of the OpenDocument document instance. 

(Note: I will make that a bulletedList but also change 9.4.5.1 to say there are objects with OpenDocument representations and those that don't have OpenDocument representations. Yes?)

9.4.5.3 <draw:object-ole>

The <draw:object-ole> element represents objects that do not have an OpenDocument Representation.

Objects without an OpenDocument representation can be: 

1) Contained in the same package as a document, in which case it is contained in a file within the package. The xlink:href attribute of this element references that file. 

2) Contained in a separate file. The xlink:href attribute of this element references that file. 

3) Contained in a child <office:binary-data> element of this element. 

A <draw:object-ole> shall use only one method of containment for any instance of that element. 

Please copy and edit this text if you have any changes.


> Editor Note: Section 17.913.38 <text:section-source> (xlink:href)
> -----------------------------------------------------------------
>
>                 Key: OFFICE-1538
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1538
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.2
>            Reporter: Robert Weir 
>            Assignee: Patrick Durusau
>            Priority: Blocker
>             Fix For: ODF 1.2
>
>
> Transcribed from ODF_Revised_Editorial_Notes_27May2009.odt
> Original author: Patrick Durusau
> Section 17.913.38 <text:section-source> (xlink:href)
> Ed. Note <draw:object> and <draw:object-ole> state: 
> The xlink:href attribute links to the object representation, as follows:
> For objects that have an XML representation, the link references the sub package of the object. The object is contained within this sub page exactly as it would as it is a document of its own.
> For objects that do not have an XML representation, the link references a sub stream of the package that contains the binary representation of the object.
> Application that support objects should support linking to objects that are contained within the same package. They may also support linking to object located outside the package.
> We need to define how to store embedded objects. Here is not right. Perhaps under the package definition? 
> Michael's response in December was that yes, we need to specify how to store embedded objects. 

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