summaryrefslogtreecommitdiff
path: root/data/ontology/comments.osxml
diff options
context:
space:
mode:
authorAndreas Stöckel <astoecke@techfak.uni-bielefeld.de>2015-03-03 15:17:51 +0100
committerAndreas Stöckel <andreas@somweyr.de>2015-03-03 15:17:51 +0100
commit78f24b65e4a84c528338cc52e71efa4aa58e656e (patch)
tree2a61cbdecae1f658999d226a9c9630bb90d9338c /data/ontology/comments.osxml
parent466ff991bcfad76d78100193aacbfaf74d542b26 (diff)
Renamed isSubtree to subtree and isRoot to root
Diffstat (limited to 'data/ontology/comments.osxml')
-rw-r--r--data/ontology/comments.osxml6
1 files changed, 3 insertions, 3 deletions
diff --git a/data/ontology/comments.osxml b/data/ontology/comments.osxml
index 621fe1c..97d152c 100644
--- a/data/ontology/comments.osxml
+++ b/data/ontology/comments.osxml
@@ -4,7 +4,7 @@
<!-- an annotation comment -->
<annotation name="comment">
- <field name="replies" isSubtree="true">
+ <field name="replies" subtree="true">
<childRef ref="reply"/>
</field>
<field name="content">
@@ -17,7 +17,7 @@
<!-- 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">
+ <field name="replies" subtree="true">
<childRef ref="reply"/>
</field>
<field name="content">
@@ -30,7 +30,7 @@
<!-- note that replies are organized in a tree fashion: One can also reply
to a reply -->
<struct name="reply">
- <field name="replies" isSubtree="true">
+ <field name="replies" subtree="true">
<childRef ref="reply"/>
</field>
<field name="content">