[ODFPlugtest] Scenarios and What Conformance? (was Re: MSO does not read LO files)

[Dennis E. Hamilton]

I like your test.

Why not just provide the file as part of the test, since one question is about consumers.

With regard to who produces it, I think that is a separate scenario check.

Even though what it is all about is interoperability, from those two cases we know what the interop cases are.

It is, of course, perfectly reasonable that OO.o 3.3.0 and 3.2.0 (the one I still run) wouldn't produce the attribute, its requirement wasn't in the specification yet (or not long enough for anyone to have noticed, etc.).  So a late changed breaks whatever their implemented anticipation of ODF 1.2 conformance is.

So when the validators check conformance, do they provide an assessment of the particular conformance that they encounter?  I.e., a Conformant OpenDocument [1.2] Spreadsheet Document shall use OpenFormula.  A Conformant Extended OpenDocument [1.2] Spreadsheet Document could still use the OpenOffice.org formula (cute that it's an extension), or whatever the formula namespace and syntax that Microsoft Office uses in their ODF 1.1 documents.  (This distinction also applies to certain use of formulas in Conformant [Extended] Text Documents.)

Are these far more material provisions being reported on by validators?  Or do the validators assume there is just one conformance as was the case for ODF 1.1?

That sort of thing is probably useful to kick around at a plugfest too.  What conformance are we talking about?

 - Dennis



-----Original Message-----
From: plugtest-bounces at opendocsociety.org [mailto:plugtest-bounces at opendocsociety.org] On Behalf Of Hanssens Bart
Sent: Wednesday, June 29, 2011 00:23
To: ODF Plugfest mailinglist
Subject: Re: [ODFPlugtest] MSO does not read LO files


Hi,

>Several people mentioned that, and I fail to see how it can have
>anything to do with a plugfest.

It is a good test to see what ODF 1.1 consumers do when opening an
ODF 1.2 document (not only MS-Office, but for instance also Google
Docs - don't know if GD supports 1.2 - or SoftMaker Office etc)


>This is not an issue of having applications agree on a certain
>interpretation of ODF. ODF1.2 as currently written unequivocably
>requires that attribute.

It is also a reminder for ODF producers to check if the files they
generate are actually valid ODF files (there are some fine validators
out there)

Even while it is clearly defined in the spec, it is still a good test because

a) we know that not all ODF 1.2 implementations follow this spec
b) it would be nice to know how various ODF 1.1 implementations
handle ODF 1.2 documents 

Anyway, I've created a scenario for those who want to perform a test:

http://plugtest.opendocsociety.org/doku.php?id=scenarios:20110715:odf12


Best regards

Bart
_______________________________________________
Plugtest mailing list
Plugtest at opendocsociety.org
http://lists.opendocsociety.org/mailman/listinfo/plugtest