[CI] Publish Documentation for efbe7cf

epo-home/REFcharter.html

@@ -134,7 +134,7 @@ <h3 class="title"><a href="index.html">eProcurement Ontology</a></h3>
     <span class="nav-text"><span class="separated"><strong>Working Group Documents</strong></span></span>
   </li>
   <li class="nav-item" data-depth="1">
-    <a class="nav-link" href="../epo-wgm/wider.html">Biannual Meetings</a>
+    <a class="nav-link" href="../epo-wgm/wider.html">Quarterly Meetings</a>
   </li>
   <li class="nav-item" data-depth="1">
     <a class="nav-link" href="../epo-wgm/cumulative.html">Cumulative Reports (by year)</a>
@@ -820,7 +820,7 @@ <h3 id="_timing_and_milestones"><a class="anchor" href="#_timing_and_milestones"
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">E2</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">First draft of conceptual model and its specification corresponding to the use cases concerned for the next meeting and incorporating the results from the discussions of the previous meeting</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">First draft of conceptual model and its specification corresponding to the use cases concerned for the next meeting and incorporating the results from the iscussions of the previous meeting</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Month 1 - October 2017</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Prepared by editors based on discussions from the previous meeting and all corresponding input for the following meeting</p></td>
 </tr>

epo-home/REFePO_Arch_Design.html

@@ -134,7 +134,7 @@ <h3 class="title"><a href="index.html">eProcurement Ontology</a></h3>
     <span class="nav-text"><span class="separated"><strong>Working Group Documents</strong></span></span>
   </li>
   <li class="nav-item" data-depth="1">
-    <a class="nav-link" href="../epo-wgm/wider.html">Biannual Meetings</a>
+    <a class="nav-link" href="../epo-wgm/wider.html">Quarterly Meetings</a>
   </li>
   <li class="nav-item" data-depth="1">
     <a class="nav-link" href="../epo-wgm/cumulative.html">Cumulative Reports (by year)</a>
@@ -357,7 +357,7 @@ <h1 class="page">eProcurement Ontology Architecture and Formalisation Specificat
 <p>Reference herein to any specific products, specifications, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favouring by the European Union.</p>
 </div>
 <div class="paragraph">
-<p>This report was prepared for the Publications Office of the European Union by InfEurope.</p>
+<p>This report was prepared for the Publications Office of the European Union by Infeurope.</p>
 </div>
 <div class="exampleblock">
 <div class="content">
@@ -523,7 +523,7 @@ <h3 id="_context_and_scope"><a class="anchor" href="#_context_and_scope"></a>1.3
 <p>In the 2020 ISA<sup>2</sup> work programme a new project has been set up to analyse existing procurement data through the lens of the newly developed conceptual model. This means that the conceptual model needs to be transposed into a formal ontology, and a subset of the existing eProcurement data must be transformed into RDF format such that they instantiate the eProcurement ontology and conform to a set of predefined data shapes. Initially, the notification phase will be considered, while subsequent datasets will be decided at a later stage.</p>
 </div>
 <div class="paragraph">
-<p>Working under the assumption that Steps 1–4 have been completed, current efforts are channelled towards designing, implementing and executing the necessary tasks to accomplish Step 5 from the above process. Once the formal ontology is created, and the XML data is transformed into RDF representation, the data can be queried to validate its suitability in satisfying the business use cases defined in (<a href="#_24">[_24]</a>, Sec. 3).</p>
+<p>Working under the assumption that Steps 1–4 have been completed, current efforts are channeled towards designing, implementing and executing the necessary tasks to accomplish Step 5 from the above process. Once the formal ontology is created, and the XML data is transformed into RDF representation, the data can be queried to validate its suitability in satisfying the business use cases defined in (<a href="#_24">[_24]</a>, Sec. 3).</p>
 </div>
 <div class="paragraph">
 <p>This document consists of an architectural specification and implementation guidelines that shall be taken into consideration when developing the formal ontology.</p>

epo-home/REFlandscaping.html

@@ -134,7 +134,7 @@ <h3 class="title"><a href="index.html">eProcurement Ontology</a></h3>
     <span class="nav-text"><span class="separated"><strong>Working Group Documents</strong></span></span>
   </li>
   <li class="nav-item" data-depth="1">
-    <a class="nav-link" href="../epo-wgm/wider.html">Biannual Meetings</a>
+    <a class="nav-link" href="../epo-wgm/wider.html">Quarterly Meetings</a>
   </li>
   <li class="nav-item" data-depth="1">
     <a class="nav-link" href="../epo-wgm/cumulative.html">Cumulative Reports (by year)</a>
@@ -472,7 +472,7 @@ <h3 id="_context"><a class="anchor" href="#_context"></a>1.1. Context</h3>
 <p>To deliver the aforementioned benefits, e-Procurement relies heavily on the exchange of data between the different systems supporting the procurement processes i.e., achieving end-to-end interoperability of public procurement processes and underlying systems, and on the availability and dissemination of procurement data to the wider public i.e., improving transparency and stimulating innovation and new business opportunities.</p>
 </div>
 <div class="paragraph">
-<p>As stated in the Commission Regulation 2015/1986 (EU), contracting authorities in the EU are legally required to publish notices above certain capital thresholds. Article 6 of that Regulation states that either the online eNotices application or the TED eSender systems should be used for electronic transmission of notices to the Publications Office of the European Union. From a different angle, the implementation of the/ a revised PSI directive across the EU is calling for open, unobstructed access to public data to improve transparency, and to boost innovation, via the reuse of public data. Procurement data has been identified as data with a high-reuse potential. Making this data available in machine-readable formats, following on from the "data as a service" paradigm, is required to maximise its reuse.</p>
+<p>As stated in the Commission Regulation 2015/1986 (EU), contracting authorities in the EU are legally required to publish notices above certain capital thresholds. Article 6 of that Regulation states that either the online eNotices application or the TED eSender systems should be used for electronic transmition of notices to the Publications Office of the European Union. From a different angle, the implementation of the/ a revised PSI directive across the EU is calling for open, unobstructed access to public data to improve transparency, and to boost innovation, via the reuse of public data. Procurement data has been identified as data with a high-reuse potential. Making this data available in machine-readable formats, following on from the "data as a service" paradigm, is required to maximise its reuse.</p>
 </div>
 <div class="paragraph">
 <p>Data exchange, access, and reuse are key requirements for efficient and transparent end-to-end public procurement. Because of this, we observe a shift in focus from the definition of procurement process standards for system-to-system exchange, to the development of data standards for publishing e-Procurement data in open, machine-readable formats (see Chapter 4 Related Ontologies/Vocabularies and Projects).</p>
@@ -1054,7 +1054,7 @@ <h3 id="_use_cases"><a class="anchor" href="#_use_cases"></a>3.2. Use cases</h3>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">3.1</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Increase cross-domain interoperability among Member States</strong></p>
-<p class="tableblock"><em>The European Union aims at providing a competitive economic environment for economic operators from different Member States. In order to achieve such a competitive environment, economic operators, public administrations, researchers, and academia should be able to access and exchange procurement information coming from different sources around Europe, allowing them to participate in calls for tenders from procurers from different Member States. Similarly, contracting authorities should be able to access information about economic operators, which are based in different Member States, and submit tenders for procured services. Making e-Procurement data available in common well-structured and machine-readable formats enhances cross-domain and trans-European competitiveness by allowing economic operators from any Member State to participate in public procurement in any other Member State.</em></p>
+<p class="tableblock"><em>The European Union aims at providing a competitive economic environment for economic operators from different Member States. In order to achieve such a competitive environment, economic operators, public administrations, researchers, and academia should be able to access and exchange procurement information coming from different sources around Europe, allowing them to participate in calls for tenders from procurers from different Member States. Similarly, contracting authorities should be able to access information about economic operators, which are based in different Member States, and submit tenders for procured services. Making e-Procurement data available in common well-structured and machine-readable formats enhances cross-domain and trans-European competiveness by allowing economic operators from any Member State to participate in public procurement in any other Member State.</em></p>
 <p class="tableblock"><strong>Example:</strong></p>
 <p class="tableblock">The VAT authority of a Member state wants to monitor the activity of a certain economic operator. By having all procurement data in all Member States published in a common and machine readable format, this data can be integrated into the systems of the VAT authority. This way it can instantly gain access to all data about any business conducted for public administrations by that economic operator in any other Member State.</p>
 <p class="tableblock"><strong>Information requirements:</strong></p>
@@ -1273,7 +1273,7 @@ <h4 id="_cen_wsbii_business_term_vocabulary_and_semantic_models"><a class="ancho
 </div>
 <div class="paragraph">
 <p>These profiles describe aspects throughout the whole procurement process such as notifications, the call for tenders, awarding and contracting.
-These profiles were implemented in several projects in Europe: the European Commission used them to build e-Prior, their open source solution for electronic invoicing and ordering, now also covering the pre-award phases; the PEPPOL community has also used them to create their own BIS specifications, resulting in a national-wide deployment of electronic invoicing in countries such as Norway, Denmark and Sweden, and other public administrations in Europe are currently basing their IT infrastructure and electronic procurement policies on deploying these standards e.g.,the National Health Service of the United Kingdom.</p>
+These profiles were implemented in several projects in Europe: the European Commission used them to build e-Prior, their open source solution for electronic invoicing and ordering, now also covering the pre-award phases; the PEPPOL  community has also used them to create their own BIS specifications, resulting in a national-wide deployment of electronic invoicing in countries such as Norway, Denmark and Sweden, and other public administrations in Europe are currently basing their IT infrastructure and electronic procurement policies on deploying these standards e.g.,the National Health Service of the United Kingdom.</p>
 </div>
 <div class="paragraph">
 <p>These profiles were updated in 2015 and examples of some profiles are listed below in Table 6 Examples of CEN BII Profiles.</p>

epo-home/REFmetgovman.html

@@ -134,7 +134,7 @@ <h3 class="title"><a href="index.html">eProcurement Ontology</a></h3>
     <span class="nav-text"><span class="separated"><strong>Working Group Documents</strong></span></span>
   </li>
   <li class="nav-item" data-depth="1">
-    <a class="nav-link" href="../epo-wgm/wider.html">Biannual Meetings</a>
+    <a class="nav-link" href="../epo-wgm/wider.html">Quarterly Meetings</a>
   </li>
   <li class="nav-item" data-depth="1">
     <a class="nav-link" href="../epo-wgm/cumulative.html">Cumulative Reports (by year)</a>
@@ -1506,7 +1506,7 @@ <h4 id="_versioning"><a class="anchor" href="#_versioning"></a>3.3.5. Versioning
 </div>
 <div class="paragraph">
 <p>While the latest version of a data model or reference data collection is clearly the most important resource to be re-used as this supports the functionality at that
-particular point in time, it is also necessary that previous versions are still available for inspection. This makes it possible to determine what functionality was available in the past. In relation to that, it is also important that the documentation of previous versions as well as change logs are kept available.</p>
+particular point in time, it is also necessary that  revious versions are still available for inspection. This makes it possible to determine what functionality was available in the past. In relation to that, it is also important that the documentation of previous versions as well as change logs are kept available.</p>
 </div>
 <div class="paragraph">
 <p>Identification of versions of structural metadata can be done by time-stamping the versions, by assigning version numbers or by combining those two approaches.</p>

epo-home/REFreferences.html

@@ -134,7 +134,7 @@ <h3 class="title"><a href="index.html">eProcurement Ontology</a></h3>
     <span class="nav-text"><span class="separated"><strong>Working Group Documents</strong></span></span>
   </li>
   <li class="nav-item" data-depth="1">
-    <a class="nav-link" href="../epo-wgm/wider.html">Biannual Meetings</a>
+    <a class="nav-link" href="../epo-wgm/wider.html">Quarterly Meetings</a>
   </li>
   <li class="nav-item" data-depth="1">
     <a class="nav-link" href="../epo-wgm/cumulative.html">Cumulative Reports (by year)</a>

epo-home/REFspecification.html

@@ -134,7 +134,7 @@ <h3 class="title"><a href="index.html">eProcurement Ontology</a></h3>
     <span class="nav-text"><span class="separated"><strong>Working Group Documents</strong></span></span>
   </li>
   <li class="nav-item" data-depth="1">
-    <a class="nav-link" href="../epo-wgm/wider.html">Biannual Meetings</a>
+    <a class="nav-link" href="../epo-wgm/wider.html">Quarterly Meetings</a>
   </li>
   <li class="nav-item" data-depth="1">
     <a class="nav-link" href="../epo-wgm/cumulative.html">Cumulative Reports (by year)</a>
@@ -1610,7 +1610,7 @@ <h3 id="_classes"><a class="anchor" href="#_classes"></a>5.1. Classes</h3>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Call For Tender</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">A Document that specifies the object of the procurement and any procurement criteria, the publication of which is the initiating step of a competitive tendering process in which qualified suppliers or contractors are invited to submit sealed bids for construction or for supply of specific and clearly defined goods or services during a specified time frame.
+<td class="tableblock halign-left valign-top"><p class="tableblock">A Document that specifies the object of the procurement and any procurement criteria, the publication of which is the initiating step of a competitive tendering process in which qualified suppliers or contractors are invited to submit sealed bids for construction or for supply of specific and clearly defined goods or services during a specified timeframe.
 Subclass of Document.
 As described by the issue 731 on GitHub, the class Call For Tender could be further detailed. Depending on further use cases, it may be necessary to distinguish between Framework Agreements and Specific Contracts. This could be done by including a 'type' property in the description of the Call For Tender or by defining subclasses.
 The issue 2432 on GitHub proposes the introduction of the class Lot. From the discussion during the next phases, the relationship between Call For Tender and Lot may need to be further detailed.</p></td>