Mark,
If this entails less changes and is a viable solution, +1.
> ford: As we discussed this specification internally it became clear
> that the main difference between queries and expressions is that
> queries have a context while expressions do not. One way of achieving
> this is to remove queryLanguage from the process altogether. This is
> how the issue was originally framed in the issue description.
>
> Another way of achieving this same goal but with fewer changes would
> be to restore the query option in the <from> and <to> variants that
> had queries with a variable as the context.
>
> Therefore, I propose the following to restore the distinction between
> queries and expressions:
>
> 1. Change existing <to> query variant to match existing <from>
> expression variant.
>
> *<to expressionLanguage=”expr-lang”>expr</to>*
>
> 2. restore the query option in the <from> and <to> that take
> variables and have them look and behave the same as
> propertyAlias queries
>
> *<from variable=”BPELVariableName” part=”NCName”?>*
>
> * <query queryLanguage=”query-lang”?>?*
>
> *query-exp*
>
> * </query>*
>
> *</from>*
>
> * *
>
> *<to variable=”BPELVariableName” part=”NCName”?>*
>
> * <query queryLanguage=”query-lang”?>?*
>
> * query-exp*
>
> * </query>*
>
> *</to>*
>
> I appreciate any feedback on this issue before I embark on submitting
> a formal proposal. The proposal will include the current version of
> the spec with only the edits for this issue appearing as changes.
>
> Thanks
>
