[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] Issue - R36 - Wrong description of attribute queryLanguage
Thanks for clarification. After reading your issue description more carefully, I see what you mean now. (i.e. on whether process queryLanguage default applies to propertyAlias). And, I am with you now. Regards, Alex Yiu Thomas Schulze wrote: >Hi Alex, > >Of course, issue 305 has not removed attribute queryLanguage in ><vprop:query>, sorry if this is not clear enough described in the issue R36 >text. Issue 305 added an own default for attribute queryLanguage in ><vprop:query> (see friendly amendment). Means, if the attribute is not >given on <vprop:query> the value specified on <process> is no longer >inherited, <vprop:query> has it's own default (that is XPath 1.0). >The in R36 mentioned text from the spec talks only about queryLanguage on ><process>. Since this attribute shares only the name with attribute >queryLanguage in <vprop:query> and nothing else, I would suggest to not >mention properties in this paragraph. > >Kind regards, > >Thomas > > > > > Alex Yiu > <alex.yiu@oracle. > com> To > wsbpel@lists.oasis-open.org, Thomas > 09.11.2006 23:23 Schulze/Germany/IBM@IBMDE > cc > Alex Yiu <alex.yiu@oracle.com> > Subject > Re: [wsbpel] Issue - R36 - Wrong > description of attribute > queryLanguage > > > > > > > > > > > >Hi Thomas, > >I am not sure what I follow you: >Thomas wrote: > Since issue 305, attribute queryLanguage of element <process> is no > longer applicable for a propertyAlias, so property definitions should > not be mentioned here > >As of this now, the spec text and XSD both define ><vprop:propertyAlias>...<vprop:query> with queryLanguage attribute. > >Issue 305 proposal did not remove queryLanguage fromp propertyAlias. >It make the usage of queryLanguage and expressionLanguage more consistent >under <from> and <to> > >Regards, >Alex Yiu > > >ws-bpel issues list editor wrote: > > > This issue has been added to the wsbpel issue list with a status of > "received". The status will be changed to "open" if a motion to open > the issue is proposed and that motion is approved by the TC. A motion > could also be proposed to close it without further consideration. > Otherwise it will remain as "received". > > > The issues list is posted as a Technical Committee document to the > OASIS WSBPEL TC pages on a regular basis. The current edition, as a > TC document, is the most recent version of the document entitled in > the "Issues" folder of the WSBPEL TC document list - the next posting > as a TC document will include this issue. The list editor's working > copy, which will normally include an issue when it is announced, is > available at this constant URL. > > > Issue - R36 - Wrong description of attribute queryLanguage > Status: received > Date added: 9 Nov 2006 > Date submitted: 08 November 2006 > Submitter: Thomas Schulze > Description: On page 23, section 5.2, lines 8-11 (first bullet), it > says: > "queryLanguage. This attribute specifies the query language > used in the process for selection of nodes in assignment, > property definition, etc. The default value for this attribute > is: " urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0", which > represents the usage of [XPath 1.0] within WS-BPEL 2.0." > The wrong description here is the part ", property definition, etc". > Since issue 305, attribute queryLanguage of element <process> is no > longer applicable for a propertyAlias, so property definitions should > not be mentioned here, IMHO. So, except for assignments this > attribute does not influence any other constructs, means "etc." is > not needed, too. > Submitter's proposal: Remove ", property definition, etc". > Changes: 9 Nov 2006 - new issue > > > > To comment on this issue (including whether it should be accepted), > please follow-up to this announcement on the > wsbpel@lists.oasis-open.org list (replying to this message should > automatically send your message to that list), or ensure the subject > line as you send it starts "Issue - R36 - [anything]" or is a reply > to such a message. If you want to formally propose a resolution to an > open issue, please start the subject line "Issue - R36 - Proposed > resolution", without any Re: or similar. > > > To add a new issue, see the issues procedures document > > > > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]