started to implement document parsing.

1 files changed, 49 insertions, 0 deletions

diff --git a/testdata/xmlparser/simple_book.oxd b/testdata/xmlparser/simple_book.oxd
new file mode 100644
index 0000000..bb8cc16
--- /dev/null
+++ b/testdata/xmlparser/simple_book.oxd
@@ -0,0 +1,49 @@
+<?xml version="1.0"?>
+<document>
+	<import rel="domain" src="book_domain.oxm"/>
+	<!-- Currently we have only one root. Thus we need no wrapper. -->
+	<!-- Note that we only reference "book" here, which resolves to the book
+		 domain as well as the book StructuredClass. This is unambigous however,
+		 because we are looking for a StructuredClass. The resolving mechanism
+		 should be able to handle this. -->
+	<book>
+	<!-- implicitly:
+	<book name="">
+		 -->
+	<!-- note that we do not refer to the attributes explicitly. Attributes are
+		 referenced by their key-value pairs as defined in the according
+		 StructType. For an example please refer to the more complex book
+		 domain. -->
+		<!--<book:paragraph>
+		<text>
+		This might be some introductory text or a dedication. Ideally, of
+		course, such elements would be semantically specified as such in
+		additional domains (or in this one).
+		</text>
+		</book:paragraph>-->
+		<!-- Note that a better version of the book domain might specify
+			 headings here. -->
+		<chapter name="myFirstChapter">
+			<!--<paragraph>
+			<text>
+			Here we might have an introduction to the chapter, including some
+			overview of the chapters structure.
+			</text>
+			</paragraph>
+			<section name="myFirstSection">
+				<paragraph>
+				<text>
+				Here we might find the actual section content.
+				</text>
+				</paragraph>
+			</section>
+			<section name="mySndSection">
+				<paragraph>
+				<text>
+				Here we might find the actual section content.
+				</text>
+				</paragraph>
+			</section>-->
+		</chapter>
+	</book>
+</document>