Removed buttons from html
authordgarijo
Sun, 28 Oct 2012 20:14:34 +0100
changeset 4576 af2d939b4df4
parent 4575 d64d62d27cdf
child 4577 e1799f847977
Removed buttons from html
dc-note/Overview.html
--- a/dc-note/Overview.html	Sun Oct 28 15:59:41 2012 +0000
+++ b/dc-note/Overview.html	Sun Oct 28 20:14:34 2012 +0100
@@ -1277,25 +1277,11 @@
  Therefore, they lead to similar complex patterns (providing a date instead of an agent associated with the corresponding activity).
  When using Dublin Core terms, it is usual to see that a resource is annotated with several <code>dct</code> assertions like creator, publisher,
  issued, date, etc., but in this phase of the mapping each term is treated independently. 
- <form action="#"><p> 
-    <input id="hide-dates" type="button" value="Hide date patterns" 
-           style="display:none"
-		   onclick="            
-            set_display_by_class('div','date pattern','none');
-            set_display_by_id('hide-dates','none');
-            set_display_by_id('show-dates','');" />
-    <input id="show-dates" type="button" value="Show date patterns"
-           onclick="            
-            set_display_by_class('div','date pattern','');
-            set_display_by_id('hide-dates','');
-            set_display_by_id('show-dates','none');" />
-   </p> 
-  </form>
+ 
 </p>
 
 <h5 id="term_created"><span class="secno">2.5.2.1 </span>dct:created</h5> 
 </p>
-<div class="date pattern" style="display:none">
 <pre class="code">
  CONSTRUCT{
  ?document a  prov:Entity .
@@ -1316,11 +1302,9 @@
   ?document dct:created ?date.
  }
  </pre>
- </div>
  
 <h5 id="term_issued"><span class="secno">2.5.2.2 </span>dct:issued</h5> 
 <p>
-<div class="date pattern" style="display:none">
 <pre class="code">
  CONSTRUCT{
  ?document a prov:Entity .
@@ -1348,13 +1332,9 @@
  }
 </pre>
 </p>
-</div>
 
 <h5 id="term_modified"><span class="secno">2.5.2.3 </span>dct:modified</h5> 
-<div class="date pattern" style="display:none">
-<p>
-As seen with the previous terms, most entity/date properties will have a similar structure.
-</p><p><pre class="code"> 
+<p><pre class="code"> 
  CONSTRUCT{
  ?document a prov:Entity .
  
@@ -1381,10 +1361,8 @@
  }
 </pre>
 </p>
-</div>
 
 <h5 id="term_dateAccepted"><span class="secno">2.5.2.4 </span>dct:dateAccepted</h5> 
-<div class="date pattern" style="display:none">
 <p><pre class="code"> 
  CONSTRUCT{
  ?document a prov:Entity .
@@ -1412,9 +1390,7 @@
  }
 </pre>
 </p>
-</div>
 <h5 id="term_dateCopyRighted"><span class="secno">2.5.2.5 </span>dct:dateCopyrighted</h5> 
-<div class="date pattern" style="display:none">
 <p><pre class="code">
  CONSTRUCT{
  ?document a prov:Entity .
@@ -1441,9 +1417,7 @@
   ?document dct:dateCopyrighted ?date.
  }
 </pre></p>
-</div>
 <h5 id="term_dateSubmitted"><span class="secno">2.5.2.6 </span>dct:dateSubmitted</h5> 
-<div class="date pattern" style="display:none">
 <p><pre class="code">
  CONSTRUCT{
  ?document a prov:Entity .
@@ -1472,97 +1446,7 @@
 </pre>
 </p>
 </div>
-</div>
-<!--
-<div id="entity_entity_mappings">
-<h4><span class="secno">2.5.3 </span>Entity-Entity mappings (How)</h4>
-<p>
-Most Dublin Core terms in this category are related to the <code>prov:wasDerivedFrom</code> property.
- They can be mapped directly, but also a complex mapping can be provided. In these cases, a specialty of SPARQL 
- CONSTRUCT queries can be used to deal with the inverse properties in Dublin Core.
-</p>
-<h5 id="term_has_Version"><span class="secno">2.5.3.1 </span>dct:isVersionOf / dct:hasVersion</h5>
-<p>
-I would say that <code>prov:wasDerivedFrom</code>><code>dct:isVersionOf</code>><code>prov:wasRevisionOf</code>. Thus:
-</p><p><pre class="code">
- CONSTRUCT {
-    ?document1 a prov:Entity ;
-       prov:wasDerivedFrom ?document2.
-    ?document2 a prov:Entity .
- } WHERE {
-    OPTIONAL { ?document1 dct:isVersionOf ?document2 . }
-    OPTIONAL { ?document2 dct:hasVersion ?document1 .}
- }
-</pre>
-</p><p>
- The OPTIONAL keyword means that the included statement does not need to exist.
- Triples in the resulting graph with variables that have no binding simply are omitted.
- In this case this leads to the correct PROV statement, if either or both source statements are present.
- From the entity/entity relations, <b>an activity can also be inferred (e.g., the activity that led to the creation of the new version)
- . We omit it here for brevity.</b>
- </p>
- <!--<p>
- In essence, these examples sketch the first part of the mapping. As everything is provided as 
- RDF statements or SPARQL CONSTRUCT queries, this mapping can simply applied to arbitrary RDF data by
- adding the statements and the resulting graphs from the queries to the data. 
- </p> this should be commented
- <p>
-<h5 id="term_has_Format"><span class="secno">2.5.3.2 </span>dct:isFormatOf / dct:hasFormat</h5>
-</p><p>
-isFormatOf is defined as “A related resource that is substantially the same as the described resource, but in another format”. This
- would map to <code>prov:alternateOf</code>. We don’t know which entities are both of them specializing, but we know that one is an alternate of the other.
-</p><p> <pre class="code">
- CONSTRUCT {
-    ?document1 a prov:Entity ;
-       prov:alternateOf ?document2.
-    ?document2 a prov:Entity .
- } WHERE {
-    OPTIONAL { ?document1 dct:isFormatof ?document2 . }
-    OPTIONAL { ?document2 dct:hasFormat ?document1 .}
- }
-</pre></p><p>
- 
-<!--
-dct:isReferencedBy / dct:references
-</p><p>
-IsReferencedBy: A related resource that references, cites, or otherwise points to the described resource.
-</p><p><pre class="code">
- 
-  CONSTRUCT {
-    ?document1 a prov:Entity ;
-    ?document2 a prov:Entity .
-       prov:wasDerivedFrom ?document2.
- } WHERE {
-    OPTIONAL { ?document1 dct:isReferencedBy ?document2 . }
-    OPTIONAL { ?document2 dct:references ?document1 .}
- }
- 
-</pre></p><p>
-</p>
-<h5 id="term_replaces"><span class="secno">2.5.3.3 </span>dct:replaces / dct:isReplacedBy</h5>
-<p><pre class="code">
- CONSTRUCT {
-    ?document1 a prov:Entity ;
-       prov:wasInfluencedBy ?document2.
-    ?document2 a prov:Entity .
- } WHERE {
-    OPTIONAL { ?document1 dct:replaces ?document2 . }
-    OPTIONAL { ?document2 dct:isReplacedBy ?document1 .}
- }
-</pre></p><p>
-<h5 id="term_source"><span class="secno">2.5.3.4 </span>dct:source</h5>
-</p><p><pre class="code">
- CONSTRUCT{
-   ?document1     a   prov:Entity ;
-                  prov:wasDerivedFrom    :subj2 .
-   ?document2     a   prov:Entity .
-  } WHERE { 
-   ?document1 dct:source ?document2.
-  }
-</pre>
-</p>
-</div>
--->
+
 </div>
 <div id="cleanup" class="section">
 <h3><span class="secno">2.5.3 </span>Cleanup</h3>