{{Under construction| The xml documentation pages are under construction. }} This page describes the Mine Action Extensible Markup Language (maXML). The maXML schema was first created 2002 to be an exchange language for the Mine Action Community. Since then maXML has evolved in step with the advances in Information Management in Mine action and with the Information management System for Mine Action (IMSMA). MaXML can be used to exchange data by any system containing Mine Action information, either with {{IMSMANG}} or other systems. The schema syntax conforms to the World Wide Web Consortium (W3C) Recommendation (October 6, 2000) for XML 1.0.
This In order to have a clear understanding of the maXML documentation introduces it is essential for the maXML reader to have a basic understanding of XML and XML schema concepts. There are several good sources of information about XML and XML schemas on the maXML architectureInternet. The documentation and especially the detailed specification is also a description of the relationship between maXML following links may provide useful in order to learn about XML and {{IMSMANG}}. XML schemas:
In order to have * XML 1.0. The XML 1.0 specification (a clear understanding of this documentation it is essential for W3C Recommendation) indicates the reader constraints to have a basic understanding of which an XML document must adhere in order to be well formed. : The W3C XML and 1.0 recommendations can be viewed [http://www.w3.org/TR/REC-xml here].* XML schema conceptsSchema Part 0 Primer. There are several good sources This document explains the basics of information about XML and XML provides a number of examples of schema and valid instance documents conforming to schemas on the Internet. : The following links may provide useful schema primer can be viewed [http://www.w3.org/TR/xmlschema-0 here].* XML Schema Part 1 Structures. This document defines the component parts of a schema and describes how they can be assembled and nested in order to learn about create an allowable structure. : The document can be viewed [http://www.w3.org/TR/xmlschema-1 here].* XML Schema Part 2 Datatypes. This document defines the data types that are built into XML, and explains how to create your own types. Data types and user-defined types can be assigned to elements and XML schemasattributes, and are another option for further constraining content your schema will allow. : The document can be viewed [http: //www.w3.org/TR/xmlschema-2 here].
* XML 1.0. The XML 1.0 specification (a W3C Recommendation) indicates On the constraints to which an XML document must adhere in order to be well formed. The W3C XML 1.0 Recommendations can be viewed [http//www.w3.org/TR/REC-xml here[MaXML Architecture]].* XML Schema Part 0 Primer. This document explains page the maXML is briefly described and on the basics of XML page [[IMSMA and provides a number maXML]] the current '''variation''' of examples of schema and valid instance documents conforming to schemas. The schema primer can be viewed [http//www.w3maXML that is used with {{IMSMANG}} 6.org/TR/xmlschema-0 here]is briefly described.* XML Schema Part 1 Structures. This document defines The pages that are describing the component parts of a the maXML schema and describes how they can be assembled and nested in order have two different user groups:* developers that would like to create an allowable structure. The document can be viewed [http//wwwmaXML files for import into {{IMSMANG}}* IMSMA administrators e.w3g.org/TR/xmlschema-1 here]for troubleshooting a xml import.* XML Schema Part 2 Datatypes. This document defines The base/focus for the data types pages that are built into XML, and explains how to create your own types. Data types and user-defined types can be assigned to elements and attributes, and are another option for further constraining content your describing the parts of the maXML schema will allowis '''{{IMSMANG}}'s current use of maXML'''. The document can be viewed [http//www.w3.org/TR/xmlschema-2 here[Data Dictionary]]is following the structure of the Data Inventory Manager.