1 $group
2 $
3 var sect = {
4 title: 'Xml document comparision'
5 };
6 section( §)
7 h4 Content model
8 p XML differentiates two types: elements containing only
9 \b element content (no character data) and mixed content
10 \b (elements that may contain character data, optionally
11 \b interspersed with child elements).
12 p Ittf documents have no mixed content. They have ittf nodes only.
13 \b They do not have the concept of element or attribute or
14 \b text.
15 p Only the application of a wizzi schema to an mTree, when loading a Wizzi Model,
16 \b can trasform an ittf node in an element or attribute or text, depending
17 \b on the schema declarations.
18 h4 Document types and document type definitions
19 p A wizzi schema is actually a documemnt type definition, but it applies to loaded mTrees
20 \b not to ITTF Documents. Ittf documents creators must design their
21 \b documents to obtain a valid mTree after composition and evaluation,
22 \b just before loading it in a Wizzi Model.
23 p An ITTF Document, when created for composing an mTree for a specific wizzi schema,
24 \b can be considered to have the type of that wizzi schema. The type of an
25 \b ITTF Document must be recognizable from its name, that must end with
26 \b '.`schema`.ittf'. Example of ITTF Document of type 'js': 'index.js.ittf'.
27 h4 Markup declaration and markup model
28 p In XML a markup declaration is a syntactical construct within a DTD declaring
29 \b an entity or defining a markup structure.
30 p Wizzi Schemas do not need to declare entities, because ITTF Document can contain
31 \b expressions and template commands. But, like DTDs, they declare an elements and
32 \b attributes structure, and like DTDs they define a model (Wizzi Model) of
33 \b an mTree content.
34 p In the wizzi factory, Wizzi Models are implemented as
35 \b javascript module, generated from a
36 \b wizzi schema declaration. They can load
37 \b valid mTrees, and may be used as a context object by the mTree loader,
38 \b model transformers and artifact generators.
39 h4 Elements and element types
40 p Wizzi Schema elements and XML DTD element types have the same goal.
41 \b Wizzi Model elements are such only after the mTree loading of an ITTF Document.
42 \b In ITTF Documents we have potential model elements, attributes and texts.
43 h4 Valid characters
44 p Ittf documents accept any character. The wizzi factory ignores the content
45 \b of documents and has no concept of data type.
46 \b Wizzi Schemas only can constrain node names and values.
47 p When generating the javascript of a Wizzi Model
48 \b the names of classes and attributes are checked and invalid chars for
49 \b javascript names are replaced with the '_' char. Class names colliding
50 \b with javascript keywords are prefixed with the letter 'x'.