Revised "MCE semantics"

[Francis Cave]

Part 3 currently says in Section 12:

"[Note: the ext and extLst elements defined in Part 1 are examples of such
extension elements. end note]"

Nevertheless, I think that Murata-san is correct. Since the schema disallows
'foo' inside 'extLst', does this not contradict the fact that MCE processing
is switched off inside application-defined extension elements? In which case
'extLst' is simply a container element for 'ext', which is the true
application-defined extension element.

Regards,

Francis



> -----Original Message-----
> From: eb2mmrt at gmail.com [mailto:eb2mmrt at gmail.com] On Behalf Of MURATA
> Makoto
> Sent: 16 November 2012 06:22
> To: SC34
> Subject: Re: Revised "MCE semantics"
> 
> > In X.4 (ExtensionElements), the current ext elements in Part 1/Part 4
> are listed.  I think what we actually want here is the extLst elements.
> Those are the OPC extension elements and ext is just a regular Part
> 1/Part 4 element that goes inside it.  This is the list of extLst I
> come up with:
> > - http://purl.oclc.org/ooxml/spreadsheetml/main
> > - http://purl.oclc.org/ooxml/presentationml/main
> > - http://purl.oclc.org/ooxml/drawingml/main
> >  - http://purl.oclc.org/ooxml/drawingml/chart
> 
> If extLst elements are app-defined ext elems,
> 
> <extLst>
>   <foo xmlns="http://www.example.org/1"/>
>   <ext>....</ext>
> </extLst>
> 
> will be untouched and OOXML applications will receive this foo element.
> But dml-main.xsd (and dml-main.rnc) does not allow such foreign
> elements.
> 
> Regards,
> Makoto