@mwichary Table 3 on page 360 of "The SGML Handbook" by Charles F. Goldfarb has a table of the _standard_ assignments for #SGML delimiters which is configurable in the SYNTAX DELIM part of the declaration. STAGO (<), ETAGO (</), MDO (<!), PIO (<?) are closed with TAGC (>), MDC (>), and PIC (>). Curly braces, part of ASCII and Unicode 2.0, are not found.
So your search is for the authorship of the #standard for STAGO, ETAGO, and TAGC. Legacy systems still in use in 1980 used a wide variety of character sets. It is possible that a legacy 6-bit character set was used as a constraint as the bias to all-upper case and lack of curly brackets is consistent with that theory.
As you want history, not speculation, I will point out that #Goldfarb wanted the system to be visually distinct because this format (like GML) was designed for humans to be able to parse and this concern would have been common. But SGML was designed and adopted by a committee building off GML and committees have documents. Good luck!
@david_megginson I worked with #SGML at a publishing company in the late 1990's. I recall the Navy using it for documentation. There was only one other person in my local area I could find that worked with SGML.
I liked working in it but it was a niche job market.
[Перевод] Вся мощь открытого исходного кода в PostgreSQL
PostgreSQL — одна из самых популярных СУБД, и это во многом благодаря открытому исходному коду. В статье рассказывается о том, как открытость кода влияет на развитие PostgreSQL и создание сообщества вокруг неё.
https://habr.com/ru/companies/flant/articles/901622/
#open_source #postgresql #исходный_код #коммиты #commit #git #git_log #sgml #git_blame #source_code
Does anyone happen to have a copy of:
Floyd, Michael. A Conversation with Charles F. Goldfarb. Web Techniques (Vol.3, Issue 11), pp.38–41, November, 1998
It used to be online, but has now disappeared, and the Internet Archive doesn’t have it either. I’d like to check a quote that I copied back then.
Markup Languages, by @j9t [@frontenddogma.com]:
https://meiert.com/en/blog/markup-languages/
#overviews #linklists #sgml #html #xml #xhtml #hdml #dhtml #mathml #wml #chtml
Well, “Episode 21: Keynote — John McCarthy” actually has a recording and he gives that quote at timestamp 1:13:15:
http://www.oopsla.org/oopsla2007/index56d8.html
http://www.oopsla.org/podcasts/Keynote_JohnMcCarthy.mp3
“When W3C decided not to use #LISP format but to imitate #SGML for that [it] showed a certain capacity to make mistakes” *laughter* “which they probably hadn't lost”
Conclusion: the first part is similar, but the second part of the original quote is unfamiliar.
Isn't the WWW a wonderful to be able to research this? #markupLanguages
@david_megginson @HugoHeagren Currently, I use https://github.com/docbook/xslTNG which depends on the open source home edition of saxon XSLT processor to convert DocBook XML to HTML/ePub, and use #CSS based publishing softwares like https://vivliostyle.org or https://www.princexml.com/
There are zero actively maintained/usable on modern computers #SGML or #DSSSL processors known to me.
The statement “`<input checkbox>` is per SGML rules equivalent to `<input type="checkbox">`, but HTML parsers treat it as `<input checkbox="">`” is…
fwiw, I used #DocBook #SGML in #Emacs to generate LaTeX/LilyPond, even when Macmillan demanded I submit MSWord¹ docs, I'd just emit them as an output! Mind you, that was last century, but I'd still do it that way today, if I had to.
___
¹ I call those apps "font painters', or WYSIAYG (what you see is ALL you get
Richard Penner
royterdw
Habr
Michael Piotrowski
Frontend Dogma
tajpulo
LdBeth
RetroComputingMX
Jens Oliver Meiert
teledyn 𓂀