[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=21995#action_21995 ]
Dennis Hamilton commented on OFFICE-3385:
-----------------------------------------
I had to think about "It is the content of the section that is derived, and that content is stored as markup"
I am all right with that. It is the markup we are describing of course, since we are talking about what is in the persistent document that is produced.
When there is a <text:section-source> with xlink:href, the xlink:show="embed" is the default. There is no xlink:actuate, default or otherwise. It appears that when the link is followed and the linked resource retrieved, what it provides is shown ass the rendering of the element (in our case, the <text:section> element, not the <text:section-source> element). It is correct that there is no specified onLoad behavior.
I think what we want to say is that the markup that is present in the document reflects that last markup that was created or derived by the producer.
It also appears we want to say that the entire process of obtaining content, presenting it, and creating markup of it is implementation-dependent ?
QUESTION: I notice that there can be both an xlink:href (and its companions) and a text:section-name attribute on the <text:section-source> element. I would have thought that they would be a mutually exclusive optional choice.
REQUEST: When you are proposing changes to text that exists in a CD05 editor revision, please say so. Otherwise, I must assume you are refeencing CD05, the listed affects version.
> 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]