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: Re: [office] Continued Lists

As we started to discuss lists, allow me to continue this old thread.

In ODF 1.2 it is not mentioned that the attribute @text:continue-list is
only allowed on the root element, see
Although it makes sense and was suggested that way.

A further question regarding the numbering of by @text:continue-list
connected lists of different style, which was already asked by Cherie
and answered https://tools.oasis-open.org/issues/browse/OFFICE-3558,
which might as well find its way into the specification.

Another defect seems that
made it to the <text:number-paragraph>
But IMHO <text:number-paragraph> should be deprecated anyway, as they
are not adding a feature to ODF, only further complexity.
Similar to
which was replaced by

Knowing what I know now, I am longing for an List ID attribute, instead
of references.
Following scenario: There is a list consistent of three separated parts
A, B, C in the document. C is pointing to B and B is pointing to A.
If we are moving part A in-between B and C, we have to update all three
references, while a document wide List ID at the list, list-item or
paragraph (which is the finally property holder anyway) would be far easier.

Is there a certain way of deprecating features in OASIS specification?

Best regards,

On 16.03.2012 12:22, Oliver-Rainer Wittmann wrote:
> Hi,
> sorry for the late response and that I did not fullfill my promise - the
> last days were quite busy.
> May be you should have a look at the proposal text which brought attribute
> text:continue-list into ODF 1.2 [1]
> Here is a quote from this proposal text regarding attribute
> text:continue-list:
> <quote>
> The purpose of these new attributes is to continue the numbering of an
> arbitrary preceding list regardless of the applied list styles. It also
> ensures that lists in <text:numbered-paragraph> representation can also
> better be modeled in the <text:list> representation.
> These new attributes should be optional and are only valid for top-level
> <text:list> elements. It should be used in favor of the existing
> text:continue-numbering attribute that has the limitations described below.
> </quote>
> What is missing in the specification is that text:continue-list is only
> valid for top-level <text:list> elements. This was in the proposal text,
> but somehow got lost.
> What is also missing is that the attribute text:continue-list shall only
> refer a top-level <text:list> element. The proposed attribute text:id was
> replace by xml:id, but somehow the previously mentioned wording got lost.
> Thus, this attribute shall only connect to top-level <text:list> elements
> together in order to form more or less one list. With is esp. used, when a
> list is spread through certain table cells.
> Another important reason for this attribute and the corresponding xml:id
> was to clarify the transformation between the alternative approaches to
> represent lists in ODF - <text:list> together with <text:list-item> vs.
> <text:numbered-paragraph>
> For <text:numbered-paragraph> mandatory attribute <text:list-id> has been
> proposed and integrated into ODF 1.2.
> [1]
> http://www.oasis-open.org/committees/download.php/23418/07-04-05-proposal-lists.odt
>  found on proposal list in our wiki [2]
> [2] http://wiki.oasis-open.org/office/List_of_Proposals
> Mit freundlichen Grüßen / Best regards
> Oliver-Rainer Wittmann
> --
> Advisory Software Engineer
> -------------------------------------------------------------------------------------------------------------------------------------------
> IBM Deutschland
> Beim Strohhause 17
> 20097 Hamburg
> Phone: +49-40-6389-1415
> E-Mail: orwitt@de.ibm.com
> -------------------------------------------------------------------------------------------------------------------------------------------
> IBM Deutschland Research & Development GmbH / Vorsitzende des
> Aufsichtsrats: Martina Koederitz
> Geschäftsführung: Dirk Wittkopp
> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
> HRB 243294
> From:	Svante Schubert <svante.schubert@gmail.com>
> To:	office@lists.oasis-open.org
> Date:	29.02.2012 14:47
> Subject:	[office] Continued Lists
> Sent by:	<office@lists.oasis-open.org>
> I got a question in regard of the @text:continue-list attribute:
> http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#attribute-text_continue-list
> It is obvious that this attribute connects two (or more) lists elements
> within a document, where the following list has the @text:continue-list
> attribute referencing to the previous list.
> From my understanding those lists are not equal to one list, which embeds
> all the in between content, because:
>    1.	The ODF 1.2 schema only allows paragraphs, headings, soft-page breaks
>       and (nested) lists within a list. The in between content may be
>       arbitrary.
>    2.	The usual indent of list content is likely not to apply to the in
>       between content (unspecified - what is the user expectation?)
> What puzzles me, is the spec is not precise in regard of
>    1.	@text:continue-list only allowing an xml:id of a list, that has the
>       same nested/indent level as the referenced list
>    2.	What happens if one of both list's list item are increased/decreased
>       in list level?
> Can someone remember the use case for this feature and/or reference to the
> discussion?
> Does this feature exists as well in other formats?
> Thanks in advance,
> Svante
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: office-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: office-help@lists.oasis-open.org

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]