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-3384) ODF 1.2-1 14.6.6<office:dde-source> omits explanation of <text:section> usage



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

Dennis Hamilton commented on OFFICE-3384:
-----------------------------------------

All I'm saying is that 14.6.6 (1) is contradictory of what is needed for <text:section> in that it says the DDE is for connecting tables and (2) fails to describe exactly what is delivered via DDE when it is used with a <text:section>, here or in 5.4.1.

Furthermore, the statement about spreadsheet usage is also bogus, because 14.6.5 and 9.8 do not limit <table:dde-links> to spreadsheet documents.

I think that is pretty specific Patrick.  That I can tell it makes no sense does not obligate me to know what paritcular sensible explanation might be the correct one.  However, ODF 1.1 seems to be a bit more illuminating on the subject.

We don't even say here or elsewhere that the DDE source is expected to deliver XML markup in some form.  This is clearly specific to the DDE source and its documentation and there is no guidance on the subject here.  Consequently, a consumer being able to deal with a paritcular source is going to be implementation-dependent, I betcha.  

The schema for <text:section> allows the markup to be any sequence of text-content instances, including nested <text:section>s, and I have no clue how many cases of text-content, such as change-marks, are meant to be handled if they arrive via the DDE source or by linking.

If it was up to me to fix this, considering that i didn't break it, I would declare it deprecated and implementation-dependent.  If a better solution is not offered by someone having a stake in this feature, I think that may be the appropriate resolution.

> ODF 1.2-1 14.6.6 <office:dde-source> omits explanation of <text:section> usage
> ------------------------------------------------------------------------------
>
>                 Key: OFFICE-3384
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3384
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Text
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Priority: Blocker
>             Fix For: ODF 1.2 CD 06
>
>
> The explanation for <office:dde-source> describes different cases with respect to tables, but makes no mention of how this works for <text:section>.  In fact, it says the element is a container for DDE connection data of tables.  
> The description in ODF 1.1 section 4.4.3 is broader than this.

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