RE: [oic] New version of interop profile draft

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

Hi Bernd,


thanks for the feedback, I've added a section on the MIME stream, and a
clause on ODF11i-Doc having to meet all "shalls" in the ODF 1.1 spec.

(Perhaps I should rephrase that, so it reads "shall be a conformant ODF
1.1 document, catching the "must"s etc)



About the thumbnail.png, I'm not sure if that would buy us much in terms
of interoperability:

- "smaller" implementations might not write a thumbnail when saving a doc,
since that might not integrate well in their file saving functionality

- not sure if ODF libraries (think server side report generators) will be able
to easily generate a thumbnail as well

So that would rule out those implementations from being "ODF 1.1 Interop
profile" compliant, while only providing some benefit to e.g. desktop file
managers and file dialog boxes


On the other hand, PNG/SVG previews for embedded objects makes more
sense IMHO:

- smaller implementations might not support those embedded objects, but
are probably capable of handling PNG/SVG (think viewers on smart phones)

- if you're using an ODF library to generate, say, embedded charts, chances
are that this library is also capable of generating a PNG/SVG preview. If not,
it should at least be possible to generate a SVG "by hand" 


Perhaps this reasoning is flawed, so I'm very interested in the opinion of the
other members :-)



Best regards,

Bart

________________________________________
From: Bernd.Eilers@Sun.COM [Bernd.Eilers@Sun.COM]
Sent: Monday, August 31, 2009 3:21 PM
To: Hanssens Bart
Cc: oic@lists.oasis-open.org
Subject: Re: [oic] New version of interop profile draft

Hi there!

*hmm* a preview image has beend required for embedded documents but not
for the main document, eg. there is no reference to the thumbnail.png
image although this is also a should requirement in the ODF specification.

For section 1.7 and the sentance "ODF11i-Doc shall contain the MIME-type
as outlined in Appendix C of the [ODF 1.1] specification." I would like
to see a reference to the section of the ODF specification describing
the mimetype substream and itīs requrirements added. The ODF
specification explizitly mentions stuff like "This stream should be
first stream of the package's zip file, it shall not be compressed, and
it shall not use an 'extra field' in its header (see [ZIP])." and I
think this should be checked here for also. Some Implementations may
violate this requirement others may not some may be able to cover up
maybe at leat partly on errors of other document creators to follow this
requirements some may not.

Kind regards,
Bernd


Hanssens Bart wrote:
> Hi,
>
>
> I've added a new draft of my ODF 1.1 interop profile proposal:
>
> http://www.oasis-open.org/committees/document.php?document_id=33986
>
>
> Please look into it (especially vendors / implementers) and let me know if the
> conformance clauses stated in this document are realistic or not.
>
> They cover:
>
> - some very simple directives about predefined meta-data elements
> - a few of the issues encountered at the The Hague plugfest (see also Jira
> OIC 5 / 6 / 7)
> - some other bits and bolts
>
> There are many more clauses to be added, and as mentioned during the
> conference calls, perhaps future work may have to be done in separate
> "modules" or "topics" before they get integrated back into this "parent"
> document.
>
> But using the "release early release often" approach, I'd like the OIC TC to
> reach consensus on an initial version, have it approved as a Committee
> Draft, then create another (set of) working draft(s) to work on additional
> issues etc (and perhaps public review / Committee spec every 4 months)
>
> If would be perfect if the first CD would be out of the door before the next
> plugfest, showing some real TC progress towards the participants
>
>
> Best regards,
>
> Bart
> ---------------------------------------------------------------------
> 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
>