ontology: Remove cardinality limits on nmo:communicationChannel

For at least the case of feed messages (the only user of
nmo:communicationChannel inside Tracker), this does not
quite represent reality, a same message can come from different
channels (eg. same developers across several planet feeds),
so remove the cardinality limit.

The change also affects the indices created on the nmo:Message
table, there will be an implicit index for the multivalued field,
so there's no need for tracker:indexed, the secondary index shared
with nmo:receivedDate has changed into making an index on
nmo:receivedDate itself, it should yield similar results together
with the index on the new standalone table for nmo:communicationChannel.

Regarding compliance with Nepomuk, nmo:communicationChannel got stuck
forever as an enhancement request at
http://dev.nepomuk.semanticdesktop.org/ticket/722, so it's not something
to care about here.

1 files changed, 2 insertions, 4 deletions

diff --git a/src/ontologies/34-nmo.ontology b/src/ontologies/34-nmo.ontology
index 063753387..c6d475c3b 100644
--- a/src/ontologies/34-nmo.ontology
+++ b/src/ontologies/34-nmo.ontology
@@ -12,7 +12,7 @@
 
 nmo: a tracker:Namespace, tracker:Ontology ;
 	tracker:prefix "nmo" ;
-	nao:lastModified "2011-08-16T11:00:00Z" .
+	nao:lastModified "2015-07-26T12:30:00Z" .
 
 # FIXME Extension requested in Nepomuk
 nmo:MimePart a rdfs:Class ;
@@ -236,6 +236,7 @@ nmo:messageSubject a rdf:Property ;
 nmo:receivedDate a rdf:Property ;
 	nrl:maxCardinality 1 ;
 	rdfs:domain nmo:Message ;
+	tracker:indexed true ;
 	rdfs:range xsd:dateTime .
 
 nmo:replyTo a rdf:Property ;
@@ -272,9 +273,6 @@ nmo:conversation a rdf:Property ;
 
 nmo:communicationChannel a rdf:Property ;
 	rdfs:comment "Connects this message to a communication channel. Every message must only be in a single channel." ;
-	tracker:indexed true ;
-	tracker:secondaryIndex nmo:receivedDate ;
-	nrl:maxCardinality 1 ;
 	rdfs:domain nmo:Message ;
 	rdfs:range nmo:CommunicationChannel .