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-1344) Public Comment:<text:sequence> behaviour (ODF all versions)

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

Patrick Durusau commented on OFFICE-1344:


Let me say your suggestion back to you and see what you think. I like your revised text but I think it is mixing declaration of the element with an example of its use. Both are legitimate but perhaps better to tease them apart, thus:

A <text:sequence> element specifies a sequence field.

A sequence field changes the value of a sequence variable by a specified formula and displays the changed value of the sequence variable in a specified format. 

Note: Sequence variables and fields are used to number repeating document elements such as pages, tables or images. In such cases, the formula could be: "sequenceVariableName + 1."  A sequence variable can be set to a certain value or not changed at all.
I am uncertain about:

"A sequence variable is referenced by the text:name attribute that appears on the element defining the sequence variable."

Mostly because when we define text:name for <text:sequence> we say: "It shall match the name of a sequence variable already declared by a preceding <text:sequence-decl>.element" The language you propose leaves the reader wondering if this element, <text:sequence> is defining the sequence variable or is it referring to the sequence variable. The language in 18.837.15 make that clear. 

Yes, yes, it does mean that the reader must look at the attributes to understand the element. But that is the case with most if all not all elements. The benefit is that we can have a consistent definition for attributes and know that when we change it, where to look for all cases where that change may cause problems. 

"The formula is given by its attribute text:formula. The display format is given by its attributes text:num-format and text:num-letter-sync." Ditto for these statements as well. 

> Public Comment: <text:sequence> behaviour (ODF all versions)
> ------------------------------------------------------------
>                 Key: OFFICE-1344
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1344
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Text
>    Affects Versions: ODF 1.0, ODF 1.0 (second edition), ODF 1.1, ODF 1.2
>            Reporter: Robert Weir 
>            Assignee: Patrick Durusau
>             Fix For: ODF 1.2
> Copied from office-comment list
> Original author: "Alex Brown" <alexb@griffinbrown.co.uk> 
> Original date: 5 Mar 2009 11:16:01 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/200903/msg00068.html

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]