Yes! We provide such a tool. Please see org.exolab.castor.xml.schema.util.XMLInstance2Schema. It's not 100% perfect, but it does a reasonable job. To enable XML validation at the parser level, please add properties to your castor.properties file as follows: org.exolab.castor.parser.namespaces=true org.exolab.castor.sax.features=http://xml.org/sax/features/validation,\ http://apache.org/xml/features/validation/schema,\ http://apache.

XML Schema acts as a template for XML data. A Schema is used to define the basic structure of an XML document, so that a group of related items will share a common format. This is important because it is much easier to process XML data which is in a consistent, predictable format. Schemas contain a combination of elements, each of which stores a single data type. Because of the flexibility of XML, an element can store anything from a simple name or phone number to a full-fledged annual report.

Tell the tool to look for names matching the filespec in this directory and all nested (and indirectly nested) directories, using the -r command line option. List a file that has XML Schemas as the content of an element that can occur more than once in a containing vocabulary (such as WSDL or XForms), and each of the contained schemas will be checked (if an option such as -wsdl, -xform, or -emb is used). In addition, if you have Eclipse or WSAD, you may select multiple files of type .

Yes, the DITA toolkit provides both DTD and XML Schema representations of the architecture. The basic concepts of DITA are not tied to implementation. Both schemas and DTDs can be used to define specializable DITA elements.

There have been some requests for an XML-Schema representation of the RecipeML format. If there continues to be sufficient interest and time permits, FormatData will most likely produce one. If a third party would like to create one, FormatData will be happy to help verify it and post it on this site.

all: It defines an unordered set of elements. Attention: all must be the only child of its parent content model and members in all only allowed to be elements and the cardinality of 0 or 1. all cannot be nested in other compositors either.

abstract is the same concepts in Java or C++, a type is abstract means it is not instantiable, or Specifies whether the complex type can be used in an instance document. True indicates that an element cannot use this complex type directly but must use a complex type derived from this complex type. final is to prevent derivation just like final class in Java. block is to prevent substitution of the ISA relationship in the OO sense.

IMHO, no, xml schema will gain more market shares, but it will never replace DTD. Xml schema has a serious problem, which is too complicated. Read an excellent article from Dr. David Mertz here Comparing W3C XML Schemas and Document Type Definitions (DTDs).C (born in 1970's), C++ (born in 1980's), Java (born in 1990's) have not finally replaced FORTRAN/COBOL ((born in 1950's) yet. .NET ((born in the 21st century) is actually making FORTRAN/COBOL more alive than before.

Not yet. On 24 October 2000, The World Wide Web Consortium (W3C) issued XML Schema as a W3C Candidate Recommendation. It will take some time for XML schema to become a W3C Recommendation, and for a BPG XML Schema to be developed and tested.

Since XML Schema is not finalized, no conversion programs are currently available. We plan to develop such a conversion program and disclose its source program under an open source licence, when XML Schema becomes a W3C recommedation. As long as you use features of Conformance Level "classic" of RELAX Core, you should be able to convert your RELAX grammars to XML Schemas automatically.

W3C Schema versions of the Archiving and Interchange DTD and the Journal Publishing DTD are now available. The DTD authors considered writing the "master" version of these tag sets in W3C XML Schema before we wrote the DTD. We understand that many people want to use XML schemas, and that there are XML tools that use only W3C XML Schema. We chose to express the "master" version of these tags sets in DTD form for several reasons (described below).

The Schema is a blueprint of all objects in the domain and when first created a default Schema exists which contains definitions for users, computers, domains etc. Because of this, you can only have one schema per domain as you cannot have multiple definitions of the same object. The default schema definition is defined in the SCHEMA.INI file that also contains the initial structure for the NTDS.DIT (storage for the Directory data). This file is located in the %systemroot%\ntds directory.

Yes. An XML schema is available for Sitemap files at http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd and a schema for Sitemap index files is available at http://www.sitemaps.org/schemas/sitemap/0.9/siteindex.xsd. You can also read more about validating your Sitemap.

If you are using DTDs, the only standard way of controlling the DTD that is used to validate a document is to insert or replace the document type declaration within the XML document itself. An example of some software that will do this is DOCTYPEChanger. A simpler method that requires a minimum of code is to use an EntityResolver. In general, you can use an EntityResolver to override any external entity in your XML document.

This issue is also related to the issue of using XML or RDF, addressed in a previous question. First of all, let us quote from the OWL Guide recommendation: ontology differs from an XML Schema in that it is a knowledge representation, not a message format. Most industry based Web standards consist of a combination of message formats and protocol specifications.

HexEdit 2.5 contains a built-in template editing facility. This facility should be regarded as "beta" as it has not been thoroughly tested and there are a few things to watch out for as mentioned below. However, it is generally much easier than creating templates by writing the XML code directly. You can turn the template editing on by double right clicking in the Display page of the Options dialog.

The FergTech current version of our schema is Version 3.0. A copy of this schema can be found on our website at http://www.fergtech.com/dynaform_v3.xsd.pdf

The scope of XML Schema is very broad. Thus, its standarization, implementation and adoption require a relatively long time. Furthermore, to take full advantage of XML Schema, extensions to DOM and SAX are required. On the other hand, RELAX is much more modest. Thus, it is easier to standardize, implement, and adopt. RELAX is a combination of (1) features of DTD, and (2) rich datatypes of XML Schema represented in the XML syntax.