* Saga look & feel?
-> what exactly is this?
-> maybe it should be explecitely defined where
it is first mentioned.

page 31:
for objects implementing the error_handler interface:
comment: is this really the best solution. Isn't it 
better to have explicit clear() method, in this way you 
can execute a batch of operations / call on the object,
and just check for any error at the end. This 
way of programming is much more in use than checking for
errors after each call.

page 32:
error states (exceptions)...
comment: maybe more OO: exceptions (error states).

page 33:
can "notimplemented" be thrown on creation of the object?

page 39:
is there a reason why in a case an exc. is raised in task, 
the parent is returned -> explanation could halp.
in addition it is a bit conflicting with the concept
priorly described, where the task implements the error_interface.

* what is metric??
-> define purpose of metric on the first use

* missing a short description of the object types?
could help understanding th types at this point in document.

page 49:
does it make sense to have a session with no context?
(assuming, that you can remove the default context).

page 51:
it could prove useful to be able to select context.
i.e. session.make_current(context);

page 58:
an overload of the "," seperator would be appreciated
?? what is the advantage of triming the leading " ".

page 56: a sentance on what exactly the attribs can be used
could help understanding the paragraph (specially the part with
reised exceptions.

page 61:
timeout exception is not mentioned as possible exception up to now.
-> a complete list of exceptions.

page 93:
purpose of task, task vs. job -> a short explanation
could be given, to ease understanding the following sections

page 122:
"CPUTimeLimit"
number of cpu (UCase) seconds consumed by the job
?? Check the JSDL??