Hi,
before we continue discussion things like pre/intra/post-matching actions,
can someone summarize the current semantics of the sitemap as it *should*
be? I can only describe it, as it is currently implemented:
- only match is allowed as top-level element
- the sitemap is processed top-down, the processing stops:
* when a serialize is reached
* when a reader is reached
* when the end is reached
- match: if match successful, processing continues inside
- select: if a test is successful, processing continues inside this test
else processing continues in otherwise
- act: action is executed. If it returns something, processing
is executed inside the element
- generate: generator is added to pipeline
- transform: transformer is added to pipeline
- serialize: serializer is added to pipeline, processing ends
- reader: reader is added to pipeline, processing ends
So the first question to answer is: is this the semantics wanted for 2.0?
Or do we have any bugs?
Nice weekend,
Carsten
<snip all>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
