From c6d83210c2c90ffb641c322c57e9b4cc39dd8be1 Mon Sep 17 00:00:00 2001
From: Tzviya <trsiegman@gmail.com>
Date: Wed, 31 Aug 2016 18:08:04 -0400
Subject: [PATCH] Remove "Other" and "misc"

Use cases in "Other" and "Misc" duplicate use cases present in other sections.
---
 index.html | 94 ------------------------------------------------------
 1 file changed, 94 deletions(-)

diff --git a/index.html b/index.html
index 2d8346d..4cbc79d 100644
--- a/index.html
+++ b/index.html
@@ -1210,100 +1210,6 @@ <h2>Navigation</h2>
 
 </section>
 
-<section>
-  <h1>Other</h1>
-
-  <section>
-   <h2>Offline Publications</h2>
-     <p>TBD</p>
-   <ul class="use-cases">
-     <li>Corp.Inc. creates an internal manual for its employees as a PWP. This
-    PWP is not published online, but is sent around to all its employees.
-    Employee Anna has some questions about figure 2b, and sends an email to
-    co-worker Bob with a locator to that figure. Bob clicks on that locator,
-    and his company-branded PWP reader opens Bob's personal copy of the
-    manual, and redirects immediatly to that figure.</li>
-    </ul>
-  </section>
-
-  <section>
-   <h2>Publication plus Annotations</h2>
-      <p>TBD</p>
-    <ul class="use-cases">
-    <li>Oksana submits a scholarly article to a EsteemedJournal. EsteemedJournal
-    puts the article through the Peer Review process, during which
-    EsteemedJounral editors and third-party reviewers provide comments on the
-    article. Ultimately, EsteemedJournal chooses not to publish Oksana's
-    article, but the comments (annotations) that have already been made should
-    persist as she submits it to RespectedJournal. </li>
-    </ul>
-  </section>
-
-  <section>
-    <h2>Specialized Domain Semantics</h2>
-      <p>TBD</p>
-    <ul class="use-cases">
-      <li>Placeholder: Formal usage terms and engineering or legal documents,
-    possibly for accessibility also.</li>
-
-      <li>Specialized semantics are required for users and processors.</li>
-    </ul>
-  </section>
-
-</section>
-
-</section>
-
-<section>
-<h1>
-Misc Requirement(s)
-</h1>
-
-<section>
-<h2>Currently unassigned</h2>
-   <p>Be able handle intermittent changes in online/offline status during a
-     single reading session while still minimizing the amount of material
-     cached locally.</p>
-
-  <p>Javascript libraries may refer to services "outside", ie, to services on
-    the Web at large (e.g., reference to Wolfram Alfa, or online google
-    services)</p>
-
-  <p>Javascript libraries may become relatively complex and may therefore be
-    packaged; this means that the packaging format should allow for other
-    packages as parts.</p>
-
-  <p>The package is fully annotatable, and annotations can be part of the
-    package and discoverable.</p>
-
-  <p>There should be a discovery service or trigger available to indicate
-    content changes or long-term availability changes.</p>
-
-  <p>Every resource within a PWP can hold it’s own rights. The rights of this resource
-    should be kept in the process of distributing the resource.</p>
-</section>
-
-    <section>
-     <h2>Basic Actions</h2>
-     <p>Anna is a self-publishing author. Anna creates a PWP, both packed and
-        unpacked. Anna uses some cloud storage system such as DropBox to publish
-        her PWP online. Her friend Bob is able to read Anna's PWP online and
-        offline, either packed or unpacked, as Bob sees fit.</p>
-    </section>
-
-    <section>
-      <h2>Online Discovery</h2>
-      <p>As a reader, I want to discover a publication on the web so that I can
-          start reading it right away. </p>
-    </section>
-
-  <section>
-    <h2>Platform Independence</h2>
-    <p>Publisher ACME creates a publication that is consumable across a variety
-      of reader platforms, whether online or offline.</p>
-  </section>
-
-</section>
 
 <section>
   <h1>Security</h1>