Re: [wsbpel] 20040902 schema comments / RNC version

[David RR Webber <david@drrw.info>]

Team,

Just wanted to capture this reference to W3C schema over in our archive 
- since we are also using the
##ANY content model for the latest noun adaptions - and so I thought 
this would
be interesting background reading.

Enjoy, DW
========================

Alex Yiu wrote:

>
> Hi, Paul and all others,
>
> [Note: I have exchanged a number of emails with Paul in private 
> already. I would like to share our conversation to the general public.]
>
> For item (2):
> I have confirmed with our XSD team at Oracle.  [Millions thanks to 
> their help and advice.]
> <xsd:anyAttribute namespace="##other"  .../> actually requires a 
> namespace-qualified attribute. Therefore, its semantics fits our 
> expectation.
>
> See section 3.10.2:
> http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#declare-openness
> ------------------------------------------------------
>
> *##other*
>     a pair of /not/ and the ·actual value·
>     <http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#key-vv> of
>     the |targetNamespace| [attribute]
>     <http://www.w3.org/TR/xml-infoset/#infoitem.element> of the
>     <schema>
>     <http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#element-schema>
>     ancestor element information item if present, otherwise ·absent·
>     <http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#key-null>. ------------------------------------------------------
>
>
> _*AND*_, Section 3.10.4: (Validation 2.* for "##other")  
> http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#section-Wildcard-Validation-Rules
> ------------------------------------------------------
> *Validation Rule: Wildcard allows Namespace Name*
> For a value which is either a namespace name or ·absent· 
> <http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#key-null> to be 
> ·valid· <http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#key-vn> 
> with respect to a wildcard constraint (the value of a {namespace 
> constraint} 
> <http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#namespace_constraint>) 
> *one* of the following must be true:
> 1 The constraint must be /any/.
> 2 *All* of the following must be true:
> 2.1 The constraint is a pair of /not/ and a namespace name or ·absent· 
> <http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#key-null> 
> ([Definition:]  call this the *namespace test*).
> 2.2 The value must not be identical to the ·namespace test· 
> <http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#key-nst>.
> 2.3 The value must not be ·absent· 
> <http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#key-null>.
> 3 The constraint is a set, and the value is identical to one of the 
> members of the set.
> ------------------------------------------------------
>
> For item (10):
> There is a real reason to have multiple documentation. Please note 
> that the documentation is i18N ready with xml:lang attribute. Users of 
> an international BPEL project may need to document the same BPEL with 
> different languages. And, again we borrow this design pattern from XML 
> Schema itself.
>
> Thanks!
>
> Regards,
> Alex Yiu
>