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.

---
 testdata/osxmlparser/comments_domain.osxml | 40 ------------------------------
 1 file changed, 40 deletions(-)
 delete mode 100644 testdata/osxmlparser/comments_domain.osxml

(limited to 'testdata/osxmlparser/comments_domain.osxml')

diff --git a/testdata/osxmlparser/comments_domain.osxml b/testdata/osxmlparser/comments_domain.osxml
deleted file mode 100644
index dc7742e..0000000
--- a/testdata/osxmlparser/comments_domain.osxml
+++ /dev/null
@@ -1,40 +0,0 @@
-<?xml version="1.0" standalone="yes"?>
-<domain name="comments">
-	<import rel="domain" src="./book_domain.osxml"/>
-
-	<!-- an annotation comment -->
-	<annotation name="comment">
-		<field name="replies" isSubtree="true">
-			<childRef ref="reply"/>
-		</field>
-		<field name="content">
-			<childRef ref="book.paragraph"/>
-		</field>
-	</annotation>
-
-	<!-- an point-like structure comment. -->
-	<struct name="comment">
-		<!-- Is there a chance to prevent users from having to redefine these
-		     two fields in comment and reply? Could we use a fieldRef here?
-		     Or would that be circular? -->
-		<field name="replies" isSubtree="true">
-			<childRef ref="reply"/>
-		</field>
-		<field name="content">
-			<childRef ref="book.paragraph"/>
-		</field>
-		<parentRef ref="book.paragraph">
-			<fieldRef ref="$default"/>
-		</parentRef>
-	</struct>
-	<!-- note that replies are organized in a tree fashion: One can also reply
-	     to a reply -->
-	<struct name="reply">
-		<field name="replies" isSubtree="true">
-			<childRef ref="reply"/>
-		</field>
-		<field name="content">
-			<childRef ref="book.paragraph"/>
-		</field>
-	</struct>
-</domain>
-- 
cgit v1.2.3