OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsbpel] Issue - 289 - draft text to describe the relationshipXML Schema and Spec



Hi all,

Here is an updated proposed text (with more input from Martin)
---------------------
Where there is disagreement between the separate XML schema files, the 
XML schemas in the appendices, any pseudo-schema in the descriptive 
text, and the normative descriptive text, the normative descriptive text 
will take precedence over the separate XML Schema files. The separate 
XML Schema files take precedence over any pseudo-schema and over any XML 
schema included in the appendices.

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 only but not valid 
according to the normative descriptive text.
---------------------

Regards,
Alex Yiu


Alex Yiu wrote:

>
> 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
>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]