2001
DOI: 10.1007/3-540-45653-8_35
|View full text |Cite
|
Sign up to set email alerts
|

A Computer Environment for Writing Ordinary Mathematical Proofs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

1
14
0

Year Published

2009
2009
2017
2017

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 13 publications
(15 citation statements)
references
References 4 publications
1
14
0
Order By: Relevance
“…The need for natural interfaces (both superficial and functional) in automated verification has been recognized to varying degrees by the designers of the Tutch proof checker [1], the Scunak mathematical assistant system [9], the ForTheL language and SAD proof assistant [31], the EPGY Theorem-Proving Environment [21], the ΩMEGA proof verifier [28], and in the work of Sieg and Cittadini [27]. The ontology-oriented, lightweight verification capabilities of the automated assistant are inspired by work in the assembly of large-scale formal and semi-formal ontologies [24].…”
Section: Related Work and Conclusionmentioning
confidence: 99%
“…The need for natural interfaces (both superficial and functional) in automated verification has been recognized to varying degrees by the designers of the Tutch proof checker [1], the Scunak mathematical assistant system [9], the ForTheL language and SAD proof assistant [31], the EPGY Theorem-Proving Environment [21], the ΩMEGA proof verifier [28], and in the work of Sieg and Cittadini [27]. The ontology-oriented, lightweight verification capabilities of the automated assistant are inspired by work in the assembly of large-scale formal and semi-formal ontologies [24].…”
Section: Related Work and Conclusionmentioning
confidence: 99%
“…Human users, who are not necessarily ATP experts, are often the source of the initial input to, and the destination of the final output from, ATP tools. Human data formats are often semi-formal, and translation is required to and from a machine usable format, e.g., [Fie01,MRS01]. In an ideal world it would not be necessary for humans to look at the machine usable input and output, nor at intermediate data being passed between tools in a component based system.…”
Section: Introductionmentioning
confidence: 99%
“…This hampers their usability within a mathematical tutoring environment. For example, when the theorem prover Otter (McCune, 2003) was used in the EPGY learning environment for checking studentgenerated proof steps, it sometimes verified seemingly large student steps easily, whereas other, seemingly trivial steps were not verified within an appropriate resource limit (McMath et al, 2001). This criticism applies foremost to machine-oriented theorem proving systems, for example, systems based on fine-grained resolution or tableaux calculi.…”
Section: Introductionmentioning
confidence: 99%