RE: [oic] first impression on conformance tests ? - <office:metadata> <dc:creator> element.

["Hanssens Bart" <Bart.Hanssens@fedict.be>]

Title: RE: [oic] first impression on conformance tests ? - <office:metadata> <dc:creator> element.

Hello Dennis,


thanks for all the remarks. Really nice to read the discussion on the
tests.

(...)


> I think there should be test cases like this.  I don't know what to
> call them. 

Hmm, "feature" tests ? Completeness tests ? Function point tests ?


>1. MODEST CONCERNS ON THE TEST ZIP

> 1.2 Using a Working Copy of the OIC SVN, the pages come up nicer than
> directly in the Zip of course (because the CSS file is found), and the
> links work.

Ah, I just unzip the whole lot in a working directory...


> However, my browser won't launch the documents/ODF11/metadata-test.odt
> file from the scenarios/html/metadata-dc-creator.htm page.
> The browser wants me to authorize an unsigned so_activex.dll and I
> am not going down that road.

You've probably installed OpenOffice.org (default install ?) with the
plugin for IE, so clicking on an ODF inside a browser fires up the
ActiveX ?



> 1.5 There needs to be a way to ensure the documents are kept as
> read-only for testing purposes.  I noticed that my test application
> wanted to update the metadata-test.odt document, although I hadn't
> knowingly modified it.
> This might be additional guidance, since Zip implementations won't
> always transfer and preserve that kind of file-system attribute
> settings.

We can't guarantee a file cannot be changed, so setting the read-only
file attribute in the zip and provide a hash is the best we can do.
In ODF 1.2 we might consider signing the files, but an implementation
can of course ignore the signature...


> 1.6 I notice that the hand-crafted meta.xml file has an XML comment
> about ODF 1.1 errata.  What errata are those?

Mm, this one (corrected in 1.2, so I should remove it from the 1.2 docs)
http://wiki.oasis-open.org/office/OpenDocument_v1.1_Errata


> 2. FURTHER CONCERNS
> 2.1 The implementation that I am using shows me an empty document. 

Yes, an "hello world, this is a test para" could be added (or other
content / tests that do show some text to the end user)


> 2.2 The problem I have with this is that I am speaking of representative
> consumer behavior for an ODF Text document.  There is no way to know
> what the connection with a dc:creator element is and what constitutes
> conformance.  Furthermore, there is no ODF conformance requirement on
> this information being available and on how implementations influence it,
> either mechanically or as an user agent or both.  There is, of course,
> also nothing specified for ODF on who has control over the dc:creator
> content and what is allowed for that content.

So, in this case the test is more heading towards interoperability, and
ODF-Next should be clearer on the conformance requirements ?


> 3. SERIOUS CONCERN
>
> 3.1 I looked at section 3.1.7 Creator, and I find this statement to be
> abominable...

Testing good old boring meta-data sure is a lot of fun isn't it  :-)



Best regards,

Bart