diff --git a/praclib/temp/core.gen.slot.base/.project b/praclib/temp/core.gen.slot.base/.project
new file mode 100644
index 0000000..76da8ab
--- /dev/null
+++ b/praclib/temp/core.gen.slot.base/.project
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>core.gen.slot.base</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+	</buildSpec>
+	<natures>
+	</natures>
+</projectDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/example_design_mechanisms.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/example_design_mechanisms.xmi
index 2b80370..4a11e7a 100644
--- a/praclib/temp/core.tech.common.base/guidances/guidelines/example_design_mechanisms.xmi
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/example_design_mechanisms.xmi
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <org.eclipse.epf.uma:ContentDescription xmi:version="2.0"
     xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore"
-    xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.2.0" xmlns:epf="http://www.eclipse.org/epf"
-    epf:version="1.2.0" xmi:id="-mAo18f36rZ1R98kpZX7HMw"
-    name="new_guideline,_K32gYAoBEdu0OeEVPFogVA" guid="-mAo18f36rZ1R98kpZX7HMw" changeDate="2006-07-10T15:11:18.051-0700"
+    xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc"
+    rmc:version="7.2.0" xmi:id="-mAo18f36rZ1R98kpZX7HMw"
+    name="new_guideline,_K32gYAoBEdu0OeEVPFogVA" guid="-mAo18f36rZ1R98kpZX7HMw" changeDate="2008-03-11T11:28:25.929-0700"
     version="1.0.0">
   <mainDescription>&lt;h3>&#xD;
     Design Mechanism Characteristics and Mapping&#xD;
@@ -17,7 +17,7 @@
         for them to survive thereafter.&#xD;
     &lt;/li>&#xD;
     &lt;li>&#xD;
-        There might be a need for several very large  objects to be stored permanently on disk for several months, never&#xD;
+        There might be a need for several very large objects to be stored permanently on disk for several months, never&#xD;
         updated, but with sophisticated means of retrieval.&#xD;
     &lt;/li>&#xD;
 &lt;/ul>&#xD;
@@ -47,7 +47,7 @@
 &lt;/p>&#xD;
 &lt;blockquote>&#xD;
     &lt;p align=&quot;center&quot;>&#xD;
-        &lt;img height=&quot;221&quot; title=&quot;Figure 1. Mapping Analysis Mechanisms to Design Mechanisms and Classes&quot;&#xD;
+        &lt;img title=&quot;Figure 1. Mapping Analysis Mechanisms to Design Mechanisms and Classes&quot; height=&quot;221&quot;&#xD;
         alt=&quot;Mapping Analyis Mechanisms to Design Mechanisms and Classes&quot; src=&quot;./resources/co_dmec1.gif&quot; width=&quot;372&quot; />&#xD;
     &lt;/p>&#xD;
 &lt;/blockquote>&#xD;
@@ -62,7 +62,7 @@
         The &lt;b>persistence&lt;/b> design mechanisms can be mapped to implementation mechanisms as Figure 2 shows:&#xD;
     &lt;/p>&#xD;
     &lt;p align=&quot;center&quot;>&#xD;
-        &lt;img height=&quot;216&quot; title=&quot;Figure 2. How persistence design mechanism map to implementation mechanism&quot;&#xD;
+        &lt;img title=&quot;Figure 2. How persistence design mechanism map to implementation mechanism&quot; height=&quot;216&quot;&#xD;
         alt=&quot;How persistence design mechanism map to implementation mechanism&quot; src=&quot;./resources/co_dmec2.gif&quot;&#xD;
         width=&quot;325&quot; />&#xD;
     &lt;/p>&#xD;
@@ -79,14 +79,14 @@
     &lt;/p>&#xD;
     &lt;blockquote>&#xD;
         &lt;p align=&quot;center&quot;>&#xD;
-            &lt;img height=&quot;110&quot; title=&quot;Figure 3. Mapping structure after optimizing the mechanisms&quot;&#xD;
+            &lt;img title=&quot;Figure 3. Mapping structure after optimizing the mechanisms&quot; height=&quot;110&quot;&#xD;
             alt=&quot;Illustration of mapping structure after optimizing the mechanisms&quot; src=&quot;./resources/co_dmec3.gif&quot;&#xD;
             width=&quot;418&quot; />&#xD;
         &lt;/p>&#xD;
-        &lt;p align=&quot;center&quot; class=&quot;picturetext&quot;>&#xD;
+        &lt;p class=&quot;picturetext&quot; align=&quot;center&quot;>&#xD;
             &lt;strong>Figure 3. Mapping structure after optimizing the mechanisms&lt;/strong>&#xD;
         &lt;/p>&#xD;
-        &lt;p align=&quot;left&quot; class=&quot;picturetext&quot;>&#xD;
+        &lt;p class=&quot;picturetext&quot; align=&quot;left&quot;>&#xD;
             The design decisions for a client class in terms of mappings between mechanisms. The &lt;font&#xD;
             face=&quot;Courier New, Courier, mono&quot;>Flight&lt;/font> class needs two forms of persistency&lt;strong>:&lt;/strong>&#xD;
             &lt;strong>in-memory storage&lt;/strong>, implemented by a predefined library routine, and &lt;strong>a&#xD;
@@ -190,9 +190,7 @@
 &lt;/h3>&#xD;
 &lt;p>&#xD;
     As with analysis mechanisms, design mechanisms can be modeled using a collaboration, which may instantiate one or more&#xD;
-    architectural or design patterns (see &lt;a class=&quot;elementLinkWithType&quot;&#xD;
-    href=&quot;./../../../legacy.legacy.obsoleted_from_openup/guidances/guidelines/using_patterns_31FFED10.html&quot;&#xD;
-    guid=&quot;_0cr7cACrEdu8m4dIntu6jA&quot;>Guideline: Using Patterns&lt;/a>).&#xD;
+    architectural or design patterns.&#xD;
 &lt;/p>&#xD;
 &lt;blockquote>&#xD;
     &lt;p>&#xD;
@@ -210,7 +208,7 @@
     collaboration.&#xD;
 &lt;/p>&#xD;
 &lt;p align=&quot;center&quot;>&#xD;
-    &lt;img height=&quot;382&quot; title=&quot;Figure 4. JDBC: Static View&quot;&#xD;
+    &lt;img title=&quot;Figure 4. JDBC: Static View&quot; height=&quot;382&quot;&#xD;
     alt=&quot;Diagram of the figure titled Static View: JDBC shows the classes (actually, the classifier roles) in the collaboration. &quot;&#xD;
      src=&quot;./resources/jdbc1.gif&quot; width=&quot;571&quot; />&#xD;
 &lt;/p>&#xD;
@@ -244,7 +242,7 @@
     A series of dynamic views follow, in Figures 5 thorough 9, to show how the mechanism actually works.&#xD;
 &lt;/p>&#xD;
 &lt;p align=&quot;center&quot;>&#xD;
-    &lt;img height=&quot;146&quot; title=&quot;Figure 5. JDBC: Initialize&quot; alt=&quot;Diagram of JDBC: Initialize&quot; src=&quot;./resources/jdbc2.gif&quot;&#xD;
+    &lt;img title=&quot;Figure 5. JDBC: Initialize&quot; height=&quot;146&quot; alt=&quot;Diagram of JDBC: Initialize&quot; src=&quot;./resources/jdbc2.gif&quot;&#xD;
     width=&quot;285&quot; />&#xD;
 &lt;/p>&#xD;
 &lt;p align=&quot;center&quot;>&#xD;
@@ -290,7 +288,7 @@
     &lt;/blockquote>&#xD;
 &lt;/blockquote>&#xD;
 &lt;p align=&quot;center&quot;>&#xD;
-    &lt;img height=&quot;253&quot; title=&quot;Figure 6. JDBC: Create&quot; alt=&quot;Diagram of JDBC: Crreate&quot; src=&quot;./resources/jdbc3.gif&quot;&#xD;
+    &lt;img title=&quot;Figure 6. JDBC: Create&quot; height=&quot;253&quot; alt=&quot;Diagram of JDBC: Crreate&quot; src=&quot;./resources/jdbc3.gif&quot;&#xD;
     width=&quot;478&quot; />&#xD;
 &lt;/p>&#xD;
 &lt;p align=&quot;center&quot;>&#xD;
@@ -306,7 +304,7 @@
     added to the database.&#xD;
 &lt;/p>&#xD;
 &lt;p align=&quot;center&quot;>&#xD;
-    &lt;img height=&quot;352&quot; title=&quot;Figure 7. JDBC: Read&quot; alt=&quot;Diagram of JDBC: Read&quot; src=&quot;./resources/jdbc4.gif&quot; width=&quot;600&quot; />&#xD;
+    &lt;img title=&quot;Figure 7. JDBC: Read&quot; height=&quot;352&quot; alt=&quot;Diagram of JDBC: Read&quot; src=&quot;./resources/jdbc4.gif&quot; width=&quot;600&quot; />&#xD;
 &lt;/p>&#xD;
 &lt;p align=&quot;center&quot;>&#xD;
     &lt;b>Figure 7. JDBC: Read&lt;/b>&#xD;
@@ -334,7 +332,7 @@
     face=&quot;Courier New, Courier, mono&quot;>DBClass&lt;/font>.&#xD;
 &lt;/p>&#xD;
 &lt;p align=&quot;center&quot;>&#xD;
-    &lt;img height=&quot;255&quot; title=&quot;Figure 8. JDBC: Update&quot; alt=&quot;Diagram of JDBC: Update&quot; src=&quot;./resources/jdbc5.gif&quot;&#xD;
+    &lt;img title=&quot;Figure 8. JDBC: Update&quot; height=&quot;255&quot; alt=&quot;Diagram of JDBC: Update&quot; src=&quot;./resources/jdbc5.gif&quot;&#xD;
     width=&quot;473&quot; />&#xD;
 &lt;/p>&#xD;
 &lt;p align=&quot;center&quot;>&#xD;
@@ -364,7 +362,7 @@
     pay to pull the persistence knowledge out of the class that encapsulates the data.&#xD;
 &lt;/p>&#xD;
 &lt;p align=&quot;center&quot;>&#xD;
-    &lt;img height=&quot;255&quot; title=&quot;Figure 9. JDBC: Delete&quot; alt=&quot;Diagram of JDBC: Delete&quot; src=&quot;./resources/jdbc6.gif&quot;&#xD;
+    &lt;img title=&quot;Figure 9. JDBC: Delete&quot; height=&quot;255&quot; alt=&quot;Diagram of JDBC: Delete&quot; src=&quot;./resources/jdbc6.gif&quot;&#xD;
     width=&quot;473&quot; />&#xD;
 &lt;/p>&#xD;
 &lt;p align=&quot;center&quot;>&#xD;
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec1.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/co_dmec1.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec1.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/co_dmec1.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec2.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/co_dmec2.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec2.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/co_dmec2.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec3.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/co_dmec3.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec3.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/co_dmec3.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc1.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc1.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc1.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc1.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc2.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc2.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc2.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc2.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc3.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc3.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc3.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc3.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc4.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc4.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc4.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc4.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc5.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc5.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc5.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc5.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc6.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc6.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc6.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc6.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/test_driven_dev_practice.xmi b/praclib/temp/practice.tech.test_driven_development.base/customcategories/test_driven_dev_practice.xmi
index 7a59a49..4601556 100644
--- a/praclib/temp/practice.tech.test_driven_development.base/customcategories/test_driven_dev_practice.xmi
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/test_driven_dev_practice.xmi
@@ -4,7 +4,7 @@
     xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc"
     rmc:version="7.2.0" xmi:id="-P_LlxVe57r9XOTpngB2ddQ"
     name="test_driven_dev_practice,_dLtGEJ-mEdyBk-WQzMU-FQ" guid="-P_LlxVe57r9XOTpngB2ddQ"
-    authors="Jim Ruehlin" changeDate="2008-01-17T13:22:16.622-0800" version="7.2.0">
+    authors="Jim Ruehlin" changeDate="2008-03-11T11:19:16.989-0700" version="7.2.0">
   <mainDescription>&lt;p>&#xD;
     The Test Driven Development practice reduces time to market by reducing the amount of time needed to integrate and&#xD;
     stabilize builds. It improves productivity by finding and fixing errors close to the time they're introduced. And it&#xD;
@@ -44,8 +44,4 @@
     TDD was originally part of Kent Beck's Extreme Programming process. It's now also used in many other Agile and&#xD;
     non-Agile contexts.&#xD;
 &lt;/p></mainDescription>
-  <keyConsiderations>See&amp;nbsp;&lt;a class=&quot;elementLink&quot;&#xD;
-href=&quot;./../../practice.tech.test_driven_development.base/guidances/supportingmaterials/measurementsz_C281C60E.html&quot;&#xD;
-guid=&quot;_ApBRYMVFEdybJe13vGdZaA&quot;>Measurementsz&lt;/a>&amp;nbsp;for information on adopting and measuring the team's capabilities in&#xD;
-test driven development.</keyConsiderations>
 </org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/enablement.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/enablement.xmi
index 502fd87..923811c 100644
--- a/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/enablement.xmi
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/enablement.xmi
@@ -3,7 +3,8 @@
     xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore"
     xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc"
     rmc:version="7.2.0" xmi:id="-FCFgETFie9XAhzcc9ZXfSg"
-    name=",_q2WJkOFvEdys887i4S_24Q" guid="-FCFgETFie9XAhzcc9ZXfSg" changeDate="2008-02-22T09:59:43.225-0800">
+    name=",_q2WJkOFvEdys887i4S_24Q" guid="-FCFgETFie9XAhzcc9ZXfSg" changeDate="2008-03-11T11:12:11.347-0700"
+    version="7.2.0">
   <mainDescription>&lt;p>&#xD;
     If you're just getting started with TDD or developer testing in general, you'll need to know why developer testing is a&#xD;
     good idea and the basics of what makes good developer tests. A good starting place is this &lt;a&#xD;
@@ -33,11 +34,9 @@
     &lt;/li>&#xD;
 &lt;/ul>&#xD;
 &lt;p>&#xD;
-    Once you're familiar with the basics of TDD, browse the capability pattern for the &lt;a class=&quot;elementLink&quot;&#xD;
-    href=&quot;./resources/test_driven_development_E3D820A5.html&quot; guid=&quot;_k7ZugY8EEdy7q8CKc_B8eg&quot;>Test Driven Development&#xD;
-    Practice&lt;/a>. This illustrates the flow between the testing and implementation tasks during test driven development.&#xD;
-    Select a task to view more detail about what needs to be done to perform the task. If you'll be creating a capability&#xD;
-    pattern or delivery process that includes TDD, see &lt;a class=&quot;elementLink&quot;&#xD;
+    Once you're familiar with the basics of TDD,&amp;nbsp;select&amp;nbsp;various tasks to view more detail about what needs to be&#xD;
+    done to perform the task. If you'll be creating a capability pattern or delivery process that includes TDD, see &lt;a&#xD;
+    class=&quot;elementLink&quot;&#xD;
     href=&quot;./../../../practice.tech.test_driven_development.base/guidances/examples/using_tdd_in_context_F77E5C22.html&quot;&#xD;
     guid=&quot;_QeE7YMCsEdyHnYlsYwuJQw&quot;>Using the TDD Practice in Context&lt;/a>. This shows one example of how TDD can be used in&#xD;
     conjunction with other activities and capability patterns to create a pattern for developing software. This is only one&#xD;
diff --git a/praclib/temp/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi b/praclib/temp/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi
index dda390b..b3ea255 100644
--- a/praclib/temp/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi
+++ b/praclib/temp/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi
@@ -3,19 +3,18 @@
     xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore"
     xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc"
     rmc:version="7.2.0" xmi:id="-H6ob8eA7gz_mOsk8ulSFMQ"
-    name=",_R7atwJfIEdyZkIR-s-Y8wQ" guid="-H6ob8eA7gz_mOsk8ulSFMQ" changeDate="2008-01-03T16:01:19.313-0800"
+    name=",_R7atwJfIEdyZkIR-s-Y8wQ" guid="-H6ob8eA7gz_mOsk8ulSFMQ" changeDate="2008-03-11T11:16:41.025-0700"
     version="7.2.0">
   <keyConsiderations>&lt;p>&#xD;
-    It is common to require that code pass all developer tests before it can be delivered in an integrated &lt;a&#xD;
-    class=&quot;elementLink&quot; href=&quot;./../../core.tech.slot.base/workproducts/software_build_slot_38848FEE.html&quot;&#xD;
-    guid=&quot;_zjwzEKg_Edyn_rXSpKp-cg&quot;>[Software Build]&lt;/a>.&#xD;
+    It is common to require that code pass all developer tests before it can be delivered in an integrated source code&#xD;
+    repository.&#xD;
 &lt;/p>&#xD;
 &lt;p>&#xD;
     Pair with the Tester during all steps of this task to gain insight on testing and quality considerations.&#xD;
 &lt;/p>&#xD;
 &lt;p>&#xD;
-    The&amp;nbsp;&lt;a class=&quot;elementLink&quot; href=&quot;./../../core.mgmt.slot.base/workproducts/work_items_slot_F12BAC46.html&quot;&#xD;
-    guid=&quot;_1QZI8EfUEdyiPI8btkmvmw&quot;>[Work Items]&lt;/a>&amp;nbsp;is implicitly used in implementation tasks to manage which&#xD;
+    The&amp;nbsp;&lt;a class=&quot;elementLink&quot; href=&quot;./../../core.mgmt.slot.base/workproducts/project_work_slot_F12BAC46.html&quot;&#xD;
+    guid=&quot;_1QZI8EfUEdyiPI8btkmvmw&quot;>[Project Work]&lt;/a>&amp;nbsp;is implicitly used in implementation tasks to manage which&#xD;
     requirements or change requests are being realized in the code.&#xD;
 &lt;/p></keyConsiderations>
   <sections xmi:id="_gjLBUJfIEdyZkIR-s-Y8wQ" name="Run developer tests" guid="_gjLBUJfIEdyZkIR-s-Y8wQ">