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 2113 - R-124: A question about PSVI properties
Summary: R-124: A question about PSVI properties
Status: NEW
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.0 only
Hardware: All Windows 3.1
: P2 normal
Target Milestone: ---
Assignee: David Ezell
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: needsDrafting
Depends on:
Blocks:
 
Reported: 2005-09-09 15:15 UTC by Sandy Gao
Modified: 2012-12-04 00:52 UTC (History)
0 users

See Also:


Attachments

Description Sandy Gao 2005-09-09 15:15:06 UTC
There are various statements in the spec of the form: "If some condition, x, is 
true, then, in the post-schema-validation infoset it has the properties 
a,b,c ..."

For example: 

"If an element is valid with respect to a type definition, as per Element 
Locally Valid (Type), in the post-schema-validation infoset the item has a 
property ... 

Furthermore, the item has one of the following alternative sets of properties: 

[type definition] 

... 

" 
Is it true that if condition x does *not hold*, then the processor is *not 
permitted* to include properties a,b,c in the PSVI, even if such information is 
available? I'm assuming this is what was intended, based on the clarifications 
drafted for the Query WG on the topic of PSVI. 

If this is the case, should the Structures spec clarify this? ...perhaps with 
wording similiar to: "The properties a, b, c are in the PSVI if and only 
if ..." 

As an aside, wouldn't it be useful to get at type information for an element 
that was not valid, if the processor had that information?