OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

opendocument-users message

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

Subject: RE: [opendocument-users] simple OO.org document goes awry in MS Office 2007 w/SP2 - what went wrong?

Hi Sander,

I agree that it would be very helpful to have implementer notes for more than one implementation.  In this particular case (the trailing slash on embedded objects), we have notes for one implementation stating that it follows the standard, but that doesn't add much information to the discussion because that approach was already documented in the standard itself.  Implementer notes for those implementations that do not follow the standard would be even more useful to current and future implementers.  I assume we'd all agree that it's more important to document a decision to deviate from the standard, than a decision to conform to the standard.

- Doug

-----Original Message-----
From: Sander Marechal [mailto:s.marechal@jejik.com]
Sent: Wednesday, June 17, 2009 5:30 AM
To: Hanssens Bart
Cc: Jan Wildeboer; marbux@gmail.com; robert_weir@us.ibm.com; opendocument-users@lists.oasis-open.org
Subject: Re: [opendocument-users] simple OO.org document goes awry in MS Office 2007 w/SP2 - what went wrong?

Hanssens Bart wrote:
> So, what vendors can do to increase interop *in this specific case*
> (since it was all about having a URI with a slash or not, trivial to
> fix IMHO) is to be liberal in what they accept and strict in what
> they produce (sounds familiar, doesn't it).

I think starting with the implementor's notes would be a good way
forward. I hope Microsoft can publish their "raw" implementor notes and
that other vendors pick up on that and start using the same format.

When you start mashing these together it should become easy to see where
the standard may lack in specificity (all vendors having many notes on
the same subject) and how applications diverge (vendors pick different
solutions or interpretations to the same problem). During the next
plugfests we could take up these issues and see how we can all agree on
an interpretation that works interoperable.

Those kinds of issues are prime candidates to send back to the TC.
Either as clarifications to the current spec, as suggestions for the
next spec or for some kind of "implemmentors recommendation".

Sander Marechal

To unsubscribe, e-mail: opendocument-users-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: opendocument-users-help@lists.oasis-open.org

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