1)  There's a rule that got absorbed into the end of rule 2 of the combining rules. The rules are also specific to element ref -> global element -> simple type. They need to be generalised to handle the four combination cases you cite. Here's an amended set:

Rules

1.        Create an empty working set of "explicit" properties. Create an empty working set of "default" properties.

2.        Move to the innermost  schema component in the chain of references.

3.    Assemble its directly relevant "explicit" properties from its local dfdl:ref (if present) and its local properties (if present), the latter overriding the former (that is, local wins). Combine these with the current working set of "explicit" properties. It is a schema definition error if there is the same property appears twice. Result is a new working set of "explicit" properties. Obtain directly relevant "default" properties from in-scope unnamed dfdl:format block (if present).  Combine these with the current working set of "default" properties, the latter overriding the former (ie, inner wins). Result is a new working set of "default" properties.

4.   Move to the schema component that references the current component, and repeat step 3. If there is no referencing component, move to step 5.

5.        Validate the resultant set of properties. The "explicit" properties take priority, "defaults" only used when no "explicit" is present. It is a schema definition error if a required property is in neither the "explicit" nor the "default" working sets.

2) I think we should also define the property term "required". I think "directly relevant" could be replaced by "applicable" (I know "directly relevant" was my term :)

3) In Fig 5 you have dfdl:lengthKind on a xs:sequence - that is no longer allowed.

4) In Fig 5 I think you should add an extra applicable property to the dfdl:format in schema 1, to show how it gets picked up. Otherwise you are not showing how all the rules are being applied, and the statement "Nothing from the default dfdl:format block in SCHEMA1" will be mis-interpreted.

Regards

Steve Hanson
Programming Model Architect, WebSphere Message  Brokers,
OGF DFDL WG Co-Chair,
Hursley, UK,
Internet: smh@uk.ibm.com,
Phone (+44)/(0) 1962-815848

From:	Suman Kalia <kalia@ca.ibm.com>
To:	Alan Powell/UK/IBM@IBMGB
Cc:	dfdl-wg@ogf.org, dfdl-wg-bounces@ogf.org
Date:	21/10/2009 03:53
Subject:	Re: [DFDL-WG] DFDL Scoping v6
Sent by:	dfdl-wg-bounces@ogf.org

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

--
dfdl-wg mailing list
dfdl-wg@ogf.org
http://www.ogf.org/mailman/listinfo/dfdl-wg --
 dfdl-wg mailing list
 dfdl-wg@ogf.org
 http://www.ogf.org/mailman/listinfo/dfdl-wg

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU