[
Lists Home |
Date Index |
Thread Index
]
Hi,
> regarding updates -- I had a question how updates work with wildcards.
>
> I presume the following schema is correct..
>
> <xs:element name="billTo">
> <xs:complexType>
> <xs:sequence>
> <xs:element name="name" type="xs:string"/>
> <xs:element name="address" type="xs:string"/>
> <xs:element name="zip" type="xs:integer"/>
> <!-- extension. one can put anything here -->
> <xs:any namespace="#all" processContents="skip" />
> </xs:sequence>
> </xs:complexType>
> </xs:element>
>
> now, consider the tree (impractical, but still..)
>
> <billTo>
> <name>ABC</name>
> <address>California</address>
> <zip>90095</zip>
> <zip>90024</zip>
> </billTo>
>
> Now consider an update (delete the first zip element) --
>
> <billTo>
> <name>ABC</name>
> <address>California</address>
> <zip>90024</zip>
> </billTo>
>
> Now, I hope both the documents are valid w.r.to the schema?? -- also, will
> the type assignment for <zip>90024</zip> change during the update??
Yes. In the first instance <zip>90024</zip> will be matched by the wildcard
and therefore will have the type xs:anyType (I think). In the second instance
<zip>90024</zip> will be matched by the zip element declaration and hence have
the type xs:integer.
Cheers,
/Eddie
>
> cheers and regards - murali.
>
> On Wed, 29 May 2002, Dare Obasanjo wrote:
>
> > > Anyways, my question is -- where will the type names and
> > > element declarations associated with an element information
> > > item in PSVI be used?
> >
> > I've seen user scenarios where both are needed.
> >
> > 1.) The type names for element declarations are useful for type based
> > queries like those that will exist in Xpath 2.0 and XQuery.
> >
> > EXAMPLE: /myco:company-roster/myco:employee[. instance of element of
> > type myco:managerType]
> >
> > where myco:managerType is a complexType defined in the schema.
> >
> > 2.) Currently MSXML ships with the ability to obtain the Schema Object
> > Model (SOM) object that represents an element or attribute declaration
> > from a DOM instance. Our users love it and we are inundiated with
> > requests to provide similar functionality for the .NET frameworks
> > version of the DOM. One user scenario involved creating a schema-aware
> > XML text editor and using the element decls for the particular element
> > being edited to determine whether the edits were valid or not which was
> > way more performant than validating on each edit.
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
|
