From e76f58e912bd6661ba755d27da97bebf711f06ad Mon Sep 17 00:00:00 2001
From: Benjamin Paassen <bpaassen@techfak.uni-bielefeld.de>
Date: Wed, 4 Feb 2015 18:24:32 +0100
Subject: added mechanism for parent parsing, which does not fully work as of
 now.

---
 testdata/xmlparser/headings_domain.oxm | 33 +++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 testdata/xmlparser/headings_domain.oxm

(limited to 'testdata/xmlparser/headings_domain.oxm')

diff --git a/testdata/xmlparser/headings_domain.oxm b/testdata/xmlparser/headings_domain.oxm
new file mode 100644
index 0000000..f83843c
--- /dev/null
+++ b/testdata/xmlparser/headings_domain.oxm
@@ -0,0 +1,33 @@
+<?xml version="1.0" standalone="yes"?>
+<domain name="headings">
+
+	<import rel="domain" src="./book_domain.oxm"/>
+
+	<struct name="heading" cardinality="{0-1}" transparent="true">
+		<!-- The parent mechanism is a curious thing. Remind yourself
+		     that parent-child-relationship in this sense are mediated
+		     by fields. So we must either reference a field that is
+		     already there or declare a new one on the fly. -->
+		<parent name="book.book">
+			<field name="heading" isSubtree="true"/>
+		</parent>
+		<parent name="book.chapter">
+			<field name="heading" isSubtree="true"/>
+		</parent>
+		<parent name="book.section">
+			<field name="heading" isSubtree="true"/>
+		</parent>
+		<parent name="book.subsection">
+			<field name="heading" isSubtree="true"/>
+		</parent>
+		<parent name="book.paragraph">
+			<field name="heading" isSubtree="true"/>
+		</parent>
+		<!-- regarding its fields we have a problem here. We do not want to
+		     declare a new field, because in fact we want to allow every
+		     bit of content that a paragraph would allow - also considering
+		     possible extensions of paragraph by other domains.
+		     So we need to reference the default field of paragraph. -->
+		<fieldRef name="book.paragraph."/>
+	</struct>
+</domain>
-- 
cgit v1.2.3