OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-collab message

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


Subject: Possible UC7 for consideration...


Hi,
  While indexing up the UC1-UC6 I was also trying to think of other cases which might present sticky results. Looking at the ODF 1.2 spec, in particular the section for annotations I see the provision for annotations to span across elements:

14.2 <office:annotation-end>
  The <office:annotation-end> element may be used to define the end of a text range of document content that spans element boundaries. In that case, an <office:annotation> element shall precede the <office:annotation-end> element. Both elements shall have the same value for their office:name attribute.

I thus propose a UC7 which includes an annotation spanning from one text:p to another as follows. Note that the same issues arise for text:bookmark-end (6.2.1.4). Though I arrived at this because one might very well want an annotation to link a disparate range.

In the example, First the paragraph text for all three paragraphs is inserted. Then the draw:frame and its caption text is added. Then an annotation is inserted spanning through the end of the caption through another paragraph and midway into the next one. Finally a word is inserted into the caption, inside the bounding region that is included in the annotation region.

In this case, for the GCT there is only the original office:annotation using its original office:name attribute. The use of buckets in the ECT would appear to make things quite sticky. One solution might be to include the whole office:annotation in each bucket and each time link back to a different annotation/office:name from the annotation-end marker. Another might be to extend the definition of office:name to allow one or more previous annotations to have the same identifier which is picked up by a single annotation-end element.

A crack at GCT for this case follows.

<text:p text:style-name="Text_20_body">
  <draw:frame draw:style-name="fr1" draw:name="Frame1" 
              text:anchor-type="paragraph" draw:z-index="0" 
              svg:x="2.0cm" svg:y="2.0cm" svg:width="8.0cm" 
    <draw:text-box fo:min-height="2.503cm">
       <text:p text:style-name="Frame_20_contents">
          This is 
          <office:annotation office:name="supereffective"
              delta:insertion-change-idref="ct2" 
              delta:insertion-type="insert-around-content">
            <dc:creator>Superman</dc:creator>
            <dc:date>7-25-2011</dc:date>
            <text:p text:style-name="Normal" >
                This part of the document rocks amigo!
            </text:p>
            </office:annotation>
            a 
          <delta:inserted-text-start 
              delta:insertion-change-idref="ct3" 
              delta:inserted-text-end-idref="it1"/>
            modified 
          <delta:inserted-text-end 
              delta:inserted-text-end-id="it1"/>
          text frame.
       </text:p>
    </draw:text-box>
  </draw:frame>

In this example an annotation has been created which spans from the  
text:p of the comment for an image through this paragraph and into the next.
</text:p>

<text:p> 
  Perhaps we have missed considering locality in the document. 
  <office:annotation-end 
     office:name="supereffective" 
     delta:insertion-change-idref="ct2" 
     delta:insertion-type="insert-around-content"/>
  
  And this part is more about the water cooler and how we all need to
  get more sun this winter. 
</text:p>



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