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] change to the existing proposal [was: Re:[office] Critical problem]


Hi,

thanks Oliver. I will now take some time to understand your new proposal.

Just two guesses:
* by introducing a text:list-id on text:list there is no need for list-override any longer. Thus your proposal doesn't
reflect a "compromise" any more.
* by introducing a text:list-id on text:list you made a change which harms backward compatibility.

Just my two cents for now. Please tell me if thats wrong. However I will try to justify these statements myself.

I'll follow up on this when I'm confident I understood the new proposal.


~Florian



>>> Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems <Oliver-Rainer.Wittmann@Sun.COM> 03/13/07 3:44 PM >>>
Florian Reuter wrote:
> Hi Thomas,
> 
> could you please send me the XML fragment. That's all I need. So again. How will
> <text:numbered-paragraph text:list-id="id1" style:name="L1"><text:p>H1</text:p><text:numbered-paragraph>
> <text:p>Text</text:p>
> <text:numbered-paragraph text:list-id="id1" style:name="L1"><text:p>H2</text:p><text:numbered-paragraph>
> <text:p>Text</text:p>
> <text:numbered-paragraph text:list-id="id2" style:name="L1"><text:p>NP1</text:p><text:numbered-paragraph>
> <text:numbered-paragraph text:list-id="id2" style:name="L1"><text:p>NP2</text:p><text:numbered-paragraph>
> <text:numbered-paragraph text:list-id="id2" style:name="L1"><text:p>NP3</text:p><text:numbered-paragraph>
> <text:numbered-paragraph text:list-id="id2" style:name="L1"><text:p>NP4</text:p><text:numbered-paragraph>
> <text:p>Text</text:p>
> <text:numbered-paragraph text:list-id="id1" style:name="L2"><text:p>Appendix</text:p><text:numbered-paragraph>
> <text:p>Text</text:p>
> 
> be represented in text:list. According to your personal understandin of the proposal?
> 
> Thats all I need.
> 
> Sometimes a "picture" speaks more than thousand words to me.
> 

Hi Florian,

Thank you very much for this use case.

I have to admit that I didn't have thought about such a use case. 
Applying the existing proposal, found at 
http://lists.oasis-open.org/archives/office/200702/msg00172.html, I 
didn't find a way to convert the given XML fragment into another XML 
fragment using <text:list>.
The problem is the following:
- Paragraph "H1" has to be included into an own <text:list> element with 
list style "L1"
- Paragraph "H2" also has to be included into an own <text:list> element 
with list style "L1", but by using text:continue-numbering="true" the 
list containing "H1" can be continued.
- Paragraphs "NP<x>" has to be included into a <text:list> element with 
list style "L1".
- For paragraph "Appendix" also an own <text:list> element is needed. 
But, I see no way to continue the list containing "H2". Attribute 
text:continue-numbering can't be used, because in this case the list 
containing the paragraphs "NP<x>" would be continued.

It had helped much more, if you had state this on your own and directly 
said, that's an insuffiency of the existing proposal.

Thus, I propose the following change to the existing proposal, found at 
http://lists.oasis-open.org/archives/office/200702/msg00172.html:
- remove point (5)
- add new point containing the following:
Introduce the following new attributes for <text:list> elements:
-- text:id with type <ref name="ID">
-- text:continue-list with type <ref name="IDREF">
These new attributes should be optional and are only valid for top-most 
<text:list> elements. Attribute text:id unambiguously identifies a 
certain list. Attribute text:continue-list states, that the current list 
has to continue the numbering of the list, which is identified by the 
value of text:continue-list.

With the proposed change it is possible to convert the given XML 
fragment using <text:numbered-paragraph> into another XML fragment using 
<text:list>. The result is:
<text:list style-name="L1" text:id="id1_1" >
   <text:list-item><text:p>H1</text:p></text:list-item>
</text:list>
<text:p>Text</text:p>
<text:list style-name="L1" text:id="id1_2" text:continue-list="id1_1" >
   <text:list-item><text:p>H2</text:p></text:list-item>
</text:list>
<text:p>Text</text:p>
<text:list style-name="L1" text:id="id2_1" >
   <text:list-item><text:p>NP1</text:p></text:list-item>
   <text:list-item><text:p>NP2</text:p></text:list-item>
   <text:list-item><text:p>NP3</text:p></text:list-item>
   <text:list-item><text:p>NP4</text:p></text:list-item>
</text:list>
<text:p>Text</text:p>
<text:list style-name="L2" text:id="id1_3" text:continue-list="id1_2" >
   <text:list-item><text:p>Appendix</text:p></text:list-item>
</text:list>



Regards, Oliver.



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