Trouble viewing the formulas? You need a MathML compatible browser.

LogicWiki:Manual of style

From LogicWiki

Jump to: navigation, search

These are the standard practices that have been agreed upon for creating pages. Please feel free to modify them as you see fit. Although, if you make major changes, you should fix pages that conform to the old MoS.

Contents

Duplication

The only condition under which material should be duplicated is when a copy is put into the developmental namespace (see below). Otherwise, there should only be one copy of the module on the wiki.

Optimal length

Modules should be short enough that no one would reasonably want to break the module up and only teach part of it. This is intended to make designing a class optimally easy for the instructor, she merely needs to choose the modules she wants to cover. If you want to group several modules together, for instance all the modules on Venn Diagrams, use the categorization system.

To do that create a page called Category:Name and put a brief description there. Then, at the bottom of the modules you wish to add, put the text [[Category:Name]]. This will automatically add them to the category. This puts a link to the category at the bottom of each article. Also when you go to Category:Name you will see a list of all the articles in that category.

Symbols

I think we agreed on the following set of logical symbols:

  • ¬ for negation
  • for and
  • for or
  • for if...then
  • for iff
  • for for all
  • for there exists
  • A,B,C for sentence letters
  • a,b,c for constants
  • P,Q,R for predicates
  • x,y,z for variables
  • for proves
  • for models

  • Models for PL need to be specified in the following way:
    • Domains
      • Domain = 0, 1, ... or
      • Domain = {0, 1, ... } or
      • Domain = All humans
    • Reference of a = 0
    • Predicates
      • P:{x | x is blue } or
      • P:{0, 1} or
      • 'Px' means x is blue
  • Pr() for probability
  • E() for expectation

Naming

When you create a page the name should be descriptive, but not refer to the particular class. We use the category system for determining which class something is for (e.g. Category:LPS 29). In order to specify what class your module is intended for put [[Category:LPS XX]] at the bottom of the module (where XX is 29, 30, or 31). This will add your module to the category LPS XX. You can add your module to as many class categories as you like.

If you want to have "sub-modules", e.g. a page with problems for your module, you should use subpages. To create a subpage for Dutch book arguments entitled "Problems" you would create the page Dutch book arguments/Problems. This should be avoided where possible, as it makes the modules more difficult for students to print out.

Namespaces

The pages on this wiki are divided up into logical categories called Namespaces. Each namespace has an associated "talk" namespace, which you access by clicking on the discussion tab at the top of the page. The main namespace has no prefix, but all others have a prefix. For instance this page, whose name is LogicWiki:Manual of style is in the LogicWiki namespace.

There are two namespaces that can only be viewed by logged in users. Those are the Dev: and Test: namespaces. These places should be used to put things for internal use. Dev: is for stuff that we are currently working on, but for one reason or another is not ready to go live. Test: is for test questions, that students shouldn't see.

You can see what pages exist in each of the namespaces by using Special:Allpages

Help

I don't really know what to put in the help pages that would be helpful. Let me know and I'll create some. Try to keep track of your questions, so that we can make this as user-friendly to others as possible.

Personal tools