W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2009

[Bug 5631] [UPD] rename and namespace inheritance

From: <bugzilla@wiggum.w3.org>
Date: Tue, 28 Apr 2009 10:05:33 +0000
To: public-qt-comments@w3.org
Message-Id: <E1LykBx-0002yQ-5C@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5631


Jonathan Robie <jonathan.robie@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jonathan.robie@redhat.com




--- Comment #3 from Jonathan Robie <jonathan.robie@redhat.com>  2009-04-28 10:05:32 ---
When I attempted to implement this, I realized that
http://lists.w3.org/Archives/Member/w3c-xml-query-wg/2008Jul/0014.html
 presents two different ways to handle the semantics of namespace propagation,
and the minutes do not tell me which of these to use:

<quote
href="http://lists.w3.org/Archives/Member/w3c-xml-query-wg/2008Jul/0014.html">
  A difficulty with propagating namespaces is that it could cause new kinds of
  conflicts, and that the result could depend on the order in which operations
  on the PUL are applied. For example consider:

  <a><b/></a>

  and an update that renames <a> to <p:a xmlns:p="p.uri"> while renaming <b>
  to <p:b xmlns:p="q.uri"/>. Then if the rename of <a> is done first, the
  rename of <b> would fail because the <b> element has acquired a conflicting
  namespace binding for the prefix "p". But if <b> is renamed first, there is
  no conflict, because the propagation of the namespace binding will
  (presumably) stop when another binding of the same prefix is encountered.

  It is possible to solve this problem by doing all propagation of namespaces
  at the end, after all other update actions have been completed (but before
  revalidation). This can be done using a similar idea to the way we "mark
  nodes for revalidation". Wherever we add a namespace binding to an element
  node, we "mark the namespace binding for propagation", and after step 5 of
  upd:applyUpdates(), we add:

  5.1 For each namespace binding that is marked for propagation,
  upd:propagate-namespace($element, $prefix, $uri) is invoked, where $element
  is the element node on which the namespace binding appears, $prefix is the
  namespace prefix, and $uri is the namespace URI. 
</quote>

Neither my notes nor the minutes tell me whether we decided to adopt this part,
marked as "possible" in the proposal.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 28 April 2009 10:05:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:27 UTC