summaryrefslogtreecommitdiff
path: root/testdata/osxmlparser/comments_ontology.osxml
blob: f2423be2096b6a9c97b5f03009d87c0205f48af3 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
<?xml version="1.0" standalone="yes"?>
<ontology name="comments">
	<import rel="ontology" src="./book_ontology.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>
</ontology>