prov-o html sections
authorTim L <lebot@rpi.edu>
Thu, 29 Mar 2012 14:26:19 -0400
changeset 2107 9adc0b96753f
parent 2106 1472949fad01
child 2108 c6006ad29605
prov-o html sections
ontology/prov-o-html-sections/description-expanded-terms.inc.html
ontology/prov-o-html-sections/description-qualified-terms.inc.html
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/prov-o-html-sections/description-expanded-terms.inc.html	Thu Mar 29 14:26:19 2012 -0400
@@ -0,0 +1,9 @@
+     <section>
+	  	<h3>Expanded Terms</h3>
+        <p>        
+This section presents the rest of classes and properties textually without using a diagram. We may use some examples in English. 
+The classes and properties covered in this section are: 
+Note, hasAnnotation, tracedTo, wasRevisionOf, hadOriginalSource, wasQuotatedFrom, hadQuotatedAgent, hadQuoterAgent, wasSummaryOf, alternateOf, terms related to Collection? Bundle? Role?? , hadRole, Location??, hadLocation?, wasStartedByActivity?? specializationOf?
+
+		</p>
+	  </section> < !-- Expaned Terms subsection -->
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/prov-o-html-sections/description-qualified-terms.inc.html	Thu Mar 29 14:26:19 2012 -0400
@@ -0,0 +1,83 @@
+     <section>
+	  	<h3>Qualified Terms</h3>
+        <p>        
+This section shows how qualified relationships in prov-dm are encoded in provo. We need two diagrams: one to show the hierarchical relationship between involvement classes, and another to using Association as an exemplar to illustrate the general pattern to qualify a binary relationship. 
+   </p>
+
+      <div style="text-align: center;">
+         <figure>
+                 <img src="prov-o-diagrams/involvements.png"
+                style="width: 70%; min-width: 25em; max-width: 60em" 
+                alt="A hierarchical illustration of simple involvements"/>
+            <figcaption>Figure 2. A hierarchical illustration of simple involvements</figcaption>
+         </figure>
+      </div>
+
+      <div style="text-align: center;">
+         <figure>
+                 <img src="prov-o-diagrams/Qualified-Association.png"
+                style="width: 70%; min-width: 25em; max-width: 60em" 
+                alt="Express association between an activity and an agent using a binary relationship and an alternatie qualified relationship"/>
+            <figcaption>Figure 3. Express association between an activity and an agent using a binary relationship and an alternatie qualified relationship</figcaption>
+         </figure>
+      </div>
+
+
+         <p>
+         We have in the current provo HTML document a diagram about qualified involvement in Section 8 “Overview of Qualified Involvement”, but we don’t think that such a diagram is great. We need to illustrate the hierarchy of involvements and some, not necessarily all, the associated object properties. The focus in the diagram will be on the elements of prov-dm that are illustrates in the previous overview sub-section. 
+         The diagram can show the following kinds on involvements, and shows some (not necessarily all) the properties that link them together, e.g., entity, activity, agent, qualified. Note that, not all the sub-classes of involvements are included here; they will appear in section 3.3 because they are additional terms in prov-o.
+         Involvement, EntityInvolvement, ActicityInvolvement, AgentInvolvement, Derivation, Usage, Generation, Association (End, Start), Responsibility, Attribution,
+         </p>
+
+         <p>
+         Turtle + Explanation. We do not to cover all the kinds of involvement and properties in the example. We only show how Derivation, Usage, Generation and Association can be expressed using this reification pattern. If need be, examples of other types of involvement should be given in section 4, where they are defined.  For the qualified relationships we provide the following example files:
+         </p>
+
+        <div class="anexample">
+           <div><b>Qualified DerivationExample</b></div>
+            <p>
+eg16-journalism-derivation.ttl, to show how additional information about derivation can be expressed, such as when it all happened.
+            </p>
+           <div class="exampleOuter">
+              <pre class="example">{% include "includes/eg16-journalism-qualified-derivation.ttl" %}</pre>
+           </div>
+        </div>
+
+        <div class="anexample">
+           <div><b>Qualified Generation Example</b></div>
+            <p>
+ eg16-journalism-generation.ttl, to show how additional information about generation can be expressed, such as when it all happened.
+            </p>
+           <div class="exampleOuter">
+              <pre class="example">{% include "includes/eg16-journalism-qualified-generation.ttl" %}</pre>
+           </div>
+        </div>
+
+        <div class="anexample">
+           <div><b>Qualified Usage Example</b></div>
+            <p>
+eg16-journalism-usage.ttl, to show how additional information about usage can be expressed, such as when it all happened.
+            </p>
+           <div class="exampleOuter">
+              <pre class="example">{% include "includes/eg16-journalism-qualified-usage.ttl" %}</pre>
+           </div>
+        </div>
+
+        <div class="anexample">
+           <div><b>Qualified Association Example</b></div>
+            <p>
+ eg16-journalism-association.ttl, to show how we can express plan or recipe used in an activity by an agent
+            </p>
+           <div class="exampleOuter">
+              <pre class="example">{% include "includes/eg16-journalism-qualified-association.ttl" %}</pre>
+           </div>
+        </div>
+
+         <div style="text-align: center;">
+            {% include "includes/qualifed-forms-starting-point.html" %}
+         </div>
+
+         <div style="text-align: center;">
+            {% include "includes/qualifed-forms-expanded.html" %}
+         </div>
+	  </section>