Gist 302c3f0062de516f2d53

100%

Gist 302c3f0062de516f2d53

✓ Published0🌍 Public

Last edited Jun 15, 2015

Created on Jun 15, 2015

This example demonstrates filtering Atom feed entries by category using a StAX parser. It reads an XML file and extracts the text content of `<title>` and `<category>` elements, printing only titles whose category contains “HTML.” The code relies on the `javax.xml.stream` API, specifically `XMLInputFactory`, `XMLEventReader`, and `XMLStreamConstants`, to iterate through events. It handles `START_ELEMENT` cases to capture element text via `parser.getElementText()`, while skipping other event types. The data source is a local file path (`webtec.atom.xml`), and error handling uses a try-catch block that outputs any exception message.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist f72a3553521c158f0eb0dccbe774455e

This example demonstrates a web scraper that extracts detailed trail information from a hiking website. It shows how structured data can be programmatically retrieved from HTML pages, specifically pulling out features, overview, and description sections. The code uses the Nokogiri library to parse the document and XPath queries to locate the relevant heading elements. After extracting each section, it cleans the text by removing newlines and excess whitespace. The scraper returns a hash containing the three descriptive fields, making the data readily accessible for further processing or visualization.

WWill Carter

57% match

Loading thumbnail…

Happy Gilmore

This example transforms an XML movie collection into a styled HTML list using XSLT. The stylesheet matches the root `<collection>` element and iterates over each `<movie>`, extracting the title, year, and genre with `xsl:value-of`. The output is a tan-background page with unordered lists per movie, styled via embedded CSS in the `<style>` block. It demonstrates client-side XML-to-HTML conversion through the `movies.xsl` stylesheet, relying solely on XSLT 1.0 template matching and `xsl:for-each` loops—no JavaScript libraries are involved.

Aamundo

56% match

Loading thumbnail…

{$title || " - "}

This example displays a list of EAD (Encoded Archival Description) titles sorted alphabetically from a collection of finalized XML files, rendered as plain paragraph elements in an XHTML page. It uses XQuery 3.1 with the `fn:collection` function to gather titles from `titleproper[@type="filing"]` nodes, and a local template function `local:template` constructs the HTML output, setting a dynamic heading level and tab title. The code demonstrates a server-side, XML-to-HTML transformation pipeline without client-side JavaScript libraries or interactive visualization components.

CCliffordAnderson

56% match

Loading thumbnail…

Gist 5ea363dfe112d08281a8c89a3f31bcff

This example scrapes trail data from a website, extracting features, overview, and description sections into a structured hash. It uses Nokogiri to parse the HTML and XPath queries to locate the relevant headings and their adjacent content, cleaning the text by removing line breaks. The code demonstrates a straightforward scraping pattern for capturing semantic sections, though it does not include visualization logic or rendering libraries. The data source is a single trail page URL, and the output is a formatted description ready for further processing or display.

WWill Carter

55% match

Loading thumbnail…

<title>Testing XPath

This example demonstrates how an XML TEI document’s structure can be queried using XPath and represented as an interactive node-link diagram. It displays the document’s hierarchical elements—such as `teiHeader`, `text`, `body`, and `p`—as circles connected by links, with text content visible alongside node labels. The visualization uses D3.js’s `d3.hierarchy` and `d3.tree` layout to calculate positions, while `d3.zoom` enables panning and zooming. The code loads the XML via a local file and parses it with `DOMParser`, then applies XPath expressions via `document.evaluate` to extract elements and text for rendering.

CCliffordAnderson

55% match

Loading thumbnail…

a simple parser for simple eaf files

This example parses ELAN annotation files into structured sentence data, extracting media references, time-aligned annotations, and translation tiers from the XML. It uses the DOM `querySelectorAll` API to navigate the EAF structure, building a time-slot index for resolving timestamps. The parser sorts sentences chronologically and merges referenced annotations with their alignable counterparts. It demonstrates a lightweight approach for converting EAF files into JSON-ready objects for further visualization or analysis.

Aamundo

55% match

Loading thumbnail…

A simple news crawler.

This example demonstrates a news crawler that fetches headlines from four Malaysian RSS feeds, extracts the full article text, and stores each story as a JSON file organized by publication date. The crawler uses `feedparser` to parse RSS feeds, `requests` to download article pages, and the `readability` library to isolate main content from HTML. `BeautifulSoup` cleans the extracted text, while `dateutil.parser` converts publication timestamps into structured day, month, and year fields. Each JSON file, saved in a local `collection` folder, contains the article’s cleaned content, original link, and parsed date components.

Aamirothman

54% match

Loading thumbnail…

Gist 2a036239a620a1b1a6ee

This example demonstrates a stopword filtering visualization. It shows a collection of common English words—"the," "a," "in," "of," and "as"—rendered as a simple text list, visually distinguishing them from a larger text corpus. The implementation uses an XML-based data structure to define the stopword set, which is then parsed and displayed. The code relies on standard browser APIs for XML parsing and DOM manipulation, presenting the filtered words in a clean, readable format. The visualization makes no attempt at complex layout or animation, instead offering a straightforward, static view of which terms are excluded from analysis, with the underlying data sourced directly from the embedded XML file.

CCliffordAnderson

54% match