On 2012-09-13 11:10, Jukka Zitting wrote:
Hi,
On Thu, Sep 13, 2012 at 10:47 AM, Marcel Reutegger <[email protected]> wrote:
remapping an existing namespace prefix in the namespace registry
somewhat breaks existing content. say we create a node foo:test,
save it and then remap prefix 'foo' to 'bar' in the namespace registry.
reading the same node again will still return foo:bar, however 'foo'
is not valid namespace prefix anymore. Was this done on purpose
or this a bug?
The idea, not implemented yet, of how such things should be handled is
to have a commit hook that looks out for changes in registered
namespace prefixes and either a) simply rejects them, or b) goes
through all existing content (potentially with a query to save time)
and automatically updates all names and paths that contain modified
> ...
We could do that for node names and some type of property values. But it
would still potentially break other things (link identifiers in content,
think a/@href).
Best regards, Julian
