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] consensus suggestion


Hi David,

The "global" list-id table is needed to get unambigious roundtrip between text:list and text:numbered-paragraph:

<text:list text:style-name="L1">
<text:list-item text:list-override="L2"><text:p>P1</text:p></text:list-item>
<text:list-item><text:p>P2</text:p></text:list-item>
<text:list-item><text:p>P3</text:p></text:list-item>
<text:list-item><text:p>P4</text:p></text:list-item>
</test:list>

would map into

<text:numbered-paragraph text:list-id="id1" text:style-name="L2"><text:p>P1</text:p></text:numbered-paragraph>
<text:numbered-paragraph text:list-id="id1" text:style-name="L1"><text:p>P2</text:p></text:numbered-paragraph>
<text:numbered-paragraph text:list-id="id1" text:style-name="L1"><text:p>P3</text:p></text:numbered-paragraph>
<text:numbered-paragraph text:list-id="id1" text:style-name="L1"><text:p>P4</text:p></text:numbered-paragraph>

which then would map back to (according to Oliver's/Thomas' proposal)

<text:list text:style-name="L2">
<text:list-item><text:p>P1</text:p></text:list-item>
<text:list-item text:list-override="L1"><text:p>P2</text:p></text:list-item>
<text:list-item text:list-override="L1"><text:p>P3</text:p></text:list-item>
<text:list-item text:list-override="L1"><text:p>P4</text:p></text:list-item>
</test:list>

This is a contradiction with on of the requirements I promised to post soon:
---

100% roundtrip fidelity between text:list and text:numbered-paragraph.

The current ODF specification states that
<quote>
A list in <text:list> representation could be converted into a list in <text:numbered-paragraph> representation and vice
versa.
</quote>
The use case derived from that is that there should be 100% roundtrip fidelity when converting between numbered
paragraph and text:list.
Actually requires that
1.an ODF list in numbered-paragraph respresentation, converted to a text:list representation, converted to a
numbered-paragraph represention must result in the same conceptional ODF list a the one before the conversion was
started.
2.an ODF list in text:list respresentation, converted to a text:numbered-paragraph representation, converted to a
text:list represention must result in the same conception ODF list as the one before the conversion was started.
The roundtrip must be deterministic to not disrupt user expecience.

---

With global list-id table
<list-id-table>
<list-id-definition list-id="i1" style-name="L1">
</list-id-table>

this disambiguity would be solved.

~Florian


>>> David Faure <faure@kde.org> 03/19/07 4:52 PM >>>
On Friday 16 March 2007, Florian Reuter wrote:
> The basic are idea is that numbered-paragraphs get a text:list-id but we introduce a list-id-table.

I dislike global mapping tables. They make it more difficult to work with documents (from applications,
XSLT scripts, etc.), because things become much less modular.

The purpose of the list-id-table is to associate a single list style with -all- the numbered paragraphs that
are part of a given list (using list-id). But why would we want a -single- list style for all those paragraphs?
This lacks the "style override" mechanism -- which we get for free when numbered paragraphs simply have
to attributes: the list-id, which is the list they are part of (which defines "this is the third paragraph"),
and the style-name, which defines the type of numbering (e.g. 3, C, or III). 

What I'm missing here is the rationale for adding this list-id-table mapping... numbered-paragraphs
specify their style, and either they all specify the same (and then the list-id-table would have that
one, so we don't need it), or the styles differ, which is fine, it's the "style override" capability; so in
both cases we don't need list-id-table, do we?

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).



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