OASIS Open Document Format for Office Applications (OpenDocument) TC

Greetings! Since we moved so quickly on the first ten (10) issues, I would like to add the next ten (10) to next week's agenda. With one change in process, I would ask for anyone with a solution or suggestion (including myself) to send a post *before* the meeting so if there are any "easy" ones (I sorta doubt it) we can clear those quickly after all the process stuff at the meeting and then move on to those that remain. That will mean preparing for the meeting in terms of discussion of the issues but that is the only way we are going to get through these as well as a number of others, plus any new issues we get from users and implementers. *************** 1. Proposal for adding Font Feature support to ODF http://tools.oasis-open.org/issues/browse/OFFICE-3414 2. 9.1.13 - confusing naming of table:title element http://tools.oasis-open.org/issues/browse/OFFICE-3404 3. 1.2-1 5.5.6 <office:change-info> content overkill http://tools.oasis-open.org/issues/browse/OFFICE-3383 4. Please standardize "Line Start Prohibition Rule" http://tools.oasis-open.org/issues/browse/OFFICE-3356 5. OpenFormula 3.4 HOST-REFERENCE-RESOLVER under-defined http://tools.oasis-open.org/issues/browse/OFFICE-3325 6. OpenFormula 3.4 HOST-REFERENCE-RESOLVER should not be implementation defined http://tools.oasis-open.org/issues/browse/OFFICE-3323 7. add formula engine information http://tools.oasis-open.org/issues/browse/OFFICE-3034 8. Comment on bibliographic section of ODF http://tools.oasis-open.org/issues/browse/OFFICE-3031 9. Comments on Digital Signatures in ODF 1.2 Part 3 http://tools.oasis-open.org/issues/browse/OFFICE-3030 10. 14.1 <office:annotation> currently not usable with <draw:page> http://tools.oasis-open.org/issues/browse/OFFICE-3022 ***************** Hope everyone is at the start of a great week! Patrick -- Patrick Durusau patrick@durusau.net Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau

Hi Patrick, some quick comments inline - Patrick Durusau wrote: > 1. Proposal for adding Font Feature support to ODF > http://tools.oasis-open.org/issues/browse/OFFICE-3414 > Makes sense to me, and let's go for option #2 (additional style attributes, in line with css) -> take it. > 2. 9.1.13 - confusing naming of table:title element > http://tools.oasis-open.org/issues/browse/OFFICE-3404 > I concur with Andreas -> close. > 3. 1.2-1 5.5.6 <office:change-info> content overkill > http://tools.oasis-open.org/issues/browse/OFFICE-3383 > Defer, change tracking is gonna be touched big time anyway. > 4. Please standardize "Line Start Prohibition Rule" > http://tools.oasis-open.org/issues/browse/OFFICE-3356 > Agreed that this is missing, but there's no concrete proposal from Murata-San -> ask for that & defer. > 7. add formula engine information > http://tools.oasis-open.org/issues/browse/OFFICE-3034 > Lots of "nice to have", "ain't this cool", but no compelling case made why this would be useful in real life -> close. > 8. Comment on bibliographic section of ODF > http://tools.oasis-open.org/issues/browse/OFFICE-3031 > Misguided feature request. Use rdf or any other out-of-band means to store the data (that will be opaque to an odf processing application anyways) -> close. > 9. Comments on Digital Signatures in ODF 1.2 Part 3 > http://tools.oasis-open.org/issues/browse/OFFICE-3030 > No material change to objections -> defer. > 10. 14.1 <office:annotation> currently not usable with <draw:page> > http://tools.oasis-open.org/issues/browse/OFFICE-3022 > Would be one down on the list of OOo extensions LibreOffice has -> take the fix. Cheers, -- Thorsten Behrens SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Attachment: pgpsgX8kvQJ8e.pgp Description: PGP signature

Thorsten, Apologies, I have been "off" email for a while, a couple of questions: On 11/01/2011 06:02 AM, Thorsten Behrens wrote: Hi Patrick, some quick comments inline - <snip> 4. Please standardize "Line Start Prohibition Rule" http://tools.oasis-open.org/issues/browse/OFFICE-3356 Agreed that this is missing, but there's no concrete proposal from Murata-San -> ask for that& defer. Are you going to follow up with Murata-san? 9. Comments on Digital Signatures in ODF 1.2 Part 3 http://tools.oasis-open.org/issues/browse/OFFICE-3030 No material change to objections -> defer. When you say defer (I am sure this will come up again with you, me or others in the future) do we mean to really "defer" or are we going to close? The reason I ask is that I would prefer to not have a grab bag of requests and possible features that form a "deferred" group. If we really mean to work on them at some point, next release cycle, ok, but let's either resolve them, or set a firm date for resolution, even if that is next release. Does that sound reasonable? Hope you are having a great week! Patrick -- Patrick Durusau patrick@durusau.net Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau

Patrick Durusau wrote: > >>4. Please standardize "Line Start Prohibition Rule" > >> http://tools.oasis-open.org/issues/browse/OFFICE-3356 > >> > >Agreed that this is missing, but there's no concrete proposal from > >Murata-San -> ask for that& defer. > > > Are you going to follow up with Murata-san? > Can do - somehow missing the minutes from last week's call still, so can't really remember what we've agreed upon. :) > >>9. Comments on Digital Signatures in ODF 1.2 Part 3 > >> http://tools.oasis-open.org/issues/browse/OFFICE-3030 > >> > >No material change to objections -> defer. > > > > When you say defer (I am sure this will come up again with you, me > or others in the future) do we mean to really "defer" or are we > going to close? > Defer until XMLDSig is final (or close to final), then open discussion again. > The reason I ask is that I would prefer to not have a grab bag of > requests and possible features that form a "deferred" group. If we > really mean to work on them at some point, next release cycle, ok, > but let's either resolve them, or set a firm date for resolution, > even if that is next release. > Doesn't work for this one, since we depend on external input. Cheers, -- Thorsten Behrens SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Attachment: pgpobnPWR7WRw.pgp Description: PGP signature

> > Are you going to follow up with Murata-san? > > > Can do - somehow missing the minutes from last week's call still, so > can't really remember what we've agreed upon. :) > Heh, just read in the minutes Rob is going to. :) Cheers, -- Thorsten Behrens SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Attachment: pgpglooa26eBF.pgp Description: PGP signature