MaXML Architecture - Revision history

Alnaucler at 18:53, 12 June 2017

2017-06-12T18:53:19Z

← Older revision		Revision as of 20:53, 12 June 2017
Line 1:		Line 1:
			{{Warning \| The form of maXML exported and imported by IMSMA differs slightly from the maXML defined by the generic maXML schema and therefore some exports will not validate to the original schema. Anyone who would like to exchange information with {{IMSMANG}} should follow IMSMA maXML dictionary to construct or read a maXML file correctly formatted for {{IMSMANG}}.}}

	As the elements in the maXML schema share many components, best practices have indicated that implementing a modular design approach benefits the designers by maximizing re-use of frequently declared groups of elements. The maXML architecture strives to take advantage of the efficiencies of re-use and has implemented a Venetian Blind schema design. The Venetian Blind design is characterized by the following:		As the elements in the maXML schema share many components, best practices have indicated that implementing a modular design approach benefits the designers by maximizing re-use of frequently declared groups of elements. The maXML architecture strives to take advantage of the efficiencies of re-use and has implemented a Venetian Blind schema design. The Venetian Blind design is characterized by the following:
	* uses type definitions as the main form of component re-use		* uses type definitions as the main form of component re-use
Line 29:		Line 31:
	# CauseArtifact		# CauseArtifact

			The maXML documentation may be obtained from [[Information Management Team \| GICHD]].
	{{NavBox XML Documentation}}		{{NavBox XML Documentation}}
	[[Category:NAA]]		[[Category:NAA]]

Alnaucler: Alnaucler moved page MaXML Architectur to MaXML Architecture without leaving a redirect

2017-06-12T12:44:39Z

Alnaucler moved page MaXML Architectur to MaXML Architecture without leaving a redirect

← Older revision	Revision as of 14:44, 12 June 2017
(No difference)

Alnaucler: Alnaucler moved page MaXML Architecture to MaXML Architectur without leaving a redirect

2017-06-12T12:44:19Z

Alnaucler moved page MaXML Architecture to MaXML Architectur without leaving a redirect

← Older revision	Revision as of 14:44, 12 June 2017
(No difference)

Alnaucler at 12:43, 12 June 2017

2017-06-12T12:43:23Z

@@ Line 9: / Line 9: @@
 MaXML consists of one schema file containing the whole specification for the language. maXML builds on definitions of a number of types in order to ensure re-usability. The types are then used to build Artifacts. The Artifacts are structured to contain different parts of the information contained in {{IMSMANG}}. The MineActionFieldReport Artifact contains information from different types of Data Entry Forms in {{IMSMANG}} while the other Artifacts contain different types of Auxiliary data. This architecture ensures maximum re-usability of commonly used data structures.
 {{NavBox XML Documentation}}
 [[Category:NAA]]

Alnaucler: Created page with "As the elements in the maXML schema share many components, best practices have indicated that implementing a modular design approach benefits the designers by maximizing re-us..."

2017-06-12T12:39:50Z

Created page with "As the elements in the maXML schema share many components, best practices have indicated that implementing a modular design approach benefits the designers by maximizing re-us..."

New page

As the elements in the maXML schema share many components, best practices have indicated that implementing a modular design approach benefits the designers by maximizing re-use of frequently declared groups of elements. The maXML architecture strives to take advantage of the efficiencies of re-use and has implemented a Venetian Blind schema design. The Venetian Blind design is characterized by the following:
* uses type definitions as the main form of component re-use
* nests element declarations within type definitions
* maximizes potential to hide namespace complexities

The Venetian Blind approach steers away from rigid hierarchical models where-in designers create new subclasses to accommodate further requirements, and link these to ever-increasingly complex tree types. The Venetian Blind approach favours elements and types that are loosely connected to a common root. The components are stand-alone and can be understood, developed, and modified independently.

MaXML uses eight artifacts that are built from complex and simple types in accordance with the Venetian Blind Design as defined above.

MaXML consists of one schema file containing the whole specification for the language. maXML builds on definitions of a number of types in order to ensure re-usability. The types are then used to build Artifacts. The Artifacts are structured to contain different parts of the information contained in {{IMSMANG}}. The MineActionFieldReport Artifact contains information from different types of Data Entry Forms in {{IMSMANG}} while the other Artifacts contain different types of Auxiliary data. This architecture ensures maximum re-usability of commonly used data structures.

{{NavBox XML Documentation}}
[[Category:NAA]]