Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Namespaces in Attribute Value..

From: Ashok <ashoksrini@-----.--->
To: Michael Kay <mhk@---.--.-->, xmlschema-dev@--.---
Date: 5/12/2004 1:30:00 PM

I tried using xs:QName..but I am not getting the
behaviour I wanted.

Here is what I am trying to do..(a little long read!)

Lets take this example schema extract:

<xs:element name="Quantity">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:float">
	<xs:attribute name="Item" type="xs:QName"/>
      </xs:extension>
     </xs:simpleContent>
   </xs:complexType>		
</xs:element>

When I author this using an Schema editor (Stylus
etc), and validate the schema it passes.

Now I change the attribute definition to 

<xs:attribute name="Item" type="abc:ItemType"/>

I validate schema and my schema editor throws the
error:
1 - Prefix: 'abc' can not be resolved to a URI
2 - SimpleType (:ItemType) for attribute: Type not
found

I want to achieve exactly the same kind of behavior as
above in my schema/instance document i.e throw this
kind of error while validating my instance document.

I defined an instance document and associated it with
the above valid schema. The instance document:

<Quantity Item="abc:Gas">234.34</Quantity>

When I validate this document, I DONT get the errors I
expect. I expected:
1- Prefix: 'abc' can not be resolved to a URI
2- SimpleType (:Gas) for attribute: Item not found


Is this possible to achieve using schemas? If so what
am I missing?

Or is it that Schema Editors have special
logic/processing in them to validate XSD's only and
flag those errors?


Thanks



--- Michael Kay <mhk@m...> wrote:
> This is what type xs:QName is for.
> 
> Michael Kay 
> 
> > -----Original Message-----
> > From: xmlschema-dev-request@w... 
> > [mailto:xmlschema-dev-request@w...] On Behalf Of
> Ashok
> > Sent: 11 May 2004 19:58
> > To: xmlschema-dev@w...
> > Subject: Namespaces in Attribute Value..
> > 
> > 
> > Hi..
> > 
> > I want to know how to validate instance documents
> that
> > has an attribute, and the value of the attribute
> is of
> > form "prefix:value".
> > 
> > To explain more clearly...
> > 
> > I have an instance document:
> > 
> > <Documents 
> >    xmlns:dd="http://test.uri.org"
> >   
> >
> xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance"
> >    xsi:schemaLocation="http://test.uri.org
> >                        c:/document.xsd">
> > 
> >    <document doctype="dd:PurchaseOrder"/>
> > 
> > </Documents>
> > 
> > How can I validate this document, such that the
> schema
> > validator checks that value of doctype attribute,
> > "PurchaseOrder" exists in namespace "dd" defined
> in
> > "document.xsd" file? Do I have to define 'doctype'
> > attribute differently in the schema?
> > 
> > This is similar to how we define type attribute in
> > standard XML schema:
> > <xsd:element name="Catalog" type="xsd:string">
> > 
> > Any pointers? 
> > 
> > Thanks
> > 
> > 
> > 	
> > 		
> > __________________________________
> > Do you Yahoo!?
> > Win a $20,000 Career Makeover at Yahoo! HotJobs  
> >
> http://hotjobs.sweepstakes.yahoo.com/careermakeover 
> > 
> > 
> 



	
		
__________________________________
Do you Yahoo!?
Yahoo! Movies - Buy advance tickets for 'Shrek 2'
http://movies.yahoo.com/showtimes/movie?mid=1808405861 

From mhk@m...  Thu May 13 05:23:32 2004
Return-Path: <mhk@m...>
X-Original-To: xmlschema-dev@l...
Delivered-To: xmlschema-dev@listhub.


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent