Fw: [wsbpel] Issue - 289 - draft text to describe the relationship XMLSchema and Spec

Am I right in thinking that we don't
have the xsd in the spec now, only a place holder appendix for it?  

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 08/09/2006 06:35 PM -----

"John Evdemon"
<> 

08/09/2006 12:56 PM

To

"Alex Yiu" <>,
"wsbpeltc" <>

cc

Subject

RE: [wsbpel] Issue - 289 - draft text
to describe the relationship XML Schema and Spec

Martin asked that we include clarification about the
which resource should be authoritative - the XSD or the spec.  I think
we are in agreement that it should be the spec. 

This raises another potential issue in that the spec contains a copy of
the XSD.  

I like Monica's suggestion to remove the copy of the XSD from the spec
because it reduces the size of the spec and avoids the potential problem
of getting out of sync with the actual XSD.

John

> -----Original Message-----

> From: Alex Yiu [mailto:]

> Sent: Wednesday, August 09, 2006 9:35 AM

> To: wsbpeltc

> Cc: Alex Yiu

> Subject: [wsbpel] Issue - 289 - draft text to describe the relationship

> XML Schema and Spec

> 

> 

> Hi all,

> 

> Here is the draft text to describe the relationship XML Schema and
Spec

> (so far ...)

> ---------------------

> XML Schemas are normative artifacts derived from the normative

> descriptive text in the specification. XML Schemas only enforce a

> subset

> of constraints described in the normative descriptive text. Hence,
a

> WS-BPEL artifact, such as a process definition, can be valid according

> to the XML Schemas but not valid by the normative specification text.

> When there is a conflict between XML schemas and the normative

> descriptive text, the normative descriptive text will take precedence

> over XML Schemas.

> ---------------------

> 

> 

> Regards,

> Alex Yiu