Slightly richer abstract and introduction

profilesont/index.html

@@ -11,12 +11,11 @@
 <section id="abstract">
   <h2>Abstract</h2>
   <p>
-    This ontology is for describing relationships between standards/specifications, profiles of them and supporting
-    artifacts, such as validating resources.
+    An ontology for listing the set of resources required for a standard or a profile of one or more standards, such as schemas, ontologies, and rules, and for specifying the relationships between them and supporting artefacts, such as controlled vocabularies, validation tools, and guidelines.
   </p>
   <p style="text-align: center;">
     The namespace for PROF terms is <code>https://w3c.github.io/dxwg/profilesont/</code>.<br />
-    The PROF ontology in OWL, encoded in RDF Turtle, is available at <a href="profilesont.ttl">profilesont.ttl</a>.
+    The PROF ontology, defined in OWL and encoded in RDF Turtle, is available at <a href="profilesont.ttl">profilesont.ttl</a>.
   </p>
   <div class="issue" data-number="398"></div>
 </section>
@@ -57,7 +56,14 @@ <h4>Profiling documents</h4>
 <section id="introduction">
   <h1>Introduction</h1>
   <p>
-    This model starts with <a href="http://dublincore.org/2012/06/14/dcterms#Standard">dcterms:Standard</a> entities
+    The profiles ontology is designed to provide a structure to describe profiles of information standards.
+    Its development was triggered by the appearance of multiple profiles of the Dataset Catalog Vocabulary [[!vocab-dcat-20140116]], and also influenced by work on profiles of the Dublin Core metadata vocabulary.
+    These profiles aim to increase interoperability within a specified community of DCAT or Dublin Core users by introducing certain limitations on the use of the general vocabulary, such as restrictions on the cardinality of certain properties, or a requirement to select values of a property from a specified controlled vocabulary.
+    The profiles have generally been specified through textually-oriented documents.
+    This ontology provides a more formally structured, machine readable alternative formalization for these profiles.
+  </p>
+  <p>
+    The model starts with <a href="http://dublincore.org/2012/06/14/dcterms#Standard">dcterms:Standard</a> entities
     which can either be Base Specifications (a standard not profiling any other Standard) or Profiles (Standards which
     do profile others). Base Specifications or Profiles can have Implementation Resource Descriptors associated with
     them that defines implementing rules for the it. Implementation Resource Descriptors must indicate the role they