Updated section 2.1

w3c · Mar 19, 2019 · 0a5ec28 · 0a5ec28
1 parent 146fad3
commit 0a5ec28
Showing 1 changed file with 15 additions and 2 deletions.
diff --git a/profiles/index.html b/profiles/index.html
@@ -236,9 +236,22 @@ <h2>Diving into profiles</h2>
       <div class="issue" data-number="597"></div>
 
  <section class="requirement" id="RPFNCTERMS"> 
-	 <h3>Profiles are named collections of properties</h3>
+	 <h3>Profiles are uniquely named sets of data constraints, such as data elements (e.g. classes, properties, value domains) that describe (meta)data.
+</h3>
     <!--<h3>Named collections of terms [RPFNCTERMS]</h3>-->
-    <p>Profiles SHOULD be made up of a collection of properties or terms, and that collection SHOULD have a name. Properties are selected from existing vocabularies. Because profiles as being described here are not limited to those in RDF, collections could be of metadata terms from any type of metadata schema.</p>
+
+    <p>
+	    When building a profile you SHOULD give it a name and you SHOULD build it from properties or terms that 
+	    you have collected from pre-existing sources. Because we are considering a wide range of profiles, 
+	    not just those in RDF, collections could be of metadata terms from any type of metadata schema, but 
+      they might also include collections of identifiers, value lists and enumerations, other data elements, 
+      and anything else that might be helpful in ensuring that the data matches the purpose intended by you 
+      and your community
+    </p>
+    <div class="note">
+      <p>In our context, "constraints" is a general notion, which include specification of optional data elements.
+     </p>
+   </div>
 <div class="issue" data-number="275"></div>
     <div class="note"><p>It could also be in roles/functions if there is nothing there about defining terms. Antoine Isaac, 2018-11-11
      </p></div>