On Mon, Apr 14, 2008 at 4:12 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ... In fact, I would be rather strict in accepting "valid" characters, > probably reducing the accepted set to just [ a..z, A..Z, 0..9 ]. Not > sure about the case mangling. But if we apply it in one place (when > mangling a title), we should also apply it in the other place (when > mangling the "nameHint". Whatever we do, it should be consistent.... As mentioned in this thread, the final goal is to create good URLs from free-form data, so I think the current filtering, as applied to parameters like "title" etc., is fine. If Carsten needs precise control on the node names being created, I'd suggest having three ways to specify the names of created nodes: 1) nodeName parameter -> no filtering at all, client must provide a valid JCR name 2) derive the name from title, description, etc. parameters -> as now, filtering creates "good" URLs, all lower case, restricted to characters a to z, 0 to 9 and underscore. 3) nameHint parameter: same as 2) but takes precedence on those parameters. In this way we have consistent filtering between 2) and 3), nice URLs, and a way to specifiy exact node names if needed. -Bertrand
