Published versions with Release id set.

docs/task_planning.html

@@ -531,7 +531,7 @@ <h1 id="_task_planning_specification" class="sect0"><a class="anchor" href="#_ta
 </thead>
 <tbody>
 <tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Release</strong>: PROC latest</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Release</strong>: PROC Release-1.5.0</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Status</strong>: TRIAL</p></td>
 </tr>
 <tr>
@@ -1021,7 +1021,7 @@ <h3 id="_related_documents"><a class="anchor" href="#_related_documents"></a>1.2
 <div class="ulist">
 <ul>
 <li>
-<p>The <a href="https://specifications.openehr.org/releases/PROC/latest/tp_vml.html" target="_blank" rel="noopener">Task Planning Visual Modelling Language (TP-VML)</a>;</p>
+<p>The <a href="https://specifications.openehr.org/releases/PROC/Release-1.5.0/tp_vml.html" target="_blank" rel="noopener">Task Planning Visual Modelling Language (TP-VML)</a>;</p>
 </li>
 <li>
 <p>The <a href="https://specifications.openehr.org/releases/RM/latest/ehr.html" target="_blank" rel="noopener">openEHR EHR Information Model</a>;</p>
@@ -2391,7 +2391,7 @@ <h3 id="_order_semantics_versus_plan_semantics"><a class="anchor" href="#_order_
 <h2 id="_task_planning_model_overview"><a class="anchor" href="#_task_planning_model_overview"></a>5. Task Planning Model Overview</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>This section and the following one describe the Task Planning model in technical detail. Most of the emphasis is on the 'definition' level of expression, with most details of the 'materialised' and 'runtime' expressions left to implementers. Throughout these sections, a version of the <a href="https://specifications.openehr.org/releases/PROC/latest/tp_vml.html" target="_blank" rel="noopener">Task Planning Visual Modelling Language (TP-VML)</a> is used to illustrate instance structures. This visual language is designed to be formally aligned to the semantics of the model.</p>
+<p>This section and the following one describe the Task Planning model in technical detail. Most of the emphasis is on the 'definition' level of expression, with most details of the 'materialised' and 'runtime' expressions left to implementers. Throughout these sections, a version of the <a href="https://specifications.openehr.org/releases/PROC/Release-1.5.0/tp_vml.html" target="_blank" rel="noopener">Task Planning Visual Modelling Language (TP-VML)</a> is used to illustrate instance structures. This visual language is designed to be formally aligned to the semantics of the model.</p>
 </div>
 <div class="paragraph">
 <p>The following UML diagram shows the <code>rm.task_planning</code> package in overview form, showing the constituent packages, <code>definition</code>, <code>materialised</code>, and <code>history</code>. The first of these packages contains the class model for the <em>definition model</em> expression of a Work Plan, i.e. the workflow structure intentionally designed to achive a goal.</p>
@@ -6715,7 +6715,7 @@ <h4 id="_creating_and_tracking_an_order"><a class="anchor" href="#_creating_and_
 <p>The Dispatchable Task might be located in a repeating section of the Plan, if the intention is to await multiple Actions for the same Instruction.</p>
 </div>
 <div class="paragraph">
-<p>An example of a Work Plan representing this scenario is available in the <a href="https://specifications.openehr.org/releases/PROC/latest/tp_examples.html#_order_coordination" target="_blank" rel="noopener">Task Planning Examples</a> document.</p>
+<p>An example of a Work Plan representing this scenario is available in the <a href="https://specifications.openehr.org/releases/PROC/Release-1.5.0/tp_examples.html#_order_coordination" target="_blank" rel="noopener">Task Planning Examples</a> document.</p>
 </div>
 </div>
 <div class="sect3">

docs/tp_examples.html

@@ -88,7 +88,7 @@ <h1 id="_task_planning_examples" class="sect0"><a class="anchor" href="#_task_pl
 </thead>
 <tbody>
 <tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Release</strong>: PROC latest</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Release</strong>: PROC Release-1.5.0</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Status</strong>: TRIAL</p></td>
 </tr>
 <tr>
@@ -152,6 +152,9 @@ <h2 id="_amendment_record"><a class="anchor" href="#_amendment_record"></a>Amend
 </thead>
 <tbody>
 <tr>
+<th class="tableblock halign-center valign-top" colspan="4"><p class="tableblock"><strong>PROC Release 1.5.0</strong></p></th>
+</tr>
+<tr>
 <th class="tableblock halign-center valign-top" colspan="4"><p class="tableblock"><strong>PROC Release 1.0.0</strong></p></th>
 </tr>
 <tr>
@@ -249,10 +252,10 @@ <h3 id="_related_documents"><a class="anchor" href="#_related_documents"></a>1.2
 <div class="ulist">
 <ul>
 <li>
-<p>The <a href="https://specifications.openehr.org/releases/PROC/latest/task_planning.html" target="_blank" rel="noopener">openEHR Task Planning Model</a>;</p>
+<p>The <a href="https://specifications.openehr.org/releases/PROC/Release-1.5.0/task_planning.html" target="_blank" rel="noopener">openEHR Task Planning Model</a>;</p>
 </li>
 <li>
-<p>The <a href="https://specifications.openehr.org/releases/PROC/latest/tp_vml.html" target="_blank" rel="noopener">openEHR Task Planning Visual Modelling Language (TP-VML)</a>;</p>
+<p>The <a href="https://specifications.openehr.org/releases/PROC/Release-1.5.0/tp_vml.html" target="_blank" rel="noopener">openEHR Task Planning Visual Modelling Language (TP-VML)</a>;</p>
 </li>
 </ul>
 </div>

docs/tp_examples/master00-amendment_record.adoc

@@ -4,6 +4,8 @@
 |===
 |Issue|Details|Raiser|Completed
 
+4+^h|*PROC Release 1.5.0*
+
 4+^h|*PROC Release 1.0.0*
 
 |[[latest_issue]]0.1.1

docs/tp_vml.html

@@ -87,7 +87,7 @@ <h1 id="_task_planning_visual_modelling_language_tp_vml" class="sect0"><a class=
 </thead>
 <tbody>
 <tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Release</strong>: PROC latest</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Release</strong>: PROC Release-1.5.0</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Status</strong>: TRIAL</p></td>
 </tr>
 <tr>
@@ -151,6 +151,9 @@ <h2 id="_amendment_record"><a class="anchor" href="#_amendment_record"></a>Amend
 </thead>
 <tbody>
 <tr>
+<th class="tableblock halign-center valign-top" colspan="4"><p class="tableblock"><strong>PROC Release 1.5.0</strong></p></th>
+</tr>
+<tr>
 <th class="tableblock halign-center valign-top" colspan="4"><p class="tableblock"><strong>PROC Release 1.0.0</strong></p></th>
 </tr>
 <tr>
@@ -271,7 +274,7 @@ <h3 id="_related_documents"><a class="anchor" href="#_related_documents"></a>1.2
 <div class="ulist">
 <ul>
 <li>
-<p>The <a href="https://specifications.openehr.org/releases/PROC/latest/task_planning.html" target="_blank" rel="noopener">openEHR Task Planning Model</a>;</p>
+<p>The <a href="https://specifications.openehr.org/releases/PROC/Release-1.5.0/task_planning.html" target="_blank" rel="noopener">openEHR Task Planning Model</a>;</p>
 </li>
 </ul>
 </div>
@@ -349,7 +352,7 @@ <h3 id="_composites"><a class="anchor" href="#_composites"></a>3.1. Composites</
 <div class="sect3">
 <h4 id="_plans"><a class="anchor" href="#_plans"></a>3.1.1. Plans</h4>
 <div class="paragraph">
-<p>TP-VML icons for <code>WORK_PLAN</code> and <code>TASK_PLAN</code> are used (<a href="https://specifications.openehr.org/releases/PROC/latest/tp_vml.html#_plan_structure">TP plan structure</a>), enabling some of the relevant meta-data to be visualised.</p>
+<p>TP-VML icons for <code>WORK_PLAN</code> and <code>TASK_PLAN</code> are used (<a href="https://specifications.openehr.org/releases/PROC/Release-1.5.0/tp_vml.html#_plan_structure">TP plan structure</a>), enabling some of the relevant meta-data to be visualised.</p>
 </div>
 <div id="tp_vml_plans" class="imageblock text-center text-center">
 <div class="content">
@@ -361,7 +364,7 @@ <h4 id="_plans"><a class="anchor" href="#_plans"></a>3.1.1. Plans</h4>
 <div class="sect3">
 <h4 id="_task_groups"><a class="anchor" href="#_task_groups"></a>3.1.2. Task Groups</h4>
 <div class="paragraph">
-<p>Task Group icons and their conditional structure derivatives use two visual elements to indicate the extent of the (<a href="https://specifications.openehr.org/releases/PROC/latest/tp_vml.html#_task_group_structure">container structure</a>) they represent from the TP model.</p>
+<p>Task Group icons and their conditional structure derivatives use two visual elements to indicate the extent of the (<a href="https://specifications.openehr.org/releases/PROC/Release-1.5.0/tp_vml.html#_task_group_structure">container structure</a>) they represent from the TP model.</p>
 </div>
 <div class="paragraph">
 <p>Since Tasks and other Task Groups within any Task Group are included by ordered containment (i.e. 'list' semantics) rather than chaining, contained items are shown connected with dashed arrows, indicating the implied ordered.</p>
@@ -376,7 +379,7 @@ <h4 id="_task_groups"><a class="anchor" href="#_task_groups"></a>3.1.2. Task Gro
 <div class="sect3">
 <h4 id="_conditional_structures"><a class="anchor" href="#_conditional_structures"></a>3.1.3. Conditional Structures</h4>
 <div class="paragraph">
-<p><a href="https://specifications.openehr.org/releases/PROC/latest/tp_vml.html#_conditional_structures_2">TP conditional structures</a> follow the same structural logic as Task Groups, with the addition of various specific meta-data as per the specificaion.</p>
+<p><a href="https://specifications.openehr.org/releases/PROC/Release-1.5.0/tp_vml.html#_conditional_structures_2">TP conditional structures</a> follow the same structural logic as Task Groups, with the addition of various specific meta-data as per the specificaion.</p>
 </div>
 <div id="tp_vml_conditionals_condition" class="imageblock text-center text-center">
 <div class="content">
@@ -406,7 +409,7 @@ <h3 id="_primitives"><a class="anchor" href="#_primitives"></a>3.2. Primitives</
 <div class="sect3">
 <h4 id="_tasks"><a class="anchor" href="#_tasks"></a>3.2.1. Tasks</h4>
 <div class="paragraph">
-<p>TP-VML Tasks correspond to formal types of the form <code>TASK&lt;T&gt;</code> (<a href="https://specifications.openehr.org/releases/PROC/latest/tp_vml.html#\_definition_model">TP main model</a>; <a href="https://specifications.openehr.org/releases/PROC/latest/tp_vml.html#\_task_actions">TP Task Action types</a>), whose concrete forms are: <code>PERFORMABLE_TASK&lt;DEFINED_ACTION&gt;</code>, <code>PERFORMABLE_TASK&lt;SUB_PLAN&gt;</code>, <code>DISPATCHABLE_TASK&lt;HAND_OFF&gt;</code>, <code>DISPATCHABLE_TASK&lt;SYSTEM_REQUEST&gt;</code>, <code>DISPATCHABLE_TASK&lt;EXTERNAL_REQUEST&gt;</code>.</p>
+<p>TP-VML Tasks correspond to formal types of the form <code>TASK&lt;T&gt;</code> (<a href="https://specifications.openehr.org/releases/PROC/Release-1.5.0/tp_vml.html#\_definition_model">TP main model</a>; <a href="https://specifications.openehr.org/releases/PROC/Release-1.5.0/tp_vml.html#\_task_actions">TP Task Action types</a>), whose concrete forms are: <code>PERFORMABLE_TASK&lt;DEFINED_ACTION&gt;</code>, <code>PERFORMABLE_TASK&lt;SUB_PLAN&gt;</code>, <code>DISPATCHABLE_TASK&lt;HAND_OFF&gt;</code>, <code>DISPATCHABLE_TASK&lt;SYSTEM_REQUEST&gt;</code>, <code>DISPATCHABLE_TASK&lt;EXTERNAL_REQUEST&gt;</code>.</p>
 </div>
 <div class="paragraph">
 <p>Performable Tasks may have one or more associated <code><em>capture_datasets</em></code>. Dispatchable Tasks may have an associated callback wait state (<code>CALLBACK_WAIT</code>).</p>
@@ -421,7 +424,7 @@ <h4 id="_tasks"><a class="anchor" href="#_tasks"></a>3.2.1. Tasks</h4>
 <div class="sect3">
 <h4 id="_events"><a class="anchor" href="#_events"></a>3.2.2. Events</h4>
 <div class="paragraph">
-<p>TP-VML Events are defined in the <a href="https://specifications.openehr.org/releases/PROC/latest/tp_vml.html#_events">Events section in the TP specification</a> and can be visually represented in three forms:</p>
+<p>TP-VML Events are defined in the <a href="https://specifications.openehr.org/releases/PROC/Release-1.5.0/tp_vml.html#_events">Events section in the TP specification</a> and can be visually represented in three forms:</p>
 </div>
 <div class="ulist">
 <ul>

docs/tp_vml/master00-amendment_record.adoc

@@ -4,6 +4,8 @@
 |===
 |Issue|Details|Raiser|Completed
 
+4+^h|*PROC Release 1.5.0*
+
 4+^h|*PROC Release 1.0.0*
 
 |[[latest_issue]]0.6.0