> From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]] > > Vadim Gritsenko wrote: > > > > > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] > > > > > > - only match is allowed as top-level element > > > > It is not correct. > > No, it *is* correct. You are proposing to change what the original > design was (which is totally fair) but it's wrong to state that the > above is incorrect.
Ok, yes, it might be correct - do not remember original design in much details :) What I meant is it looks to me like it is not logical. > > I propose to allow following constructs: > > * map:match > > * map:select > > * map:act > > I'm +5 on this, and can help implement this if everybody agrees. > > ok, for act, but select? Actually, I'm surprised that people are to add actions first, not selectors. Selectors look like first and obvious choice for promoting them as first-class sitemap citizens: I do not see lots of difference between them and matchers. Consider an example of root sitemap: <map:select type="host"> <map:when test="www"> <map:mount/> <map:when/> <map:when test="one"> <map:mount/> <map:when/> <map:when test="two"> <map:mount/> <map:when/> <map:otherwise> <map:mount/> <map:otherwise/> </map:select> And creating WildcardURISelector and RegexpURISelector does not look like a challenge. Don't you think that matchers and selectors should have same rights? Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]