[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Quiz: what's the value space of the <Publisher> element?

  • From: "Michael Kay" <mike@saxonica.com>
  • To: "'Costello, Roger L.'" <costello@mitre.org>,<xml-dev@l...>
  • Date: Mon, 22 Jun 2009 17:00:37 +0100

RE:  Quiz: what's the value space of the <Publisher> element?
> 
> Consider this element declaration:
> 
>     <xs:element name="Publisher" type="xs:string"/>
> 
> What is Publisher's value space? 

Technically, an element does not have a value space. Only a type has a value
space. The value space here is clearly the set of all (legal XML) strings.
> 
> 
> The Publisher element is being used by Book:
> 
> 
>     <xs:element name="Book">
>         <xs:complexType>
>             <xs:sequence>
>                 <xs:element name="Title" type="xs:string"/>
>                 <xs:element name="Author" type="xs:string"/>
>                 <xs:element name="Date" type="xs:gYear"/>
>                 <xs:element name="ISBN" type="xs:string"/>
>                 <xs:element ref="Publisher" />
>             </xs:sequence>
>         </xs:complexType>
>     </xs:element>
> 
> 
> Okay, what is Publisher's value space?

Again, wrong terminology. But the set of things that can appear within a
Publisher that appears within a Book is potentially constrained both by the
type of the Book element and by the type of the Publisher element.

> 
> XML Schema 1.1 has a new element, the <assert> element. It 
> can impose additional constraints on the Publisher element. 
> For example, the <Book> element is nested within a 
> <BarnesAndNoble> element, which has an <assert> element that 
> constrains the Publisher element to a maximum string length 
> of 140 characters:
> 
> 
>     <xs:element name="BarnesAndNoble">
>         <xs:complexType>
>             <xs:sequence>
>                 <xs:element ref="Book" maxOccurs="unbounded" />
>             </xs:sequence>
>             <xs:assert 
> test="not(Book[string-length(Publisher) gt 140])" />
>         </xs:complexType>
>     </xs:element>
>

Nothing new here: you could also use key/keyref at the level of a Book to
constrain what can appear in the Publisher element.
> 
> What this means is that an element declaration cannot be 
> understood on its own, in isolation. 
> 
> To understand an element you must understand all possible 
> ancestors of the element. 
> 

Not really. The system is designed so that the set of valid Publisher
elements is determined by the type of the Publisher element; but if you want
to say that not all valid values of Publisher are allowed when the Publisher
is a book publisher, then you can do so. For example, you might have some
way of excluding magazine publishers.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay  



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.