It has been pretty interesting designing this Object Model in JavaScript for OPML. Mainly because I have found several flaws in the design that if fixed will make it a lot better to use. I discovered them because I am using the Object Model directly in AJAX Tagger version 2.0.
The basic problem is that I didn't completly understand the OPML specification and I started to implement the mini API before I knew more about it. The area that I need to extend in the object model is around the attributes of the outline element. I only thought you had a type and text, but it turns out the specification is quite loose around the attributes that you can have, but there are several well used attributes that hook up with files, links, html and rss etc. I will document them some other time.Other than that the OPML XML that it generates seems to be good, apart from the quoting of " and the &'s :)
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.
I love to learn about what you are building, and how I can help with Chrome or Web development in general, so if you want to chat with me directly, please feel free to book a consultation.
I'm trialing a newsletter, you can subscribe below (thank you!)
