YES. And...the @whatwg did include serialization to serve XML. They also prove that entire shifts in approach don't have to be limited to any spec/rec/standards org but independently driven. XML, XForms, XSLT remain in use. Medical documentation for example use XML ontologies.
This tweet is unavailable
1
6
Yes. And of course we saw CSS Frameworks emerge largely because var() - now CSS has functions. It's been a long-standing issue as it's emerging as hybrid declarative and function. Hmmm. Maybe that's a good thing? I tend toward declarative for markup and style as foundational.
1
They are in use, and a good person for examples is Steven Pemberton, who continues to speak on these topics and other XML/Semantic Web long-time influencers with W3C ties use them, mostly intranets. But XML's kids are alive. SVG anyone? :)
1
Y'all need to check out Saxon-JS 2
Saxon-JS 2 is available today: XSLT 3.0 and XPath 3.1 in versions for Node.js and the browser, and now with its own XSLT compiler, no longer dependent on Saxon-EE. It's fast and it's free. saxonica.com/saxon-js/index.… #xslt #xpath #xml
1
2
Node.js for compiling XSLT? I'm kinda startled but shouldn't be at all. Great to know about and must see this in action. Thank you Martynas!
2
2
My thoughts go right to security and generating code, even quality, clean, rigorous code, is in part contributing to reliance on tools over language skills. Know the code is a reasonable ethic for use at all. And a mantra since Perl/CGI server side era.
Apr 26, 2021 · 11:10 AM UTC
1
1