Rewriting the scope of Part 3

Chris Rae Chris.Rae at
Tue Jul 5 20:12:23 CEST 2011

Hi Jesper - I think this is right, and this actually matches what Murata-san was mentioning about us seeding the pre-processor in those Parts. This was something that Florian had worked on during the Berlin WG4 meetings, and I think the solution works well but I'd like to see that integrated into the standard before we think about separating these Parts into other standards.


-----Original Message-----
From: Jesper Lund Stocholm [mailto:jesper.stocholm at] 
Sent: 03 July 2011 23:05
To: Chris Rae; MURATA Makoto (FAMILY Given); SC34
Subject: RE: Rewriting the scope of Part 3

Hi Chris,

> -----Original Message-----
> From: Chris Rae [mailto:Chris.Rae at]
> Sent: Thursday, June 30, 2011 6:57 PM
> To: MURATA Makoto (FAMILY Given); SC34
> Subject: RE: Rewriting the scope of Part 3
> Hi all - if I remember correctly, we do have a slight problem with
> MCE generic with regard to the suspension of MCE processing inside
> collections. I know we talked in Berlin about some possible ways to
> around that, but I don't think we settled on anything - I'd be
> to head down the road of generalising MCE before that problem is

Would a pragmatic solution be to generalise MCE and - ahem - 'extend' or 'augment' it in Part 1 and Part 4 of OOXML?

Med venlig hilsen / Best regards

Jesper Lund Stocholm

CIBER Danmark A/S
Mobil: +45 3094 5570
Email: jesper.stocholm at

CONFIDENTIALITY NOTICE AND NOTICE REGARDING NO ELECTRONIC SIGNATURE: The materials in this electronic transmission (including attachments) may be subject to attorney-client or work product privilege, may be private and confidential and are the property of the sender. The information contained is intended only for the named addressee(s) and should not be considered evidence of intent to be bound to any agreement. The taking of any action in reliance on the contents is strictly prohibited. If you are not the intended recipient of this message, please immediately notify the sender and promptly delete this message.

More information about the sc34wg4 mailing list