Re: [XPath30] erroneous text in "2.2.4 Consistency Constraints"

I think the text is correct. It's saying that if there is a reference to X then there must also be a declaration of X, for example, if there is an element declaration with type T in the in-scope schema definitions, then there must be a type T in the in-scope schema definitions.

Note that XSD itself doesn't have this requirement (although many implementations do). In XSD (see 1.1 part 1 §5.3) missing components don't make the schema invalid, they just cause validation to fail if the missing component is actually needed.

Michael Kay
Saxonica

> On 19 Jun 2018, at 06:48, Mukul Gandhi <gandhi.mukul@gmail.com> wrote:
> 
> Hi all,
>    In the section "2.2.4 Consistency Constraints" of XPath 3.0 spec, the 3rd bullet point says,
> 
> "Any reference to a global element, attribute, or type name in the in-scope schema definitions must have a corresponding element, attribute or type definition in the in-scope schema definitions."
> 
> I think, this text is wrong and should not be there (or must be modified appropriately). In the above cited text, both the source and target is mentioned as "in-scope schema definitions" which doesn't look right to me.
> 
> 
>  
> 
> -- 
> Regards,
> Mukul Gandhi