deploy: 3f37340

index.html

@@ -335,6 +335,9 @@
           <li>
             <a href="#standardized-core-components-and-extensions-for-data-economy-specifications" class="toc-h1 toc-link" data-title="Standardized Core Components and Extensions for Data Economy Specifications">Standardized Core Components and Extensions for Data Economy Specifications</a>
           </li>
+          <li>
+            <a href="#introduction" class="toc-h1 toc-link" data-title="Introduction">Introduction</a>
+          </li>
           <li>
             <a href="#core-components" class="toc-h1 toc-link" data-title="Core Components">Core Components</a>
               <ul class="toc-list-h2">
@@ -423,10 +426,10 @@
       <div class="content">
         <h1 id='standardized-core-components-and-extensions-for-data-economy-specifications'>Standardized Core Components and Extensions for Data Economy Specifications</h1>
 <p>A library of standardized core components and extentions to be used for example in Data Contracts and Data Product Sopecications. Solution vendors are invited to add extensions. </p>
-<h1 id='core-components'>Core Components</h1>
-<p>These are shared core components between data economy standards. By default the core components are very limited and compact to keep the overall standards easy to adopt. The usecases can be extended by expanding the core components with standardized versioned extensions. </p>
+<h1 id='introduction'>Introduction</h1>
+<p><strong>Core components</strong> are shared between data economy standards. By default the core components are very limited and compact to keep the overall standards easy to adopt. </p>
 
-<p>Extension pattern is universal and same in all core components. The core components can be extended with two distinctive patterns. Internal (locally used) woould use &quot;x-localized&quot; element and inside it is your local extension content. </p>
+<p>The usecases can be extended by expanding the core components with localized and standardized versioned <strong>extensions</strong>. Extension pattern is universal and same in all core components. The core components can be extended with two distinctive patterns. Internal (locally used) woould use &quot;x-localized&quot; element and inside it is your local extension content. </p>
 
 <blockquote>
 <p>Example of local extension usage:</p>
@@ -443,7 +446,7 @@ <h1 id='core-components'>Core Components</h1>
 <div class="highlight"><pre class="highlight yaml"><code>
 <span class="na">x-standardized</span><span class="pi">:</span>
 
-</code></pre></div><h2 id='access'>Access</h2><h2 id='data'>Data</h2><h2 id='data-quality'>Data Quality</h2>
+</code></pre></div><h1 id='core-components'>Core Components</h1><h2 id='access'>Access</h2><h2 id='data'>Data</h2><h2 id='data-quality'>Data Quality</h2>
 <p>Data quality extensions defined separately.</p>
 <h2 id='pricing'>Pricing</h2>
 <p>Pricing is the process whereby a business sets the price at which it will sell its products and services. Pricing <strong>OBJECT</strong> consists of mandatory and optional attributes. This element contains pricing plans related data to be used for example in displaying the items in a marketplace or as part of a data contract.   </p>