Skip to content

Commit 610009e

Browse files
douglmdouglm
committed
Update generated files
1 parent f2ed35a commit 610009e

File tree

5 files changed

+3353
-1534
lines changed

5 files changed

+3353
-1534
lines changed

‎generated/draft-ietf-calext-ical-tasks.err.html‎

Lines changed: 21 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,9 @@
88
.severity3 { font-style: italic; color: grey; }
99
</style>
1010
</head><body><h1>sources/draft-ietf-calext-ical-tasks.err.html errors</h1>
11-
<ul><li><p><b><a href="#Relaton">Relaton</a></b>: Severity 3: <b>17</b> errors</p></li>
11+
<ul><li><p><b><a href="#Relaton">Relaton</a></b>: Severity 3: <b>4</b> errors</p></li>
1212

13-
<li><p><b><a href="#Style">Style</a></b>: Severity 2: <b>4</b> errors</p></li>
13+
<li><p><b><a href="#Style">Style</a></b>: Severity 2: <b>5</b> errors</p></li>
1414

1515
<li><p><b><a href="#Document_Attributes">Document Attributes</a></b>: Severity 1: <b>1</b> errors</p></li>
1616

@@ -22,50 +22,11 @@ <h2 id="Relaton">Relaton</h2>
2222
<th width="30%">Message</th><th width="40%">Context</th><th width="5%">Severity</th></thead>
2323
<tbody>
2424
<tr class="severity3">
25-
<td></td><th><code>--</code></th>
26-
<td>Downloaded index from <code>https://​raw.​githubusercontent.com/​relaton/​relaton-data-rfcs/​main/index-v1.zip</code></td><td><pre></pre></td><td>3</td></tr>
27-
<tr class="severity3">
28-
<td></td><th><code>--</code></th>
29-
<td>cache /home/​mike/snap/​metanorma/​231/.relaton/​cache/​ietf/: version is obsolete and cache is cleared.</td><td><pre></pre></td><td>3</td></tr>
30-
<tr class="severity3">
31-
<td></td><th><code>--</code></th>
32-
<td>cache /home/​mike/snap/​metanorma/​231/.relaton/​cache/omg/​: version is obsolete and cache is cleared.</td><td><pre></pre></td><td>3</td></tr>
33-
<tr class="severity3">
3425
<td></td><th><code>(Cal­Connect Task Architecture V1.0</code></th>
3526
<td><code>(Cal­Connect Task Architecture V1.0</code> does not have a recognised prefix</td><td><pre></pre></td><td>3</td></tr>
3627
<tr class="severity3">
3728
<td></td><th><code>IETF draft-ietf-calext-subscription-upgrade</code></th>
38-
<td>Not found.</td><td><pre></pre></td><td>3</td></tr>
39-
<tr class="severity3">
40-
<td></td><th><code>OMG BPMN 2.0.2</code></th>
41-
<td>Found: <code>OMG BPMN 2.0.2</code></td><td><pre></pre></td><td>3</td></tr>
42-
<tr class="severity3">
43-
<td></td><th><code>RFC 2119</code></th>
44-
<td>Found: <code>RFC 2119</code></td><td><pre></pre></td><td>3</td></tr>
45-
<tr class="severity3">
46-
<td></td><th><code>RFC 4791</code></th>
47-
<td>Found: <code>RFC 4791</code></td><td><pre></pre></td><td>3</td></tr>
48-
<tr class="severity3">
49-
<td></td><th><code>RFC 4918</code></th>
50-
<td>Found: <code>RFC 4918</code></td><td><pre></pre></td><td>3</td></tr>
51-
<tr class="severity3">
52-
<td></td><th><code>RFC 5545</code></th>
53-
<td>Found: <code>RFC 5545</code></td><td><pre></pre></td><td>3</td></tr>
54-
<tr class="severity3">
55-
<td></td><th><code>RFC 5546</code></th>
56-
<td>Found: <code>RFC 5546</code></td><td><pre></pre></td><td>3</td></tr>
57-
<tr class="severity3">
58-
<td></td><th><code>RFC 8174</code></th>
59-
<td>Found: <code>RFC 8174</code></td><td><pre></pre></td><td>3</td></tr>
60-
<tr class="severity3">
61-
<td></td><th><code>RFC 9073</code></th>
62-
<td>Found: <code>RFC 9073</code></td><td><pre></pre></td><td>3</td></tr>
63-
<tr class="severity3">
64-
<td></td><th><code>RFC 9074</code></th>
65-
<td>Found: <code>RFC 9074</code></td><td><pre></pre></td><td>3</td></tr>
66-
<tr class="severity3">
67-
<td></td><th><code>RFC 9253</code></th>
68-
<td>Found: <code>RFC 9253</code></td><td><pre></pre></td><td>3</td></tr>
29+
<td>not found in cache, if you wish to ignore cache please use <code>no-cache</code> option.</td><td><pre></pre></td><td>3</td></tr>
6930
<tr class="severity3">
7031
<td></td><th><code>RFC5545</code></th>
7132
<td><code>RFC5545</code> does not have a recognised prefix</td><td><pre></pre></td><td>3</td></tr>
@@ -79,31 +40,38 @@ <h2 id="Style">Style</h2>
7940
<th width="30%">Message</th><th width="40%">Context</th><th width="5%">Severity</th></thead>
8041
<tbody>
8142
<tr class="severity2">
82-
<td>000035</td><th><code><a href='sources/draft-ietf-calext-ical-tasks.html#_introduction'>_​introduction</a></code></th>
43+
<td>000036</td><th><code><a href='sources/draft-ietf-calext-ical-tasks.html#_introduction'>_​introduction</a></code></th>
8344
<td>Hanging paragraph in clause</td><td><pre>&lt;clause id=&quot;_introduction&quot; inline-header=&quot;false&quot; obligation=&quot;normative&quot;&gt;
8445
&lt;title&gt;Introduction&lt;/title&gt;
85-
&lt;p id=&quot;_99b259c5-536b-2212-29fb-dfa205a6eb6b&quot;&gt;This document specifies extensions to the existing Internet Calendaring and Scheduling Core Object Specification (iCalendar) &lt;eref type=&quot;inline&quot; bibitemid=&quot;RFC5545&quot; citeas=&quot;RFC 5545&quot;/&gt;, and associated protocols, in order to enhance the structured communication and execution of tasks. The enhancements allow for the communication, time planning and scheduling of tasks by and between automated systems (e.g. in smart power grids, business process management systems) as well as for human centered tasks.&lt;/p&gt;
46+
&lt;p id=&quot;_b5b55fe9-a51e-3cd8-50e2-eaf01dbf8858&quot;&gt;This document specifies extensions to the existing Internet Calendaring and Scheduling Core Object Specification (iCalendar) &lt;eref type=&quot;inline&quot; bibitemid=&quot;RFC5545&quot; citeas=&quot;RFC 5545&quot;/&gt;, and associated protocols, in order to enhance the structured communication and execution of tasks. The enhancements allow for the communication, time planning and scheduling of tasks by and between automated systems (e.g. taxi dispatch systems, in smart power grids, business process management systems) as well as for human centered tasks.&lt;/p&gt;
47+
48+
&lt;p id=&quot;_661d834c-cd2d-1845-81bd-5378fdcb0bee&quot;&gt;A &quot;task&quot; is a representation of an item of work assigned to an individual or organization. In the iCalendar Object Model &lt;eref type=&quot;inline&quot; bibitemid=&quot;RFC5545&quot; citeas=&quot;RFC 5545&quot;/&gt; the representation of tasks is by &quot;VTODO&quot; calendar components. Tasks can be identified in a number of situations, either informally as ad-hoc tasks in personal &quot;to-do&quot; lists or more formally in: Business processes - ranging from repetitive workflows to adaptive cases and trouble ticketing Project Management - whether for large scale construction projects or collaborative software development&lt;/p&gt;</pre></td><td>2</td></tr>
49+
<tr class="severity2">
50+
<td>000149</td><th><code><a href='sources/draft-ietf-calext-ical-tasks.html#architecture'>architecture</a></code></th>
51+
<td>Hanging paragraph in clause</td><td><pre>&lt;clause id=&quot;architecture&quot; inline-header=&quot;false&quot; obligation=&quot;normative&quot;&gt;
52+
&lt;title&gt;Task Architecture&lt;/title&gt;
53+
&lt;p id=&quot;_e0825f67-031d-113a-47fe-0ab1991127f0&quot;&gt;A reference architecture for task calendaring and scheduling is defined in order to identify the key logical elements involved in task management and the interfaces between them to enable interoperability. Central to this architecture is the Calendar and Scheduling System. The logical elements identified here establish an appropriate separation of concerns and clarify the responsibilities of different elements. However, the architecture does not prescribe a binding or packaging of elements, i.e., software systems may be developed where some elements are tightly bound and the interfaces between bound elements are not exposed. The task architecture is also described in &lt;eref type=&quot;inline&quot; bibitemid=&quot;TARCH&quot; citeas=&quot;(CalConnect Task Architecture V1.0&quot;/&gt;.&lt;/p&gt;
8654

87-
&lt;p id=&quot;_baa80340-ea14-cdb7-ec37-8a9dad6e962b&quot;&gt;A &quot;task&quot; is a representation of an item of work assigned to an individual or organization. In the iCalendar Object Model &lt;eref type=&quot;inline&quot; bibitemid=&quot;RFC5545&quot; citeas=&quot;RFC 5545&quot;/&gt; the representation of tasks is by &quot;VTODO&quot; calendar components. Tasks can be identified in a number of situations, either informally as ad-hoc tasks in personal &quot;to-do&quot; lists or more formally in:&lt;/p&gt;</pre></td><td>2</td></tr>
55+
&lt;figure id=&quot;_2bad07e9-7d07-cbdb-fa76-b5ac14dacdcd&quot;&gt;</pre></td><td>2</td></tr>
8856
<tr class="severity2">
89-
<td>000298</td><th><code><a href='sources/draft-ietf-calext-ical-tasks.html#task-specification'>task-specification</a></code></th>
57+
<td>000316</td><th><code><a href='sources/draft-ietf-calext-ical-tasks.html#task-specification'>task-specification</a></code></th>
9058
<td>Hanging paragraph in clause</td><td><pre>&lt;clause id=&quot;task-specification&quot; inline-header=&quot;false&quot; obligation=&quot;normative&quot;&gt;
9159
&lt;title&gt;Task Specification&lt;/title&gt;
92-
&lt;p id=&quot;_7d34a8cb-accd-1ac9-f182-d621a228c1fe&quot;&gt;The specification of tasks must be semantically explicit in order for them to be managed within the context of a business process or project, and be understood by both humans and IT systems. The &lt;eref type=&quot;inline&quot; bibitemid=&quot;RFC5545&quot; citeas=&quot;RFC 5545&quot;/&gt; &quot;VTODO&quot; calendar component only provides for simple ad-hoc tasks or &apos;to do&apos; lists, and is therefore extended by this specification as follows:&lt;/p&gt;
60+
&lt;p id=&quot;_249d4f62-a5fc-653e-9b05-4b74eeeee5ad&quot;&gt;The specification of tasks must be semantically explicit in order for them to be managed within the context of a business process or project, and be understood by both humans and IT systems. The &lt;eref type=&quot;inline&quot; bibitemid=&quot;RFC5545&quot; citeas=&quot;RFC 5545&quot;/&gt; &quot;VTODO&quot; calendar component only provides for simple ad-hoc tasks or &apos;to do&apos; lists, and is therefore extended by this specification as follows:&lt;/p&gt;
9361

94-
&lt;dl id=&quot;_de073d3c-5264-38a0-44f9-1a435528b1cc&quot;&gt; &lt;dt&gt;Task type&lt;/dt&gt;</pre></td><td>2</td></tr>
62+
&lt;dl id=&quot;_b9bfc80d-f4e6-beaf-872c-4f7b061cf496&quot;&gt; &lt;dt&gt;Task type&lt;/dt&gt;</pre></td><td>2</td></tr>
9563
<tr class="severity2">
96-
<td>001028</td><th><code><a href='sources/draft-ietf-calext-ical-tasks.html#caldav-support'>caldav-support</a></code></th>
64+
<td>001044</td><th><code><a href='sources/draft-ietf-calext-ical-tasks.html#caldav-support'>caldav-support</a></code></th>
9765
<td>Hanging paragraph in clause</td><td><pre>&lt;clause id=&quot;caldav-support&quot; inline-header=&quot;false&quot; obligation=&quot;normative&quot;&gt;
9866
&lt;title&gt;CalDAV Support for Task Mode&lt;/title&gt;
99-
&lt;p id=&quot;_af710561-e720-81cb-9069-2c2e67257f6c&quot;&gt;The CalDAV &lt;eref type=&quot;inline&quot; bibitemid=&quot;RFC4791&quot; citeas=&quot;RFC 4791&quot;/&gt; calendar access protocol allows clients and servers to exchange iCalendar data. With the introduction of the &quot;TASK-MODE&quot; property in this specification, different automated task management behaviours may be delegated to the server by the Task Organizer depending upon the value of &quot;TASK-MODE&quot;.&lt;/p&gt;
67+
&lt;p id=&quot;_5e249cbf-b084-7f8b-7a5f-a16d5e7267e1&quot;&gt;The CalDAV &lt;eref type=&quot;inline&quot; bibitemid=&quot;RFC4791&quot; citeas=&quot;RFC 4791&quot;/&gt; calendar access protocol allows clients and servers to exchange iCalendar data. With the introduction of the &quot;TASK-MODE&quot; property in this specification, different automated task management behaviours may be delegated to the server by the Task Organizer depending upon the value of &quot;TASK-MODE&quot;.&lt;/p&gt;
10068

101-
&lt;p id=&quot;_81045c8e-8478-2d32-05fd-a1e8e2d64741&quot;&gt;In order for a CalDAV client to know what task modes are available, a CalDAV server advertises a CALDAV:supported-task-mode-set WebDAV property on calendar home or calendar collections if it supports the use of the &quot;TASK-MODE&quot; property as described in this specification. The server can advertise a specific set of supported task modes by including one or more CALDAV:supported-task-mode XML elements within the CALDAV:supported-task-mode-set XML element. If no CALDAV:supported-task-mode XML elements are included in the WebDAV property, then clients can try any task mode, but need to be prepared for a failure when attempting to store the calendar data.&lt;/p&gt;</pre></td><td>2</td></tr>
69+
&lt;p id=&quot;_a99e3c6f-a9f1-9dd3-9326-7b19ab1e9f68&quot;&gt;In order for a CalDAV client to know what task modes are available, a CalDAV server advertises a CALDAV:supported-task-mode-set WebDAV property on calendar home or calendar collections if it supports the use of the &quot;TASK-MODE&quot; property as described in this specification. The server can advertise a specific set of supported task modes by including one or more CALDAV:supported-task-mode XML elements within the CALDAV:supported-task-mode-set XML element.&lt;/p&gt;</pre></td><td>2</td></tr>
10270
<tr class="severity2">
103-
<td>001086</td><th><code><a href='sources/draft-ietf-calext-ical-tasks.html#_new_and_updated_icalendar_elements_registration'>_new_and_​updated_​icalendar_​elements_​registration</a></code></th>
71+
<td>001106</td><th><code><a href='sources/draft-ietf-calext-ical-tasks.html#_new_and_updated_icalendar_elements_registration'>_new_and_​updated_​icalendar_​elements_​registration</a></code></th>
10472
<td>Hanging paragraph in clause</td><td><pre>&lt;clause id=&quot;_new_and_updated_icalendar_elements_registration&quot; inline-header=&quot;false&quot; obligation=&quot;normative&quot;&gt;
10573
&lt;title&gt;New and updated iCalendar Elements Registration&lt;/title&gt;
106-
&lt;p id=&quot;_3d34ed84-e14c-860f-bc92-b8331536a1ff&quot;&gt;This specification updates &lt;eref type=&quot;inline&quot; bibitemid=&quot;RFC5545&quot; citeas=&quot;RFC 5545&quot;/&gt; by adding and updating a number of elements according to the procedures and templates specified in &lt;eref type=&quot;inline&quot; bibitemid=&quot;RFC5545&quot; citeas=&quot;RFC 5545&quot;&gt; &lt;localityStack&gt; &lt;locality type=&quot;section&quot;&gt; &lt;referenceFrom&gt;8.2&lt;/referenceFrom&gt; &lt;/locality&gt; &lt;/localityStack&gt; &lt;/eref&gt;.&lt;/p&gt;
74+
&lt;p id=&quot;_8cff9d3c-52f3-961b-6812-ea92760acc44&quot;&gt;This specification updates &lt;eref type=&quot;inline&quot; bibitemid=&quot;RFC5545&quot; citeas=&quot;RFC 5545&quot;/&gt; by adding and updating a number of elements according to the procedures and templates specified in &lt;eref type=&quot;inline&quot; bibitemid=&quot;RFC5545&quot; citeas=&quot;RFC 5545&quot;&gt; &lt;localityStack&gt; &lt;locality type=&quot;section&quot;&gt; &lt;referenceFrom&gt;8.2&lt;/referenceFrom&gt; &lt;/locality&gt; &lt;/localityStack&gt; &lt;/eref&gt;.&lt;/p&gt;
10775

10876
&lt;clause id=&quot;_update_of_the_status_registry&quot; inline-header=&quot;false&quot; obligation=&quot;normative&quot;&gt;</pre></td><td>2</td></tr>
10977
</tbody></table>

0 commit comments

Comments
 (0)