[Zip] Re: [Zope3-dev] Zope 3 ids, names, and unicode

[Florent Guillaume]

Martijn Faassen  <faassen@vet.uu.nl> wrote:
> Agreed. I'd complain a lot if Zope were to adopt weird urls.
> I mean, even the ';' thingy in URL is already raising storms, imagine
> what would happen if we were to say Zope 3 only has 15315353abxf15135 :).
> This also sort of hooks into the whole REST versus SOAP debate, where
> the SOAP approach would be equivalent to the weird URLs (or no URLs at
> all, but URLs that opaque aren't *real* URLs anyway..)

Zope wouldn't enforce weird URLs on people who keep their ids to
US-ASCII anyway.

But as a developer and as a user there have been a number of time where
I wanted full unicode ids. For instance in CMF I want the login name to
be fully accented, and the login name happens to be also the id of the
Members home directory of the user...

So my vote would be to have full Unicode ids, and when putting ids in
URLs encode them in UTF-8 and let URI/URL octet-escaping do the rest.
That would mean that a URL with an id of 'déjà vu' in it would look
like:
http://www.example.com/Zope/d%c3%a9j%c3%a0%20vu/view
But I really think that nobody reads URLs these days.


And it would be so much cleaner to not have arbitrary restrictions in
Zope 3...


[This would mean no legible latin-1 URLs... but this is not reliable
anyway as the URI/URL RFC doesn't specify in what charset URL octets are
to be interpreted (witness supposedly latin-1 URL on a macintosh). So no
big deal.]


Florent

-- 
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 87  http://nuxeo.com  mailto:fg@nuxeo.com