Hi Kiran,
Except that you're not consistently using namespace prefixes--your schema has <element> tags bound to the xsd prefix and <key> et al bound to the null prefix--what you're doing looks fine to me... Stay tuned; this stuff is a high priority for us now, so hopefully in the next week or so you'll see some progress. Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 416-448-3519, T/L 778-3519 E-mail: [EMAIL PROTECTED] Kiran Halwai <[EMAIL PROTECTED]>@e34.esmtp.ibm.com on 04/20/2001 02:19:20 PM Please respond to [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Clarification: key/keyref Hi Neil , I checked out Xerces/java from CVS and built it. Now it's not even making sure that it has unique values for Key and also does not check for keyref values in key set. Here is the sample XSD and XML. I checked with both keeping prefix to schema (xsd:schema) and without keeping the prefix. Am I doing something wrong here? What all I want is ValidSet.ValidID should be unique and Values.ID should always be any one in ValidSet.ValidID set. Just trying to implement Primary Key using 'key' and Referential Key using 'keyref'. Please help ... Regards, Kiran ----------------------------------------------------- <?xml version="1.0"?> <xsd:schema xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"; targetNamespace="my.trial" xmlns:my="my.trial" elementFormDefault="qualified"> <xsd:element name="trial"> <xsd:complexType> <xsd:sequence> <xsd:element name="ValidSet" type="my:ValidSetType" maxOccurs="unbounded"/> <xsd:element name="Values" type="my:ValuesType" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> <key name="valid_values"> <selector xpath="my:ValidSet"/> <field xpath="my:ValidID"/> </key> <keyref name="value" refer="valid_values"> <selector xpath="my:Values"/> <field xpath="my:ID"/> </keyref> </xsd:element> <xsd:complexType name="ValidSetType"> <xsd:sequence> <xsd:element name="ValidID" type="xsd:positiveInteger"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="ValuesType"> <xsd:sequence> <xsd:element name="ID" type="xsd:positiveInteger"/> </xsd:sequence> </xsd:complexType> </xsd:schema> ----------------------------------------------------- <?xml version="1.0"?> <trial xmlns = "my.trial" xmlns:my="my.trial" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"; xsi:schemaLocation = "my.trial keykref.xsd"> <ValidSet> <ValidID>1</ValidID> </ValidSet> <ValidSet> <ValidID>1</ValidID> </ValidSet> <Values> <ID>1</ID> </Values> <Values> <ID>3</ID> </Values> </trial> ----------------------------------------------------- [EMAIL PROTECTED] wrote: > Hi Kiran, > > Since I'm not sure the users list has been kept quite up to date with the > status of features in the CVS repository, here's where I think we're at: > > block and final are now supported. > fixed/default values of elements are supported except in the case of mixed > content models (coming soon). Quite a number of constraints are supported, > and more will be added soon. > I think Elena is working on nillable as we write. > Support for identity constraints will also hopefully be improved soon. > > Alpha testing on any or all of these features is always appreciated; all > you need to do is checkout Xerces from CVS (instructions available off of > the http://xml.apache.org site) and build it. > > Hope that helps, > Neil > > Neil Graham > XML Parser Development > IBM Toronto Lab > Phone: 416-448-3519, T/L 778-3519 > E-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
