-
Notifications
You must be signed in to change notification settings - Fork 0
/
OMA-Template-ORG.html
434 lines (381 loc) · 12.9 KB
/
OMA-Template-ORG.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
<!DOCTYPE html>
<html>
<head>
<title>OMA [FunctionalName] Technical Specification</title>
<meta charset="UTF-8">
<script src="http://openmobilealliance.github.io/Tools/builds/respec-oma-common.js"
async class="remove">
</script>
<script class="remove">
var respecConfig = {
// for editor use
docType: "TS", // options are BASE, RD, AD, TS, SUP, ETS, ORG
subtitle: "File_Name",
shortName: "shortName",
otherLinks: [{
key: "Other Link",
data: [{
value: "Link Name",
href: "#location"
}]
}],
editors: [{
name: "Editor Name",
url: "http://example.com/",
company: "Editor Company",
companyURL: "http://example.org/",
mailto: "[email protected]",
note: "editor note"
}],
authors: [{
name: "Author Name",
url: "http://example.com/",
company: "Author Company",
companyURL: "http://example.org/",
mailto: "[email protected]",
note: "author note"
}],
interactiveLinks: [{
name: "Link Name",
description: "Link Description",
uri: "http://example.com/",
},{
name: "Second Link Name",
description: "Second Link Description",
uri: "http://example2.com/",
}],
// for staff only
specStatus: "DRAFT", // options are Draft, Candidate, Approved, Historic
publishDate: ""
};
</script>
</head>
<body>
<!-- table of content & table of figures -->
<section id="toc"></section>
<section id="tof"></section>
<section id="tot"></section>
<!-- start scope -->
<section>
<h2>Scope</h2>
<aside class="example">
<p>Define as it relates to Open Mobile Alliance Activity. If it adds clarity,
define what is not in the scope.</p>
<strong>DELETE THIS COMMENT.</strong>
</aside>
</section>
<!-- end scope -->
<!-- start terminology and conventions -->
<section>
<h2>Terminology and Conventions</h2>
<!-- start conventions -->
<section>
<h2>Conventions</h2>
<p>The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”,
“MAY”, and “OPTIONAL” in this document are to be interpreted as described in [[!RFC2119]].</p>
<p>All sections and appendixes, except “Scope” and “Introduction”, are normative, unless they are explicitly
indicated to be informative.</p>
</section>
<!-- end conventions -->
<!-- start definitions -->
<section>
<h2>Definitions</h2>
<dl>
<dt><dfn>Definition Title 1</dfn></dt>
<dd>Defintion Data 1 (description).</dd>
</dl>
<dl>
<dt><dfn>Definition Title 2</dfn></dt>
<dd>Defintion Data 2 (description).</dd>
</dl>
<p>Kindly consult [[OMADICT]] for more definitions used in this document.</p>
</section>
<!-- end definitions -->
<!-- start abbreviations -->
<section>
<h2>Abbreviations</h2>
<dl>
<dt><abbr title="Title Abbreviation 1">Abbreviation 1</abbr></dt>
<dd>Definition Data for Abbreviation 1.</dd>
</dl>
<dl>
<dt><abbr title="Title Abbreviation 2">Abbreviation 2</abbr></dt>
<dd>Definition Data for Abbreviation 2.</dd>
</dl>
<p>Kindly consult [[OMADICT]] for more abbreviations used in this document.</p>
</section>
<!-- end abbreviations -->
</section>
<!-- /end terminology and conventions -->
<!-- start introduction -->
<section class="informative">
<h2>Introduction</h2>
<aside class="example">
<p>From a market perspective... </p>
<ul>
<li>What can you do with this specification?</li>
<li>What problem does this solve?</li>
<li>How can this specification be applied?</li>
<li>Consider the target audience and provide deployment examples as possible.</li>
</ul>
<strong> TO BE DELETED. </strong>
</aside>
<!-- start version 1.0 -->
<section>
<h2>Version 1.0</h2>
<aside class="example">
<p>This section provides a high level, concise and informative description of the main functionality
supported in the initial version of the specification.</p>
<p>The description should be brief, target length
should be a few paragraphs. When the enabler or reference release is finished, this description
should be aligned with the final functionality.</p>
<strong>DELETE THIS COMMENT.</strong>
</aside>
</section>
<!-- end Version 1.0-->
<!-- start Version x.y -->
<section>
<h2>Version x.y</h2>
<aside class="example">
<p>This section should be included for each new major or minor version of the specifications.
It should provide a high level, concise and informative description of the <strong>new or modified
functionaliy</strong> introduced in this version of the specification, compared to the previous version.</p>
<p>The description should be brief, target lenght should be a few paragraphs.
When the enabler or reference release is finished, this description should be aligned with the final
functionality differences.</p>
<strong>DELETE THIS COMMENT.</strong>
</aside>
</section>
<!-- end Version x.y -->
<!-- start Version x.y.z -->
<section>
<h2>Version x.y.z</h2>
<aside class="example">
<p>This section should be included for each new service release of the specification.</p>
<p>It should describe at at high level the main changes made to the specification compared to
the previous version. The description should be brief, target lenght should be one paragraph.</p>
<strong>DELETE THIS COMMENT</strong>
</aside>
</section>
<!-- end Version x.y.z -->
</section>
<!-- end introduction -->
<!-- start sections as needed -->
<section>
<h2>Sections As Needed</h2>
<aside class="example">
<p>Sections for the normative specification text. Fill in as needed.</p>
<p>The following validates the styles used for the headers.</p>
<strong>DELETE THIS COMMENT.</strong>
</aside>
<!-- start Example Level 2 -->
<section>
<h2>Example Level 2</h2>
<aside class="example">
<p>Sections for the normative specification text. Fill in as needed.</p>
<p>The following validates the styles used for the headers.</p>
<strong>DELETE THIS COMMENT.</strong>
</aside>
<!-- start Example Level 3 -->
<section>
<h2>Example Level 3</h2>
<aside class="example">
<p>Sections for the normative specification text. Fill in as needed.</p>
<p>The following validates the styles used for the headers.</p>
<strong>DELETE THIS COMMENT.</strong>
</aside>
<!-- start Example Level 4 -->
<!-- start example level 4 -->
<section>
<h2>Example Level 4</h2>
<aside class="example">
<p>Sections for the normative specification text. Fill in as needed.</p>
<p>The following validates the styles used for the headers.</p>
<strong>DELETE THIS COMMENT.</strong>
</aside>
<figure id="fig1_example">
<img src="images/fig1_example.png" />
<figcaption>Example Figure</figcaption>
</figure>
<!-- start example table -->
<table>
<caption> Example Table</caption>
<thead>
<tr>
<td> </td>
<td>Column1</td>
<td>Column2</td>
</tr>
</thead>
<tbody>
<tr>
<td>Row1</td>
<td>Grid 1,1 data</td>
<td>Grid 1,2 data</td>
</tr>
<tr>
<td>Row2</td>
<td>Grid 2,1 data</td>
<td>Grid 2,2 data</td>
</tr>
</tbody>
</table>
<!-- end example table -->
</section>
<!-- end Example Level 4 -->
</section>
<!-- end Start Example Level 3 -->
</section>
<!-- end Start Example Level 2 -->
</section>
<!-- end sections as needed -->
<!-- start another section -->
<section>
<h2>Another Section</h2>
<aside class="example">
<p>Sections for the normative specification text. Fill in as needed.</p>
<p>The following validates the styles used for the headers.</p>
<strong>DELETE THIS COMMENT.</strong>
</aside>
<!-- start Another Sub-section -->
<section>
<h2>Another Sub-section</h2>
<aside class="example">
<p>More text goes here ...</p>
<strong>DELETE THIS COMMENT</strong>
</aside>
</section>
<!-- end Another Sub-section -->
</section>
<!-- end another section -->
<!-- start scr requirements -->
<section class="appendix">
<h2>Static Conformance Requirements (Normative)</h2>
<p>The notation used in this appendix is specified in [SCRRULES].</p>
<aside class="example">
<p>The following is a model of a set of SCR tables.</p>
<strong>DELETE THIS COMMENT.</strong>
</aside>
<!-- start scr for xyz client -->
<section>
<h2>SCR for XYZ Client</h2>
<table>
<caption> SCR for XYZ Client</caption>
<thead>
<tr>
<td>Item</td>
<td>Function</td>
<td>Reference</td>
<td>Requirement</td>
</tr>
</thead>
<tbody>
<tr>
<td>XYZ-C-001-M</td>
<td>Something mandatory</td>
<td>Section x.y</td>
<td>(XYZ-C-004-O OR XYZ-C-003-M) AND XYZ-C-002-O</td>
</tr>
<tr>
<td>XYZ-C-002-O</td>
<td>Something optional</td>
<td>Section x.y</td>
<td> </td>
</tr>
<tr>
<td>XYZ-C-003-M</td>
<td>Dependencies on ZYX</td>
<td>Section x.y</td>
<td>ZYX:MCF</td>
</tr>
<tr>
<td>XYZ-C-004-O</td>
<td>Dependencies on ZYX</td>
<td>Section x.y</td>
<td>ZYX:MCF</td>
</tr>
</tbody>
</table>
</section>
<!-- end scr for xyz client -->
<!-- start scr for xyz server -->
<section>
<h2>SCR for XYZ Server</h2>
<table>
<caption> SCR for XYZ Server</caption>
<thead>
<tr>
<td>Item</td>
<td>Function</td>
<td>Reference</td>
<td>Requirement</td>
</tr>
</thead>
<tbody>
<tr>
<td>XYZ-S-001-M</td>
<td>Something mandatory</td>
<td>Section x.y</td>
<td>(XYZ-S-004-O OR XYZ-S-003-M) AND XYZ-S-002-O</td>
</tr>
<tr>
<td>XYZ-S-002-O</td>
<td>Something optional</td>
<td>Section x.y</td>
<td> </td>
</tr>
<tr>
<td>XYZ-S-003-M</td>
<td>Dependencies on ZYX</td>
<td>Section x.y</td>
<td>ZYX:MSF</td>
</tr>
<tr>
<td>XYZ-S-004-O</td>
<td>Dependencies on ZYX</td>
<td>Section x.y</td>
<td>ZYX:OSF</td>
</tr>
</tbody>
</table>
</section>
<!-- end scr for xyz server -->
</section>
<!-- end scr requirements -->
<!-- start additional appendix -->
<!-- note that there is no need for appendix class -->
<section>
<h2> Additional Appendix</h2>
<aside class="example">
<p>If needed, add annex to provide additional information to support the document.</p>
<p>In general, this information should be informative, as normative material should be contained in
the primary body of the document.</p>
<p>Note that the styles for the headers in the appendix (App1, App2, App3) are different than the main body.
The use below is intended to validate the styles to be used. Remove if not needed.</p>
<strong>DELETE THIS COMMENT.</strong>
</aside>
<!-- start App Headers -->
<section>
<h2>App Headers</h2>
<p> Text goes here.</p>
<!-- start More Headers -->
<section>
<h2>More Headers</h2>
<p> More text goes here.</p>
<!-- start Even More Headers -->
<section>
<h2>Even More Header</h2>
<p> More text goes here.</p>
</section>
<!-- end Even More Headers -->
</section>
<!-- end More Headers -->
</section>
<!-- end App Headers -->
</section>
<!-- end additional appendix -->
<aside class="example">
<p>Text goes here.</p>
</aside>
</body>
</html>