As published the W3C XML Schema specification references XML 1.0 explicitly, and incorporates by reference certain key definitions, in particular those of the 'Char', 'Name' and 'S' character classes. XML 1.1 changes the contents of these classes, so although nothing in the existing XML Schema specification specifically bars infosets produced by XML 1.1 conformant parsers, such infosets, if they exploit any of the relevant changes in XML 1.1, will not be accepted as valid by conformant XML Schema 1.0 processors.
XSLT stylesheets are designed to transform XML documents. Coupled with Java extensions, stylesheets can also be a powerful complement to XML Schema when grammar-based validation cannot cover all the constraints required. In this article, Peter Heneback presents the case for validating documents using XSLT with Java extensions and provides practical guidance and code samples.
The rules for finding schema components when validating a document using W3C's XML Schema 1.0 are widely misunderstood. This presentation will the rules for constructing a schema and describe the reasoning behind the design.
Designers of XML formats have to face the problem of how to design their formats to be extensible and yet be resilient to changes due revisions of the format. This presentation covers various techniques and considerations for versioning XML formats.
Document Model selection is a key success factor in XML. Approaches include: adopting an existing model, modifying a model to meet your needs, and creating one to meet your needs. Advantages and disadvantages of each are discussed.
Our work presents an experiment with a modeling tool that captures domain knowledge in a fashion natural to business users while producing formal models for use in IT processes. We demonstrate the use of this tool for designing XML Schemas.
The next century will be an XML century, make no mistake about it. All our documents, even checks, credit card slips, personal letters, recipes, technical documents, everything, will benefit from XML technologies. Students are already learning XML in schools, and big businesses are using it to publish their databases on the web. The appearance of the electronic spreadsheet ten years ago changed the way we do business. XML will change the way we write documents.
The UK Local e-Government Standards Body was established late in 2003, and tasked with compiling an XML based data standards catalogue for use by UK Local Authorities. This is to be achieved by mapping existing standards, identifying gaps to be filled, advising and supporting local Councils, their partners and suppliers on the interpretation and adoption of standards, and establishing processes for developing new standards as required. However, UK Local Authorities have been developing e-services for several years already, so this new effort has to take place in a context where many projects are already under way, using a variety of business models, and with diverse approaches to XML interoperability design. An additional factor is the traditional tension between central and local government, which has led to patchy and inconsistent adoption of the national UK e-Government Interoperability framework. This paper is an account of the methodology developed by CSW Group Ltd and the LeGSB to tackle this situation.
From initial data modeling, to technical XML Schema design and critical programmatic realization, we have an actionable, real-world set of comprehensive recommendations that can help you formulate a successful XML implementation.
The high integration costs which exist today mean that we must automate interface maintenance and integration tasks or go insane, or worse, out of business. Ongoing pressure to reduce software development costs while increasing the quality and completeness of the work provide an opportunity for the use of model driven computing. MDA (Model Driven Architecture) is a technique for model based platform independent software specification based on the MOF (Meta-Object Facility) and XMI (XML Meta-data Interchange) standards from the OMG (Object Management Group). There are a number of tool vendors using XMI (especially UML (Unified Modeling Language) drawing tools) but common use and value seem to be slow to show themselves.
During the past twenty years, a huge number of custom languages - at least hundreds, perhaps a couple of thousand - have been attempted. Almost all have been miserable failures. That is to say, the vast majority have failed to achieve wide adoption, and those that were adopted have often failed to achieve their goals, whether of reducing costs, enriching applications, or both.
RELAX NG is a simple schema language for XML, based on RELAX and TREX. A RELAX NG schema specifies a pattern for the structure and content of an XML document. A RELAX NG schema thus identifies a class of XML documents consisting of those documents that match the pattern. A RELAX NG schema is itself an XML document.
Web Services Description Language is the standard format for describing a web service in XML format. In this tutorial you will learn what is WSDL and Why and How to use it. WSDL is very easy to learn and very important for Web Services.
About ten years ago, a handful of highly specialised consultants were trying with missionary zeal to establish SGML as the basic format in technical communication; today, the XML-standard is no longer something that can be dispensed with, and is, in fact, even mandatory in many projects. This article takes a look in hindsight at the beginnings of SGML and XML, and the current developments and standards around XML, and also hazards a guess at what the years to come might hold in store.
XML stands for eXtensible Markup Language. XML is used to aid the exchange of data. The language makes it possible to define data in a structured way. XML tags are not predefined like HTML. XML lets you create your own unique tags that are meaningful for your data, hence the use of the term 'extensible.'
As world events and business opportunities collide, the requirements for interoperable document formats become increasingly evident. Mandating XML for systems is a first step, but real information can't be shared effectively without a common understanding on the semantics and usage of the markup. One solution is to use agreed-on custom schemas. Another is to cite well-standardized formats such as XHTML, or deploy more specific XML formats such as Microsoft Office XML or the OpenDocument Format. None of these latter formats were written with a particular semantic usage in mind. They are of more general applicability than custom-built schemas, can be used for human-readable documents, and can be built into specific tools.
Maybe XML is more like a carcinogen. We don't notice it's there, but we're still getting exposed to it. In ever-increasing doses. But unlike a carcinogen, XML is not bad for our health; in fact, it has many life-enhancing properties. Well, work-enhancing properties.
This paper describes the design of a new language to formally specify constraints over Topic Maps. This language allows to express contextual conditions on classes of Topic Maps and the corresponding processing syntem. With XTche, a topic map designer defines a set of restrictions that enables to verify if a particular topic map is semantically valid. As the manual checking of large topic maps (frequent in real cases) is impossible, it is mandatory to provide an automatic validator.