RE: Special cases for PrefixRewrite in C14N 2.0

> I am thinking that we should change the definition of prefixRewrite so that
> we go by URI and not by prefix.  i.e.  each visibility utilized prefix gets
> mapped to a new prefix, so that there is a 1:1 mapping between URIs and
> new prefixes, but not a 1:1 mapping between original prefixes and new
> prefixes.  With this definition  we would get 1a), 2b and 3b) which I think
> makes more sense.

I would agree, with the caveat that this might only apply within a particular subtree? In other words, if the URI is on the namespace stack, it makes sense to remember the prefix used, but does that make sense if it's been popped off the stack but then appears again in another disjoint subtree?

I guess I would suggest favoring whatever is easiest to describe, and therefore get right. Even if there's some duplication or inefficience.

-- Scott

Received on Wednesday, 27 April 2011 19:01:36 UTC