Felix Röthenbacher wrote:
[...]
Generally +1, but I'd suggest to change the parameter order
according to lenyadoc://
{<module-name>:<pub-id>:<area>:<doc-lang>:<doc-id>:<p1>:<p2>:<...>:<px>
The parameter order of the lenyadoc: protocol was chosen because it's
hard to separate things apart if it comes to the document id because of
the '/' used as parameter separator and as name separator in paths.
So I would say it was not a free chosen design decision but rather
driven by the technical limitations.
OK.
An alternative would be to introduce a general document locator syntax,
which would be the same as the "location" part of the lenyadoc:// URL:
doc-locator ::= /<pub-id>/<area>/<language>/<doc-id>
Actually, I would like to propose to use a different parameter separator
than the slash '/'. My favourite would be to use the colon ':' as it is
neither used in the document id nor in any other part used to pin down a
specific document. The advantage would be to be able to clearly separate
each part of a document url, plus no swallowing of '/' in sitemap
matchers.
So the scenario would be to use:
doc-locator ::= //<pub-id>:<area>:<language>:<doc-id>
for an absolute document url, or
doc-locator ::= /<language>:<doc-id>
>
for a document url relative to the current publication.
+1, although I'm still in doubt if we should support relative locators.
I think it is also a necessity to simplify the parameter passing in
the sitemap pipeline, especially to break the dependency on the
page-envelope module. It seems to be better to pass the parameters
explicitely to the pipeline with the same approach described above.
I agree.
This raises the question if we should even use the URL snippet for
the document locator, or rather a globally unique ID (either generated
by the system, or assigned upon document creation). This would allow
to match the document locator using a single asterisk, which would
probably simplify pipelines.
Thanks for your proposal, I share your concerns.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
