Ruben Verborgh’s data

Matches in Ruben’s data for { <https://dx.doi.org/10.1016/j.websem.2019.04.001> ?p ?o }

• j.websem.2019.04.001 author me.
• j.websem.2019.04.001 author tom_schrijvers.
• j.websem.2019.04.001 author dorthe_arndt.
• j.websem.2019.04.001 author me.
• j.websem.2019.04.001 creator me.
• j.websem.2019.04.001 creator tom_schrijvers.
• j.websem.2019.04.001 creator dorthe_arndt.
• j.websem.2019.04.001 creator me.
• j.websem.2019.04.001 about Notation_.
• j.websem.2019.04.001 about reasoning.
• j.websem.2019.04.001 about Research.
• j.websem.2019.04.001 about RDF.
• j.websem.2019.04.001 author me.
• j.websem.2019.04.001 author tom_schrijvers.
• j.websem.2019.04.001 author dorthe_arndt.
• j.websem.2019.04.001 author me.
• j.websem.2019.04.001 coparticipatesWith me.
• j.websem.2019.04.001 coparticipatesWith tom_schrijvers.
• j.websem.2019.04.001 coparticipatesWith dorthe_arndt.
• j.websem.2019.04.001 coparticipatesWith me.
• j.websem.2019.04.001 type PublicationVolume.
• j.websem.2019.04.001 type ScholarlyArticle.
• j.websem.2019.04.001 type Article.
• j.websem.2019.04.001 type Document.
• j.websem.2019.04.001 type Document.
• j.websem.2019.04.001 type Document.
• j.websem.2019.04.001 type Q386724.
• j.websem.2019.04.001 type CreativeWork.
• j.websem.2019.04.001 type Work.
• j.websem.2019.04.001 P50 me.
• j.websem.2019.04.001 P50 tom_schrijvers.
• j.websem.2019.04.001 P50 dorthe_arndt.
• j.websem.2019.04.001 P50 me.
• j.websem.2019.04.001 maker me.
• j.websem.2019.04.001 maker tom_schrijvers.
• j.websem.2019.04.001 maker dorthe_arndt.
• j.websem.2019.04.001 maker me.
• j.websem.2019.04.001 title "Implicit quantification made explicit: How to interpret blank nodes and universal variables in Notation3 Logic".
• j.websem.2019.04.001 isPartOf journal_of_web_semantics.
• j.websem.2019.04.001 name "Implicit quantification made explicit: How to interpret blank nodes and universal variables in Notation3 Logic".
• j.websem.2019.04.001 label "Implicit quantification made explicit: How to interpret blank nodes and universal variables in Notation3 Logic".
• j.websem.2019.04.001 name "Implicit quantification made explicit: How to interpret blank nodes and universal variables in Notation3 Logic".
• j.websem.2019.04.001 topic Notation_.
• j.websem.2019.04.001 topic reasoning.
• j.websem.2019.04.001 topic Research.
• j.websem.2019.04.001 topic RDF.
• j.websem.2019.04.001 subject Notation_.
• j.websem.2019.04.001 subject reasoning.
• j.websem.2019.04.001 subject Research.
• j.websem.2019.04.001 subject RDF.
• j.websem.2019.04.001 authorList b0_b1940.
• j.websem.2019.04.001 topic Notation_.
• j.websem.2019.04.001 topic reasoning.
• j.websem.2019.04.001 topic Research.
• j.websem.2019.04.001 topic RDF.
• j.websem.2019.04.001 abstract "Since the invention of Notation3 Logic, several years have passed in which the theory has been refined and applied in different reasoning engines like cwm, EYE, and FuXi. But despite these developments, a clear formal definition of Notation3’s semantics is still missing. This does not only form an obstacle for the formal investigation of that logic and its relations to other formalisms, it has also practical consequences: in many cases the interpretations of the same formula differ between reasoning engines. In this paper we tackle one of the main sources of that problem, namely the uncertainty about implicit quantification. This refers to Notation3’s ability to use bound variables for which the universal or existential quantifiers are not explicitly stated, but implicitly assumed. We provide a tool for clarification through the definition of a core logic for Notation3 that only supports explicit quantification. We specify an attribute grammar which maps Notation3 formulas to that logic according to the different interpretations and thereby define the semantics of Notation3. This grammar is then implemented and used to test the impact of the differences between interpretations on practical cases. Our dataset includes Notation3 implementations from former research projects and test cases developed for the reasoner EYE. We find that 31% of these files are understood differently by different reasoners. We further analyse these cases and categorize them in different classes of which we consider one most harmful: if a file is manually written by a user and no specific built-in predicates are used (13% of our critical files), it is unlikely that this user is aware of possible differences. We therefore argue the need to come to an agreement on implicit quantification, and discuss the different possibilities.".
• j.websem.2019.04.001 datePublished "2019".
• j.websem.2019.04.001 mainEntityOfPage arndt_jws_2019.
• j.websem.2019.04.001 sameAs j.websem.2019.04.001.
• j.websem.2019.04.001 isPrimaryTopicOf arndt_jws_2019.
• j.websem.2019.04.001 page arndt_jws_2019.
• j.websem.2019.04.001 number "58".
• j.websem.2019.04.001 number "100501".
• j.websem.2019.04.001 volume "58".
• j.websem.2019.04.001 locator "58".
• j.websem.2019.04.001 locator "100501".
• j.websem.2019.04.001 volume "58".
• j.websem.2019.04.001 position "58".
• j.websem.2019.04.001 volumeNumber "58".
• j.websem.2019.04.001 endingPage "100501".
• j.websem.2019.04.001 startingPage "100501".
• j.websem.2019.04.001 pageEnd "100501".
• j.websem.2019.04.001 pageStart "100501".
• j.websem.2019.04.001 pageEnd "100501".
• j.websem.2019.04.001 pageStart "100501".