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] Groups - Proposal for generic representationof tracked changes for ODF (generic-ct-proposalV5-updates.odt) uploaded


Hi Robin,

It hadn't occurred to me that with "application" you mean "format" so
that ODF would be one application of some more general GCT. 
As far as I am concerned this subcommittee deals with ODF. So I read the
proposal within the context of ODF and if there are choices given for
the writer I would assume that these choices are intended to be
available inside ODF. Perhaps we need a translation of the GCT proposal
to ODF.

On Wed, 2011-09-14 at 02:25 -0600, Robin LaFontaine wrote:
> On 13/09/2011 15:42, Andreas J. Guelzow wrote: 
> > -------------
> > While having delta:removed-content allows the deleted content to place
> > elsewhere, it still allows it to be retained in situ. This does not seem
> > to resolve the issue that a 1.2 or earlier implementation when
> > encountering this element needs to understand it to be able to ignore
> > the element content.  
> I am not sure I understand your comment. I would not envisage a 1.2 or
> earlier implementation could read GCT at all, nor could it read most
> of ECT either. In the same way 1.1 reader cannot understand all of
> 1.2.

Of course an ODF 1.2 consumer would not be able to interpret the GCT
elements within an ODF 1.3 file. But if that consumer views the GCT
elements inside the ODF 1.3 file as foreign elements, I would hope that
the result would make some sense. So character content should not remain
in-situ but moved somewhere else.

Andreas  

-- 
Andreas J. Guelzow, PhD, FTICA
Concordia University College of Alberta



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