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-3458) ODF 1.2 CD05-1 5.4.2<text:section-source> incompletely defined

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

Dennis Hamilton commented on OFFICE-3458:

Ach Himmel!!!

You're right, Michael, I read the schema incorrectly.  No need to change it although the second form you offer is more in-the-face.

That solves the problem of how there can be a section that includes other sections by reference that doesn't have to be included from anything.


Now we just need to be clear in the description that one way a section can link to another section is by its name in a <text:section-source> as well as by an xlink:href.

> ODF 1.2 CD05-1 5.4.2 <text:section-source> incompletely defined
> ---------------------------------------------------------------
>                 Key: OFFICE-3458
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3458
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Part 1 (Schema), Text
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Assignee: Michael Brauer
>             Fix For: ODF 1.2 CD 06
> The schema shows all.
> The definition of 5.4.2 is as follows:
> """
> The <text:section-source> element indicates that an enclosed section is a linked section.
> """
> But all <text:section> elements are linked sections and/or the presence of the DDE element also shows that.
> The *difference* with <text:section-source> is that if it has a text:section-name attribute, that is the name of a section that is a source for the <text:section> that is the parent of the <text:section-source> element.
> Now, because the xlink:href can beused instead of the text:section-name to to a fragment having an xml:id that matches, this is not the only way to gain section text from the same XML document and from a different XML document in the package.   So there is no actual requirement that the link is to an "external" document or one that is not very close by.
> ABOUT xlink:show="embed" PROBLEMS
> My understanding of that default/only value is that this means the included content is to be rendered as if it were there in place of the <text:section-source> element -- that is how [XLink] defines the xlink:show="embed" case.
> What we really want, here, is that it is rendered in place of the <text:section> element.  Or, put differently, it is cached *in* the <text:section> element and it is the cache that is rendered.
> Then section 5.4.1 needs to be adjusted to be more clear about what the cases are, perhaps via OFFICE-3386.  This should be discussed along with OFFICE-3386.

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]