Wiki Law School talk:MPEP Outline/Archive 1

From wikilawschool.net. Wiki Law School does not provide legal advice. For educational purposes only.
< Wiki Law School talk:MPEP Outline
Revision as of 17:32, August 17, 2007 by Ischick (talk | contribs) (Current status of MPEP Outline)

If you have ideas, suggestions, feedback, etc., about the Wiki Law School:MPEP Outline project, please add them here:

Hello. I'm planning to stiudy for the patent bar this summer. I would also like to help contribute to this MPEP outline. Please let me know what I can do to help. Marc.


Great! As you may have noticed, the MPEP sections are huge. Really huge, and full of stuff that we don't need to know for the patent bar. Some of these unnecessary parts are pretty obvious; such as the forms that examiners use in their patent examinations.

I think this project can be divided into two main phases: formatting and substantive editing. The formatting is a mind-numbing and thankless task. If this appeals to you, here is a brief description of what we need:

Formatting Help Needed

What I have started doing is:

  • breaking up the chapters into their component sections
    • (see MPEP 700 as an example, all it does is transclude each individual section into the main chapter outline.)
    • do this by cutting and pasting each main section into new pages that are named "MPEP <section number>" i.e., MPEP 701
  • adding the heading markers throughout the text, as follows:
    • for secondary section headings (i.e., 702.01) add "===" (three equal signs) before and after the section number and title:
      • "===702.01 Obviously Informal Cases==="
    • for tertiary section headings (i.e., 704.11(a)) add "====" (four equal signs) before and after the section number and title:
      • "===704.11(a) Examples of Information Reasonably Required==="
  • add the templates Template:MPEP Chapter to each chapter and Template:MPEP Section to each section.
    • These templates include category tags and navigation templates.
    • If you don't have experience with wikis, don't worry about this one unless you want me to explain how this works; you have to define variables for the template (but it's pretty simple).

Substantive Editing Help Needed

Participating in the editing process is what will help us learn the MPEP and prepare for the patent bar. This will require reading each section, deciding if it is important for the patent bar, deleting if not, and summarizing if it is.

How can you tell if something needs to stay or go? Some things are obviously unnecessary for our purpose, so immediately delete those. Otherwise, just play it by ear. Taking old exams will help you get a feel for what is tested and what is not. Plus, taking old exams is the most important part of your study regimen (IMO). If in doubt, leave the section there and ask on the discussion page for that section (as opposed to this talk page for the entire project).

I have started with MPEP 700 because I believe it is the most important chapter. The other biggies are MPEP 600 and MPEP 2100. If you want to begin there, that would be great.

Other

Also, please check out the Patent Bar Preparation page, if you have anything to add, please feel free.


If all this makes sense, great. If not, please let me know. I'm glad to have you aboard and look forward to your contribution! Sysop 20:44, 23 May 2007 (MST)

Now I have memorial day weekend plans: MPEP 600.

Sounds like a fun weekend! If you have any questions and want to see an example, some sections of MPEP 700 are formatted in a way I think is good (including proper headings and navigation template).

I will be spending a lot of time for the next few days on migrating the wiki to a new server, which will allow us more flexibility (like a table of contents that is limited to only certain headings and that does not have the annoying section numbers (1.1, 1.1.1, etc.)).Sysop 17:28, 25 May 2007 (MST)

So I read 600. Wow. This is going to be tough. I'm taking a look at some old exams this weekend to guage what of 600 should stay and what should go.

Yes, this is certainly no small task. As I have been going through and making small changes to various sections, I think I have arrived at a better method of making this outline rather than editing an entire chapter at a time:

  • Take a practice exam
  • Go through answers of the practice exam one at a time.
  • Each answer (usually) cites the MPEP section that pertains. Go to that section, and rework only that relevant part (not the entire chapter nor even the entire section).
  • By doing this thing piecemeal, we will slowly make progress, and most importantly, we will focus on learning the material--especially the material that is tested.
  • After we (including anybody else that will be helping out) have worked on the sections that are tested, we can then start to look at other portions of the MPEP, perhaps deleting parts that appear to not be important and then reworking the others.

You may have noticed that MPEP 600 is now broken into sections. I have also included the section navigation templates. To edit a section, you must edit only the section; if you click the "edit" tab at the top of the page while viewing the MPEP Chapter 600 page, you will only see the inclusion tags for each section.

To get to the individual sections, click the "[edit]" link to the right of that section, or click on the section heading in the text.

One last thing: you "read 600?" Does this mean you read through the entire chapter? Wow indeed. Color me impressed. That is quite a chunk of reading.--Sysop 00:53, 1 June 2007 (MDT)

Current status of MPEP Outline

Hi, I'm preparing to take the patent bar and would like to help out on this project. I think it has potential to be a wonderful resource as well as a nice way to study the MPEP. I made an account today, but am having trouble determining where the current needs are. Is there a systematic approach to the outlining process or should I just pick a place and start working? If that's the case, is there a simple way to determine if a section is effectively completed? Thanks - Ian