[Versa] Versa issue: drawing the line on entailments

[Uche Ogbuji]

Well, Mike opened the door, so I guess I'll just have to heave through
with my huge catalog of open Versa issues.

First one: a while back Chime wondered what sort of entailments Versa
should sanction at the language level.  His message:

http://lists.fourthought.com/pipermail/ril/2004-September/000354.html

We should have a proper answer to this in the spec.  Right now 4Suite's
implementation does rdf:type inferencing, as he says, but I've always
been willing to separate the query language from such matters.  My
suggestion is that we state that Versa does not require any entailment
within an RDF model, but that a back end is free to do so.  Sure this
means that Versa results can different between back ends, but I think
that what inferences an implementation handles for the user is a
separate issue to document.


-- 
Uche Ogbuji                               Fourthought, Inc.
http://uche.ogbuji.net                    http://fourthought.com
http://copia.ogbuji.net                   http://4Suite.org
Use CSS to display XML, part 2 - http://www-128.ibm.com/developerworks/edu/x-dw-x-xmlcss2-i.html
XML Output with 4Suite & Amara - http://www.xml.com/pub/a/2005/04/20/py-xml.html
Use XSLT to prepare XML for import into OpenOffice Calc - http://www.ibm.com/developerworks/xml/library/x-oocalc/
Schema standardization for top-down semantic transparency - http://www-128.ibm.com/developerworks/xml/library/x-think31.html