Sample MVC for William

100%

Sample MVC for William

✓ Published0🌍 Public

Last edited Apr 25, 2017

Created on Apr 25, 2017

This example demonstrates a simple Model-View-Controller architecture for generating an HTML listing of the first 50 article titles from a TEI XML collection. It shows how an XQuery REST endpoint (`%rest:path`) routes requests to a controller function, which delegates rendering to a separate view module. The view uses standard XQuery functions like `fn:collection` and `element` to transform TEI-encoded text segments directly into HTML paragraphs.

AI-generated description

Similar vizzes

Loading thumbnail…

Experiments with XQuery, RESTXQ, and MVC in BaseX

This example demonstrates a model-view-controller (MVC) architecture for serving a web-based corpus of Charles Baudelaire’s poems, with XQuery functions defining RESTful routes. It shows how BaseX’s RESTXQ annotations (`%rest:path`, `%rest:GET`) map URLs like `/`, `/about`, and `/contents` to controller functions, while a separate view module generates XHTML pages with Bootstrap styling. The model module queries the `fleurs-du-mal` collection to extract contributor names and poem titles for dynamic content. The code highlights XQuery’s role in both server-side logic and HTML templating, without any client-side JavaScript or charting libraries.

CCliffordAnderson

73% match

Loading thumbnail…

{$title}

This example demonstrates a minimal XQuery web application for the Corpus Baudelaire project, serving static XHTML pages and dynamic poem routes. It shows how RESTXQ annotations declare endpoints for the root path, an about page, a credits page, and a parameterized poem URL, with each route returning a simple HTML document via a shared display function. The code relies on the RESTXQ API for request routing and the XQuery standard library for string concatenation and element construction, though it renders no actual data visualization.

CCliffordAnderson

67% match

Loading thumbnail…

Render module for search namespace

This example shows how TEI-encoded play texts can be rendered into a formatted HTML view, using the `render:render` and `render:recurse` functions to map XML elements like `tei:head`, `tei:speaker`, and `tei:stage` to headings, bold labels, and paragraphs. It relies on XQuery’s `typeswitch` and recursion to process the document tree, while the `render:titles` function generates a hyperlinked table of contents from a list of play elements. The code directly uses the XQuery 3.0 module system and the `declare function` syntax, with no external JavaScript libraries.

CCliffordAnderson

62% 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

61% match

Loading thumbnail…

This example of recursive descent in XQuery is adapted from Joe Wicentowski (https://gist.github.com/joewiz/2331558#file-typeswitch-skeleton-xq). It rather naively formats scenes from the Folger Library Shakespeare TEI editions for display in HTML. This example is intended for the demonstration of the concept, not actual use.

This example shows recursive descent in XQuery rendering scenes from a Folger Library Shakespeare TEI edition into HTML. It demonstrates how a typeswitch pattern matches distinct TEI elements—such as `tei:head`, `tei:w`, `tei:stage`, and `tei:speaker`—to produce formatted output like headings, stage directions, and speaker labels. The code relies on XQuery 3.0’s built-in `typeswitch` and function recursion, using `local:render` and `local:recurse` to traverse the XML tree. It serializes to XHTML via `exist:serialize`, pulling the source document from `/db/shakespeare/JC.xml` without external libraries.

CCliffordAnderson

61% match

Loading thumbnail…

For Arne

This example visualizes the structure of a single TEI-encoded article by extracting metadata from an XML source and rendering it as a document-tree diagram. It shows the hierarchical relationships between the article’s title, author, issue, and page-range fields, emphasizing how the original bibliographic data maps onto the TEI structure. The visualization uses an XQuery script with XPath queries to pull specific values, such as the issue and article numbers via regular-expression replacement, and the starting/ending pages from the `biblScope`. The rendering then relies on a force-directed layout (via `d3.forceSimulation`) to position nodes, with each node representing a TEI element and links showing parent–child dependencies. The data source is the gist’s embedded TEI file, and the output is a static SVG generated client-side, reflecting the parsed metadata without additional interaction.

CCliffordAnderson

60% match

Loading thumbnail…

BaseX Server

This example shows a minimal RESTful web application built with BaseX, a native XML database, that serves XHTML pages for a poetry corpus. The code defines four GET endpoints—root, `/about`, `/credits`, and `/poem/{name}`—each returning a simple HTML page via the `view:display-contents` function. The implementation uses BaseX’s RESTXQ annotations (`%rest:path`, `%rest:GET`) and XQuery modules (`api.xqm`, `model.xqm`, `view.xqm`). The `model:credits` function supplies static HTML content, while the view module constructs the page skeleton. Data is hardcoded in XQuery, with no external datasets or JavaScript libraries involved.

CCliffordAnderson

59% match

Loading thumbnail…

Error 404

This example demonstrates a RESTful API built with BaseX and XQuery, returning dynamic XML responses for various routes, including a custom 404 error page. It shows how URL path parameters and HTTP status codes are handled through the `%rest:path` and `%rest:GET` annotations, with a fallback error handler that issues a 404 status. The code uses the `rest` and `http` output serialization, while the model and view modules (model.xqm and view.xqm) separate data retrieval—querying ORCID person names—from presentation, rendering lists as HTML paragraphs. No client-side visualization libraries are involved; the focus is on server-side routing and structured data delivery.

CCliffordAnderson

58% match