If you happen to have Visual Studio, open the DTD file an you should have a button to &quot;Create Schema&quot; out of it.
&lt;br/&gt;
I haven&#39;t checked if it was available on Express edition, though.

The W3C offers [one][1]. There are also [online converters][2].


  [1]: http://www.w3.org/2000/04/schema_hack/
  [2]: http://www.hitsw.com/xml_utilites/

Try xmlpad from https://download.cnet.com/XmlPad/3000-7241_4-10252051.html to convert DTD to XSD. Really nice tool.

http://www.thaiopensource.com/relaxng/trang.html

Trang converts between different schema languages for XML. It supports the following languages:

- RELAX NG (XML syntax)
- RELAX NG compact syntax
- XML 1.0 DTDs
- W3C XML Schema

http://www.thaiopensource.com/relaxng/trang-manual.html

Is there a library to convert XML to JSON in Ruby?

Ruby XML to JSON Converter?

This question is a spin-off from [this one][1]. Some history: when I first learned Perl, I pretty much always used `glob` rather than `opendir` + `readdir` because I found it easier. Then later various posts and readings suggested that `glob` was bad, and so now I pretty much always use `readdir`.

After thinking over [this recent question][2] I realized that my reasons for one or the other choice may be bunk. So, I&#39;m going to lay out some pros and cons, and I&#39;m hoping that more experienced Perl folks can chime in and clarify. The question in a nutshell is are there compelling reasons to prefer `glob` to `readdir` or `readdir` to `glob` (in some or all cases)?

### `glob` pros:

 1. No dotfiles (unless you ask for them)
 2. Order of items is guaranteed
 3. No need to prepend the directory name onto items manually
 4. Better name (c&#39;mon - `glob` versus `readdir` is no contest if we&#39;re judging by names alone)
 5. (From [ysth&#39;s answer](#1507507); cf. `glob` cons 4 below) Can return non-existent filenames:

        @deck = glob &quot;{A,K,Q,J,10,9,8,7,6,5,4,3,2}{\x{2660},\x{2665},\x{2666},\x{2663}}&quot;;


### `glob` cons:

 1. Older versions are just plain broken (but &#39;older&#39; means pre 5.6, I think, and frankly if you&#39;re using pre 5.6 Perl, you have bigger problems)
 2. Calls `stat` each time (i.e., useless use of `stat` in most cases).
 3. Problems with spaces in directory names (is this still true?)
 4. (From [brian&#39;s answer](#1506886)) Can return filenames that don&#39;t exist:

        $ perl -le &#39;print glob &quot;{ab}{cd}&quot;&#39;

### `readdir` pros:

 1. (From [brian&#39;s answer](#1506886)) `opendir` returns a filehandle which you can pass around in your program (and reuse), but `glob` simply returns a list
 2. (From [brian&#39;s answer](#1506886)) `readdir` is a proper iterator and provides functions to `rewinddir`, `seekdir`, `telldir`
 3. Faster? (Pure guess based on some of `glob`&#39;s features from above. I&#39;m not really worried about this level of optimization anyhow, but it&#39;s a theoretical pro.)
 4. Less prone to edge-case bugs than `glob`?
 5. Reads everything (dotfiles too) by default (this is also a con)
 6. May convince you not to name a file `0` (a con also - see [Brad&#39;s answer](#2365358))
 7. Anyone? Bueller? Bueller?

### `readdir` cons:

 1. If you don&#39;t remember to prepend the directory name, you **will** get bit when you try to do filetests or copy items or edit items or...
 2. If you don&#39;t remember to `grep` out the `.` and `..` items, you **will** get bit when you count items, or try to walk recursively down the file tree or...
 3. Did I mention prepending the directory name? (A sidenote, but my very first post to the Perl Beginners mail list was the classic, &quot;Why does this code involving filetests not work some of the time?&quot; problem related to this gotcha. Apparently, I&#39;m still bitter.)
 4. Items are returned in no particular order. This means you will often have to remember to sort them in some manner. (This could be a pro if it means more speed, and if it means that you actually *think* about how and if you need to sort items.) **Edit**: Horrifically small sample, but on a Mac `readdir` returns items in alphabetical order, case insensitive. On a Debian box and an OpenBSD server, the order is utterly random. I tested the Mac with Apple&#39;s built-in Perl (5.8.8) and my own compiled 5.10.1. The Debian box is 5.10.0, as is the OpenBSD machine. I wonder if this is a filesystem issue, rather than Perl? 
 5. Reads everything (dotfiles too) by default (this is also a pro)
 6. Doesn&#39;t necessarily deal well with a file named `0` (see pros also - see [Brad&#39;s answer](#2365358))

 


  [1]: https://stackoverflow.com/questions/1499672/how-do-i-open-an-array-of-files-in-perl
  [2]: https://stackoverflow.com/questions/1499672/how-do-i-open-an-array-of-files-in-perl

What reasons are there to prefer glob over readdir (or vice-versa) in Perl?

I have a DTD that I need to convert to an XSD (XML schema) file.  Is there a free utility or simple way to accomplish this?

Free DTD to XSD conversion utility?

<p>I have a DTD that I need to convert to an XSD (XML schema) file.  Is there a free utility or simple way to accomplish this?</p>


I&#39;m attempting to override the default `ToggleButton` appearance. Here&#39;s the XML that defines the `ToggleButton`:

    &lt;ToggleButton android:id=&quot;@+id/FollowAndCenterButton&quot;
    		android:layout_width=&quot;30px&quot;
    		android:layout_height=&quot;30px&quot;
   			android:textOn=&quot;&quot; android:textOff=&quot;&quot; android:layout_alignParentLeft=&quot;true&quot;
   			android:layout_marginLeft=&quot;5px&quot;
   			android:layout_marginTop=&quot;5px&quot; android:background=&quot;@drawable/locate_me&quot;/&gt;

Now, we have two 30 x 30 icons we want to use for the clicked/non-clicked states. Right now we have code that programmatically changes the background icon depending on the state:

    centeredOnLocation.setOnClickListener(new OnClickListener() {
	        public void onClick(View v) {
	            if (centeredOnLocation.isChecked()) {
                    centeredOnLocation.setBackgroundDrawable(getResources().getDrawable(R.drawable.locate_me_on));
                } else {
                    centeredOnLocation.setBackgroundDrawable(getResources().getDrawable(R.drawable.locate_me));
	            }
            }
    });

Obviously I&#39;m looking for a better way to do this. I&#39;ve tried to make a selector for the background image, which would automatically switch between the states:

     &lt;selector xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;&gt;
     &lt;item android:drawable=&quot;@drawable/locate_me&quot; /&gt; &lt;!-- default --&gt;
     &lt;item android:state_checked=&quot;true&quot;
           android:drawable=&quot;@drawable/locate_me_on&quot; /&gt; &lt;!-- pressed --&gt;
     &lt;item android:state_checked=&quot;false&quot;
           android:drawable=&quot;@drawable/locate_me&quot; /&gt; &lt;!-- unchecked --&gt;
 &lt;/selector&gt;


But this does not work; reading the `ToggleButton` API (http://developer.android.com/reference/android/widget/ToggleButton.html), it appears that the only inherited xml attributes are

        XML Attributes
    Attribute Name 	Related Method 	Description
    android:disabledAlpha 		The alpha to apply to the indicator when disabled. 
    android:textOff 		The text for the button when it is not checked. 
    android:textOn 		The text for the button when it is checked. 

There does not seem to be the android:state_checked attribute, despite the class having the method `isChecked()` and `setChecked()`.


So, is there a way to do what I want in XML, or am I stuck with my messy workaround?


Android: Specify two different images for togglebutton using XML

I&#39;m searching a lightweight API (preferable single class) to convert a

    Map&lt;String,String&gt; map = new HashMap&lt;String,String();

to XML and, vice versa, convert the XML back to a `Map&lt;String,String&gt;`.

example:

    Map&lt;String,String&gt; map = new HashMap&lt;String,String();
    map.put(&quot;name&quot;,&quot;chris&quot;);
    map.put(&quot;island&quot;,&quot;faranga&quot;);
    
    MagicAPI.toXML(map,&quot;root&quot;);

result:

    &lt;root&gt;
      &lt;name&gt;chris&lt;/chris&gt;
      &lt;island&gt;faranga&lt;/island&gt;
    &lt;/root&gt;

and back:

    Map&lt;String,String&gt; map = MagicAPI.fromXML(&quot;...&quot;);


I don&#39;t want to use [JAXB][1] or [JSON conversion API][2]. It doesn&#39;t have to take care of nested maps or attributes or anything else, just that simple case.
Any suggestions?


----------

I created a working copy &amp; paste sample. Thanks to [fvu][3] and [Michal Bernhard][4].

[Download latest XStream framework][5], &#39;core only&#39; is enough.

    Map&lt;String,Object&gt; map = new HashMap&lt;String,Object&gt;();
    map.put(&quot;name&quot;,&quot;chris&quot;);
    map.put(&quot;island&quot;,&quot;faranga&quot;);
    
    // convert to XML
    XStream xStream = new XStream(new DomDriver());
    xStream.alias(&quot;map&quot;, java.util.Map.class);
    String xml = xStream.toXML(map);
    
    // from XML, convert back to map
    Map&lt;String,Object&gt; map2 = (Map&lt;String,Object&gt;) xStream.fromXML(xml);

No converters or anything else is required. Just the [xstream-x.y.z.jar][6] is enough.


  [1]: http://jaxb.java.net/
  [2]: http://json.org/java/
  [3]: https://stackoverflow.com/users/112079/fvu
  [4]: https://stackoverflow.com/users/70786/michal-bernhard
  [5]: http://xstream.codehaus.org/download.html
  [6]: http://repository.codehaus.org/com/thoughtworks/xstream/xstream/1.3.1/xstream-1.3.1.jar

How to convert XML to java.util.Map and vice versa?

I am now learning [`XmlDocument`][1] but I&#39;ve just ran into [`XDocument`][2] and when I try to search the difference or benefits of them I can&#39;t find something useful, could you please tell me why you would use one over another ?


  [1]: http://msdn.microsoft.com/en-us/library/system.xml.xmldocument.aspx
  [2]: http://msdn.microsoft.com/en-us/library/system.xml.linq.xdocument.aspx

XDocument or XmlDocument

I have googled this question, but I do not understand clearly what is an XML schema and DTD (document type definition), and why the XML schema is more powerful compared to DTD. 

Any guidance would be highly appreciated. 


What is difference between XML Schema and DTD?

I ran one of my xml files through a schema generator and everything generated was what was expected, with the exception of one node:

    &lt;xs:element name=&quot;office&quot; type=&quot;xs:NCName&quot;/&gt;

What exactly is `xs:NCName`?  And why would one use it, rather `xs:string`?

What is an xs:NCName type and when should it be used?

I am using Spring and in `application-context.xml` I have the following definitions: 

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
    &lt;beans xmlns=&quot;http://www.springframework.org/schema/beans&quot;
       xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
       xmlns:util=&quot;http://www.springframework.org/schema/util&quot;
       xmlns:context=&quot;http://www.springframework.org/schema/context&quot;
       xmlns:aop=&quot;http://www.springframework.org/schema/aop&quot;
       xmlns:tx=&quot;http://www.springframework.org/schema/tx&quot;
       xmlns:p=&quot;http://www.springframework.org/schema/p&quot;
       xmlns:security=&quot;http://www.springframework.org/schema/security&quot;
       xsi:schemaLocation=&quot;
       http://www.springframework.org/schema/beans 
       http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
       http://www.springframework.org/schema/util 
       http://www.springframework.org/schema/util/spring-util-2.0.xsd
       http://www.springframework.org/schema/context
       http://www.springframework.org/schema/context/spring-context-2.1.xsd
       http://www.springframework.org/schema/tx
       http://www.springframework.org/schema/tx/spring-tx.xsd
       http://www.springframework.org/schema/aop
       http://www.springframework.org/schema/aop/spring-aop-2.0.xsd
       http://www.springframework.org/schema/security
       http://www.springframework.org/schema/security/spring-security-2.0.xsd&quot;
       &gt;

.....

**When my internet connection is lost, I cannot run my application via tomcat or jetty.** 

It gives: 

    [main] WARN  org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Ignored XML validation warning
    org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document &#39;/spring-beans-2.0.xsd&#39;, because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not &lt;xsd:schema&gt;.
    	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
    	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.warning(ErrorHandlerWrapper.java:96)
    	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:380)
    	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318)
    	at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(XSDHandler.java:2541)
    	at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaWarning(XSDHandler.java:2532)
    	at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getSchemaDocument(XSDHandler.java:1836)
    	at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:531)
    	at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:552)
    	at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.findSchemaGrammar(XMLSchemaValidator.java:2408)
    	at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1753)
    	at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:685)
    	at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:400)
    	at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:626)
    	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3095)
    	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:921)
    	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
    	at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
    	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
    	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)
    	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
    	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
    	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225)
    	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)
    	at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75)
    	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396)
    	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342)
    	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
    	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
    	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
    	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
    	at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:124)
    	at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:92)
    	at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:123)
    	at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:423)
    	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:353)
    	at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
    	at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
    	at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
    	at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548)
    	at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
    	at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
    	at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
    	at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
    	at org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115)
    	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    	at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
    	at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
    	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    	at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
    	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    	at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
    	at org.mortbay.jetty.Server.doStart(Server.java:224)
    	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    	at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:132)
    	at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:441)
    	at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:383)
    	at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:210)
    	at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184)
    	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
    	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
    	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
    	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
    	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
    	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
    	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
    	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
    	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
    	at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    	at java.lang.reflect.Method.invoke(Method.java:597)
    	at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    	at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    2009-11-13 15:31:25,675 [main] ERROR org.springframework.web.context.ContextLoader - Context initialization failed
    org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 23 in XML document from class path resource [application-context.xml] is invalid; nested exception is org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element &#39;beans&#39;.
    	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:404)
    	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342)
    	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinit........

Any suggestions how to fix it? 

Spring schemaLocation fails when there is no internet connection

What is the difference between an `XML Schema` and `WSDL`?

The difference I noticed is that `WSDL` contains `XSD` and in `WSDL` we can declare operations, but not in `XSD`. Is that correct?

What is the difference between XSD and WSDL?

I often have to design XML schemas for different XML-bases import routines. It is clear that XML schemas will evolve over time or they could contain bugs to be fixed, so it is important to capture the schema&#39;s version and to have some mechanism to bind against a specific version.

Currently I have two scenarios:

 1. The bug is found within the schema and all schema instances must comply with the fixed version.

 2. The schema upgraded and should be considered as preferable but an old one should be also supported.

Finally I came up with storing version information within the namespace of schema:

    targetNamespace=&quot;http://schemas.company.com/Geodesy/2010/River.xsd&quot;

When fixing a bug I fix it in the same namespace but if I&#39;m about to upgrade a schema then I need to create a new namespace but with upgrade month added:

    targetNamespace=&quot;http://schemas.company.com/Geodesy/2010/01/River.xsd&quot;

And if I have more than one upgrade in a month then just append a day too:

    targetNamespace=&quot;http://schemas.company.com/Geodesy/2010/01/17/River.xsd&quot;

Do you know any better approach?

What are the best practices for versioning XML schemas?

I am trying to create an XSD, and trying to write the definition with the following requirement:

 - Allow child element specified to appear any number of times (0 to unbounded)
 - Allow child elements to be in any order

I looked around and found various solutions like [this][1]:

    &lt;xs:element name=&quot;foo&quot;&gt;
      &lt;xsl:complexType&gt;
        &lt;xs:choice minOccurs=&quot;0&quot; maxOccurs=&quot;unbounded&quot;&gt;
          &lt;xs:element name=&quot;child1&quot; type=&quot;xs:int&quot;/&gt;
          &lt;xs:element name=&quot;child2&quot; type=&quot;xs:string&quot;/&gt;
        &lt;/xs:choice&gt;
      &lt;/xs:complexType&gt;
    &lt;/xs:element&gt;


But from what I understand xs:choice still only allows single element selection. Hence setting the MaxOccurs to unbounded  like this should only mean that &quot;any one&quot; of the child elements can appear multiple times. Is this accurate? 

If above solution is incorrect, how can I achieve what I stated above in my requirement?

**EDIT**: What if the requirement is as follows?

 - Element child1 child2 can appear any
   number of times (0 to unbounded)
 - Elements to be in any order
 - Elements child3 and child4 should appear exactly once.

For example, 
this xml is valid:

    &lt;foo&gt;
    &lt;child1&gt; value &lt;/child1&gt;
    &lt;child1&gt; value &lt;/child1&gt;
    &lt;child3&gt; value &lt;/child3&gt;
    &lt;child2&gt; value &lt;/child2&gt;
    &lt;child4&gt; value &lt;/child4&gt;
    &lt;child1&gt; value &lt;/child1&gt;
    &lt;/foo&gt;

but this is not (missing child3)

    &lt;foo&gt;
    &lt;child1&gt; value &lt;/child1&gt;
    &lt;child1&gt; value &lt;/child1&gt;
    &lt;child2&gt; value &lt;/child2&gt;
    &lt;child4&gt; value &lt;/child4&gt;
    &lt;child1&gt; value &lt;/child1&gt;
    &lt;/foo&gt;



  [1]: http://social.msdn.microsoft.com/Forums/en/xmlandnetfx/thread/decedc59-b991-4e2f-b2cf-41ac139f734f

XSD - how to allow elements in any order any number of times?

I want to use either a DTD or an XSD to describe my XML document. I&#39;ve read that XSDs are better than DTDs since they support namespaces and data types, and that DTDs are older.

Does this mean that I should only use XSDs for all future needs and totally ignore DTD as an option? Should I even bother learning the structure of DTDs?

What factors should I consider when choosing between XSD and DTD?

How to choose between DTD and XSD

The &quot;old&quot; HTML/XHTML standards have a DTD (Document Type Definition) defined for them:

HTML 4.01 http://www.w3.org/TR/html401/sgml/dtd.html  
XHTML 1.0 http://www.w3.org/TR/xhtml1/dtds.html#a_dtd_XHTML-1.0-Strict  

&lt;strike&gt;This DTDs specify the rules for nesting elements - &quot;which types of elements may appear in which types of elements&quot;. I made a diagram for XHTML 1.0 here&lt;/strike&gt; (sorry, I no longer have that resource)

I would like to update that diagram with a new version which also includes the new HTML5 elements. However, there doesn&#39;t seem to be a HTML5 DTD. It seems that the nesting rules are defined by the various content models that are defined in HTML5.  

So there is no DTD, correct?  

***Follow-up question:*** Is there a reason why there is no DTD in HTML5? The DTD is such a nice method of defining the nesting rules for all the different types of elements. Why wouldn&#39;t they include such a thing?

***Update:*** I found this: http://www.w3.org/TR/html5/dom.html#kinds-of-content I guess, this is the closest to having a DTD.  

***Update:*** The Visual Studio Team made a XML Schema for XHTML5. I guess that answers my question: [Link](https://web.archive.org/web/20120730085926/http://blogs.msdn.com/b/webdevtools/archive/2009/11/18/html-5-intellisense-and-validation-schema-for-visual-studio-2008-and-visual-web-developer.aspx)

Where is the HTML5 Document Type Definition?

I have this dtd : http://fast-code.sourceforge.net/template.dtd
But when I include in an xml I get the warning :
No grammar constraints (DTD or XML schema) detected for  the document.
The xml is : 

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
    &lt;!DOCTYPE templates PUBLIC &quot;//UNKNOWN/&quot; &quot;http://fast-code.sourceforge.net/template.dtd&quot;&gt;

    &lt;templates&gt;
	&lt;template type=&quot;INSTANCE_OF_CLASS&quot;&gt;
		&lt;description&gt;Used to Create instance of class&lt;/description&gt;
		&lt;variation&gt;asasa&lt;/variation&gt;
		&lt;variation-field&gt;asasa&lt;/variation-field&gt;
		&lt;class-pattern&gt;asasa&lt;/class-pattern&gt;
		&lt;getter-setter&gt;setter&lt;/getter-setter&gt;
		&lt;allowed-file-extensions&gt;java&lt;/allowed-file-extensions&gt;
		&lt;number-required-classes&gt;1&lt;/number-required-classes&gt;
		&lt;allow-multiple-variation&gt;false&lt;/allow-multiple-variation&gt;
		&lt;template-body&gt;
			&lt;![CDATA[
				// Creating new instance of ${class_name}
				final ${class_name} ${instance} = new ${class_name}();
				#foreach ($field in ${fields})
					${instance}.${field.setter}(${field.value});
				#end
			]]&gt;
		&lt;/template-body&gt;
	&lt;/template&gt;
    &lt;/templates&gt;

**EDIT** : I changed the xml, I am getting this error now:
&gt; The content of element type &quot;template&quot; must match &quot;(description,variation?,variation-field?,allow-
 multiple-variation?,class-pattern?,getter-setter?,allowed-file-extensions?,number-required-
 classes?,template-body)&quot;.

No grammar constraints (DTD or XML schema) detected for the document

I&#39;ve seen several discussions on the net about how great it would be to have an XML schema or DTD for logback.xml file to have at least the very basic validation and auto-completion in IDEs like IDEA or Eclipse, but I never saw any solution.

Did you?

Content Type	Original Author	Original Content on Stackoverflow
Question	Jeremy Stein	View Question on Stackoverflow
Solution 1 - Xml	Serge	View Answer on Stackoverflow
Solution 2 - Xml	Martin v. Löwis	View Answer on Stackoverflow
Solution 3 - Xml	asingh	View Answer on Stackoverflow
Solution 4 - Xml	Andriy Plokhotnyuk	View Answer on Stackoverflow

Free DTD to XSD conversion utility?

Xml Problem Overview

Xml Solutions

Solution 1 - Xml

Solution 2 - Xml

Solution 3 - Xml

Solution 4 - Xml

What reasons are there to prefer glob over readdir (or vice-versa) in Perl?

Ruby XML to JSON Converter?

Attributions