Archive for the ‘CoPs in Math’ Category

Three types of mathematicians

Wednesday, November 26th, 2008

Cristian Calude and I discussed the price and gains of content mark-up. He emphasized that unless we provide interesting features, mathematicians will not see the value in content mark-up and the reason for additional efforts (e.g. when using sTeX instead of LaTeX).

Below you find three groups of mathematician that most likely need different amount of arguments to be convinced (please note that I am not citing Cris. I simply present what I remember from our discussion and made up the names of the groups):

  • Pen-and-Paper guys: They only use computers for publishing but all mathematics is actual developed on paper. The publishing process is seen as a tedious and inconvenient activity that takes time away from the actual job that a mathematicians wants to do. The digitalization is annoying (proof reading). In earlier times, this was done by secretaries and the publisher, but nowadays publishers only accept LaTeX, which is really seen as a burden by this group of mathematician.
  • LaTeX Lovers: There are mathematicians that think in LaTeX. The use it a lot for developing their ideas and incrementally revising proofs with colleagues. This groups seems to have an increasing influence on scientific publishing as most publisher (in mathematics) will nowadays reject a submission if it is not provided in LaTeX.
  • Innovators: The third group wants even more. (We didn’t really talk about this group long) For example, this groups promotes semantic technologies and aims at making mathematics machine-processable as well as bringing mathematics to the web. I assume that includes vast parts of the MKM community.

Maybe we need to start asking ourselves: Would we use our tools and services? (Who is using sTeX?) And if so, for which activities? Think of the very early steps towards a new topic. Would you like to be forced to content mark-up? Although we provide full flexibility in switching between concepts, simply having to establish theories and marking up structure really slows down the creative thinking. So when is a good timing of using content-based techniques? Do we restrict it to the very last stage of scientific work, i.e. the publishing process, or teaching (the latter not even recognized as scientific activity)?

I am collecting arguments on gains and burdens of content mark-up (in the panta rhei trac), in particular, with a focus on the technologies and services provided by KWARC. I’d appreciate your feedback and comments!

Assessment and Reputation System for Mathematics

Wednesday, October 22nd, 2008

I have the feeling that the challenge of bringing mathematicians and computers closer together, requires a lot of expertise in the field of pure mathematics and the more technical-field of mathematical knowledge management. The latter requires a good overview on mathematical tools, in particular, computer algebra systems and theorem provers as well as other mathematical editors (e.g. Plato). Moreover, the step-wise formalization of mathematical text seems to be a core interest and competence of the whole KWARC group rather then my own research focus.

Looking at the discussion with Cris on the confidence in proofs, acceptance of proofs as well as trust in proofs, I am wondering, whether we could use our understanding of the mathematical practice and use it for providing an assessment and reputation system for mathematics, i.e. something that we could attach onto a repository of mathematical knowledge and use to facilitate the collaboratively assessment of the mathematical community on different layers:

  • Is (the proof) published in journals (considering the impact factor of these journals)
  • Was it accepted by the Zentralblatt or Mathematical Reviews (adding more confidence)?
  • How long was the proof tested by the mathematical community?
  • How many proofs do exist for the theorem?
  • Is it a nice proof/ theorem (beauty)?
  • Is it correct? (later adding automatic verification methods …)
  • Can it be understood (e.g. measured by the numbers of references and re-uses)? How hard can it be understood?
  • Is it re-used by the community, i.e. is it relevant and useful for further mathematical work?

We can imagine a top-down and bottom-up approach:

  1. The top down approach requires the user’s explicit assessment of the content: evaluating the users’ ratings, tags, bookmarks
  2. The bottom up approach could implicitly provide the relevance of content making use of the logical and narrative structure of the mathematical knowledge: computing theory interrelations, citations, …

I will discuss with Cris, whether he thinks that this would lead to a useful application for mathematicians.

Discussion with Cristian Calude

Tuesday, October 21st, 2008

My second meeting with Cristian Calude has clarified some of the issues from the first meeting
Please note that Cris does not necessarily share my personal opinions and summaries on this page.

  • Confidence in and Acceptance of proofs: In the previous meeting, I haven’t be sure about what Cris means with context. Cris means by this, that the confidence in a theorem increases by the number of applications, i.e. the number of times it is reused by others e.g. to prove another theorem. This application can be interpreted in two ways: (1) Other mathematicians understood the prove and (2) the mathematical community assessed this contribution to be relevant. In particular, Cris again pointed out that there a several dimensions of a accepted and significant theorem: Neither beauty nor correctness are enough, but it also has to be understood and used by the community, i.e. it needs to be relevant and useful for further mathematical work.
  • Reusing trusted and correct Theorems: Cris illustrated today how critical it is to reuse only trusted and correct theorems and that even then mathematicians have no certainty as there is no absolute correctness: In 1988, Yoichi Miyaoka, number theorist at the Max Planck Institute in Bonn, claimed that he had proven the Fermat’s Theorem (eventually proved by A. Wiles). As I was told, his actual proof was not the direct flaw, but when checking his proof step-by-step, the professional referees identified that one of the theorems he re-used was incorrect. However, that theorem had been published and reused by other mathematicians, but had not been carefully checked so far (cf. NY Time). This is a phenomena I have heard before, i.e. sometimes proofs without central interest to the community are not extensively checked.
  • Mathematics and Computers: As far as I understood, Cris is interested in integrating traditional and unconventional mathematics, i.e. axiomatic-deductive thinking and computer-supported experimenting to finally achieve a proof. He believes that mathematical proofs will more and more be checked by computers. Of course, this will be a gradual process, from solely human referees to fully automatized proof checking. In our last meeting, we identified to ways of addressing the problem of bringing mathematicians and computers closer together: (1) less formal and human-friendly systems and (2) new ways (of thinking and the respective tools) for encoding mathematical knowledge. Cris is envisioning a process that will support authors to convert their proofs (consisting of text and formulae) to fully formal formats that can be object of automatic provers. In a first step, he would like to see that we can distinguish pure comments from text that is part of the proof. This would require tools and a respective representation format for mathematical documents: The tools need to (semi-)automatize the annotation of mathematical text. Different technologies can be of use from natural language parsing to semi-automated semantic annotation ideally integrated in the publication processes of mathematicians (see sTeX as semantic extension for LaTeX; invasive editors for MS PPT and Word; Sentido; and SWiM). The format has to support the mark-up of narrative, rhetorical, but also mathematical concepts (see OMDoc and its extension in the 2.0 version). However, apart from the format and tools, Cris vision also includes a social aspect that has to evolve over time, i.e. mathematicians have to trust in computer-checked proofs and they actually have to use the tools for formalizing their documents and this leads us to an ongoing-discussion, also referred to as authoring-dilemma (see Andrea’s work).
  • Collaboration with Cris: Potentially, Cris and I will work on a programmatic paper of what one should do to help integrating traditional and new mathematical practice, i.e. to motivate our this vision and to give concrete suggestion on how to realize it step by step. However, in a next meeting I will introduce him to my work and areas I am involved in, from there on we will make further decision. I will also give a seminar talk here in some weeks to introduce my work to the CS/ math department.

Proving and Programming

Tuesday, October 21st, 2008

Notes on Cristian S. Calude et al. (2007) Proving and Programming (see also previous post, see slides). Please note that the authors do not necessarily share my personal opinions and summaries on this page.

There is a strong analogy between proving theorems in mathematics and writing programs in computer science. Programming gives mathematics a new form of understanding. The computer is the driving force behind these changes.

  • “Theorems (in mathematics) correspond to algorithms and not programs (in computer science)”
  • “Programs (in computer science) correspond to mathematical models.”
  • Proving the correctness of algorithms is seldom a focus in software projects (but: even testing/ documenting is sometimes neglected)
  • Do some programming language facilitate/ required to put more focus on the correctness of the algorithms (e.g. functional language such as scala or ML; where programs are closer to mathematical models than in imperative languages)?
  • Can bugs be avoided? Can the use of rigorous mathematical proofs guarantee that software and hardware perform as expected?
  • Many projects and products dedicated to automated testing of program correctness, for example, VIPER or TestEra (automated testing of Java programs).
  • What do proof obligations (Verpflichtung) have to do with the correctness of programs?: e.g. Barthe et al. discuss the “interaction between compilation and verification condition generators (VC generators), which are used in many interactive verification environments to guarantee the correctness of source programs, and by several proof carrying code (PCC) architectures to check the correctness of compiled programs. Such VC generators operate on annotated programs that carry loop invariants and procedure specifications expressed as preconditions and postconditions, and yield a set of proof obligations that must be discharged in order to establish the correctness of the program.” (loop and procedure level; see also specification languages such as CASL for the representation of precondition, invariants, and postconditions, i.e. proofs obligation)
  • But correctness proof for a program, adds very little to one’s confidence in the program: “Beware of bugs in the above code: I have only proved it correct, not tried it. (Knuth)” (p.310)
  • Checking new types of proofs: probabilistic, experimental, hybrid proofs (computation plus theoretical arguments) (p.311 ff.)

Further readings

Mathematical Proving

Tuesday, October 21st, 2008

Notes on (1) Cristian S. Calude et al. (2003) Passages of Proof and (2) Cristian S. Calude et al. (2004): Mathematical Proofs at a Crossroad .

Please note that the authors do not necessarily share my personal opinions and summaries on this page.

Stages of mathematics

  1. pre-Greek mathematics dominated by observation, intuition, experience
  2. Greek deductive mathematics based on theorems; Euclid’s geometry; see also Pythagoras,Thales, Aristotle, Euclid, Archimedis. (Euclid became the reference for axiomatic-deductive thinking, see more recent works in mathematics, physics, computer science, biology, linguistics, which follow this tradition)
  3. Mathematical language triggered by need for precision and rigour. Previously ordinary language was used “dominated by imprecision resulting from its predominantly spontaneous use, where emotional factors and lack of care have an impact”. Galilei, Descartes, Newton, Leibniz, … contribute to a shift from ordinary to a mixed language, i.e. ordinary language supplemented by an artificial component of symbols, formulas, and equations
  4. The epsilon rigour; 19th century, Cauchy, Weierstrass (coping with processes with infinitely many steps such as limit, continuity, differentiability, and integrability)
  5. The challenge of the principle of non–contradiction and the logical crisis (Russell–Whitehead, Hilbert, Brouwer); 19th/20th century; optimistic towards the possibility to arrange the whole mathematics as a formal system and to decide for any possible statement whether it is true or false.
  6. Gödel’s incompleteness theorem (1931): “every formal system which is finitely specified, rich enough to include the arithmetic, and consistent (free of contradiction), is incomplete”, distinction between truth and provability (1:p.173 ff.); Chaitin (1975) suggests that complexity is a source of incompleteness
  7. Reconciliation of empirical–experimental mathematics with deductive mathematics (today): Four-colour Problem (4CT; 1976; by Kenneth Appel & Wolfgang Haken; proof of 4CT by Neil Robertson, Daniel P. Sanders, Paul Seymour and Robin Thomas ; or the Kepler Conjecture by Thomas Hales) realized by the use of computer programs as pieces of mathematical proof
  8. Quantization: Proofs are no longer exclusively based on logic and deduction, but also empirical and experimental.

What is mathematical proof?

  • “A proof is a series of logical steps based on some axioms and deduction rules which reaches a desired conclusion. Every step in a proof can be checked for correctness by examining it to ensure that it is logically sound.” (1:p. 171)
  • But who checks the proof (as human and Computer agents make mistakes)? Often proofs are falsified after having been published and then corrected (e.g. Appel/ Haken take on Kempe’s ideas). Some proofs cannot be checked by single humans (being to long and/or accomplished by computer-assistance) such as 4CT. (1:p. 171)
  • “Mathematics cannot be conceived without proofs: [..] proofs and theorems go together; the object of a proof is to reach a theorem, while theorems are validated by proofs” (1:p.172).
  • But: Mathematics is more than proofs. “What the mathematical community seems to value most are ideas. The most respected mathematicians are those with strong intuitions. (Harris)”. (1:p.172)
  • Three dimensions of proofs:
    • syntactically: the formal proof, but “proof is only one step in the direction of confidence” (1:p.174, see Edmund Landau)
    • semantically: (truth value) “correctness by itself does not validate a proof, it is also necessary to understand it” (1:p.175; René Thom, Daniel Cohen, William Thurston) “the mission of mathematics is understanding”, consequently, computer-assisted proofs are harder to accept (see 4CT), but also deductive proofs are sometimes only understood by few mathematicians (see 1:p.176), “a theorem is validated if it has been accepted by a general agreement of the mathematical community” (Thom, 1:p.178), “a theorem is a statement that could be checked individually by a mathematician and confirmed also individually by at least two or three mathematicians, each of them working independently” (1:p.178) thus proposing the notion of an “agnogram … a theorem-like statement that we have verified as best we could, but whose truth is not know with the kind of assurance we attach to theorems and about which we must thus remain, to some extend, agnostic” (Swart, 1:p.178), “we believe the experts and we cannot tell for ourselves” (1:p.179), “mathematics occupies a special place [among other disciplines], where we believe anyone who claims to have proved a theorem on the say – so of just a few people – that is, until we hear otherwise” (1:p.179), “… in mathematics you can really argue that this is as close to absolute truth as you can get (Joe Spencer)” (1:p.179)
    • pragmatical: (relevance & use) “truth is not where you find it, but where you put it” (Perlis). “no matter how precise the rules are, we need human consciousness to apply the rules and to understand them and their consequences” (1:p.183)
  • Aspects of mathematical proofs: deduction/ syllogistic reasoning (most visible aspect), but also: observation, intuition, experiment, visual representations, induction, analogy, and examples; some belonging to the preliminary steps, whose presence is not made explicit (when finally presenting the proof), but without which proofs cannot be conceived (2-p.17; see previous post); proving is a very heterogeneous process

In real life proofs may be different …

  • Proof by obviousness: “The proof is so clear that it need not be mentioned.”
  • Proof by general agreement: “All in favour?”
  • Proof by calculus: “This proof requires calculus, so we’ll skip it.”
  • Proof by lost reference: “I know I saw it somewhere”
  • Proof by necessity: “It had better be true, or the entire structure of mathematics would crumble to the ground.”
  • Proof by plausibility: “It sounds good, so it must be true.”
  • Proof by intimidation: “Don’t be stupid; of course it’s true.”
  • Proof by terror: When intimidation fails
  • Proof by lack of sufficient time: “Because of the time constraint, I’ll leave the proof to you.”
  • Proof by tessellation: “This proof is the same as the last.”
  • Proof by majority rule: Only to be used if general agreement is impossible
  • Proof by authority: “Well, Don’t Knuth says it’s true, so it must be!”
  • Proof by intuition: “I just have this gut feeling”

Towards Artificial Mathematics and quasi-empirical proofs

  • equivalence between the logical and computational proofs
  • logical/ conventional proofs: traditional; reasoning of humans (see Euclid, …); the logical process, i.e. finding a finite sequence of sentences strictly obeying some axioms and inference rules
  • computational/ unconventional: computational process (machines are constructed based on sequences of sentences by humans) producing these sequences; but: proofs can contain steps that can never be verified by humans (based on the equivalence: development of artificial mathematicians, i.e. theorem provers such as Mathematica, Maple, MathLab)
  • classical but unconventional proofs also comprise classical proof of excessive length and complexity (e.g. the classification of finite simple groups; 1:p.176/183)
  • Artificial mathematicians are far less ingenious and subtle than human mathematicians, but they surpass their human counterparts by being infinitely more patient and diligent.
  • Towards quantum computational proofs: conversion from computation into a sequence of sentences may not longer be possible, quantum automation are able to check a proof, but fail to reveal a “trace” of the proof (we don’t why it true), (quasi-empirical) quantum proofs might influence how we learn/ understand mathematics; leading to new ways to understand (and practice) mathematics, although we might not fully accept/trust unconventional proofs, the computational result is “a mathematical activity because it advances our knowledge of mathematics” (1:p.184)
  • Overall: “There is little difference between traditional and unconventional types of proofs as [..] i) mathematical truth cannot always be certified by proof, ii) correctness is not absolute, but almost certain, as mathematics advance by making mistakes and correcting and re-correcting them (see Lakatos), iii) non-deterministic and probabilistic proofs do not allow mistakes in the applications of rules, the are just indirect forms of checking, iv) the explanatory component, the understanding emerging from proofs [..] is subjective and has no bearing on formal correctness.” (1:p.184)
  • Experimental Mathematics – as systematic mathematical experimentation ranging from hypotheses building to assisted proofs and automated proof-checking-will play an increasingly important role and will become part of the mainstream of mathematics. There are many reasons for this trend: They range from logical (the absolute truth simply doesn’t exist), sociological (correctness is not absolute [..]), economic (powerful computers will be accessible to more and more people), and psychological (results and success inspire emulation)” (2-p.26)

Knowledge is acquired through reason and by experiment: Should proofs belong exclusively to logic? Or should we also accept empirical-experimental arguments? Towards blending logical and empirical-experimental arguments. There is hope for integration! (see also next post)

Discussion with Cristian Calude

Thursday, October 16th, 2008

My first meeting with Cristian Calude has brought up many interesting aspects and thoughts, I shortly sketch here and I do not yet fully understand …
Please note that Cris and all other researchers mention do not necessarily share my personal opinions and summaries on this page.

  • Mathematical Collaboration: In mathematics (and other disciplines), interdisciplinary authors often only know parts of the paper they co-author. If you contact one for the authors, your are sometimes directed to the original writer, as your contact might now able to tell you about all paragraphs in the paper. Cris has experienced this during papers with Chaitin, also both are well-experienced mathematicians, they have different ways of thinking (more visual in contrast to more analytical thinking), which sometimes made it difficult to understand each other’s solution.
  • Mathematical Proofs: Cris’s friend, a logician, never looks at proofs. If he likes a theorem, he tries to proof it himself, but studying other people’s proof is not of interest for him
  • Mathematical Practice: There is a research group of ethno-mathematicians here at the University of Auckland (e.g. see Bill Barton) looking at questions such as: How does the mother tongue language influence mathematics? Are the metaphors in different languages the same?
  • Struggling with Notations: When giving a lecture in Leibzig, Chris experienced that the students struggled with his lecture. They understood the ideas, but when it came to solving assignments and applying the concepts in the lecture, they struggled with notations introduced by Chris as they had learned others.
  • Mathematicians and Computers: Chris pointed to an interesting question: How can we train mathematicians to use computers and not to be afraid of their results (i.e. trust in automatic proofs)?. Many parts are implicit when proving, but computers need everything explicated. We have to ways of bringing mathematicians and computers closer together: (1) Making automatic provers more accessible and human-oriented, i.e. decreasing the level of formality needed for interacting with formal prove systems (see MKM proceedings on e.g. Mizar, i.e. “an attempt to reconstruct mathematical vernacular into a formal language which can be read by humans and also verified by software”, or Coq, Mathematica) and (2) Training mathematicians so that their encodings are more accessible for machines, i.e. in order to use computers, mathematicians need to change their way of encoding knowledge.
  • Mathematicians and Computers: For (2), Chris suggested to start at looking at referee processes: What kind of questions does a referee ask? What aspects do mathematical referee look at? They mostly do not fully check the presented proof and pose specific questions which may help us to identify how knowledge has to be encoded to be communicated more efficiently (between humans and eventually between humans and computers).
  • Mathematical Practice: There are two processes in mathematics: (1) The process of discovery, which is very informal, includes several gaps, and is a slow and iterative approaching of a more and more coherent solution. (2) The process of presenting a result, i.e. the writing up of a solution. Both processes are valuable. We know several tools supporting (2) and in our group we also aim at supporting this process (with a Wiki for collaborative editing and a management of change system, …). However, process (1) requires tools that do not kill the creativity of mathematicians, i.e. that do not enforce notations/ styles and require tedious and correct mark-up of thoughts … but leave room for intuitions, gaps, and mistakes. And also eLearning systems (e.g. panta-rhei) should support process (1) as mathematical education should not focus on the presentation of results but should teach students how to discover math. However, towards the end of process (1), mathematicians might have to/ want to draw on computers (theorem provers and computer algebra systems) to verify their results.
  • Confidence in and Acceptance of proofs: In mathematics we observe different degrees of confidence of a proof, i.e. a proof is accepted in a social process and on different layers: (1) It can be published in a journal (and thus reviewed and accepted by the journal chairs) and (2) it can be accepted by reviewers of the two reviewing databases, Mathematical Reviews and Zentralblatt, and (3) it can be certified (i.e. verified by computers; see e.g. Coquand et al). Moreover, (4) the credibility of a theory increases with the number of proofs for its theorems (see e.g. collection of 79 approaches to proving the Pythagorean theorem) and its use in different context (I am not yet sure what Cris means by context. My first guess is that this relates to the reuse of a theory and its interrelation to other theories, i.e. the number of views and theory morphism. Basically, the structures that were used by Immanuel and Florian to do their PhD on logic translation and theory management; see next meeting). To sum up, a proof is not necessarily correct, but its confidence can increase.
  • Communal Acceptance: The Clay Mathematics Institute of Cambridge, Massachusetts (CMI) nominates its Millennium Prize Problems for one million dollar. The respective proof has to be published and resist community testing for 2 years. Thus, the mathematical community is very aware of the fact that only publishing a proof does not mean that it is correct.

Further readings

Typicality of exercises

Saturday, September 20th, 2008

Discussion at the JEM Symposium on “math tutoring: tools and feedback” in Heerlen, Netherlands.

I have been reading a two papers by Manfred Kerber, Erica Melis, and Jörg Siekman on the typicality of examples which raised my interest and which I would like to further elaborate on. See below my notes on both papers. During the JEM Symposium I tried to get other perspectives on this topic:

Johan Jeuring mentioned that their worked out examples (in their exercise web service) are actually (hopefully/ ideally/ potentially) typical examples to illustrate a problem. The study of Gemma Corbalan showed that this kind of feedback was more helpful then only providing feedback to a concrete solution.

However, Johan was wondering whether the context-aware handling of typical exercises would provide a significant variance, that is, if the users’ subject views on what is typical really varies enough that a context-aware exercise framework and respective markup makes sense (in particular for mathematics; analogously to our notation framework). However, he also mentioned that in particular in computer science there are a lot of changes going on e.g. wrt. to which programming language is used for illustrating specific programming concepts.

George Goguadze said that he would not base the selection of examples on the typicality. First of all, teachers have a subjective view on which examples/ exercise are typical for a particular audience. And secondly, students have a subjective understanding what is typical (e.g. base don their prior education). But his comment actually illustrates that their are different understandings of typicality, so explicating these might potentially be helpful. For example, teachers can provide typical examples in their lecture, but receive feedback on the student’s view on these. Based on the exercise material (and a pool of further exercises) of the teacher, a tools could select the typical exercises from a student’s perspective (based on the interrelation and annotation of exercises).

Notes on the two papers by Manfred Kerber etAl:

  • Typical examples are examples that are representative for a particular situation or concept; they play an important role in human knowledge representation and reasoning (see also reasoning by analogy, case based reasoning)
  • Typical examples are easy to remember and are sufficient to catch important aspects of the general case.
  • We can distinguish different types of typical examples (depending of the type of concepts or situation they help to explain): procedural examples (e.g. illustrating an induction proof), typical examples for concepts (e.g. a violin, a chair), typical examples of a situation (e.g. opening a door); typical examples for a proof or a theorem, typical examples for a plan
  • Typicality of examples is a well-known research area in empirical psychology (see references below)
  • Representation of examples by a data structure like a semantic net, frame structure, or within neural net.
  • Typicality ratings distinguishes typical examples from atypical examples: direct ratings (Is this a typical example?); reaction time (Answer true or false: [example] is a [category-name]); reproduction of examples (list or draw an example of a category member); asymmetry of similarity rating (less typical examples are often considered to be more similar to typical example than the converse); generalization (Humans generalize more likely from typical examples than from arbitrary examples)
  • CoPs and typicality: Can typicality be influenced by context parameters? Do interpretation (preference) vary among different communities of practice? Can context-aware handling of typical example help to find and select typical example for a CoP or an individual? Do the typical examples (identified for a specific context/ CoP) improve understanding (in contrast to the default typical example)?
  • CoPs and typicality: Are some notations typical for a CoP (e.g. if their are most frequently used by this CoP or preferred by most members of the Cop)?

Further References:

Semantic Technologies and mathematical notations

Wednesday, September 17th, 2008

How can we encourage users to use semantic technologies? Users should not be forced to adapt to semantic systems. Instead we want to adapt the system’s interfaces to make them more intuitive and usable, that is, we want to adapt these systems to the practice of the users. Our applications at KWARC are based on a mathematical scenario (although they can be applied to other domains).

As one of the first practices, we have focus on mathematical notations, which seem to be an important aspects for using or neglecting semantic technologies and content. Consequently, we have focus on how to make systems more notations-aware and how to allow them to adapt wrt. to notations. Below I am listing assumptions and questions that I am interested in.

  • Notations are an issue in learning, in particular, in educational settings. For this we are soon launching a survey.
  • We are not sure whether the adaptation of notation is usable in education scenarios and whether we should allow our students to change the notation of the lecturer.
  • A scientists wants to read a document without spending time and efforts in understanding its notations.
  • There are no editors or search engine yet that allow users to freely enter their notations. They all inscribe a specific notation system. Adapting the interface (wrt. to notation) can improve the acceptance and usage of these tools.
  • The sharing of e.g. lecture notes is hampered due to different notations systems of the lecturer. Notation adaptation can potentially improve and allow better sharing of digital materials.

Communities of Practice in Mathematical eLearning

Friday, September 12th, 2008

My talk went well, but I had the feeling that it was far too technical for most participants and didn’t hit their interest. There was not enough time to introduce techniques we use (OMDoc, OpenMath, PMathML, JOMDoc, …). Moreover, the focus of the workshop seems to be on tools that can and are already used in mathematical education, as well as evaluation on the use of technology in education, system demonstrations, and tutorials. Maybe I should have focused on the panta rhei systems, its features, and how to use it in educational scenarios. The details on mathematical practice, the notation conversion and JOMDoc might have been too much. I was hoping to get feedback on the questionnaires, surveys, and the integration of interactive exercises. Unfortunately, I did not receive any questions or comments. But this was the first day of the workshop and I will most likely get a chance to discuss some of these issues off line. Hopefully I will also understand what the focus and concern of this workshop is, so far it is not clear to me.

Presentation by Christine Müller (me), Jacobs University, at the 4th European Workshop on Mathematical & Science eContents; the abstract and presentation are available at the JEM Network Homepage.

Do Mathematicians really need/ want/ use/ accept (Mathematical) Software?

Wednesday, July 30th, 2008

Hypotheses: Mathematical Software needs MoC (well at least that was what I was going to show)

Evidence: I am referring to software that helps finding a proof, that supports the iterative process of adding proving steps and deleting them again, that is the tedious process of slowly approaching the proof in a notation one is satisfied with. I am not referring to theorem provers that proof lemma’s for us and fill in correct steps automatically nor to tools that help digitalizing already known or written proofs. The continuous revision and multiple revision require a permanent adaptation of previous written proofs steps, thus, respective software with management of change support is valuable for mathematicians.

Another feature: The tedious proving process is very different to the final proof or the later presentation of the process to other (in publications, books, slides, and even in discussions with other mathematicians). Thus, for reconstructing the actual proving process, the software can offer recording functionalities. This could be used by others (in particular students) to better understand the methodology of finding a proof and the heuristics used to require the proof (well, we can’t look in the mathematicians head; some iterations made not be entered but rather take place in the human mind or using pen and paper).

Revision/ Concerns: However, do mathematicians really want such a tool? It would be tedious to enter notations (and particularly to decide on a notation, thus, slowing down the actually thinking) and most likely mathematicians rather stick to their heads and paper. So we should rather ask: When do mathematicians use software? Where can software potentially ease up their life? Is this maybe rather after the finding of a proof; when it comes to the point the mathematicians want to share it with others, publish it; verify it (automatically)? So then we would not need software that supports the tedious, iterative phase of finding proofs … but rather software that supports the publication process (still then change management is useful, since notations/ text evolve – also when writing down an already completed proof) — and the learning experience (since young mathematicians need to learn how to proof).

So does learning software in mathematics make sense? Can it potentially ease up the learning experience? What can software do better/ more efficient/ and less costly then human specialists?

A final though: Mathematicians tend to collaborate to solve proofs (really?). And with the growing globalization, they can refer to modern technology to find potential collaborators and to communicate (do they?). Software can indeed be useful to provide the respective search facilities; communication channels; and digital working spaces (including change management). Software can thus influence and change mathematical practice by opening new spaces to do math (potentially interesting for particular young mathematicians).