QCR vs. non-QCR

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

QCR vs. non-QCR

Does Protege still allow *non*-qualified cardinality restrictions? I have the
following Turtle bit:

This amounts in Manchester syntax to

Interestingly, Protege construes this as

The problem is that the property  has a certain well-specified range, range
that is *not*  (though certainly included in it). Why is it that Protege
turns my emphatically non-QCR into a QCR?

Sent from: http://protege-project.136.n4.nabble.com/Protege-User-f4659818.html
protege-user mailing list
[hidden email]