stylesWithEffects / musings ?

[Alex Brown]

Dear all,

Returning to this topic (which I find very hard, since there is a cat's cradle of interactions between different provisions of the different Parts) ...

*If* we accept that Part 3 applies, then  clause 9.1 has:

"Future versions of markup specifications shall specify new namespaces for any markup that is enhanced or 
modified by the new version  [...]"

And while it is perhaps not 100% clear what "enhanced or modified" means, changing the content model is certainly "modifying the markup".

So I think this means any extension which re-uses an existing OOXML Namespace has to use the element defined in that Namespace (by Parts 1 and 4) "as is". If there is a desire to modify the markup the elements must be subsumed into a new Namespace using the mechanism that Clause 9.1 goes on to describe.

And so if we want "future versions of markup specifications", they need to have new all-new Namespaces when building on existing OOXML markup. 

- Alex.


> -----Original Message-----
> From: Alex Brown [mailto:alexb at griffinbrown.co.uk]
> Sent: 17 February 2010 16:06
> To: Doug Mahugh; Horton, Gareth; MURATA Makoto (FAMILY Given); e-
> SC34-WG4 at ecma-international.org
> Subject: RE: stylesWithEffects / musings ?
> 
> Doug hi
> 
> > I agree with your comment about not validating parts that are not
> > referenced via a known relationship type.  Such parts may not even be
> > XML at all.  (As I blogged in a contrived example some time ago:
> > http://blogs.msdn.com/dmahugh/archive/2006/11/25/arbitrary-content-
> in-
> > an-opc-package.aspx)
> 
> Yup that's true - but in this case the Part has a MIME type which ends with
> "+xml", so we might be tempted to have a go (or indeed to sniff resources to
> see if they are XML) ...
> 
> - Alex.
> 
> 
> __________________________________________________________
> ____________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> __________________________________________________________
> ____________
> 
> __________________________________________________________
> ____________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> __________________________________________________________
> ____________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________