OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Attributes v Elements

----- Original Message -----
From: "Iain W Fergusson" <fergusson_iain@jpmorgan.com>
To: <duane@xmlglobal.com>
Cc: <Pcj@Inxar.Org>; <Tom.D.Conder@Lmco.Com>; <xml-dev@lists.xml.org>
Sent: Thursday, May 17, 2001 11:25 AM
Subject: Re: Attributes v Elements

> >You would be better off to use a more definitive description of what the
> >monetary value is.   "USDollar" is really the value for "Currency".  Try
> >something like this:
> >
> ><Price currency="USD">10</Price>
> >
> In the above example <price> has to be described in XML Schema using a
> <complexType>, because of the presence of the currency attribute.
> There is then no way of constraining the contents of <price> to be a
> If you need to validate that <price> is a number, it has to be a
> which cannot have attributes.

This is incorrect. There is no problem describing the Price element and
constraining the content to be a number. XML Schema provides facilities for
describing types with attributes and constrained text content. The type
definition would look like this;

<xs:complexType name='PriceType' >
    <xs:extension base='xs:decimal' >
      <xs:attribute name='currency' type='xs:string' />

a global element declaration could then be used to reference the PriceType;

<xs:element name='Price' type='PriceType' /> <!-- playing fast and loose
with namespaces for brevity -->


Martin Gudgin