This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5925 - Schema used to assess instance validity
Summary: Schema used to assess instance validity
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Virginia Smith
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-31 20:45 UTC by Sandy Gao
Modified: 2008-12-09 18:04 UTC (History)
2 users (show)

See Also:


Attachments

Description Sandy Gao 2008-07-31 20:45:17 UTC
Related to bug 4797. Changes made under 4797 may help improve or fix this issue.

In the conformation section 8:

"1. In each instance document in the model, the [validity] property of the root element and all of its attributes and descendants MUST NOT be "invalid" when schema validity is assessed with respect to the referenced XML Schema documents in the model's definition documents. [XML Schema Structures]"

This has a few problems:

- Instance documents are assessed with respect to "schemas", not "schema documents".

- It's not clear what "the referenced XML Schema" mean. Instance documents do not need to reference schemas. As we've clarified, schemas are bound to instance documents (in ways not specified in the Core spec, but IF provides a way to do it.)

- "the referenced schema" assumes there is only one schema bound to each instance, but IF allows the same instance to be validated against multiple schemas (with different bindings).

Suggest to change the cited bullet to:

"1. In each instance document in the model, the [validity] property of the root element and all of its attributes and descendants MUST NOT be "invalid" when schema validity is assessed with respect to any schema that is bound to this instance document. [XML Schema Structures]

Note: How schemas are bound to instance document is not defined by this specification. Multiple schemas may be bound to the same instance document."
Comment 1 Pratul Dublish 2008-08-07 20:01:39 UTC
Resolution in 8/7 call - fix as per the proposal in Comment #1. Note to editors: This bug may have an overlap with 5797. 
Comment 3 John Arwe 2008-08-13 21:20:22 UTC
A question on how precisely we intend to use "schema" vs "schema document(s)".  I see that the editors used the exact proposed wording (A Good Thing), I also remember Sandy saying that those words were written somewhat hastily and might need to be tweaked.

IIRC, Schema folks use "schema" to mean the set of "in memory" schema components used to assess the validity of an instance, without regard to the origin of said components.  Thus, with respect to a single validity assessment episode, it is always singular.

IIRC, Schema folks use "schema document(s)" to mean one or more documents, that after parsing, result in schema components (a schema) being built.

----------
Excerpt 1:
In each instance document in the model, the [validity] property of the root element and all of its attributes and descendants MUST NOT be "invalid" when schema validity is assessed with respect to any schema that is bound to this instance document. [ XML Schema Structures ]

Comment: exactly matches my IIRC definitions.  "any schema" is valid because in http://www.w3.org/Bugs/Public/show_bug.cgi?id=5797#c2 the wg explicitly decided that, for any given model instance document, 0 schema documents might be bound to it... and I assume (Schema folks kindly confirm) this means it is possible that no schema (perhaps more precisely, a schema containing zero schema components) is used to assess the instance (laxly, per 5797).

----------
Excerpt 2:
Note:

How schemas are bound to instance documents is not defined by this specification. Multiple schemas may be bound to the same instance document.

Comment: by my IIRC definitions, should be changed as follows
from: Multiple schema         s may be bound
to  : Multiple schema documents may be bound

At this point I am neither advocating this nor proposing it, simply trying to motivate our Schema experts to think about it in advance of this week's meeting.
Comment 4 Sandy Gao 2008-08-14 14:36:38 UTC
> from: Multiple schema         s may be bound
> to  : Multiple schema documents may be bound

I did mean "schemas" in the proposal. In IF <schemaBindings>, it's possible that the same instance document appears under more than one <schemaBinding>s, which means that instance is bound to more than one *schemas*.

If this sentence becomes a source of confusion, maybe we can try:

"Multiple schemas may be bound to the same instance document. Each schema may be constructed from multiple schema documents."

This does run the risk of repeating things mentioned earlier, e.g. those in the conformance requirement list.
Comment 5 Kumar Pandit 2008-08-14 18:48:43 UTC
resolution on 8/14: fix accepted.