Merge pull request #103 from linked-statistics/issue-59

Statistical vs non-statistical

coos.html

@@ -239,7 +239,7 @@ <h2>COOS Namespace and Vocabulary</h2>
 						<td><a href="#activities">Section 3. Activities</a></td>
 					</tr>
 					<tr>
-						<td>coos:StatisticalProductionActivity</td>
+						<td>coos:ProductionActivity</td>
 						<td><a href="#activities">Section 3. Activities</a></td>
 					</tr>
 					<tr>
@@ -311,15 +311,15 @@ <h2>COOS Namespace and Vocabulary</h2>
 						<td><a href="#products">Section 5. Products</a></td>
 					</tr>
 					<tr>
-						<td>coos:StatisticalEntity</td>
+						<td>coos:Entity</td>
 						<td><a href="#products">Section 5. Products</a></td>
 					</tr>
 					<tr>
-						<td>coos:StatisticalProduct</td>
+						<td>coos:Product</td>
 						<td><a href="#products">Section 5. Products</a></td>
 					</tr>
 					<tr>
-						<td>coos:StatisticalDataset</td>
+						<td>coos:Dataset</td>
 						<td><a href="#products">Section 5. Products</a></td>
 					</tr>
 					<tr>
@@ -491,20 +491,20 @@ <h3>Base GSBPM model</h3>
 
 				<p>To materialize a clear distinction between the model itself and the statistical process which is modeled, the ontology defines classes that inherit from <code>prov:Activity</code>. Using PROV allows to describe an activity that really happens at a certain time, to specify who undertakes the activity and what entities it consumes or produces.</p>
 
-				<p>Basically, three classes are defined in this ontology: <code>StatisticalProductionActivity</code>, <code>Phase</code> and <code>SubProcess</code>.</p>
+				<p>Basically, three classes are defined in this ontology: <code>ProductionActivity</code>, <code>Phase</code> and <code>SubProcess</code>.</p>
 
-				<p><code>StatisticalProductionActivity</code> is a sub-class of <code>prov:Activity</code>. Instances of this class are intended to be larger than a GSBPM phase. If they correspond to a statistical production process they are typed using the <code>dcterms:type</code> property with the <code>statisticalProductionProcess</code> individual.</p>
+				<p><code>ProductionActivity</code> is a sub-class of <code>prov:Activity</code>. Instances of this class are intended to be larger than a GSBPM phase. If they correspond to a statistical production process they are typed using the <code>dcterms:type</code> property with the <code>statisticalProductionProcess</code> individual.</p>
 
 				<pre class="example nohighlight" title="Examples of statistical production activities">
-				ex:produce-study-2021 a coos:StatisticalProductionActivity ;
+				ex:produce-study-2021 a coos:ProductionActivity ;
 					rdfs:label "Produce study on legal population 2021"@en .
 
-				ex:produce-census-2021 a coos:StatisticalProductionActivity ;
+				ex:produce-census-2021 a coos:ProductionActivity ;
 					rdfs:label "Produce census 2021"@en ;
 					dcterms:type coos:statisticalProductionProcess .
 				</pre>
 
-				<p><code>Phase</code> and <code>SubProcess</code> are both sub-classes of <code>StatisticalProductionActivity</code>. A link to the GSBPM taxonomy using the property <code>dcterms:type</code> is made on instances of these classes to formalize to what part of the GSBPM the activity that happened corresponds. Additionally, the idea that each phase is made up of its different sub-processes can be represented by using the Dublin Core <code>dcterms:hasPart</code> and <code>dcterms:isPartOf</code> properties.</p>
+				<p><code>Phase</code> and <code>SubProcess</code> are both sub-classes of <code>ProductionActivity</code>. A link to the GSBPM taxonomy using the property <code>dcterms:type</code> is made on instances of these classes to formalize to what part of the GSBPM the activity that happened corresponds. Additionally, the idea that each phase is made up of its different sub-processes can be represented by using the Dublin Core <code>dcterms:hasPart</code> and <code>dcterms:isPartOf</code> properties.</p>
 
 				<pre class="example nohighlight" title="Examples of instances phase and sub-process">
 				ex:collect-census-2021 a coos:Phase ;
@@ -538,7 +538,7 @@ <h3>Base GSBPM model</h3>
 
 				<h3>Adding GAMSO</h3>
 
-				<p>Introducing GAMSO in this framework is not very difficult. The terminology used in the model shows that the main concepts are activity and activity areas. GAMSO describes two kinds of activities: those that are of statistical nature, for example “Manage Statistical Methodology”, and those that are in support of statistical activities, like “Manage Finances”. To account for this distinction, COOS defines two different classes: <code>StatisticalActivity</code> and <code>Activity</code>. <code>Activity</code> is a subclass of <code>prov:Activity</code> and a superclass of <code>StatisticalActivity</code>, which in turn is a superclass of the <code>StatisticalProductionActivity</code> introduced previously.</p>
+				<p>Introducing GAMSO in this framework is not very difficult. The terminology used in the model shows that the main concepts are activity and activity areas. GAMSO describes two kinds of activities: those that are of statistical nature, for example “Manage Statistical Methodology”, and those that are in support of statistical activities, like “Manage Finances”. To account for this distinction, COOS defines two different classes: <code>StatisticalActivity</code> and <code>Activity</code>. <code>Activity</code> is a subclass of <code>prov:Activity</code> and a superclass of <code>StatisticalActivity</code>, which in turn is a superclass of the <code>ProductionActivity</code> introduced previously.</p>
 
 				<p>The GAMSO activity areas are not really activities by themselves, but rather “boxes” used to classify the activities. This makes them instances of <code>skos:Concept</code> to represent this “taxonomic” nature, or more precisely of a specific <code>ActivityArea</code> class, which is a sub-class of <code>skos:Concept</code>.</p>
 
@@ -556,10 +556,10 @@ <h3>Adding GAMSO</h3>
 
 				<p>In addition, COOS defines the <code>OverarchingActivity</code> class, which represents a supporting activity that applies to all production phases, e.g. metadata management, data management, statistical methodology management, etc. These activities correspond to the overarching processes in the GSBPM and the statistical activities in Corporate Support in GAMSO. These activities support the execution of phases and sub-processes effectively. When harmonized and standardized, overarching activities enable the efficient execution of the entire statistical production process.</p>
 
-				<p>Finally, two properties are needed to describe how an <code>Activity</code> classified with GAMSO relates to a <code>StatisticalProductionActivity</code> classified with GSBPM:</p>
+				<p>Finally, two properties are needed to describe how an <code>Activity</code> classified with GAMSO relates to a <code>ProductionActivity</code> classified with GSBPM:</p>
 
 				<ul>
-					<li><code>supports</code>: an <code>Activity</code> helps to perform a <code>StatisticalProductionActivity</code>, e.g. a sub-process;</li>
+					<li><code>supports</code>: an <code>Activity</code> helps to perform a <code>ProductionActivity</code>, e.g. a sub-process;</li>
 					<li><code>uses</code>: conversely, a statistical production activity will require one or several activities in order to function.</li>
 				</ul>
 
@@ -593,7 +593,7 @@ <h3>Adding GAMSO</h3>
 
 				<h3>Adding GSIM and CSDA</h3>
 
-				<p>Adding the Generic Statistical Information Model (GSIM) in this framework allows us to refine <code>StatisticalActivity</code> even further. In parallel to <code>StatisticalProductionActivity</code>, two additional sub-classes of <code>StatisticalActivity</code> can be defined:</p>
+				<p>Adding the Generic Statistical Information Model (GSIM) in this framework allows us to refine <code>StatisticalActivity</code> even further. In parallel to <code>ProductionActivity</code>, two additional sub-classes of <code>StatisticalActivity</code> can be defined:</p>
 				<ul>
 					<li><code>StatisticalProgram</code>: it is essentially a set of activities carried out to produce statistics. These statistics are about the set of units in scope for the program, e.g. “All persons with a university degree”, within a given subject field, e.g. income statistics, tourism, etc.</li>
 					<li><code>StatisticalProgramCycle</code>: statistical program activities are often repeated over time in iterations called cycles. A StatisticalProgramCycle is one of those iterations for a specific time and geography. To link a cycle to the corresponding program, it is recommended to use `dcterms:isPartOf`. Nevertheless, this property does not convey aspects like temporality, so a more specific property might be defined in a future version of COOS.</li>
@@ -684,11 +684,11 @@ <h2>Organizations</h2>
 
 			<h2>Products</h2>
 
-			<p>Finally, the information that activities, capabilities and processes use and produce needs to be described. This is captured by an <code>InformationObject</code> class that aligns with the notion of “information object” in GSIM, i.e. all GSIM classes are going to be sub-classes of <code>InformationObject</code>. A <code>StatisticalInformationObject</code> is essentially an <code>InformationObject</code> representing statistical information, i.e. they are the inputs and outputs in the design and production of statistics. Some of those statistical information objects are also entities in the <code>Prov</code> sense, which are captured by the <code>StatisticalProduct</code> and <code>StatisticalDataset</code> classes, corresponding to the GSIM Product and GSIM Data Set, respectively. </p>
+			<p>Finally, the information that activities, capabilities and processes use and produce needs to be described. This is captured by an <code>InformationObject</code> class that aligns with the notion of “information object” in GSIM, i.e. all GSIM classes are going to be sub-classes of <code>InformationObject</code>. A <code>StatisticalInformationObject</code> is essentially an <code>InformationObject</code> representing statistical information, i.e. they are the inputs and outputs in the design and production of statistics. Some of those statistical information objects are also entities in the <code>PROV</code> sense, which are captured by the <code>Product</code> and <code>Dataset</code> classes, corresponding to the GSIM Product and GSIM Data Set, respectively. </p>
 
 			<p>Here again, the PROV vocabulary is useful, in particular to provide provenance information on products and to link them to activities and organizations (for example <code>prov:wasGeneratedBy</code> from a product to an activity).</p>
 
-			<p>The <code>StatisticalDataset</code> class is also declared as a daughter of <code>dcat:Dataset</code>, which allows the reuse of DCAT (or StatDCAT-AP), in particular to document datasets and their different distributions, group them in catalogues, etc.</p>
+			<p>The <code>Dataset</code> class is also declared as a daughter of <code>dcat:Dataset</code>, which allows the reuse of DCAT (or StatDCAT-AP), in particular to document datasets and their different distributions, group them in catalogues, etc.</p>
 
 			<figure id="image-prod">
 				<img src="img/coos-prod.png" alt="Products vocabulary main classes" title="Products vocabulary main classes"/>