- From: Kasimier Buchcik <kbuchcik@4commerce.de>
- Date: Wed, 27 Apr 2005 13:43:32 +0200
- To: Kasimier Buchcik <kbuchcik@4commerce.de>
- Cc: XML-SCHEMA <xmlschema-dev@w3.org>
Hi, It might be that I found an answer for my question: In "3.2.5 Attribute Declaration Information Set Contributions" we have the following: "If the attribute information item was not ·strictly assessed·, then instead of the values specified above, 1 The item's [schema normalized value] property has the ·initial value· of the item as its value; 2 The [type definition] and [member type definition] properties, or their alternatives, are based on the ·simple ur-type definition·." The question - now more clearly definable for me - if an attribute, which was not strictly assessed, can be a target for IDCs fields, could be answered with yes, assuming IDCs use the PSVI when evaluating. Is this correct? I dearly need some advice here, even if it reveals to be an "implementation dependant" thingy. Regards, Kasimier On Tue, 2005-04-26 at 19:41 +0200, Kasimier Buchcik wrote: > Hi, > > On Tue, 2005-04-26 at 19:36 +0200, Kasimier Buchcik wrote: > > Hi, > > > > how to handle the following scenario? > > > > - an attribute was validated against a "skip" wildcard > > - OR an attribute was validated against a "lax" wildcard and no > > corresponding declaration was existent > > - an IDC field evaluated to such an attribute > > > > Validation rule "Identity-constraint Satisfied" says: > > > > "3 For each node in the ·target node set· all of the {fields}, with that > > node as the context node, evaluate to either an empty node-set or a > > node-set with exactly one member, which must have a simple type" > > > > Should such an attribute have a simple type? Should we fall back > > to "anySimpleType" here - similar to elements, where we fall back to > > "anyType" if the wildcard was "lax"? > > > > Example: > > > > Schema: > > <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"> > > <xsd:element name="foo"> > > <xsd:complexType> > > <xsd:anyAttribute namespace="##any" processContents="skip"/> > > </xsd:complexType> > > <xsd:key name="aKey"> > > <xsd:selector xpath="."/> > > <xsd:field xpath="@bars"/> > > Correction: this should be <xsd:field xpath="@bar"/> > > > </xsd:key> > > </xsd:element> > > </xsd:schema> > > > > Instance: > > <foo bar="abc"/> > > > > XSV 2.8 reports: > > > > "missing one or more fields [<XSV.util.xpath.XPath instance at > > 0x0131A120>] from key {None}aKey > > > > while Xerces-J 2.6.2 and MSXML 4.0 both eat it. > > Kasimier
Received on Wednesday, 27 April 2005 11:43:38 UTC