# XML XML is a markup language and restricted form of SGML used to represent structured data and processed by software modules. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A Failed XML-Based DSL Design Using a Large Regular Expression DevFeed: [A Failed XML-Based DSL Design Using a Large Regular Expression]() Original publisher: [Read original article]() Author: Remy Porter Published: 2026-09-07T06:30:00Z Content type: opinion Language: en Sources: [The Daily WTF]() Topics: [XML](), [Structured-data](), [bug](), [Code]() Tags: [best-of](), [bug](), [code](), [documentation](), [domain-specific-languages](), [dsls](), [regex](), [xml]() ### AI overview The article revisits a failed attempt to build a domain-specific language with XML schemas and a 1,310-character regular expression. It describes a bug in the expression and criticizes the resulting design as an unsuccessful effort to save labor. ### Source excerpt It's a holiday here in the US, a celebration of labor, so we're reaching back through the archives for a story about an attempt to be labor saving that was not successful. Original. --Remy I've had to write a few domain-specific-languages in the past. As per Remy's Law of Requirements Gathering, it's been mostly because the users needed an Excel-like formula language. The danger of DSLs, of course, is that they're often YAGNI in the extreme, or at least a sign that you don't really understand your problem. XML, coupled with schemas, is a tool for building data-focused DSLs. If you have some complex structure, you can convert each of its features into an XML attribute. For example, if you had a grammar that looked something like this: The Source specification obeys the following syntax source = ( Feature1+Feature2+... ":" ) ? steps Feature1 = "local" | "global" Feature2 ="real" | "virtual" | "ComponentType.all" Feature3 ="self" | "ancestors" | "descendants" | "Hierarchy.all" Feature4 = "first" | "last" | "DayAllocation.all" If features are specified, the order of features as given above has strictly to be followed. steps = oneOrMoreNameSteps | zeroOrMoreNameSteps | componentSteps oneOrMoreNameSteps = nameStep ( "." nameStep ) * zeroOrMoreNameSteps = ( nameStep "." ) * nameStep = "#" name name is a string of characters from "A"-"Z", "a"-"z", "0"-"9", "-" and "_". No umlauts allowed, one character is minimum. componentSteps is a list of valid values, see below. Valid 'componentSteps' are: - GlobalValue - Product - Product.Brand - Product.Accommodation - Product.Accommodation.SellingAccom - Product.Accommodation.SellingAccom.Board - Product.Accommodation.SellingAccom.Unit - Product.Accommodation.SellingAccom.Unit.SellingUnit - Product.OnewayFlight - Product.OnewayFlight.BookingClass - Product.ReturnFlight - Product.ReturnFlight.BookingClass - Product.ReturnFlight.Inbound - Product.ReturnFlight.Outbound - Product.Addon - Product.Addon.Service - Product.Addon.ServiceFeatu ## DocLang: a markup language for LLMs DevFeed: [DocLang: a markup language for LLMs]() Original publisher: [Read original article]() Author: Kim Martineau Published: 2026-08-12T12:00:00Z Content type: article Language: en Sources: [IBM Research]() Topics: [XML](), [Parser](), [Parsing](), [Large Language Model](), [Generative AI](), [HTML]() Tags: [ai](), [algorithms](), [generative-ai](), [llms](), [news](), [parsing](), [xml]() ### AI overview IBM researchers introduce DocLang, a constrained XML sub-language designed to help large language models interpret document structure. The article explains how it represents semantics, layout, bounding boxes, and reading order, and how it may reduce token use, latency, and inference costs in AI pipelines. ### Source excerpt The lead researcher behind IBM's popular document parser, Docling, explains why generative AI needs its own document standard. ## DAC7 Reporting: A Practical Guide for Platform Operators DevFeed: [DAC7 Reporting: A Practical Guide for Platform Operators]() Original publisher: [Read original article]() Author: Aarthi Poonia Published: 2026-07-31T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [data](), [XML]() Tags: [compliance](), [data](), [eu](), [guide](), [identity](), [marketplaces](), [platform](), [tax]() ### AI overview A practical guide to DAC7 reporting for digital platform operators, covering scope, seller due diligence, required identity and earnings data, annual reporting obligations, exclusions, deadlines, and the effect of a merchant-of-record arrangement. ### Source excerpt What DAC7 reporting requires from platforms: who must report, which activities are in scope, the seller data to collect, and the 31 January deadline. ## kPointer Replaces cw-json with Support for JSON, YAML, HTML, and XML DevFeed: [kPointer Replaces cw-json with Support for JSON, YAML, HTML, and XML]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-22T12:27:15Z Content type: release Language: en Sources: [The CommonsBlog]() Topics: [data](), [JSON](), [YAML](), [HTML](), [XML](), [Command-line interface](), [test]() Tags: [blog](), [cli](), [data](), [html](), [json](), [sdk](), [test](), [testing](), [xml](), [yaml]() ### AI overview kPointer replaces cw-json as a library for extracting values from structured data. It supports JSON, YAML, HTML, and XML through adapter-style abstractions, adds JavaScript access path notation, and includes conformance testing and a CLI. ### Source excerpt The cw-json project has been replaced by kPointer -- learn what kPointer offers! ## Rich Text And Code Editing: RichTextArea And A Syntax-Highlighting CodeEditor DevFeed: [Rich Text And Code Editing: RichTextArea And A Syntax-Highlighting CodeEditor]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-28T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Syntax Highlighting](), [Code](), [cross-platform](), [Web](), [JavaScript](), [Kotlin](), [Python](), [CSS](), [JSON](), [XML]() Tags: [code](), [code-completion](), [cross-platform](), [css](), [javascript](), [kotlin](), [python](), [syntax](), [web](), [xml]() ### AI overview The article describes RichTextArea and CodeEditor, two Codename One visual editors built on a shared semantic abstraction. A bundled cross-platform web-view engine is the default backend, while ports can provide optional native peers. The CodeEditor supports syntax highlighting for eight languages, themes, automatic bracket and quote closing, and asynchronous code completion. ### Source excerpt RichTextArea and a syntax-highlighting CodeEditor, both built on a shared editor abstraction with a cross-platform web-view engine and an optional native peer. ## How to Design APIs DevFeed: [How to Design APIs]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-06-02T06:41:25Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [API](), [Architecture & Design](), [interface](), [CRUD](), [GraphQL](), [gRPC](), [HTTP](), [JSON](), [XML]() Tags: [api](), [apis](), [crud](), [graphql](), [how-to](), [http](), [interface](), [json](), [rest](), [rpc]() ### AI overview A tutorial on API design covering interface contracts, resource and endpoint naming, request and response formats, API paradigms, and modeling relationships between entities. ### Source excerpt Key considerations to keep in mind ## OpenAPI, ORM, SVG and Lottie DevFeed: [OpenAPI, ORM, SVG and Lottie]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-01T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [OpenAPI Specification](), [Code generation](), [SQLite](), [Object-relational mapping](), [JSON](), [XML](), [SVG](), [ASP.NET Core](), [FastAPI](), [Nest]() Tags: [build](), [fastapi](), [http](), [java](), [json](), [lottie](), [maven-plugin](), [net](), [openapi](), [orm](), [rest](), [spring](), [svg](), [xml]() ### AI overview A Codename One release follow-up describes a shared build-time code generation pipeline for OpenAPI client generation, a SQLite ORM, JSON and XML mappers, SVG and Lottie transcoders, and a declarative router. The pipeline emits typed Java from annotations or declarative source files without reflection. ### Source excerpt An OpenAPI client generator, a JPA-shaped SQLite ORM, JAXB-shaped JSON / XML mappers, build-time SVG / Lottie transcoders, and a declarative router with deep links. All on the same build-time codegen pipeline. ## From RSS to Atom DevFeed: [From RSS to Atom]() Original publisher: [Read original article]() Published: 2026-05-04T00:00:00Z Content type: opinion Language: en Sources: [Susam Pal]() Topics: [Atom Feed](), [RSS Feed](), [Lisp](), [Git](), [XML]() Tags: [2026](), [git](), [git-commit](), [lisp](), [rss](), [xml]() ### AI overview The author describes switching a personal website from RSS feeds to Atom feeds in 2026. The change was implemented in Common Lisp, took about an hour, and included replacing RSS item identifiers with UUID-based Atom entry identifiers and updating feed templates. ### Source excerpt Yesterday, I switched my website from RSS feeds to Atom feeds. In case you are wondering whether you have somehow landed on an ancient post from 2010, no, you have not. Yes, this is the year 2026, and I have finally switched from RSS feeds to Atom feeds. Yes, I am fifteen, or perhaps twenty, years too late. Contents Impulse Coding Atom Entries Temporary Workaround Does It Matter? References Impulse Coding I have always wanted to do this but could never make the time for it. Finally, it happened while I was giving my brain some rest from my ongoing algebraic graph theory studies. That's when I felt like spending a little time on my website and doing a little Lisp to change the feeds from RSS to Atom. I suppose this was impulse coding, a bit like impulse buying, except that I ended up with an Atom feed instead of a new book. I find it quite surprising that when I have plenty of time, it usually does not occur to me to do these things, but when I am too busy and really short of time, these little ideas possess me during the short breaks I take. My personal website is one of my passion projects. Common Lisp is one of my favourite programming languages. So any time spent on this passion project using my favourite programming language is a very relaxing experience for me. It serves as an ideal break between intense study sessions. It took about an hour to implement the changes needed to make the switch from RSS to Atom. In the end, I could go back to my studies reinvigorated. In case you are curious, here is the Git commit where I implemented the change from RSS to Atom: 596e1dd. As you might notice, a large portion of the change consists of replacing the key attribute in each post with the uuid attribute. The key attribute value was used as the value of the element in the RSS feeds. While an arbitrary short string could serve as the element for the items in an RSS feed, the element of the entries in an Atom feed needs to be a URI. It turns out UUID URN ## How The New York Times Games Team Delivered Accessible, Cross-Platform Dark Mode DevFeed: [How The New York Times Games Team Delivered Accessible, Cross-Platform Dark Mode]() Original publisher: [Read original article]() Author: The NYT Open Team Published: 2026-04-16T15:35:45Z Content type: article Language: en Sources: [New York Times]() Topics: [Dark Mode](), [Mobile](), [Android](), [iOS](), [Jetpack Compose](), [ui](), [Design system](), [XML](), [pull-requests](), [SwiftUI](), [Objective-C]() Tags: [accessible](), [android](), [collaboration](), [cross-platform](), [dark-mode](), [design](), [design-system](), [engineering](), [ios](), [jetpack-compose](), [pull-requests](), [swiftui]() ### AI overview The New York Times Games team describes implementing accessible, brand-consistent dark mode across its mobile app. The work coordinated design and engineering across Android and iOS, including XML and Jetpack Compose screens, legacy and modern interfaces, shared assets, external libraries, and testing. ### Source excerpt Bringing accessible, brand-consistent dark mode to life in The New York Times Games app through cross-platform design and engineering collaboration.Illustration by Allie Sullberg By Vanessa Johnson, Daniel Falokun, Michael Ingber and Oleksandr Zabiiako The Games Mobile App introduced dark mode back in October. This seamless implementation was a collaborative effort, requiring careful planning and management of design, cross-platform coordination, and engineering work across both legacy and modern user interface systems. The process to implement dark mode across the app included consideration on the visuals, colors, and icons that are mode specific to maintain legibility and brand consistency. The New York Times Games team is excited to have delivered this feature before the end of 2025, and thrilled to be able to roll out a feature that continues to make our app accessible for all. Development Work on Mobile On the development side, the mobile and web engineers synchronized assets which were colors, fonts, and images to ensure that hybrid screens showed the correct styles and colors. This was possible since our design system across mobile was constructed in a way that encouraged consistency and scalability across platforms. With clear and easy to follow designs supported by our internal design system, Android and iOS could ensure consistency on both platforms. Screens in dark mode From an Android perspective, it required separate approaches for XML (Extensive Markup Language) based screens which use an imperative, hierarchical approach and Jetpack Compose screens that use a more modern declarative approach. XML and Jetpack Compose are different ways the UI can be constructed. To ensure dark mode compatibility, all features were revisited to make sure they were adapted, especially the additions that were being worked on during the dark mode project. Another aspect of this development was updating external libraries that required making pull requests, creating a versi ## Python 3.12.13, 3.11.15 and 3.10.20 are now available! DevFeed: [Python 3.12.13, 3.11.15 and 3.10.20 are now available!]() Original publisher: [Read original article]() Author: Thomas Wouters Published: 2026-03-03T00:00:00Z Content type: release Language: en Sources: [Python Insider]() Topics: [Python](), [releases](), [Security](), [Python 3.10](), [XML](), [Parser](), [HTML](), [SSL]() Tags: [html](), [http](), [memory](), [memory-safety](), [python](), [python-3-10](), [releases](), [security](), [ssl]() ### AI overview Python 3.12.13, 3.11.15, and 3.10.20 are security-only source releases addressing vulnerabilities and hardening email, HTTP, XML, HTML, denial-of-service, and SSL handling. ### Source excerpt [Python Releases For Your Security!](https://discuss.python.org/t/python-3-12-13-3-11-15-and-3-10-20-are-now-available/106363) New security releases for 3.10, 3.11 and 3.12 are now available. ## Moved my blog to \[blog.wagemakers.be\](https://blog.wagemakers.be) DevFeed: [Moved my blog to \[blog.wagemakers.be\](https://blog.wagemakers.be)]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2026-01-26T17:26:00Z Content type: tutorial Language: en Sources: [stafwag Blog]() Topics: [migration](), [hosting](), [GitHub](), [Security](), [RSS Feed](), [Hugo](), [Atom](), [XML]() Tags: [atom](), [blog](), [disquss](), [github](), [hosting](), [html](), [https](), [hugo](), [jekell](), [migration](), [rss](), [security](), [security-privacy](), [xml]() ### AI overview The author moved the blog from GitHub to self-hosted hosting and documents the migration issues encountered. The article covers HTML redirects, updating hardcoded links, Disqus comment reindexing, and difficulties redirecting RSS feeds when moving from Octopress to Jekyll. ### Source excerpt If you follow my blog posts with an RSS reader, update the rss feed to: https://blog.wagemakers.be/atom.xml ...If you want to continue to follow me off-course ;-) I moved my blog from GitHub to my own hosting ( powered by Procolix ). Procolix sponsored my hosting for 20 years, till I decided to start my company Mask27.dev. One reason is that Microsoft seems to like to put "copilot everywhere", including on repositories hosted on github. While I don't dislike AI ( artificial intelligence ), LLM ( Large Language Models ) are a nice piece of technology. The security, privacy, and other issues are overlooked or even just ignored. The migration was a bit more complicated as usual, as nothing "is easy" ;-) You'll find the pitfalls of moving my blog below as they might be useful for somebody else ( including the future me ). ## \[Pentesting\] ONVIF (CCTV cameras) auth DevFeed: [\[Pentesting\] ONVIF (CCTV cameras) auth]() Original publisher: [Read original article]() Published: 2025-11-27T23:00:00Z Content type: tutorial Language: en Sources: [Dennis Yurichev]() Topics: [passwords](), [XML](), [Python]() Tags: [auth](), [camera](), [cameras](), [password](), [python](), [tcp](), [xml]() ### AI overview This article examines ONVIF authentication for CCTV cameras over TCP. It explains the username, password digest, nonce, and date fields, gives the digest calculation, and describes using Hashcat to crack a known password digest. ### Source excerpt [Pentesting] ONVIF (CCTV cameras) auth ## XML Modelling in OpenAPI 3.2: A Quiet but Important Upgrade for Enterprise Teams DevFeed: [XML Modelling in OpenAPI 3.2: A Quiet but Important Upgrade for Enterprise Teams]() Original publisher: [Read original article]() Author: Zaid Daba'een Published: 2025-11-14T14:54:07Z Content type: tutorial Language: en Sources: [DeveloperHub.io]() Topics: [OpenAPI Specification](), [XML](), [upgrade](), [API]() Tags: [api-design](), [engineering](), [enterprise](), [openapi](), [upgrade](), [xml]() ### AI overview OpenAPI 3.2 expands XML modelling with clearer support for namespaces, attributes, mixed content, and precisely named nested wrappers. The article explains how these capabilities address limitations in OpenAPI 3.1 and reduce reliance on parallel XSDs, proprietary extensions, and prose documentation. ### Source excerpt OpenAPI 3.2 modernises XML support with richer modelling, proper attribute handling, and nested structures. It removes old workarounds and gives enterprise teams clearer, more accurate ways to define their XML based APIs. ## Changes in ipSpace.net RSS Feeds DevFeed: [Changes in ipSpace.net RSS Feeds]() Original publisher: [Read original article]() Published: 2025-10-08T04:40:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [RSS Feed](), [Atom](), [Atom Feed](), [Hugo](), [XML](), [HTML]() Tags: [hugo](), [rss](), [update](), [web](), [xml]() ### AI overview The author describes replacing the ipSpace.net RSS and Atom feed generation system with static Hugo-generated feeds, adding redirects for older URLs, and discontinuing the free-content feed. The changes followed a Feedburner failure that prevented Apple Podcasts from discovering a new episode. The article also discusses feed formatting issues involving iTunes tags, whitespace trimming, HTML escaping, content truncation, and conversion of HTML to plain text. ### Source excerpt TL&DR: You shouldn't see any immediate impact of this change, but I'll eventually clean up old stuff, so you might want to check the URLs if you use RSS/Atom feeds to get the list of ipSpace.net blog posts or podcast episodes. The (hopefully) final URLs are listed on this page. Executive Summary: I cleaned up the whole ipSpace.net RSS/Atom feeds system. The script that generated the content for various feeds has been replaced with static Hugo-generated RSS/Atom feeds. I added redirects for all the old stuff I could find (including ioshints.blogspot.com), but I could have missed something. The only defunct feed is the free content feed (which hasn't changed in a while, anyway), as it required scanning the documents database. You can use this page to find the (ever-increasing) free content. And now for the real story ;) Read more ... ## OpenAPI 3.2 adds OAuth device flow, structured tags, QUERY, streaming, and XML modeling DevFeed: [OpenAPI 3.2 adds OAuth device flow, structured tags, QUERY, streaming, and XML modeling]() Original publisher: [Read original article]() Author: Zaid Daba'een Published: 2025-10-05T12:12:40Z Content type: article Language: en Sources: [DeveloperHub.io]() Topics: [OpenAPI Specification](), [OAuth](), [HTTP](), [Streaming](), [Tooling](), [XML]() Tags: [deprecated](), [engineering](), [event-streaming](), [extension](), [http](), [oauth](), [openapi](), [schema](), [streaming]() ### AI overview The article reviews proposed OpenAPI 3.2 changes, including OAuth device flow support, hierarchical tags, the QUERY method, clearer multipart definitions, streaming API support, and improved XML modeling. It describes the release as incremental and compatible with OpenAPI 3.1. ### Source excerpt See what's new in OpenAPI v3.2. Better structure, better auth support, better file and stream handling - no breaking changes. ## Compose Unstyled v1.40: Android XML themes DevFeed: [Compose Unstyled v1.40: Android XML themes]() Original publisher: [Read original article]() Author: Alex Styl Published: 2025-08-14T00:00:00Z Content type: release Language: en Sources: [Composables - Concise, no-fluff video tutorials for Android developers]() Topics: [Compose](), [Jetpack Compose](), [migration](), [Android](), [XML](), [material-components]() Tags: [adapter](), [android](), [api](), [compose](), [jetpack](), [jetpack-compose](), [material-components](), [migration](), [performance](), [v1](), [xml]() ### AI overview Compose Unstyled v1.40.0 introduces the resolveTheme API, which lets Jetpack Compose resolve selected values from existing Android XML themes during a gradual migration from Views. The approach avoids maintaining duplicate theme sources, but each resolution has a measurable performance cost and is intended to be temporary. ### Source excerpt v1.40.0 introduces a new resolveThemeX() API to make the migration to Jetpack Compose simpler. ## Announcing Microsoft.PowerShell.PlatyPS 1.0.0 DevFeed: [Announcing Microsoft.PowerShell.PlatyPS 1.0.0]() Original publisher: [Read original article]() Author: Jason Helmick, Sean Wheeler Published: 2025-07-24T21:35:14Z Content type: release Language: en Sources: [PowerShell Team]() Topics: [PowerShell PlatyPS](), [PowerShell](), [Markdown](), [PowerShell Release](), [Documentation](), [XML](), [GitHub]() Tags: [documentation](), [github](), [markdown](), [microsoft](), [net](), [powershell](), [powershell-platyps](), [release]() ### AI overview Microsoft announces the general availability of Microsoft.PowerShell.PlatyPS 1.0.0, a rewritten tool for authoring PowerShell help in Markdown and converting it to MAML XML. The release adds new cmdlets, improved help descriptions, an object model, cmdlet chaining, higher performance, and support for Windows, Linux, and macOS. ### Source excerpt We are pleased to announce the general availability of Microsoft.PowerShell.PlatyPS 1.0.0, a tool to build PowerShell help files. The post Announcing Microsoft.PowerShell.PlatyPS 1.0.0 appeared first on PowerShell Team. ## Where Are the NETCONF/YANG Tools? DevFeed: [Where Are the NETCONF/YANG Tools?]() Original publisher: [Read original article]() Published: 2025-06-04T05:38:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [NETCONF](), [Tooling](), [Network](), [Automation](), [XML]() Tags: [netconf](), [network](), [network-automation](), [tooling](), [xml]() ### AI overview The article examines difficulties finding reliable, current tooling for NETCONF/YANG network-device configuration and model inspection. It discusses ncclient's incomplete documentation, abandoned or outdated YANG tools, installation problems on modern Python versions, and the challenges of using Docker-based tooling. It mentions pyang as a possible tool and asks readers to recommend maintained alternatives. ### Source excerpt Jo attempted to follow the vendor Kool-Aid recommendations and use NETCONF/YANG to configure network devices. Here's what he found (slightly edited): IMHO, the whole NETCONF ecosystem primarily suffers from a tooling problem. Or I haven't found the right tools yet. ncclient is (as you mentioned somewhere else) an underdocumented mess. And that undocumented part is not even up to date. The commit hash at the bottom of the docs page is from 2020... I am amazed how so many people got it working well enough to depend on it in their applications. Read more ... ## Repost: On the Advantages of XML DevFeed: [Repost: On the Advantages of XML]() Original publisher: [Read original article]() Published: 2025-05-26T06:07:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [XML](), [JSON](), [NETCONF](), [Artificial Intelligence](), [Python](), [ChatGPT]() Tags: [ai](), [automation](), [chatgpt](), [json](), [netconf](), [python](), [xml]() ### AI overview This reposted discussion examines XML and JSON for network automation. It argues that XML's semantic structure can support reliable, maintainable automation despite XML's size and complexity, while describing mixed results from ChatGPT-generated XPath and Python code, including failures in a fuller ncclient solution. ### Source excerpt Continuing the discussion started by my Breaking APIs or Data Models Is a Cardinal Sin and Screen Scraping in 2025 blog posts, Dr. Tony Przygienda left another thoughtful comment worth reposting as a publicly visible blog post: Having read your newest rant around my rant ;-} I can attest that you hit the nail on the very head in basically all you say: XML output big? yeah. JSON squishy syntax? yeah. SSH prioritization? You didn't live it until you had a customer where a runaway python script generated 800+ XML netconf sessions pumping data ;-) Read more ... ## From ePA 2.6 to 3.0 : Healthcare Data Integration for Electronic Patient Records at HelloBetter DevFeed: [From ePA 2.6 to 3.0 : Healthcare Data Integration for Electronic Patient Records at HelloBetter]() Original publisher: [Read original article]() Author: Anna J McDougall Published: 2025-05-20T09:27:30Z Content type: tutorial Language: en Sources: [Anna J McDougall]() Topics: [data](), [implementation](), [Authentication](), [Back end](), [Front end](), [XML](), [pdf]() Tags: [authentication](), [backend](), [data](), [electronic-patient-record](), [engineering-management](), [export](), [frontend](), [germany](), [healthcare](), [healthtech](), [integration](), [pdf](), [pipeline](), [platform](), [product](), [project](), [software-architecture](), [technical](), [terminal]() ### AI overview This technical post describes HelloBetter's implementation journey from Germany's ePA 2.6 to ePA 3.0. It covers HealthID login, ePA data export, PDF and XML document writing, and the frontend and backend integrations used to connect therapeutic data across systems. The implementation was completed pending BfArm approval. ### Source excerpt From ePA 2.6 to 3.0: A Technical Journey in Healthcare Data Integration for Electronic Patient Records...so far Germany has a bad reputation for digitalisation, so the government's push to implement an electronic patient record ("elektronische Patientenakte" or ePA) for its citizens and residents is a step in the right direction. As an official digital health application ("digitale Gesundheitsapplikation" or "DiGA"), we are obligated to shift to the ePA 3.0 implementation. The government rollout has been plagued with technical difficulties and delays, but we're now at a point where we have completed our implementation successfully, pending BfArm approval. In this post, I want to cover the exact steps we and had to take to achieve this. I want to thank Senior Product Manager Tanja Lembcke and Senior Backend Engineer Chaythanya Sivakumar for their contributions to this piece. The Challenge: Connecting Patient Data Across Systems The electronic patient record (ePA) and HealthID integration project had a clear mission: we wanted to give our patients the ability to log into the HelloBetter platform using their HealthID (which they access through their insurance company) and export their HelloBetter data into their ePA. A successful implementation would mean that both doctors and patients can electronically access therapeutic data whenever they need it. To make this happen for the patient data at HelloBetter, we partnered with two key players: RISE for ePA system access and Azuma for HealthID system access. Our journey began in 2024 when our backend team laid the groundwork for ePA 2.6, setting up the pipeline and data export in our staging environment. We successfully implemented both PDF and XML document writing capabilities, along with the frontend and backend integrations for HealthID login. How It All Works: The Architectural SideHealthID Authentication The first piece of the puzzle is connecting to and authorising the user's HealthID. This part of the system has remai ## Screen Scraping in 2025 DevFeed: [Screen Scraping in 2025]() Original publisher: [Read original article]() Published: 2025-05-07T09:32:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Structured-data](), [JSON](), [XML](), [Parsing](), [Python]() Tags: [automation](), [blog-post](), [code](), [data](), [json](), [parsing](), [python](), [xml]() ### AI overview The article examines why screen scraping remains necessary for network devices that lack reliable JSON or XML output. It compares screen-scraped text with structured data, noting that JSON and XML can be larger and that manually generated or legacy structured output may be invalid or unavailable. It also argues that XML is generally harder to process than JSON, especially for large objects and data involving namespaces. ### Source excerpt Dr. Tony Przygienda left a very valid (off-topic) comment to my Breaking APIs or Data Models Is a Cardinal Sin blog post: If, on the other hand, the customers would not camp for literally tens of years on regex scripts scraping screens, lots of stuff could progress much faster. He's right, particularly from Juniper's perspective; they were the first vendor to use a data-driven approach to show commands. Unfortunately, we're still not living in a perfect world: Read more ... ## Inner Loop Agents DevFeed: [Inner Loop Agents]() Original publisher: [Read original article]() Published: 2025-04-19T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [Large Language Model](), [Tool](), [Parsing](), [Ollama](), [vllm](), [JSON](), [Reinforcement learning](), [XML]() Tags: [agents](), [anthropic](), [api](), [json](), [llm](), [ollama](), [openai](), [parsing](), [reinforcement-learning](), [tools](), [vllm](), [xml]() ### AI overview This article explains "inner loop agents," a design in which an LLM can parse and execute tool calls within the model-serving loop instead of returning control to a client. It discusses how software such as Ollama and vLLM handles model-specific tool-call formats and suggests that concurrent tool use during generation is a key motivation. ### Source excerpt What if an LLM could use tools directly? In this post I discuss a potentially divergent view of agents, where agents are less like systems and more like LLMs specially trained to solve problems with a specific set of tools. ## SAML roulette: the hacker always wins DevFeed: [SAML roulette: the hacker always wins]() Original publisher: [Read original article]() Author: Gareth Heyes Published: 2025-03-18T14:55:43Z Content type: article Language: en Sources: [PortSwigger Research]() Topics: [GitLab](), [Vulnerabilities](), [Security](), [XML](), [Exploit](), [Authentication](), [Authorization](), [Ruby](), [Library]() Tags: [attacks](), [authentication](), [authorization](), [exploit](), [github](), [gitlab](), [library](), [research](), [ruby](), [saml](), [security](), [testing](), [vulnerabilities](), [vulnerability](), [xml]() ### AI overview This security research post explains how round-trip attacks and namespace confusion in the ruby-saml library can be chained to bypass signature verification and obtain unauthenticated administrative access to GitLab Enterprise. It describes parser inconsistencies involving REXML and Nokogiri, XML mutations using comments and CDATA, and a testbed for evaluating SAML libraries. The supplied article text ends during the discussion of DOCTYPE analysis. ### Source excerpt Introduction In this post, we'll show precisely how to chain round-trip attacks and namespace confusion to achieve unauthenticated admin access on GitLab Enterprise by exploiting the ruby-saml library ## MDN 2024 content projects DevFeed: [MDN 2024 content projects]() Original publisher: [Read original article]() Author: vadim-makeev Published: 2025-01-08T00:00:00Z Content type: article Language: en Sources: [MDN Blog]() Topics: [Documentation](), [Web platform](), [HTTP](), [XML](), [Accessibility](), [LaTeX](), [math](), [HTML](), [Markdown]() Tags: [2025](), [accessibility](), [docs](), [html](), [http](), [latex](), [markdown](), [math](), [web-platform]() ### AI overview MDN Web Docs reviews its 2024 content projects, describing audits and updates to popular but outdated or incomplete material. The work focused on HTTP, MathML, and web Manifests, with particular detail on improved MathML documentation, examples, LaTeX annotations, browser compatibility data, and accessibility information. ### Source excerpt Let's have a look at MDN Web Docs content projects in 2024, with highlights of our top picks and recommended reading, and at what's next on MDN for 2025. [Next page]()