BEGIN:VCALENDAR
PRODID:-//Grails iCalendar plugin//NONSGML Grails iCalendar plugin//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VEVENT
DTSTAMP:20260920T111737Z
DTSTART;TZID=Australia/Melbourne:20190301T060000
DTEND;TZID=Australia/Melbourne:20190301T080000
SUMMARY:Consequence theoretic semantics and entailment
UID:20260920T111737Z-iCalPlugin-Grails@fe80:0:0:0:20f6:41ff:fe59:be4a%3
TZID:Australia/Melbourne
LOCATION:Old Arts\, Parkville\, Australia\, 3010
DESCRIPTION:<p>Dave Ripley (Monash) will present "Consequence theoretic semantics and entailment" at 11 in Old Arts 152 on 1 March.</p>\n<p>Abstract: The purpose of this talk is to present and begin to articulate an alternative to both model-theoretic and proof-theoretic semantics: consequence-theoretic semantics. On this approach\, both proofs and models are mere technical auxiliaries\, without any direct connection to meaning. Meaning is rather located in the consequence relation itself. The key theoretical notion I will use\, borrowing from Greg Restall\, is that of a position---a collection of assertions and denials. Some positions are ruled out\, and others are not.</p>\n<p>On this basis\, a consequence-theoretic semantics\, like any semantics\, owes (among other things) an account of entailment. But while consequence is a matter of ruling out\, entailment seems to be a matter of guaranteeing or ruling in\; it's not immediately obvious how to use a position-theoretic framework to understand entailment. This talk shows how to do it\, by developing a notion of equivalence between positions\, and using this to understand when assertions and denials can be implicit in a position. Seen this way\, entailment and consequence might have the same extension\, or they might not\; it depends on what structural features consequence itself has. I'll show a few examples of this dependence.</p>\n&nbsp\;
ORGANIZER;CN=Shawn Standefer:
METHOD:PUBLISH
END:VEVENT
END:VCALENDAR
