I
think that is effectively what I caught in the issues list (which I updated
during the meeting), but all in one sentence - 2nd para
reads:
An extension syntax token, in the form of an
element or attribute qualified by a "namespace" identified in an
<extension> element that is used outside of an <extension> element,
MUST be included in the BPEL process's definition in order to actually apply an
extension semantics to a BPEL process. It is this extension syntax token, rather
than the extension declaration, that indicates that new/changed semantics apply.
is
that ok ? The first sentence is rather long.
Peter
That is pretty close
Diane. We just need to put the word "extension" at the end of the first
sentence in <>'s to convey that we mean the <extension> element
defined in WS-BPEL rather than any generic extension. Like below
..
Add a clarification of the meaning of
extension syntax token by the following sentence to say "in the form of an
element or attribute qualified by a namespace declared through an
<extension> element " . An extension syntax token, in the form of an element or
attribute that is used outside of an <extension> element, MUST be
included in the BPEL process's definition in order to actually apply an
extension semantics to a BPEL process.
Regards,
Prasad
Diane Jordan wrote:
The amendment as I wrote it
down (and reread it to the group) awas: Add a clarification of the meaning of extension syntax token by the
following sentance to say "in the form of an element or attribute qualified
by a namespace declared through an extension element " .
An extension syntax token, in the
form of an element or attribute that is used outside of an <extension>
element, MUST be included in the BPEL process's definition in order to
actually apply an extension semantics to a BPEL process.
Is this closer to what you
expected?
Regards, Diane IBM
Emerging Internet Software Standards drj@us.ibm.com (919)254-7221 or
8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709
Hi,
The 1st amendment to the proposed resolution for issue
92.6 as captured in the 1st half of the minutes
reads,
"‘extension syntax token’ will be better defined and
clarified. An extension syntax token, in the form of an extension or
attribute declared through an extension element that is used outside of
an extension element."
That does not read well at all or make
sense to me. I believe it was more in the lines of
"An
extension syntax token, in the form of an element or attribute qualified
by an extension namespace and used outside of an <extension>
element MUST be included in the BPEL process's definition
..."
Does anyone have a better recollection?
Regards,
Prasad
jevdemon@microsoft.com
wrote:
>The document named DRAFT Minutes for 7/13/2005 Conference
Call >(2005-07-13-WS-BPEL-Minutes.pdf) has been submitted by John
Evdemon to the >OASIS Web Services Business Process Execution Language
(WSBPEL) TC document >repository. > >Document
Description: > > >View Document Details: >http://www.oasis-open.org/apps/org/workgroup/wsbpel/document.php?document_id=13610 > >Download
Document: >http://www.oasis-open.org/apps/org/workgroup/wsbpel/download.php/13610/2005-07-13-WS-BPEL-Minutes.pdf > > >PLEASE
NOTE: If the above links do not work for you, your email
application >may be breaking the link into two pieces. You may
be able to copy and paste >the entire link address into the address
field of your web browser. > >-OASIS Open Administration >
>
--------------------------------------------------------------------- To
unsubscribe from this mail list, you must leave the OASIS TC
that generates this mail. You may a link to this group and all your
TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
|