Merge pull request #384 from bernafarias/gh-pages

Updating context diagram

bp.html

@@ -681,7 +681,7 @@ <h2>Scope</h2>
     </section>
     <section id="context" class="informative">
       <h2>Context</h2>
-      <p>In general, the Best Practices proposed for publication and usage of
+      <p>The following diagram illustrates the context considered in this document. In general, the Best Practices proposed for publication and usage of
         Data on the Web refer to <a href="#dataset">datasets</a> and <a href="#distribution">
           distributions</a>. Data is published in different distributions, which are specific physical form of a dataset. By data, "we mean known facts
         that can be recorded and that have implicit meaning" [[Navathe]]. These
@@ -690,29 +690,19 @@ <h2>Context</h2>
         data consumers </a>, without regard to purpose, audience, interest,
         or license. Given this heterogeneity and the fact that data publishers
         and data consumers may be unknown to each other, it is necessary to
-        provide some information about the datasets that may also contribute to
+        provide some information about the datasets and distributions that may also contribute to
         trustworthiness and reuse, such as: structural metadata, descriptive
         metadata, access information, data quality information, provenance
         information, license information and usage information. </p>
       <p>An important aspect of publishing and sharing data on the Web
         concerns the architectural basis of the Web [[WEBARCH]].
-        An important aspect of this is the identification principle that says that URIs
+        A relevant aspect of this is the identification principle that says that URIs
         should be used to identify resources. In our context, a resource may be
         a whole dataset or a specific item of given dataset. All resources
         should be published with stable URIs, so that they can be referenced and
-        make links, via URIs, between two or more resources.</p>
-      <p>The following diagram illustrates the dataset composition (data values
-        and metadata) together with other components related to the dataset
-        publication and usage. Data values correspond to the data itself and may
-        be available in one or more distributions, which should be defined by
-        the publisher considering data consumer's expectations. The Metadata
-        component corresponds to the additional information that describes the
-        dataset and dataset distributions, helping the manipulation and the
-        reuse of the data. In order to allow easy access to the dataset and
-        its corresponding distributions, multiple dataset access mechanisms
-        can be available. Finally, to promote the interoperability among
-        datasets it is important to adopt vocabularies and standards. </p>
-      <img src="images/context.jpg" alt="Our Context" height="280" width="480">
+        make links, via URIs, between two or more resources. Finally, to promote the interoperability among datasets it is important to adopt data vocabularies and standards. </p>
+      <!--<p>The following is a composite diagram illustrating the anatomy of a published and acessible Web dataset. Data values correspond to the data itself and may be available in one or more distributions, which should be defined by the publisher considering data consumer's expectations. The Metadata component corresponds to the additional information that describes the dataset and dataset distributions, helping consumers manipulate and reuse the data. In order to allow easy access to the dataset and its corresponding distributions, multiple dataset access mechanisms can  be available. Finally, to promote the interoperability among datasets it is important to adopt data vocabularies and standards.  </p>-->
+      <img src="images/context.png" alt="Our Context" height="280" width="680">
     </section>
     <section id="namespaces" class="informative">
       <h2> Namespaces </h2>