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: RE: [office-collab] Possible UC7 for consideration...

I think there may be a misunderstanding about what "ECT" (and ODF 1.2 already) can do with annotations.

The <office:annotation> element has change-trackable content.  This is provided in the content of the annotation itself, which consists of paragraphs and lists.

I don't believe the <office:annotation-end> is used to mark the end of the annotation but the end of the normal text that the annotation applies to.  (That is, it is the difference between the annotation applying at point and applying to a segment of the visible content of the document.)  In that sense, it is like a bookmark, end, when present and in that case the <office:annotation> is like a bookmark start while also providing the content of the annotation in its own child elements.

Also, the office:name is not an ID, so "duplicates" are not an issue the way they are for ID-valued markers.

Finally <office:annotation-end> is new in ODF 1.2 and the explanation of it is all there is to be seen.  The absence of semantics is really wonderful, isn't it?  The same goes for the attributes on <office:annotation> that appear to treat the annotation contents as fitting within a type of frame insertion.

It is not expected that any change in the annotation itself could have a span that is partially in and partially without the annotation, any more than one would expect that with any other kind of framed content.  It is outside of the running text.  When an <office:annotation-end> appears, there is also the consideration if the <office:annotation> were, in addition to providing the annotation, treated like a bookmark start having the <office:annotation-end> as the end marker.  In that case, the previously unsolved problem with regard to change-marking of off-hierarchy begin and end markers applies, but that is not to change in the annotation but in what the annotation applies to, it seems to me.

It would be interesting to find an implementation of <office:annotation-end> to see how it is used, if at all.

 - Dennis

-----Original Message-----
From: Robin LaFontaine [mailto:robin.lafontaine@deltaxml.com] 
Sent: Monday, August 15, 2011 03:17
To: office-collab@lists.oasis-open.org
Subject: Re: [office-collab] Possible UC7 for consideration...

On 13/08/2011 00:54, John Haug wrote: 



	Is change markup for an annotation necessary?


We do have this requirement:

	2.4 Track all possible types of change
	- track all types of change, e.g. across hierarchy, tables, styles etc.

It is clear that ECT cannot track changes in annotation at the moment, but how easy or difficult it is to extend it to do this will help to inform our decision. We need to know if we need significant work and several pages of examples/documentation for every new construct we wish to include. 

Alternatively, if ECT cannot be extended to do this, then we need to know that if we go with ECT then we cannot track changes in annotation or any similar constructs.


-- -----------------------------------------------------------------
Robin La Fontaine, Director, DeltaXML Ltd  "Change control for XML"
T: +44 1684 592 144  E: robin.lafontaine@deltaxml.com      
Registered in England 02528681 Reg. Office: Monsell House, WR8 0QN, UK
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 

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