From a7019614896fdd3e29b9a28f6a8cfd2c1b365983 Mon Sep 17 00:00:00 2001
From: Benjamin Paassen <bpaassen@techfak.uni-bielefeld.de>
Date: Sun, 1 Mar 2015 20:47:25 +0100
Subject: Renamed domain to ontology.

---
 data/domain/headings.osxml | 33 ---------------------------------
 1 file changed, 33 deletions(-)
 delete mode 100644 data/domain/headings.osxml

(limited to 'data/domain/headings.osxml')

diff --git a/data/domain/headings.osxml b/data/domain/headings.osxml
deleted file mode 100644
index 055a204..0000000
--- a/data/domain/headings.osxml
+++ /dev/null
@@ -1,33 +0,0 @@
-<?xml version="1.0" standalone="yes"?>
-<domain name="headings">
-
-	<import rel="domain" src="book"/>
-
-	<struct name="heading" cardinality="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. -->
-		<parentRef ref="book.book">
-			<field name="heading" isSubtree="true" optional="true"/>
-		</parentRef>
-		<parentRef ref="book.chapter">
-			<field name="heading" isSubtree="true" optional="true"/>
-		</parentRef>
-		<parentRef ref="book.section">
-			<field name="heading" isSubtree="true" optional="true"/>
-		</parentRef>
-		<parentRef ref="book.subsection">
-			<field name="heading" isSubtree="true" optional="true"/>
-		</parentRef>
-		<parentRef ref="book.paragraph">
-			<field name="heading" isSubtree="true" optional="true"/>
-		</parentRef>
-		<!-- 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 ref="book.paragraph.$default"/>
-	</struct>
-</domain>
-- 
cgit v1.2.3