Â¥Ö÷

JenaÍÆÀí½éÉÜÖеÄÁ½¶ÎÓ¢ÎÄÃèÊö£¬¸÷λ´óÄðïæ¿´¿´¾ßÌåÊÇʲôÒâ˼ The default API supports accessing all entailed information at the level of individual triples. This is surprisingly flexible but there are queries which cannot be easily supported this way. The first such is when the query needs to make reference to an expression which is not already present in the data. For example, in description logic systems it is often possible to ask if there are any instances of some class expression. Whereas using the triple-based approach we can only ask if there are any instances of some class already defined (though it could be defined by a bNode rather than be explicitly named). To overcome this limitation the InfModel API supports a notion of "posit", that is a set of assertions which can be used to temporarily declare new information such as the definition of some class expression. These temporary assertions can then be referenced by the other arguments to the listStatements command. With the current reasoners this is an expensive operation, involving the temporary creation of an entire new model with the additional posits added and all inference has to start again from scratch. Thus it is worth considering preloading your data with expressions you might need to query over. However, for some external reasoners, especially description logic reasoners, we anticipate restricted uses of this form of listStatement will be important.    Êղؠ  ·ÖÏí   ¶¥(0)

----------------------------------------------
ŬÁ¦Ñ§Ï°ÓïÒåºÍ±¾Ìå~~

	µÚ2Â¥

¿´Á˺þ㬻¹ÊDz»Ì«Ã÷°×ÕâÁ½¶Î»°µÄÈ·ÇÐÒâ˼£¬°ÝÍи÷λ°ï°ïСµÜÁË£¡£¡

----------------------------------------------
ŬÁ¦Ñ§Ï°ÓïÒåºÍ±¾Ìå~~

	µÚ3Â¥

Ö÷ÒªÊǽ²jenaÖÐInfModelµÄʵÏÖ»úÖÆ£¬Ò²¾ÍÊÇa notion of "posit"ÕâÖÖ·½·¨£¬ËüÄÜ¿Ë·þµÚÒ»¶ÎËù˵µÄ¾ÖÏÞÐÔ£¬µ«ÊÇĿǰʵÏÖЧÂʱȽϵͣ¬ËùÒÔÒªrestricted uses of this form of listStatement

	µÚ4Â¥

Â¥ÉϵĴó¸ç£¬Äã½²µÄÕâЩ̫high levelÁË°É¡£¡£¡£¡£Äܲ»ÄܾßÌåЩ¡£¡£¡£ ÎÒ¾Íû¸ãÇå³þ£¬ÃèÊöÂß¼­ÏµÍ³ºÍ»ùÓÚÈýÔª×éµÄ·½·¨²»Í¬Ö®´¦ÔÚÄÄÀï¡£¡£¡£

----------------------------------------------
ŬÁ¦Ñ§Ï°ÓïÒåºÍ±¾Ìå~~