Re: Option syntax

/ Innovimax SARL <innovimax@gmail.com> was heard to say:
| It seems one more time impression are conflicting with statement

Right. We need to say what you suggested:

| <p:option
|  name = QName
|  select = XPath expression>
|   (p:pipe |
|    p:document |
|    p:inline)?
| </p:option>
|
| Then what is the context of the XPath evaluation when none is
| specified ? an empty sequence ? the default readable port ? something
| other ?

I think we should say that if an explicit context is not given then
there is no context. In that case, any expression that makes reference
to the context (by using "/", or position(), or anything else that
would refer to the context) is an error.

The JAXP API is already spec'd this way and I think other XPath APIs
are similar.

Without a context, you can still resolve variable references, perform
string manipulations, etc. so it is valuable.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Wink at small faults; for thou has
http://nwalsh.com/            | great ones.--Thomas Fuller (II)