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-3385) ODF 1.2-1 5.4.1<text:section> Fails to deal with modified/unmodified limitations

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

Michael Brauer commented on OFFICE-3385:

The sentence in question can be found in the ODF 1.2 CD05 editor revision 2 draft.

The resolution of this particular issue has to be seen context of OFFICE-3458, which cleans up the language regarding sections in general.

Regarding the bottom line above: We should not say the "the following markup is derived by access". It is not really the markup that is derived from another source. It is the content of the section that is derived, and that content is stored as markup. Also, says "is" is not correct, since this could be read as that the section content is updated while a document is loaded. That is not the case.  But in general, the bottom line is okay.

> ODF 1.2-1 5.4.1 <text:section> Fails to deal with modified/unmodified limitations
> ---------------------------------------------------------------------------------
>                 Key: OFFICE-3385
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3385
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Public Review
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Assignee: Patrick Durusau
>             Fix For: ODF 1.2 CD 06
> The <text:section> is allowed to contain any sequence of element-content instances.  The text suggests that this sequence of child elements is obtained from some source.  The presence of the text permits a consumer to interpret the document without re-accessing the source (or even when the source is not accessible).
> There is also the prospect, not described in ODF 1.2, but explicitly accounted for in ODF 1.1 (and by the presence of optional protection attributes on the <text:section> element) that the content obtained from the source has been modifed by the producer.
> What is not clear here or in ODF 1.1 is whether certain element content is acceptable from a source or must always be a result of modification of the sourced markup.  For example, what does it mean for change-marks to be obtained in the markup from a source?  a <text:section> element? Any <text:*-ref> elements?  Any bookmarks and index marks of various kinds?  Any already-used xml:id, etc.?
> There seems to need to be considerable qualification involved in what is obtained from a source and what may have resulted from modification of source-obtained markup.

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]