Re: [office-collab] Lists - information overflow

[Svante Schubert <svante.schubert@gmail.com>]

Hi Thorsten,

On 28.02.2013 10:50, Thorsten Behrens wrote:
> Hi Svante,
>
> you wrote:
>> I came to the following conclusion:
>>
>>  1. All template list styles (those from the styles.xml) should be
>>     provided by operations, when wiring an ODF document by operations
>>     over the net. In case an application allows the choice of existing
>>     predefined list styles.
>>     (We might even specify default styles in the standard to guarantee a
>>     consistent look and feel for ODF documents)
>>  2. Even if there is only one paragraph in the above example, which only
>>     uses one list level style of a list style, the complete set of list
>>     definition level 1 to 10 needs to be wired gathered from the list
>>     hierarchy, otherwise the run-time behavior would differ. For
>>     instance if a user expands the list (usually pressing CR after an
>>     existing list item, here "Hello list!" and lowers the list level a
>>     new list level style would be applied. Which should be used? In this
>>     case the 9th list level style from the above example. Therefore all
>>     available list level definition have to be provided by an operation.
>>
> I wonder if this it yet relevant for the SC task (which is change
> tracking) - aren't we quickly entering the realm of application
> runtime behaviour here, that so far the TC has carefully avoided to
> mandate?
>
The tracking of changes is the tracking of run-time behavior.
But you are right that the collaboration is by far not as important as
change-tracking to us. Still we need to understand what is the XML
difference when we edit (e.g. list) during run-time.
I use the real-time collaboration as theoretical model, to get a better
understanding of the mandatory operations.
And certainly the argument: "we never did this before" should not be an
argument at all for us, quite the opposite. ;)

Let me switch the scenario, imagine an ODF application would only load
and save a document with a list as described earlier with level 5
paragraph and 11 list styles associated. What would be the valid
serialization for that list?
I believe, that the correct way would be to collect all list level
styles available and not for instance only use the list style directly
around the paragraph and fill up the missing list levels with defaults
(e.g. numbering).

PS: To ease testing, find a (valid ODF 1.2) test file attached, it is
the last list that is the one of interest.

Cheers,
Svante

Attachment: ListStyleResolutionPlusDeepList.odt
Description: application/vnd.oasis.opendocument.text