Merge pull request #760 from w3c/updates-intro-2

Updates intro 2

profiles/index.html

@@ -49,9 +49,9 @@ <h3>Overview of DXWG documents on profiles</h3>
     <h2>Introduction</h2>
     <p><em>This section is non-normative.</em></p>
     <p>
-			A <em>profile</em> is generally understood as being the outline of some "thing" when seen from a specific point of view. 
-			<em>Profiling</em> is also the task of distilling the essential aspects or character of something, such as a person, 
-			from a specific angle. Also, in the craft domain, a profile is taken by a tool that matches itself in detail 
+			A <em>profile</em> can be understood as an outline of some "thing" when seen from a specific point of view. 
+			Also, <em>Profiling</em> is the task of distilling the essential aspects or character of something, such as a person, 
+			from a specific angle. In the craft domain, a profile is taken by a tool that matches itself in detail 
 			to the contours of a 3-dimensional object and returns a 2-dimensional accurate representation from which other 
 			formable materials can be constrained and fashioned to that profile, or matched with it to determine how accurately 
 			it portrays the original 3-dimensional object from which the profile was taken.
@@ -69,15 +69,15 @@ <h2>Introduction</h2>
       identified base specifications.
     </p>
     <p>
-      Good data practice begins with the builders of vocabularies and ontologies. Builders of vocabularies and
-      ontologies are encouraged to make their work as broadly applicable as possible so as to maximize future adoption.
+      Good data practice generally begins with vocabulary and ontology designers who
+      are encouraged to make their work as broadly applicable as possible so as to maximize future adoption.
       As a result, vocabularies and ontologies typically define a data model using minimal semantics. For example,
       DCAT [[vocab-dcat-2]] defines the concept of a dataset as an abstract entity with distributions and data services
-      as means of accessing data; it is silent on whether a distribution should be in a particular serialization, or
-      set of serializations. It is also silent on how data services should be configured. While it states that the
+      as means of accessing data; there is no mention of whether a distribution should be in a particular serialization, or
+      set of serializations, nor of how data services should be configured. While it states that the
       value of dcat:theme should be a SKOS [[skos-reference]] concept, it does not specify a particular SKOS concept
-      scheme, and so on. Other vocabularies, such as Dublin Core Terms [[DCTERMS]], are equally parsimonious in their
-      prescriptions of how they should be used. This means that data models and methods of working can be applied in
+      scheme, and so on. Other vocabularies, such as Dublin Core Terms [[DCTERMS]], are similarly for general use. 
+	  This means that data models and methods of working can be applied in
       different circumstances than those in which the original definition work was carried out and, in that sense,
       these promote broad interoperability.
     </p>
@@ -92,16 +92,16 @@ <h2>Introduction</h2>
       this property MUST be from this specific code list".
     </p>
     <p>
-      This document is about how to formulate and communicate profiles.
+      This document is about how to formulate and communicate profiles and the ways in which profiles can be 
+		identified and related to each other.
     </p>
-    <div class="issue" data-number="417"></div>
     <div class="issue" data-number="450"></div>
 
     <section id="definitions">
       <h3>Definitions</h3>
     <p>
-			We recognise that the term 'profile' occurs in several different domains, and that there are a range of definitions 
-			available within different communities. We have taken this into account but for the purpose of this document we 
+			We recognise that the term 'profile' occurs in several domains, and that there are a range of definitions 
+			available from different communities. We have taken this variability into account but for the purpose of this document we 
 			are using the following definitions:
     <p>
       <dl>
@@ -152,13 +152,13 @@ <h3>Examples of profiles and related work</h3>
         Profiles can take a number of forms and can have a variety of relationships to existing vocabularies, 
 				standards, and other profiles. We recognise this variety, but for the purposes of this document we are focusing 
 				on the most general forms of profile and profiling. Although it is not possible to list all of the types 
-				of profiles, some illustrations of frequently-used profiles are:
+				of profiles, some illustrations of frequently-used profiles include:
       </p>
 			<ul>
 				<li>
 					profiles that are subsets of a larger vocabulary. These reduce the vocabulary terms of a broad data 
 					standard to a smaller number of terms that are useful for a particular community member or application. 
-					An example of this is <a href="http://bibfra.me/">BIBFRA.me</a> designed for library materials. It defines 
+					An example of this is <a href="http://bibfra.me/">BIBFRA.me</a>, which is designed for library materials and defines 
 					both a core set of terms as well as profiles for specialized communities such as cataloging of rare materials 
 					or early printing trade. In this community, all profiles use only terms from a single vocabulary.
 				</li>
@@ -195,7 +195,7 @@ <h3>Examples of profiles and related work</h3>
 
 
   <div class="issue" data-number="416"></div>
-	<div class="issue" data-number="242">See comment <a href="https://github.com/w3c/dxwg/issues/242#issuecomment-408916364">408916364</a></div>
+  <div class="issue" data-number="242">See comment <a href="https://github.com/w3c/dxwg/issues/242#issuecomment-408916364">408916364</a></div>
 
 
   <section id="whatisaprofile">