Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] XML Schema assistance

From: "Chiusano Joseph" <chiusano_joseph@---.--->
To: "Ray Cauchi" <ray@-----.---.-->, <xml-dev@-----.---.--->
Date: 11/2/2004 12:33:00 PM
In general, you'll want to declare local <title> elements for those 
places in which their declarations differ from the global declarations. This is 
necessary because these differing <title> elements have the same name as 
the global <title> element but a different format.
 
Kind Regards,
Joseph Chiusano
Booz Allen Hamilton
Strategy and Technology Consultants to 
the World
 


  
  
  From: Ray Cauchi [mailto:ray@t...] 
  
Sent: Monday, November 01, 2004 11:57 PM
To: 
  xml-dev@l...
Subject: [xml-dev] XML Schema assistance 
  


  Hi folks

I have defined a W3C XML Schema that allows markup 
  of Policy documents. (BTW - I am new at schema design!)

A valid xml 
  structure follows:

<?xml version="1.0" encoding="UTF-8"?>
<policy xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
  xsi:noNamespaceSchemaLocation="myschema.xsd">
<X-TAB>        </X-TAB><section>
<X-TAB>        </X-TAB><X-TAB>        </X-TAB><title>Section 1 Title</title>
<X-TAB>        </X-TAB><X-TAB>        </X-TAB><clause>string text</clause>
<X-TAB>        </X-TAB></section>
<X-TAB>        </X-TAB><section>
<X-TAB>        </X-TAB><X-TAB>        </X-TAB><title>Section 2 Title</title>
<X-TAB>        </X-TAB><X-TAB>        </X-TAB><clause>string text</clause>
<X-TAB>        </X-TAB><X-TAB>        </X-TAB><clause>more text</clause>
<X-TAB>        </X-TAB></section>
<X-TAB>        </X-TAB><section>
<X-TAB>        </X-TAB><X-TAB>        </X-TAB><title>Section 3 Title</title>
<X-TAB>        </X-TAB><X-TAB>        </X-TAB><clause>text - <link 
  href="http://www.website.com/">a link</link></clause>
<X-TAB>        </X-TAB></section>
</policy>

So you can see 
  that each main section of a document is marked up as a 
  <section></section>, and each section must have a 
  <title></title>

No problem, the schema works fine as far as 
  I have so far tested.

What I wish to do though, is enforce two specific 
  <section>'s : in other words, the first <section> in each document 
  will always have a specific <title>. That being, for arguments sake, 
  <title>Section 1: Policy Purpose</title>.

Similarly, the 
  second section will also have a specific title - that being 
  <title>Section 2: Document Glossary</title>

All other 
  <title>'s used in a document will be required (where they exist), but 
  their content will not be fixed.

I have made 
  <title></title> a global element. How can i now instantiate it 
  twice, with specific content, once for each section?? I am using the XMLSpy">XMLSpy 
  schema GUI tool, and each time I try to provide a fixed value, that value 
  becomes global...and thus applies to all <title> tags in the document. I 
  am using the <title> element in the following elements - hence its 
  global definition :

<section>
<part>
<hmajor> 
  (major heading)
<hminor> (minor heading)



Do I need to 
  create a <s1title> and <s2title> separate to my original 
  <title> element, or is there a more clever way of approaching this 
  issue? I am thinking there is but I am a tad stumped! Any assistance would be 
  hugely appreciated.


<X-SIGSEP>
  </X-SIGSEP>Best Regards

Ray Cauchi
Manager/Lead 
  Developer




( T W E E K ! 
  )
PO Box 468 Katoomba NSW Australia 
  2780
p: +61 2 4757 1600
f: +61 2 4757 3808
m: 0414 270 400
e: 
  ray@t...
w: www.tweek.com.au


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