-
Notifications
You must be signed in to change notification settings - Fork 6
/
04_01_bibliography.html
766 lines (706 loc) · 34.5 KB
/
04_01_bibliography.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
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
---
layout: rawpage
title: Declarative Markup: An Annotated Bibliography
permalink: /resources/bibliography
date: 2018-09-18
---
<!DOCTYPE html>
<html>
<head>
<title>Declarative Markup: An Annotated Bibliography</title>
<meta charset="utf-8" />
<meta name="date" content="2018-09-17" />
<meta name="title" content="Declarative Markup: An Annotated Bibliography"/>
<meta name="description"
content="A list of resources about and related to declarative markup" />
<meta name="keywords"
content="declarative markup, generic markup, descriptive markup, XML, SGML"/>
<style type="text/css">
.annotation
{
margin-left: 25px;
background: #E8E8E8;
padding: 5px;
max-height: 50px;
overflow-y: scroll;
}
.annotation p
{
margin-top: 0;
}
.annotation:hover
{
margin-left: 25px;
background: #E8E8E8;
padding: 5px;
max-height: 600px;
overflow-y: scroll;
}
.annotation:hover p
{
margin-top: 1em;
}
.annotation:focus
{
margin-left: 25px;
background: #E8E8E8;
padding: 5px;
max-height: 600px;
overflow-y: scroll;
}
.annotation:focus p
{
margin-top: 1em;
}
.ref-location
{
margin-left: 25px;
border-left: 1px;
margin-top: 0px
}
section
{
margin-left: 25px;
}
section h1
{
border-top: 2px solid #aaaaaa;
padding-top: 0.5em;
margin-left: -25px;
}
.sig
{
text-align: right;
}
.toc
{
}
.toc h3
{
margin-bottom: 0.5em;
}
.toc ul
{
margin-top: 0;
}
</style>
</head>
<body>
<p>This list<label for="mn-contribute"
class="margin-toggle">⊕</label>
<input type="checkbox" id="mn-contribute" class="margin-toggle"/>
<span class="marginnote">Do you know of a declarative markup resource
that’s missing from this list? Do you have an annotation to add?
The bibliography is a community effort,
please contribute!
Details <a href="#contribute">below</a>.</span>
of works about declarative markup is, as all such lists
must be, incomplete and based on the opinions of the contributors.
The intent is to make available the widely scattered literature on
the philosophy of markup that has been variously called “generic
markup”, “descriptive markup”, and “declarative markup”. Works that
have sections that are about declarative markup are within scope for
this list, especially if annotated to point to the portion of the
document that is <b>about</b> declarative markup per se. Works that
are about particular declarative markup languages, declarative
programming, XML, CSS, or any of hundreds of related concepts but
that do not directly address <strong>declarative markup</strong>
should be in the “Related Concepts” appendix of this bibliography,
not in the body of the document.</p>
<p>Annotations on this list are used to describe the work, point to
portions of a work that are particularly relevant to declarative
markup, and provide the annotator’s opinion on the work. All
annotations should be signed by the annotator. We ask that if you
disagree with an annotation you write an additional annotation with
your point of view; do not edit, remove, or replace some else’s
annotation.</p>
<aside class="toc">
<h3>Table of Contents</h3>
<ul>
<li><a href="#declmarkup">About Declarative Markup <i>per se</i></a></li>
<li><a href="#markupuses">Declarative Markup Uses</a></li>
<li><a href="#collections">Other Collections of Markup-related Materials</a></li>
<li><a href="#related">Related Concepts</a></li>
<li><a href="#contribute">How to contribute</a></li>
</ul>
</aside>
<section id="declmarkup">
<h1>About Declarative Markup <i>per se</i></h1>
<div class="bib-entry">
<h2 class="sort-name">Clark</h2>
<h3 class="ref-title">“Content Management and the Separation of Presentation and Content.” by David P. Clark</h3>
<p class="ref-location">
Clark, David P. “Content Management and
the Separation of Presentation and Content.” Technical
Communication Quarterly 17.1. (2008): 35-60.
<a href="https://www.tandfonline.com/doi/abs/10.1080/10572250701588624">https://www.tandfonline.com/doi/abs/10.1080/10572250701588624</a>
</p>
<div class="annotation">
<p>The importance of separating presentation from content is
taken as a given in many kinds of publishing, despite the fact
that the notion of separation has received little critical
scrutiny. I provide a closer look at the separation, first by
providing contemporary and historical context, then by laying
out key distinctions in the ways the separation argument is
used in Web design versus Web content management versus
full-featured content management systems (CMSs). I suggest
that these distinctions are critical in how we should view the
separation and the implications of the separation for the work
of technical communicators.</p>
<p class="sig">annotation source: publisher’s abstract</p>
</div>
</div>
<div class="bib-entry" id="HORSE1">
<h2 class="sort-name">DeRose</h2>
<h3 class="ref-title">“Markup Overlap: A Review and a Horse” by Steven DeRose</h3>
<p class="ref-location">
<a href="http://conferences.idealliance.org/extreme/html/2004/DeRose01/EML2004DeRose01.html"
>http://conferences.idealliance.org/extreme/html/2004/DeRose01/EML2004DeRose01.html</a>
</p>
<div class="annotation">
<p>This oft-cited paper is both a review of various solutions
to the overlap problem, and a recommendation of yet another
solution called HORSE. This solution, a clever style of typed
segment-boundary delimiter (see <a href="Overlap01">TEI
MLW18</a>) has become a particularly popular method for
handling overlap. It was even recommended to the TEI-C by the
Special Interest Group on Overlap. See also my <a
href="#HORSE2">response</a> to this paper.</p>
<p class="sig">annotated by: Syd Bauman</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Fennell</h2>
<h3 class="ref-title">“Are we losing the declarative Web?” by Philip Fennell</h3>
<p class="ref-location">
<a href="http://archive.li/q92S5" title="Are we losing the declarative Web? - O’Reilly Community">http://archive.li/q92S5</a>
</p>
<div class="annotation">
<p>“I’m an unashamed fan of the XML stack and because of it, the declarative
web too.”</p>
<p class="sig">annotation source: quote from the document</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Fennell</h2>
<h3 class="ref-title">“Extremes of XML” by Philip Fennell</h3>
<p class="ref-location">
Conference proceedings, XML London 2013.
<a href="https://xmllondon.com/2013/xmllondon-2013-proceedings.pdf#page=80" title="Extremes of XML - conference proceedings, XML London 2013">https://xmllondon.com/2013/xmllondon-2013-proceedings.pdf#page=80</a>
</p>
<div class="annotation">
<p>“The Extensible Markup Language (XML) is a meta language, it is used
to describe other languages and as such it has been phenomenally
successful, it has been drawn into just about every information
domain imaginable, not to mention some you really can’t… When
looking at the extremes of XML, what I find fascinating is not how
much or how fast but the breadth of applications to which XML has
been applied, and this is what one could call the ‘XML Envelope’.”</p>
<p class="sig">annotation source: quote from the document</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Gennusa</h2>
<h3 class="ref-title">“Evolution and use of generic markup languages” by P. L. Gennusa</h3>
<p class="ref-location">
Gennusa P.L. (1999) Evolution and use of generic markup languages. In: Möhr
W., Schmidt I. (eds) SGML und XML. Springer, Berlin, Heidelberg
<a href="https://link.springer.com/chapter/10.1007/978-3-642-46881-0_2"
>https://link.springer.com/chapter/10.1007/978-3-642-46881-0_2</a>
</p>
<div class="annotation">
<p>A chapter in a book on SGML and XML. Most of the book is in German, this
chapter and one other are in English.</p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Horton</h2>
<h3 class="ref-title">“Separate content and presentation” by Sarah Horton</h3>
<p class="ref-location">
<a href="http://universalusability.com/access_by_design/document_structure/separate.html"
>http://universalusability.com/access_by_design/document_structure/separate.html</a>
</p>
<div class="annotation">
<p>“The Web is a medium designed to remove access
requirements and to make content accessible to all. … The
key to device independence and universal access is in the
separation of content and presentation.”
</p>
<p class="sig">annotation source: quote from the document</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Kyrnin</h2>
<h3 class="ref-title">“Why Use Semantic HTML?” by Jennifer Kyrnin</h3>
<p class="ref-location">
<a href="https://www.lifewire.com/why-use-semantic-html-3468271"
>https://www.lifewire.com/why-use-semantic-html-3468271</a>
</p>
<div class="annotation">
<p>“Creating web documents that have meaning behind the page
rendered in a browser is very important. Here are some
pointers as to how to understand and write semantic markup.”</p>
<p class="sig">annotation source: quote from the document</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Maler</h2>
<h3 class="ref-title">“Developing SGML DTDs: From Text to Model to Markup” by Eve Maler and Jeanne El Andaloussi</h3>
<p class="ref-location">
<a href="http://www.xmlgrrl.com/publications/DSDTD/">http://www.xmlgrrl.com/publications/DSDTD/</a>
</p>
<div class="annotation">
<p>The first, best, and most authoratitive book on design of
markup vocabularies. While the examples are all SGML (obsolete
for all of us) and the syntax is DTDs (still in use in some
communities but clearly not <i>au courant</i>), the point of
this book is the logic behind vocabulary design and that is
absoultely still current. For the reader interested in
declarative markup and too impatient to read the whole book I
suggest starting with Section 4.1.2. “Learning to Recognize
Semantic Components”.</p>
<p>The reader may also be interested in a blog entry in
“Pushing String” about this book: <a
href="http://www.xmlgrrl.com/blog/publications/developing-sgml-dtds/"
>http://www.xmlgrrl.com/blog/publications/developing-sgml-dtds/</a>
</p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Ornbo</h2>
<h3 class="ref-title">“The importance of semantic markup” by George Ornbo</h3>
<p class="ref-location">
<a href="https://shapeshed.com/the-importance-of-semantic-markup/"
>https://shapeshed.com/the-importance-of-semantic-markup/</a>
</p>
<div class="annotation">
<p>“Creating web documents that have meaning behind the page
rendered in a browser is very important. Here are some
pointers as to how to understand and write semantic
markup.”</p>
<p class="sig">annotation source: quote from the document</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Pemberton</h2>
<h3 class="ref-title">“The Power of the Declarative” by Steven Pemberton</h3>
<p class="ref-location">
<a href="https://www.w3.org/2009/Talks/04-02-steven-declarative/"
>https://www.w3.org/2009/Talks/04-02-steven-declarative/</a>
</p>
<div class="annotation">
<p>A short slide presentation about declarative markup, emphasizing its
power and compactness</p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Pemberton</h2>
<h3 class="ref-title">“The 100 Year Web: In Praise of XML” by Steven Pemberton</h3>
<p class="ref-location">
Pemberton, Steven. “The 100 Year Web: In Praise of XML.” Presented at
Balisage: The Markup Conference 2018, Washington, DC, July 31 - August 3, 2018.
In Proceedings of Balisage: The Markup
Conference 2018. Balisage Series on Markup Technologies, vol.
21 (2018).
<a href="https://www.balisage.net/Proceedings//vol21/author-pkg/Pemberton01/BalisageVol21-Pemberton01.html">https://doi.org/10.4242/BalisageVol21.Pemberton01.</a>
</p>
</div>
<div class="bib-entry">
<h2 class="sort-name">Piez</h2>
<h3 class="ref-title">“Beyond the ‘descriptive vs. procedural’ distinction” by Wendell Piez</h3>
<p class="ref-location">
<a href="http://conferences.idealliance.org/extreme/html/2001/Piez01/EML2001Piez01.html"
>http://conferences.idealliance.org/extreme/html/2001/Piez01/EML2001Piez01.html</a>
</p>
<div class="annotation">
<p>This 2001 paper has lost the link to its CSS but the content is as
relevant now as it ever was. See particularly the section “Generic
markup as a form of rhetoric”.</p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Piez</h2>
<h3 class="ref-title">“Format and Content: Should they be separated? Can they
be?” by Wendell Piez</h3>
<p class="ref-location">
<a href="http://conferences.idealliance.org/extreme/html/2005/Piez01/EML2005Piez01.html"
>http://conferences.idealliance.org/extreme/html/2005/Piez01/EML2005Piez01.html</a>
</p>
<div class="annotation">
<p>Conventionally, XML design and application methodologies
propose that the format in which we create, store and maintain
documentary data be isolated from the format of its
presentation: this doctrine is usually designated as the
“separation of format from content”, and the advantages of the
layered architecture it implies are often cited as a
compelling rationale for XML as a standards-based markup
technology. Yet experienced markup designers know that in
practice, the separation is often more easily described than
achieved, and that this design decision (like any other)
involves tradeoffs.</p>
<p class="sig">annotated source: Excerpt from the document abstract</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Smith</h2>
<h3 class="ref-title">“The Standard Generalized Markup Language (SGML) for
Humanities Publishing” by Joan M. Smith</h3>
<p class="ref-location">
<a href="https://academic.oup.com/dsh/article-abstract/2/3/171/931654"
>https://academic.oup.com/dsh/article-abstract/2/3/171/931654</a>
</p>
<div class="annotation">
<p>This announcement of the SGML Standard features generic
markup. Even the abstract is more about generic markup than
about SGML itself.</p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">TEI Consortium</h2>
<h3 class="ref-title">TEI: A Gentle Introduction to XML</h3>
<p class="ref-location">
<a href="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SG.html"
>http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SG.html</a></p>
<div class="annotation">
<p>An excellent introduction. The section: <a
href="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SG.html#SG111"
>Descriptive Markup</a> is a short, clear, description of
declarative markup and the rest of the document is an
excellent discussion of how XML and declarative markup work
together.</p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Usdin</h2>
<h3 class="ref-title">“The semantics of ‘semantic’” by B. Tommie Usdin</h3>
<p class="ref-location">
<a href="http://www.balisage.net/Proceedings/vol10/html/Usdin01/BalisageVol10-Usdin01.html"
>http://www.balisage.net/Proceedings/vol10/html/Usdin01/BalisageVol10-Usdin01.html</a></p>
<div class="annotation">
<p>Readers interested in generic markup should start reading
at the heading “The word ‘semantic’”. From that abstract:
There was a time when I knew what the word “semantic” meant.
That was a long time ago. Since then many people, on many
occasions, in many contexts, have corrected my
misunderstanding of the meaning of semantic. Perhaps it
means nothing, or everything. Or perhaps I’m simply
misinformed.</p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Usdin</h2>
<h3 class="ref-title">“YAMC? Why are we here? Why are we here again?” by B. Tommie Usdin</h3>
<p class="ref-location">
Usdin, B. Tommie. “YAMC? Why are we here? Why are we here
again?” Presented at Balisage: The Markup Conference 2018,
Washington, DC, July 31 - August 3, 2018. In Proceedings of
Balisage: The Markup Conference 2018. Balisage Series on
Markup Technologies, vol. 21 (2018).
<a href="https://www.balisage.net/Proceedings/vol21/html/Usdin02/BalisageVol21-Usdin02.html">https://doi.org/10.4242/BalisageVol21.Usdin02.</a>
</p>
<div class="annotation">
<p>Transcript of a talk. Readers interested in declarative markup may want
to skip the first few paragraphs which are about the conference rather
than markup.</p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Watson</h2>
<h3 class="ref-title">“Brief History of Document Markup” by Dennis G. Watson</h3>
<p class="ref-location">
<a href="http://chnm.gmu.edu/digitalhistory/links/pdf/chapter3/3.19a.pdf"
>http://chnm.gmu.edu/digitalhistory/links/pdf/chapter3/3.19a.pdf</a></p>
<div class="annotation">
<p>This short document includes a very clear description of generic markup.</p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Webster</h2>
<h3 class="ref-title">Short definition in Webster online</h3>
<p class="ref-location">
<a href="http://www.webster-dictionary.org/definition/generic%20markup"
>http://www.webster-dictionary.org/definition/generic%20markup</a>
</p>
<div class="annotation">
<p>Webster’s Dictionary online almost has it. The reference to
SGML is confusing a specific syntax that can, but is not
necessarily generic markup with the main principle of generic
or declarative markup.</p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
</section>
<section id="markupuses">
<h1>Declarative Markup Uses</h1>
<p>Documents about languages that are declarative, uses of
declarative markup, and other topics that are germain to a
discussion of declarative markup but are not primarily about
declarative markup as a concept</p>
<div class="bib-entry">
<h2 class="sort-name">Applen</h2>
<h3 class="ref-title">“The Rhetorical Nature of XML: Constructing Knowledge in Networked Environments” by Applen & McDaniel</h3>
<p class="ref-location"> Applen, J., McDaniel, R. (2009). The Rhetorical Nature
of XML. New York: Routledge.</p>
<div class="annotation">
<p>Simultaneously the best and the worst book on XML i’ve ever
read (with apologies to the authors if they are reading this)
- the technical misunderstandings about XML are deep (e.g.,
no, + doesn’t mean it’s optional in a DTD). This book is
recommended highly for its perspectives but be warned that the
more technical parts contain a lot of mistakes; Chapters 1, 3,
and 7 are particularly helpful.</p>
<p class="sig">annotated by: Liam Quin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Baker</h2>
<h3 class="ref-title">“Structured Writing: Rhetoric and Process” by Mark Baker</h3>
<p class="ref-location"> <!-- found empty, 2018-10-05 —Syd --> </p>
<div class="annotation">
<p>“Baker explains what structured writing is and how you can
use different structures to achieve different purposes. The
book focuses on how you can partition and manage the
complexity of the content creation process using structured
writing techniques to ensure that everything is handled by the
person or process with the skills, time, and resources to
handle it effectively.”</p>
<p class="sig">annotation source: Description of the book by
Richard Hamilton at <a
href="http://xmlpress.net/2018/09/11/structured-writing-rhetoric-and-process/"
>http://xmlpress.net/2018/09/11/structured-writing-rhetoric-and-process/</a></p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Lie</h2>
<h3 class="ref-title">“Cascading Style Sheets” by Håkon Wium Lie</h3>
<p class="ref-location">
<a href="http://www.wiumlie.no/2006/phd/css.pdf"
>http://www.wiumlie.no/2006/phd/
http://www.wiumlie.no/2006/phd/css.pdf</a> Thesis submitted for the
degree of Doctor Philosophiœ Faculty of Mathematics and Natural Sciences
University of Oslo Norway 2005
</p>
<div class="annotation">
<p>From the Overview:</p>
<blockquote>
<h2>Chapter 2: Structured documents</h2>
<p>Style sheet languages and structured documents are mutually
dependent. Without style sheets, structured documents cannot be
presented, and without structured documents there is nothing for
style sheets to present. Chapter 2 starts by introducing the ladder
of abstraction which is proposed as a measuring tool for structured
document formats. Such formats developed prior to the web (Scribe,
LaTeX, ODA, SGML) and for the web (HTML, XML) are described.
Finally, the role of transformation languages vs. style sheet
languages is discussed.</p>
<h2>Chapter 3: Style sheets prior to the web</h2>
<p>Chapter 3 is the first chapter in which style sheets are discussed in
some detail. The first part of the chapter establishes a set of
criteria for style sheet languages; in order to qualify as a style
sheet language six components must be present: syntax, selectors,
properties, values and units, value propagation and a formatting
model. Three style sheet languages developed before the Web (FOSI,
DSSSL and P94) are described. The historical background of each is
followed by a technical review.</p>
<h2>Chapter 4: Style sheet proposals for the web</h2>
<p>This chapter is a survey of the style sheet languages that were
proposed for the web in the period 1993-1996. Nine different
proposals are reviewed according to the criteria established in the
previous chapter.</p>
</blockquote>
<p>Obviously, the rest of the thesis would be of particular interest to a
reader interested in the declarative markup known as CSS.</p>
<p>Its glossary definition of ‘declarative language’ may also be of
interest:</p>
<blockquote>
<h2>declarative language</h2>
<p>A declarative language is a general term for languages
which express relationships between variables, as opposed to
imperative languages which specify explicit sequences of
steps to be followed, in order to produce a result. Often,
declarative languages are not Turing-complete, while
imperative languages are. All style sheet languages
described in this thesis are declarative.</p>
</blockquote>
<p class="sig">annotated by: Tony Graham</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Quin</h2>
<h3 class="ref-title">“The World Wide Success That Is XML” by Liam Quin</h3>
<p class="ref-location">
<a href="https://www.w3.org/blog/2018/07/the-world-wide-success-that-is-xml/"
>https://www.w3.org/blog/2018/07/the-world-wide-success-that-is-xml/</a>
</p>
<div class="annotation">
<p>Most of the XML Working Groups have been closed by now;
this year saw XQuery and XSLT close, their work successfully
completed.</p><p>As we wind down work on standardizing the XML
stack at W3C it’s worth looking at some of what we have
accomplished and why. W3C XML, the Extensible Markup Language,
is one of the world’s most widely-used formats for
representing and exchanging information. The final XML stack
is more powerful and easier to work with than many people
know, especially for people who might not have used XML since
its early days.</p>
<p class="sig">annotated source: excerpt from the document</p>
</div>
</div>
</section>
<section id="collections">
<h1>Other Collections of Markup-related Materials</h1>
<div class="bib-entry">
<h2 class="sort-name">Balisage Series on Markup Technologies</h2>
<h3 class="ref-title">Proceedings of Balisage starting in 2008</h3>
<p class="ref-location"><a href="https://www.balisage.net/Proceedings/index.html">https://www.balisage.net/Proceedings/index.html</a></p>
<div class="annotation">
<p>Balisage is an annual conference devoted to the theory and practice of descriptive markup and related technologies for structuring and managing information.</p>
<p class="sig">annotated from the conference web site</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Cover Pages</h2>
<h3 class="ref-title">The Cover Pages at OASIS</h3>
<p class="ref-location"><a href="http://xml.coverpages.org/index.html">http://xml.coverpages.org/index.html</a></p>
<div class="annotation">
<p>Frozen in 2010, the Cover Pages are a detailed record of the development of SGML and XML, including descriptions of events, products, and specifications. Many of the links still work; the value of this enormous resource will fade over time but as of 2018 it is still a treasure trove.</p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">Extreme Markup Languages, Proceedings</h2>
<h3 class="ref-title">Proceedings of Extreme Markup Languages 2001 - 2007</h3>
<p class="ref-location"><a href="http://conferences.idealliance.org/extreme/index.html">http://conferences.idealliance.org/extreme/index.html</a></p>
<div class="annotation">
<p>Extreme Markup Languages was a conference series devoted to Markup Languages, including but not limited to SGML and XML. Many people consider it the predecessor to "Balisage: The Markup Conference".</p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">JATS-Con proceedings</h2>
<h3 class="ref-title">JATS-Con conference proceedings</h3>
<p class="ref-location"><a href="https://www.ncbi.nlm.nih.gov/books/NBK65129/">https://www.ncbi.nlm.nih.gov/books/NBK65129/</a></p>
<div class="annotation">
<p>Starting in 2010, JATS-Con is a (mostly) annual event about the Journal Article Tag Suite and related XML vocabularies. The proceedings include formal articles, slides, and videos of presentations. </p>
<p class="sig">annotated by: B. T. Usdin</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">MarkupUK</h2>
<h3 class="ref-title">Proceedings of MarkupUK</h3>
<p class="ref-location"><a href="http://markupuk.org/webhelp/">http://markupuk.org/webhelp/</a></p>
<div class="annotation">
<p>Markup UK is a conference about XML and other mark-up languages</p>
<p class="sig">annotated from the conference web site</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">XML.com</h2>
<h3 class="ref-title">“XML.com” by Textuality</h3>
<p class="ref-location"><a href="https://www.xml.com/">https://www.xml.com/</a></p>
<div class="annotation">
<p>XML.com contains curated information aimed at professionals in fields where XML is widely used. These include publishing (for example, technical documentation and technical publishing) and healthcare (for example, HL7 and related work).</p>
<p class="sig">from the site</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">XML London, Proceedings</h2>
<h3 class="ref-title">Proceedings of the XML London conference</h3>
<p class="ref-location">2016 <a href="http://xmllondon.com/2016/xmllondon-2016-proceedings.pdf">http://xmllondon.com/2016/xmllondon-2016-proceedings.pdf</a></p>
<p class="ref-location">2015 <a href="http://xmllondon.com/2015/xmllondon-2015-proceedings.pdf">http://xmllondon.com/2015/xmllondon-2015-proceedings.pdf</a></p>
<p class="ref-location">2014 <a href="http://xmllondon.com/2014/xmllondon-2014-proceedings.pdf">http://xmllondon.com/2014/xmllondon-2014-proceedings.pdf</a></p>
<p class="ref-location">2013 <a href="http://xmllondon.com/2013/xmllondon-2013-proceedings.pdf">http://xmllondon.com/2013/xmllondon-2013-proceedings.pdf</a></p>
<div class="annotation">
<p>A 2 day conference for XML, Linked Data and W3C technology users to discuss their experiences while discovering the latest innovations and what others are doing in the industry.</p>
<p class="sig">annotated from the conference web site</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">XML Prague, Proceedings</h2>
<h3 class="ref-title">XML Prague Archive</h3>
<p class="ref-location"><a href="http://www.xmlprague.cz/archive/">http://www.xmlprague.cz/archive/</a></p>
<div class="annotation">
<p>Sessions and posters from XML Prague starting in 2005 include PDF of the proceedings and video of presentations starting in 2007.</p>
<p class="sig">annotated from the conference web site</p>
</div>
</div>
</section>
<section id="related">
<h1>Related Concepts</h1>
<div class="bib-entry" id="HORSE2">
<h2 class="sort-name">Bauman</h2>
<h3 class="ref-title">“TEI HORSEing Around” by Syd Bauman</h3>
<p class="ref-location">
<a href="http://conferences.idealliance.org/extreme/html/2005/Bauman01/EML2005Bauman01.html"
>http://conferences.idealliance.org/extreme/html/2005/Bauman01/EML2005Bauman01.html</a>
</p>
<div class="annotation">
<p>This paper focuses on how the markup suggested by <a
href="#HORSE1">DeRose</a> can be constrained, and suggests a
method of creating those constraints automatically for TEI
schemata. Some say its most useful contribution is an <a
href="http://conferences.idealliance.org/extreme/html/2005/Bauman01/EML2005Bauman01.html#t8">appendix</a>
which puts forth a suggested nomenclature for discussing XML
overlap and various solutions.</p>
<p class="sig">annotated by: Syd Bauman</p>
</div>
</div>
<div class="bib-entry">
<h2 class="sort-name">TEI Metalanguage Workgroup</h2>
<h3 class="ref-title"> Notes on SGML Solutions to Markup Problems</h3>
<p class="ref-location">
<a href="http://www.tei-c.org/Vault/ML/mlw18.txt"
>http://www.tei-c.org/Vault/ML/mlw18.txt</a></p>
<div class="annotation">
<p>An early, detailed examination of various methods of
encoding overlapping hierarchical structures in SGML.</p>
<p class="sig">annotated by: Syd Bauman</p>
</div>
</div>
</section>
<section id="contribute">
<h1>How to Contribute</h1>
<p><cite>Markup Declaration</cite> wants your input!</p>
<p>If you know of a resource that’s missing from this bibliography,
or if you have an annotation to add, please contribute!</p>
<p>For each entry, we need the title of the work, the names of the
author or authors, and an annotation. If the annotation is an excerpt
from the work, that’s all you have to say. If it’s a personal comment
on the work, please include your name as you’d like it to be published.
(You can see how we’ll format that and put it on the page by looking
at the examples above.)</p>
<p>There are three options for contributing:</p>
<ol>
<li>
<p>If you want, you can just <a href="/contact">send it to us</a>.</p>
</li>
<li>
<p>A little more work for you, but a little easier for us, would
be to
<a href="https://github.com/markupdeclaration/markupdeclaration.org/issues=">create an issue</a> that contains the details needed for the bibliography.
</p>
</li>
<li>
<p>Finally, if you’re comfortable with GitHub and HTML, feel free to fork
<a href="https://github.com/markupdeclaration/markupdeclaration.org">the
repository</a>, edit <code>_pages/04_01_bibliography.html</code>,
and send us a pull request</p>
<p>The markup is a little bit odd, we concede, because some of the
publishing mechanics (<a href="https://jekyllrb.com/">Jekyll</a>)
bleed through into the content. We may try to fix that in the
future. For now, just leave the extra few lines of text at the
top of the file alone.</p>
</li>
</ol>
</section>
</body>
</html>