diff options
author | Boris Kolpackov <boris@codesynthesis.com> | 2014-04-10 12:57:06 +0200 |
---|---|---|
committer | Boris Kolpackov <boris@codesynthesis.com> | 2014-04-10 12:57:06 +0200 |
commit | 884dea7531962b17ef843ac2175faa050e8b0758 (patch) | |
tree | d70950ab2a6f314b06f37faa67252678ce3007b1 /examples/cxx/tree/order/mixed/README | |
parent | 0f6ff689dc6bae8fed94da0fcabd39f015e7a62b (diff) |
Add support for ordered types, mixed content
Diffstat (limited to 'examples/cxx/tree/order/mixed/README')
-rw-r--r-- | examples/cxx/tree/order/mixed/README | 45 |
1 files changed, 45 insertions, 0 deletions
diff --git a/examples/cxx/tree/order/mixed/README b/examples/cxx/tree/order/mixed/README new file mode 100644 index 0000000..e66c1ad --- /dev/null +++ b/examples/cxx/tree/order/mixed/README @@ -0,0 +1,45 @@ +This example shows how to use ordered types to capture mixed content +text and to maintain order information between elements and text. + +In this example we use mixed content model to describe text with +embedded links in the form: + + This paragraph talks about <a href="uri">time</a>. + +The example transforms such text into plain text with references in +the form: + + This paragraph talks about time[uri]. + +It also saves the modified text back to XML in order to verify the +element and text order. + +The example consists of the following files: + +text.xsd + XML Schema which describes "text with links" instance documents. + +text.xml + Sample XML instance document. + +text.hxx +text.cxx + C++ types that represent the given vocabulary as well as a set of + parsing and serialization functions. These are generated by XSD + from text.xsd. Note that the --ordered-type-mixed option is used + to indicate to the XSD compiler that all types with mixed content + should be automatically treated as ordered. + +driver.cxx + Driver for the example. It first calls one of the parsing functions + that constructs the object model from the input XML file. It then + iterates over the text and elements in the content order to convert + the document to its plain text representation. The driver then adds + another paragraph of text and a link to the object model while showing + how to maintain the content order. Finally, it saves the modified + text back to XML to verify that the content order is preserved in + the output document. + +To run the example on the sample XML instance document simply execute: + +$ ./driver text.xml |