Issue - R50 - resolution

This issue was received after the close
of the public review period, so the TC is not required to formally consider
it and vote on a disposition.  In the interest of completeness, I
asked Peter to put it on the list with a closed no change status and link
some of the relevant email that explains that.   

Regards, Diane

IBM  Emerging Internet Software Standards



(919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709

----- Forwarded by Diane
Jordan/Raleigh/IBM on 01/30/2007 10:26 AM -----

ws-bpel issues list editor
<> 

01/29/2007 09:06 AM

Please respond to



To



cc

Subject

[wsbpel] Issue - R50 - validating non-XML
format message (soap with attachment)

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 - R50 - validating non-XML format message (soap
with attachment)

Status: received

Date added: 29 Jan 2007

Origin: Public comment (public
comment list)

Date submitted: 25 Jan 2007

Submitter: Jingfeng
Li

Description: In the current version of the spec, it implies that the
message is XML format. The "validate" can be used to perform
the validation checking of the XML format message. 

But, what happens if the message is a soap with attachment?
For example, how to check its format, or do something like query some part
of its?

Links: John
Evdemon, 26 Jan 2007     Mary
McRae, 26 Jan 2007

Changes: 29 Jan 2007 - new issue

To comment on this issue (including whether it should be
accepted), please follow-up to this announcement on the 
list (replying to this message should automatically send your message to
that list), or ensure the subject line as you send it starts "Issue
- R50 - [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 - R50 - Proposed resolution", without any Re: or
similar. 

To add a new issue, see the issues procedures document