Re: [office-metadata] Backward compatibility mechanism (achievedby the preserving of information not understood)

[Patrick Durusau <patrick@durusau.net>]

Rob,

Ah, a small light flickers! ;-)

OK, but in the context of the metadata SC, we would want to have a use 
case where *all* metadata MUST be preserved for the reasons you mention. 
The question of preserving other foreign content being beyond our 
purview, although one that we can raise in the TC with such a use case 
for metadata.

Since I did not understand it, I did not include it in the rough draft.

I will try to work up something by tomorrow (anyone else can jump in as 
well) for discussion for inclusion in a revision of the use cases document.

Hope you are having a great day!

Patrick

robert_weir@us.ibm.com wrote:

>
> I believe the former was intended.  But keep in mind that ODF 1.0 says 
> that preserving foreign content is only a "SHOULD".   If an 
> implementation does not do this, and strips out unknown content, 
> possibly metadata, when writing, then round-tripping of documents 
> between semantically-rich and non-semantically-rich editors would be 
> suboptimal.  So I'd recommend this use case to encourage us to think 
> about changing the "SHOULD" to "MUST", or suggest other conventions 
> for allowing such information not to be lost when exchanging documents 
> among a heterogenous set of editors.
>
> -Rob
>
> Patrick Durusau <patrick@durusau.net> wrote on 06/28/2006 09:35:34 AM:
>
> > Greetings!
> >
> > Can someone clarify the use case:
> >
> > Backward compatibility mechanism (achieved by the preserving of
> > information not understood)?
> >
> > ODF already specifies that information that is not understood is to be
> > preserved.
> >
> > Or is this a case of where ODF defined an element and then later
> > re-defined an element and metadata would signal which definition should
> > be applied? And failing that, simply leave the element alone?
> >
> > 


-- 
Patrick Durusau
Patrick@Durusau.net
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model
Member, Text Encoding Initiative Board of Directors, 2003-2005

Topic Maps: Human, not artificial, intelligence at work!