Ehm, is this supposed to be SPAM? I remember that you also made this same weird suggestion in a previous thread without given any background why. And I still don't understand what Executable English is supposed to be ... I never heard about anybody using it nor do I think that any customer will think about using it given that - well, let's call it "quite old" fashioned web appearance ...
So, for me this attempt is more than off-topic. And sorry, I don't want to be rude, I'm just confused by your messages on the Apache Jena mailing list, when a user asks for support and not about alternatives @others: do you know anything about this tool/project/framework whatever? > Hi Pierre, > > You may like to write your example in Executable English. (The vocabulary > is open, > so you could also use phrases in French). > > Executable English is a platform for cooperative writing of self-serve, > self-explaining analytics in open vocabulary English. It's live online > with many examples. You are cordially invited to write and run your own > examples too. Just point your browser to executable-english.com . Shared > use is free, and there are no commercials. > > Enjoy! - Adrian > > Adrian Walker > Executable English LLC > San Jose, CA, USA > (USA) 860 830 2085 (California time) > www.executable-english.com > > > > > > On Fri, Jul 19, 2019 at 9:48 AM Pierre Grenon <[email protected]> > wrote: > >> Hello, >> >> (I apologise for I am not sure if this has been addressed before and I >> have not found the right thread or documentation.) >> >> The configuration file below seems to allow reasoning with either a GRR or >> an out of the box reasoner on the same dataset. >> >> However, I don't think it allows combining inferences from both reasoners >> at the same time. I am not sure how to achieve this through configuration. >> >> (Happy to provide an example of data and rule for the GRR. I've noticed >> this when adding a rule to classify undeclared individuals, i.e., >> individuals appearing in the subject position of a triple. The rule to the >> effect that if they do, they are instances of a class A. It is possible to >> derive the instantiation. However, it is not possible to combine it with >> type inheritance from a reasoner. If class A is a subclass of class B, >> there is no inference to the effect that the individual is also an instance >> of class B.) >> >> With many thanks and kind regards, >> Pierre >> >> >> >> >> ----- >> >> >> @prefix : <http://base/#> . >> @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . >> @prefix tdb2: <http://jena.apache.org/2016/tdb#> . >> @prefix ja: <http://jena.hpl.hp.com/2005/11/Assembler#> . >> @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . >> @prefix fuseki: <http://jena.apache.org/fuseki#> . >> >> :theService a fuseki:Service ; >> rdfs:label "Service with update and query to >> test minimal dataset with inference using an instance of generic rule >> reasoner and RDFSExptRuleReasoner" ; >> fuseki:dataset :theDataset ; >> #:tdb_dataset_readwrite ; >> fuseki:name "Conference2" ; >> fuseki:serviceQuery "query" , "sparql" ; >> fuseki:serviceReadGraphStore "get" ; >> fuseki:serviceReadWriteGraphStore >> "data" ; >> fuseki:serviceUpdate "update" ; >> fuseki:serviceUpload "upload" . >> >> :theDataset a ja:RDFDataset ; >> ja:defaultGraph <#theUnionModel> >> . >> >> <#theUnionModel> a ja:UnionModel ; >> ja:rootModel <#theRootModel> ; >> ja:subModel <#theModel_GRR> , <#theModel_RDFS> . >> >> <#theRootModel> a ja:Model ; >> ja:baseModel <#theGraph> ; >> . >> >> >> <#theModel_GRR> a ja:InfModel ; >> ja:baseModel <#theGraph> ; >> ja:reasoner [ >> ja:reasonerURL < >> http://jena.hpl.hp.com/2003/GenericRuleReasoner> ; >> ja:rulesFrom >> <file:///C:/dev/apache-jena-fuseki-3.10.0/data/conference/conference1.rules> >> >> ] ; >> . >> >> THIS E-MAIL MAY CONTAIN CONFIDENTIAL AND/OR PRIVILEGED INFORMATION. >> IF YOU ARE NOT THE INTENDED RECIPIENT (OR HAVE RECEIVED THIS E-MAIL >> IN ERROR) PLEASE NOTIFY THE SENDER IMMEDIATELY AND DESTROY THIS >> E-MAIL. ANY UNAUTHORISED COPYING, DISCLOSURE OR DISTRIBUTION OF THE >> MATERIAL IN THIS E-MAIL IS STRICTLY FORBIDDEN. >> >> IN ACCORDANCE WITH MIFID II RULES ON INDUCEMENTS, THE FIRM'S EMPLOYEES >> MAY ATTEND CORPORATE ACCESS EVENTS (DEFINED IN THE FCA HANDBOOK AS >> "THE SERVICE OF ARRANGING OR BRINGING ABOUT CONTACT BETWEEN AN INVESTMENT >> MANAGER AND AN ISSUER OR POTENTIAL ISSUER"). DURING SUCH MEETINGS, THE >> FIRM'S EMPLOYEES MAY ON NO ACCOUNT BE IN RECEIPT OF INSIDE INFORMATION >> (AS DESCRIBED IN ARTICLE 7 OF THE MARKET ABUSE REGULATION (EU) NO >> 596/2014). >> (https://www.handbook.fca.org.uk/handbook/glossary/G3532m.html) >> COMPANIES WHO DISCLOSE INSIDE INFORMATION ARE IN BREACH OF REGULATION >> AND MUST IMMEDIATELY AND CLEARLY NOTIFY ALL ATTENDEES. FOR INFORMATION >> ON THE FIRM'S POLICY IN RELATION TO ITS PARTICIPATION IN MARKET SOUNDINGS, >> PLEASE SEE https://www.horizon-asset.co.uk/market-soundings/. >> >> HORIZON ASSET LLP IS AUTHORISED AND REGULATED >> BY THE FINANCIAL CONDUCT AUTHORITY. >> >> >> -- Lorenz Bühmann AKSW group, University of Leipzig Group: http://aksw.org - semantic web research center
