SVG is preceded by and informed by postscript and PDF. The postscript language reference manual is 912 pages. https://www.adobe.com/jp/print/postscript/pdfs/P

SVG is preceded by and informed by postscript and PDF. The postscript language reference manual is 912 pages. https://www.adobe.com/jp/print/postscript/pdfs/PLRM.pdf https://www.adobe.com/jp/print/postscript/pdfs/PLRM.pdf The PDF reference is 978 pages. https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/pdf_reference_archives/PDFReference.pdf https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/pd... SVG, if it's less than either is actually doing well... IMO these three technologies and the accompanying docs are masterpieces, despite bloat. Digging in to those reference docs can almost be fun The author's idea of SlimSVG sounds interesting, but I think focusing on the file format isn't enough -- one powerful feature of SVG is that it's part of the DOM. Can there be a better system than the DOM+JS for allowing a dynamic document? EG, document object model in JSON (maybe with JSON schema) and allow updates with JSON patch, with a client/server model for updates. (There's more to DOM) Personally I think XML is well suited to this task, and am glad to have learned of SVG Native from this thread