W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > September 2007

Re: towards consensus on fixup, part 2

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 07 Sep 2007 13:20:58 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <m2veamgznp.fsf@nwalsh.com>
/ Alex Milowski <alex@milowski.org> was heard to say:
| For example, p:insert or p:replace take whole element subtrees
| and put the into another document.  If those elements have dependencies
| on in-scope namespaces, you'd break the content if the in-scope namespaces
| aren't copied.  If you rely upon namespace fixup, you'd only get
| namespace declarations for the elements and attributes of that subtree and
| not extra ones that exist for the content (as they weren't copied).

Why? The node that you're inserting has some number of in-scope
namespaces. I'd expect namespace fixup to preserve all of them without
regard to which ones were (or weren't) actually needed on the element
or its descendants.

Perhaps we should tweak our definition of namespace fixup a little bit
to make that clearer:

  [Definition: Some steps can produce XML documents which could not
  have been produced by directly parsing any instance document
  (because they contain nodes which have in-scope namespaces that are
  not declared or in-scope namespaces with conflicting prefixes, for
  example). To represent such a document in a serializable way, the
  XProc processor must sometimes add additional namespace nodes,
  perhaps even renaming prefixes, to satisfy the constraints of
  Namespaces in XML. This process is referred to as namespace fixup.]

                                        Be seeing you,

Norman Walsh <ndw@nwalsh.com> | If you cannot find the truth right
http://nwalsh.com/            | where you are, where else do you expect
                              | to find it?-- Dogen

Received on Friday, 7 September 2007 17:21:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:44 UTC