<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (rybesh)</title>
    <link>https://pinboard.in/u:rybesh/public/</link>
    <description>recent bookmarks from rybesh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://www.kqed.org/arts/12939686/avant-garde-musician-forrest-fang-on-the-art-of-the-double-life"/>
	<rdf:li rdf:resource="https://www.grubstreetproject.net/"/>
	<rdf:li rdf:resource="https://ruthtillman.com/post/openrefine-api-basics/"/>
	<rdf:li rdf:resource="https://treecg.github.io/specification/"/>
	<rdf:li rdf:resource="https://github.com/ThHanke/rdf-reasoner-konclude"/>
	<rdf:li rdf:resource="https://martinfowler.com/articles/what-is-code.html"/>
	<rdf:li rdf:resource="https://github.com/Scaseco/nqpatch-posix"/>
	<rdf:li rdf:resource="https://www.tigrisdata.com/blog/fifty-agents-one-bucket/"/>
	<rdf:li rdf:resource="https://ibusiness.bamboohr.com/careers/448"/>
	<rdf:li rdf:resource="https://huggingface.co/datasets/Aklakan/wikidata-sorted-nquads-and-diffs"/>
	<rdf:li rdf:resource="https://cidoc-crm.org/html/cidoc_crm_v7.1.3.html"/>
	<rdf:li rdf:resource="https://lbt.bibsoc.org.uk/index.php?title=London_Book_Trades"/>
	<rdf:li rdf:resource="https://kb-labb.github.io/easyaligner/get-started/overview.html"/>
	<rdf:li rdf:resource="https://www.loc.gov/catdir/cpso/roman.html"/>
	<rdf:li rdf:resource="https://github.com/atomotic/iiif/tree/main/cmd/mkiiif"/>
	<rdf:li rdf:resource="https://github.com/d-flood/triiiceratops/tree/main"/>
	<rdf:li rdf:resource="https://codeberg.org/phochste/notation3tests"/>
	<rdf:li rdf:resource="https://connectedplaces.online/the-purpose-of-protocols/"/>
	<rdf:li rdf:resource="https://github.com/rupertl/gridlock"/>
	<rdf:li rdf:resource="https://www.newsjunkie.net/article/introducing-guide-to-public-archives"/>
	<rdf:li rdf:resource="https://llmstxt.org/"/>
	<rdf:li rdf:resource="https://github.com/yaravind/knowledge-graph-rag-structured"/>
	<rdf:li rdf:resource="https://awslabs.github.io/SPARQL-CDTs/spec/latest.html"/>
	<rdf:li rdf:resource="https://github.com/DataTreehouse/maplib"/>
	<rdf:li rdf:resource="https://lu.is/2026/03/on-monsters-and-men/"/>
	<rdf:li rdf:resource="https://www.philschmid.de/agent-harness-2026"/>
	<rdf:li rdf:resource="https://isamples.org/"/>
	<rdf:li rdf:resource="https://deepseek.ai/blog/deepseek-engram-v4-architecture"/>
	<rdf:li rdf:resource="https://hitchdev.com/strictyaml/why/implicit-typing-removed/"/>
	<rdf:li rdf:resource="https://github.com/ruven/iipsrv"/>
	<rdf:li rdf:resource="https://uri4uri.is4.site/"/>
	<rdf:li rdf:resource="https://rednegra.net/blog/20260212-virtual-scroll/"/>
	<rdf:li rdf:resource="https://datatracker.ietf.org/doc/rfc8820/"/>
	<rdf:li rdf:resource="https://datatracker.ietf.org/doc/rfc3227/"/>
	<rdf:li rdf:resource="https://www.w3.org/International/questions/qa-address-formats"/>
	<rdf:li rdf:resource="https://w3c-facade-x.github.io/facade-x-metamodel/"/>
	<rdf:li rdf:resource="https://www.wwp.neu.edu/research/publications/documentation/other/dates_and_times_in_DH.xhtml"/>
	<rdf:li rdf:resource="https://github.com/git/git/blob/master/Documentation/gitdatamodel.adoc"/>
	<rdf:li rdf:resource="https://marketplace.visualstudio.com/items?itemName=marimo-team.vscode-marimo"/>
	<rdf:li rdf:resource="https://scholarsphere.psu.edu/resources/39688670-949f-4223-a31c-41afbade9135"/>
	<rdf:li rdf:resource="https://github.com/unum-cloud/usearch"/>
	<rdf:li rdf:resource="https://github.com/sdockray/spineless?tab=readme-ov-file"/>
	<rdf:li rdf:resource="https://journal.digitalmedievalist.org/article/id/8073/"/>
	<rdf:li rdf:resource="https://iscc.io/"/>
	<rdf:li rdf:resource="https://www.britishmuseum.org/collection/object/C_SSB-243-11"/>
	<rdf:li rdf:resource="https://github.com/typemytype/drawbot"/>
	<rdf:li rdf:resource="https://www.sqlite.org/fts5.html"/>
	<rdf:li rdf:resource="https://developer.mozilla.org/en-US/docs/Web/API/Media_Session_API"/>
	<rdf:li rdf:resource="https://github.com/DigiClass/LOD-People/tree/main/sample-data"/>
	<rdf:li rdf:resource="https://github.com/simonw/system-exploration-g/blob/main/src/system_prompt.md"/>
	<rdf:li rdf:resource="https://github.com/NatLibFi/Skosmos/wiki/Data-Model#deprecated-concepts"/>
	<rdf:li rdf:resource="https://github.com/ULB-Darmstadt/shacl-form"/>
	<rdf:li rdf:resource="https://github.com/rdf-ext/shacl-engine"/>
	<rdf:li rdf:resource="https://coar-notify.net/"/>
	<rdf:li rdf:resource="https://web.archive.org/web/20241009144707/https://ics.uci.edu/~alspaugh/cls/shr/allen.html"/>
	<rdf:li rdf:resource="https://litestar.dev/"/>
	<rdf:li rdf:resource="https://www.science.org/content/blog-post/stir-bars-can-t-be-ignored"/>
	<rdf:li rdf:resource="https://git.gammaspectra.live/git/go-away"/>
	<rdf:li rdf:resource="https://bas.codes/posts/python-slicing"/>
	<rdf:li rdf:resource="https://github.com/sparna-git/skos-play"/>
	<rdf:li rdf:resource="https://github.com/emdonahue/prov"/>
	<rdf:li rdf:resource="https://github.com/microsoft/markitdown"/>
	<rdf:li rdf:resource="https://3d.laboratorium.net/2025-01-02-a-quarter-century"/>
	<rdf:li rdf:resource="https://lists.apache.org/thread/cjwmdkp34mcsn8m4hvt2125mk9nqy3nt"/>
	<rdf:li rdf:resource="https://github.com/LingDong-/rrpl"/>
	<rdf:li rdf:resource="https://chinese-radical-vis.glitch.me/"/>
	<rdf:li rdf:resource="https://latin.stackexchange.com/questions/16006/why-is-tonos-sometimes-rendered-different-from-oxia"/>
	<rdf:li rdf:resource="https://github.com/rudof-project/rudof"/>
	<rdf:li rdf:resource="https://www.minizinc.org/"/>
	<rdf:li rdf:resource="https://forms.hypermedia.app/playground/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://www.kqed.org/arts/12939686/avant-garde-musician-forrest-fang-on-the-art-of-the-double-life">
    <title>Avant-Garde Musician Forrest Fang On the Art of the Double Life | KQED</title>
    <dc:date>2026-06-29T14:39:03+00:00</dc:date>
    <link>https://www.kqed.org/arts/12939686/avant-garde-musician-forrest-fang-on-the-art-of-the-double-life</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Over the course of our hour-long discussion, Fang references figures who have excited his musical imagination over the years: the still vital work of John Coltrane; the continuing explorations of legendary English guitarist Robert Fripp and Arizona synthesist Steve Roach; and another longtime local stalwart, his fellow sonic experimenter Robert Rich, with whom Fang has collaborated over the years.

Fang also gives a good deal of credit to another group of local performers when he discusses his musical development in the Bay Area: “I joined a group of Asian American musicians,” he recalls, “who were primarily into jazz — Miya Masaoka, Mark Izu, Francis Wong.” They invited him to participate in the San Francisco Gagaku Society, “a sort of a workshop Miya founded” in 1990. (Gagaku itself is an orchestral form of royal Japanese music developed over centuries, combining wind, stringed and percussive instruments in large ensembles.)]]></description>
<dc:subject>music</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7bf61755320b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:music"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.grubstreetproject.net/">
    <title>Topographies of Literature &amp; Culture in Eighteenth-Century London :: Grub Street Project</title>
    <dc:date>2026-05-28T13:51:07+00:00</dc:date>
    <link>https://www.grubstreetproject.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Grub Street Project is a digital edition of eighteenth-century London. By mapping its print culture, literature, and trades, it aims to create both a historically accurate visualization of the city's commerce and communications, and a record of how its authors and artists portrayed it.]]></description>
<dc:subject>printing history data visualization</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:458a548aab43/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:printing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ruthtillman.com/post/openrefine-api-basics/">
    <title>OpenRefine: API Basics and Repeat Operations | Ruth Kitchin Tillman</title>
    <dc:date>2026-05-13T22:58:55+00:00</dc:date>
    <link>https://ruthtillman.com/post/openrefine-api-basics/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[OpenRefine has an API. Not just for reconciliation, but an API you can use to perform actions from creating/deleting a project to blanking down columns and mass editing.]]></description>
<dc:subject>refine</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8734c471412b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:refine"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://treecg.github.io/specification/">
    <title>The TREE hypermedia specification</title>
    <dc:date>2026-05-13T21:50:33+00:00</dc:date>
    <link>https://treecg.github.io/specification/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The TREE specification provides instructions for clients to interpret and navigate Web APIs structured as search trees. It defines how members (sets of quads) in a dataset can be distributed across multiple pages interlinked through relationships. The specification introduces key concepts such as tree:Collection (a set of members), tree:Node (the pages in the search tree), and tree:Relation (links between nodes). By interpreting such qualified relations and search forms, TREE enables clients to efficiently retrieve their members of interest.

]]></description>
<dc:subject>hypermedia pagination versioning specification</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1574cd8f5f77/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pagination"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:versioning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:specification"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/ThHanke/rdf-reasoner-konclude">
    <title>ThHanke/rdf-reasoner-konclude: OWL-DL tableau reasoning via Konclude compiled to WebAssembly. Async TypeScript API — pass an N3.js Store, get inferred triples back.</title>
    <dc:date>2026-05-13T18:09:29+00:00</dc:date>
    <link>https://github.com/ThHanke/rdf-reasoner-konclude</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[OWL-DL tableau reasoning via Konclude compiled to WebAssembly. Async TypeScript API — pass an N3.js Store, get inferred triples back.]]></description>
<dc:subject>owl reasoner wasm</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:aaa710d7f54c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:owl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reasoner"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wasm"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://martinfowler.com/articles/what-is-code.html">
    <title>What Is Code?</title>
    <dc:date>2026-05-12T22:49:57+00:00</dc:date>
    <link>https://martinfowler.com/articles/what-is-code.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[What is code? At a high level, the answer to this question seems obvious. Code is what developers write: instructions expressed in a programming language that tells machines what to do. For years, writing code meant typing it out, word by word. Progress is measured by how efficiently code can be produced, compiled, tested and deployed. With modern LLMs we no longer need to type every word to produce code. Large amounts of executable code can now be generated from high-level descriptions. This forces a deeper question: If producing code becomes cheaper, what remains valuable about code?
]]></description>
<dc:subject>inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5198e816316e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/Scaseco/nqpatch-posix">
    <title>Scaseco/nqpatch-posix: Fast RDF patch creation and application of sorted N-Triples/N-Quads using only POSIX tools</title>
    <dc:date>2026-05-01T23:45:35+00:00</dc:date>
    <link>https://github.com/Scaseco/nqpatch-posix</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Command-line tools for efficiently patching large sorted N-Quads RDF files. Implemented as bash scripts backed by the POSIX tooling awk, sort, comm, and sed.
]]></description>
<dc:subject>rdf unix</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:52a2c8f51d1a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:unix"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.tigrisdata.com/blog/fifty-agents-one-bucket/">
    <title>Fifty agents for the price of one bucket | Tigris Object Storage</title>
    <dc:date>2026-04-30T23:43:22+00:00</dc:date>
    <link>https://www.tigrisdata.com/blog/fifty-agents-one-bucket/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[LanceDB and DuckDB both run as embedded libraries inside the agent process, not as separate servers you provision and manage. They read the Lance file directly from Tigris over S3, pulling only the columns and row groups each query needs. The data stays on storage; the compute runs wherever the agent runs. No database server in between, and both engines read the same file with no migration.]]></description>
<dc:subject>storage</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2c820505083f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:storage"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ibusiness.bamboohr.com/careers/448">
    <title>Knowledge Graph &amp; Ontology Engineer (AI Knowledge Representation) Product - Fort Lauderdale, Florida (Remote)</title>
    <dc:date>2026-04-26T12:19:27+00:00</dc:date>
    <link>https://ibusiness.bamboohr.com/careers/448</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Position Description

We are seeking an experienced Knowledge Graph & Ontology Engineer to design, implement, and govern the knowledge representation layer for next-generation AI systems. This role builds the foundational knowledge structures—ontologies, semantic models, knowledge graphs, provenance, and data fusion patterns—that enable AI agents and LLM applications to reason over enterprise knowledge reliably. You will collaborate closely with Retrieval/Relevance engineering, AI researchers, and data engineering to ensure our knowledge is well-structured, consistent, explainable, and evolvable.


Major Areas of Responsibility

       
         Knowledge Representation & Semantic Modeling

    Develop and maintain ontologies, knowledge graphs, and semantic data models to structure and integrate domain knowledge for improved reasoning and downstream retrieval.
    Define canonical entities, relationships, attributes, and constraints, including taxonomy/controlled vocabularies and semantic definitions.
    Establish schema versioning, governance, and backward compatibility strategies to evolve the knowledge model safely.

    Data Fusion & Knowledge Integration
    Aggregate disparate knowledge bases and heterogeneous data into a fused, consistent representation with clear semantics and lineage.
    Design integration patterns for structured + unstructured sources (e.g., documents → entities/relations) and maintain alignment across domains.

    Provenance, Lineage, and Data Quality
    Define and enforce provenance/lineage standards (source attribution, timestamps, confidence, auditability).
    Collaborate with pipeline engineers to implement validation rules and quality gates for knowledge graph construction (e.g., integrity constraints, anomaly detection).
    Cognitive Memory & Persistent Knowledge Structures (Representation View)
    Design representation primitives that support cognitive memory architectures for AI agents (identity, episodic traces, persistent facts, context scoping).

    Collaboration & Documentation
    Partner with Retrieval/Relevance engineering to define metadata contracts and “safe traversal” semantics for graph-aware retrieval.
    Maintain clear documentation of schemas, ontologies, knowledge modeling guidelines, and governance processes.
    Evaluate and integrate new technologies and research in knowledge representation and semantic modeling.


Required Knowledge, Skills, and Abilities

    Bachelor’s or Master’s degree in Computer Science, Data Science, Machine Learning, or related field (or equivalent experience).
    Proven experience building knowledge graphs, semantic data models, and/or enterprise knowledge bases.
    Experience with semantic technologies and standards (as applicable): RDF, OWL, SPARQL (or equivalent graph/ontology concepts).
    Strong foundations in data modeling, entity resolution/canonicalization, and schema governance.
    Proficiency in Python and working with data pipelines (in collaboration with data engineering).
    Excellent analytical, problem-solving, and cross-functional communication skills.


Nice To Haves

    Experience designing agent memory representations (episodic/semantic memory patterns, long-term context).
    Familiarity with LLM grounding patterns (provenance, citations, trust signals).
    Experience with graph databases and tooling (e.g., Neo4j/AWS Neptune equivalents).
    Experience with data-centric AI and training data quality assessment.



Primary Ownership (What success looks like)

    The knowledge model is correct, consistent, explainable, and governable.
    High-quality entity resolution + clean relationships + strong provenance coverage.
    Stable schemas that evolve without breaking downstream applications.



The anticipated salary range for this position is $180,000 - $240,000 annually, depending on experience and qualifications. iBusiness Funding provides a comprehensive benefits package, including medical, dental, and vision coverage; 401(k) with company match, and paid time off. ]]></description>
<dc:subject>inls620 jobs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:36b64260451a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:jobs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://huggingface.co/datasets/Aklakan/wikidata-sorted-nquads-and-diffs">
    <title>Aklakan/wikidata-sorted-nquads-and-diffs · Datasets at Hugging Face</title>
    <dc:date>2026-04-22T01:10:00+00:00</dc:date>
    <link>https://huggingface.co/datasets/Aklakan/wikidata-sorted-nquads-and-diffs</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This repository publishes byte-sorted Wikidata N-Triples (truthy statements) together with sorted RDF patches (RDF-Patch format).
Everything is plain-text, fully streamable, and compressed with bzip2 (.bz2).]]></description>
<dc:subject>wikidata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7734a842a2df/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wikidata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cidoc-crm.org/html/cidoc_crm_v7.1.3.html">
    <title>Classes &amp; Properties Declarations of CIDOC-CRM version: 7.1.3</title>
    <dc:date>2026-04-22T00:27:47+00:00</dc:date>
    <link>https://cidoc-crm.org/html/cidoc_crm_v7.1.3.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[CIDOC-CRM version 7.1.3 was released on February 2024 including 81 Classes and 160 Properties.

In current page, you can:

Navigate through Classes & Properties declarations of version 7.1.3 by:
Scrolling up/down the current page.
Using the hyperlinks defined for each Class or Property identifier (e.g. E1 CRM Entity).
Using the control located at the upper-right corner of this page (Click on 'Navigate to a section' text). Type any part of the Class or Property full name, and press Enter or select the preferred option in order to be automatically navigated to the relevant declaration.
Copy to clipboard a direct reference link to the Class or Property declaration, by clicking on the 'Link icon'  next to each entity name.
Navigate to the Translations & Versioning information of each Class or Property, by clicking on the 'Language icon'  next to each entity name.
Open the Class or Property hierarchical Graph, by clicking on the 'Graph icon'  next to each entity name.
Show all outgoing and incoming properties of each class, by clicking on the (show all properties) link next to each Class name. The list of outgoing and incoming properties includes both direct and inherited properties.]]></description>
<dc:subject>crm reference ontology</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:fe4fb23b8702/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:crm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://lbt.bibsoc.org.uk/index.php?title=London_Book_Trades">
    <title>London Book Trades</title>
    <dc:date>2026-04-22T00:26:27+00:00</dc:date>
    <link>https://lbt.bibsoc.org.uk/index.php?title=London_Book_Trades</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Bibliographical Society is pleased to present this new website building upon Michael Turner's original database.]]></description>
<dc:subject>bibliography</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3c5af09f0716/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliography"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://kb-labb.github.io/easyaligner/get-started/overview.html">
    <title>easyaligner</title>
    <dc:date>2026-04-19T10:52:41+00:00</dc:date>
    <link>https://kb-labb.github.io/easyaligner/get-started/overview.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[easyaligner is a forced alignment library for aligning text transcripts with audio. It is designed with a focus on ease of use, flexibility, and performance.]]></description>
<dc:subject>transcription</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:529e95840323/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:transcription"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.loc.gov/catdir/cpso/roman.html">
    <title>ALA-LC Romanization Tables</title>
    <dc:date>2026-03-30T23:38:06+00:00</dc:date>
    <link>https://www.loc.gov/catdir/cpso/roman.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The ALA-LC Romanization Tables are a set of standardized transliteration schemes developed jointly by the American Library Association (ALA) and the Library of Congress (LC) for converting text from non-Latin scripts into Latin characters for use in library catalogs and bibliographic records.]]></description>
<dc:subject>bibliography metadata language i18n</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c4bd2aa25d20/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:i18n"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/atomotic/iiif/tree/main/cmd/mkiiif">
    <title>iiif/cmd/mkiiif at main · atomotic/iiif</title>
    <dc:date>2026-03-23T20:26:10+00:00</dc:date>
    <link>https://github.com/atomotic/iiif/tree/main/cmd/mkiiif</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Generates a IIIF Presentation API v3 manifest from a directory of images or a PDF file.]]></description>
<dc:subject>IIIF</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:bd2775728ad7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:IIIF"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/d-flood/triiiceratops/tree/main">
    <title>d-flood/triiiceratops: A modern IIIF viewer with a small footprint (despite the name) distributed as a web component that can be dropped into any HTML page or frontend framework.</title>
    <dc:date>2026-03-23T20:25:49+00:00</dc:date>
    <link>https://github.com/d-flood/triiiceratops/tree/main</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A modern IIIF viewer with a small footprint (despite the name) distributed as a web component that can be dropped into any HTML page or frontend framework.]]></description>
<dc:subject>IIIF</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:40a4f71e86f4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:IIIF"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://codeberg.org/phochste/notation3tests">
    <title>phochste/notation3tests: A cross reasoner compliance test suite for the Notation3 language. - Codeberg.org</title>
    <dc:date>2026-03-22T20:56:03+00:00</dc:date>
    <link>https://codeberg.org/phochste/notation3tests</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A cross reasoner compliance test suite for the Notation3 language.
]]></description>
<dc:subject>n3 testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:695ad158f4c2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:n3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://connectedplaces.online/the-purpose-of-protocols/">
    <title>The Purpose of Protocols – Connected Places</title>
    <dc:date>2026-03-22T19:33:46+00:00</dc:date>
    <link>https://connectedplaces.online/the-purpose-of-protocols/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Stafford Beer, the management cybernetician, had a phrase for this kind of claim: ‘the purpose of a system is what it does.’ Not what it intends, not what its designers hope for, but what it produces. Applied to four decades of open protocol history, the pattern is consistent: protocol design can constrain how actors operate within a system, but it cannot ensure the conditions that keep the broader ecosystem functioning. The newer protocols engage with governance and power far more directly than their predecessors did, but the distance between architectural intent and operational reality has proven resistant to even the most thoughtful design.
]]></description>
<dc:subject>protocol design philosophy cybernetics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:009f109dbd86/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:protocol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:philosophy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cybernetics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/rupertl/gridlock">
    <title>rupertl/gridlock: Extract source code from line printer listing PDFs.</title>
    <dc:date>2026-03-18T17:20:50+00:00</dc:date>
    <link>https://github.com/rupertl/gridlock</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[There are a large number of computer programs of historical value where the only version remaining is a line printer listing scanned into a PDF. The code is often in uncommon languages and has particular format requirements, such as column positioning.

Often researchers want to extract the text, for analysis or to get it running again, but existing techniques to get source code text are not ideal. Traditional OCR (optical character recognition) systems do a poor job at positioning characters correctly on the page, and often stumble at accurately extracting computer code as they are trained on prose. You can always read the code and manually type it in again, but bitter experience shows that this is a tedious job and you will make many typos.

Gridlock is an attempt to address this, combining a grid segmenter with LLM (Large Language Model) OCR techniques to produce a fast and quite accurate result, with some manual intervention. The system uses the Google Gemini 2.5 Pro model right now, but with some coding it should work with other LLMs.]]></description>
<dc:subject>ocr code pdf</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2af0246b4f45/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ocr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pdf"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.newsjunkie.net/article/introducing-guide-to-public-archives">
    <title>Introducing: Newsjunkie’s Guide to Public Archives | Newsjunkie</title>
    <dc:date>2026-03-17T18:10:31+00:00</dc:date>
    <link>https://www.newsjunkie.net/article/introducing-guide-to-public-archives</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Newsjunkie.net is a resource guide for journalists. We show who's behind the news, and provide tools to help navigate the modern business of information.
]]></description>
<dc:subject>public archives</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d420810c24ac/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:public"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://llmstxt.org/">
    <title>The /llms.txt file – llms-txt</title>
    <dc:date>2026-03-13T19:01:39+00:00</dc:date>
    <link>https://llmstxt.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We propose adding a /llms.txt markdown file to websites to provide LLM-friendly content. This file offers brief background information, guidance, and links to detailed markdown files.]]></description>
<dc:subject>ai documentation standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5767b51d06b0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/yaravind/knowledge-graph-rag-structured">
    <title>yaravind/knowledge-graph-rag-structured: Graph RAG on structured data using maplib</title>
    <dc:date>2026-03-13T18:16:12+00:00</dc:date>
    <link>https://github.com/yaravind/knowledge-graph-rag-structured</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This project demonstrates a deterministic, high-precision Graph RAG system for structured data. It targets Data Scientists and AI Engineers who want to build reliable agents over tabular data without losing the semantic structure to vector embeddings.

]]></description>
<dc:subject>graphrag</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:251b2aaa0e24/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:graphrag"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://awslabs.github.io/SPARQL-CDTs/spec/latest.html">
    <title>SPARQL CDTs: Representing and Querying Lists and Maps as RDF Literals</title>
    <dc:date>2026-03-09T14:35:37+00:00</dc:date>
    <link>https://awslabs.github.io/SPARQL-CDTs/spec/latest.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This specification defines an approach to represent generic forms of composite values (lists and maps, in particular) as literals in RDF, and corresponding extensions of the SPARQL language. These extensions include an aggregation function to produce such composite values, functions to operate on such composite values in expressions, and a new operator to transform such composite values into their individual components.

]]></description>
<dc:subject>rdf sparql lists maps data structure specification</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1773659f1cac/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sparql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:lists"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:maps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:structure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:specification"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/DataTreehouse/maplib">
    <title>DataTreehouse/maplib</title>
    <dc:date>2026-03-09T14:32:01+00:00</dc:date>
    <link>https://github.com/DataTreehouse/maplib</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[maplib is written in Rust, it is built on Apache Arrow using Pola.rs and uses libraries from Oxigraph for handling linked data as well as parsing SPARQL queries.

maplib allows you to leverage your existing skills with Pandas or Polars to extract and wrangle data from existing databases and spreadsheets, before applying simple templates to them to build a knowledge graph. You can also read knowledge graphs extremely quickly from a wide variety of serialization formats. Using the built-in SPARQL, SHACL and Datalog engines means you can query, inspect, enrich and validate and then serialize the knowledge graph immediately. All query results are Polars Dataframes that are transferred zero-copy from Rust to Python. Currently, maplib is in-memory and supports around 100M triples on 32GB of RAM.]]></description>
<dc:subject>python rust rdf sparql shacl datalog polars</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b4c605d81df5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sparql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:shacl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:datalog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:polars"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://lu.is/2026/03/on-monsters-and-men/">
    <title>Of Monsters, Men, and Lawyers - lu.is</title>
    <dc:date>2026-03-05T02:32:47+00:00</dc:date>
    <link>https://lu.is/2026/03/on-monsters-and-men/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Programmers can be very bad about (1) because we tend to underestimate how much LLM-based coding tools have had massive investment in what are coming to be called “harnesses”: complex combinations of tooling+prompting+context that wrap the generalist LLM in a tight cocoon of specific knowledge about coding and codebases. So programmers tend to say “LLMs are great at coding” when what they really mean is “LLMs plus extremely extensive harnesses are great at coding”. This is an extremely important difference, and one that misleads non-programmers (and again, many programmers) into thinking that “LLMs” will be great at other fields without the big investment in harnesses.
Programmers are also bad about (1) because the biggest pot of money in the long history “sell pickaxes to miners” is at stake, so when I say “big investment” I mean literally hundreds of billions of dollars. Not yet so much in lawyer harnesses. Both developers and lawyers having this discussion need to remember that.
Lawyers cannot rest on our laurels. Our pot of money is still pretty big, so there will be broad and deep legal harnesses, most likely sooner rather than later. Those harnesses will have carefully crafted instructions and context, and will absolutely crush general-purpose tools + naive lawyer-drafted instructions. We’re not there yet, and I’m pretty skeptical that the existing duopoly will be the ones to produce those harnesses. (Harvey and Clio are of course both frantically trying to do this, but I haven’t been able to test them much yet.) But it absolutely will come, and thanks to aggregation theory, it is going to come for your niche no matter how niche you think it is.]]></description>
<dc:subject>agent harness law</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:72b1c511a95c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:agent"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:harness"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:law"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.philschmid.de/agent-harness-2026">
    <title>The importance of Agent Harness in 2026</title>
    <dc:date>2026-03-05T02:24:23+00:00</dc:date>
    <link>https://www.philschmid.de/agent-harness-2026</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We are heading toward a convergence of training and inference environments. We see a new bottleneck being context durability. The Harness will become the primary tool for solving "model drift". Labs will use the harness to detect exactly when a model stops following instructions or reasoning correctly after the 100th step. This data will be fed directly back into training to create models that don't get "tired" during long tasks.

As builders and developers the focus should shift:

Start Simple: Do not build massive control flows. Provide robust atomic tools. Let the model make the plan. Implement guardrails, retries and verifications.
Build to Delete: Make your architecture modular. New models will replace your logic. You must be ready to rip out code.
The Harness is the Dataset: Competitive advantage is no longer the prompt. It is the trajectories your Harness captures. Every time your agent fails to follow an instruction late in a workflow can be ued for training the next iteration.]]></description>
<dc:subject>agent harness</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b61341fad3bf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:agent"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:harness"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://isamples.org/">
    <title>Internet of Samples: iSamples – iSamples</title>
    <dc:date>2026-02-25T15:22:14+00:00</dc:date>
    <link>https://isamples.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Internet of Samples (iSamples) is a multi-disciplinary and multi-institutional project funded by the National Science Foundation to design, develop, and promote service infrastructure to uniquely, consistently, and conveniently identify material samples, record metadata about them, and persistently link them to other samples and derived digital content, including images, data, and publications.]]></description>
<dc:subject>identifiers samples collecting</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:233bde0a125a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:samples"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collecting"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://deepseek.ai/blog/deepseek-engram-v4-architecture">
    <title>DeepSeek Engram: V4 Architecture Revealed? Solving Transformer's Fatal Memory Flaw</title>
    <dc:date>2026-02-23T18:57:24+00:00</dc:date>
    <link>https://deepseek.ai/blog/deepseek-engram-v4-architecture</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Currently, Mixture of Experts (MoE) has become the mainstream architecture for large language models, powering systems like DeepSeek V3, Mixtral, and others. However, it's fundamentally still based on the Transformer architecture, which lacks a native "knowledge lookup" mechanism.
This means that many tasks that should be solved in O(1) time — like retrieving factual information — have to be "simulated" through extensive computations. The model essentially has to compute its way to remember things that could simply be looked up.
💡 Example: To identify the entity "Diana, Princess of Wales," an LLM has to consume multi-layer attention and FFN to gradually combine features. In theory, this process could be completed through a single knowledge lookup operation — like looking up a word in a dictionary.
The paper argues that this is fundamentally wasteful: using expensive compute cycles to repeatedly "rediscover" static knowledge that could be retrieved in constant time.]]></description>
<dc:subject>llm memory</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d0308ba3227a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:llm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:memory"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hitchdev.com/strictyaml/why/implicit-typing-removed/">
    <title>The Norway Problem - why StrictYAML refuses to do implicit typing and so should you - HitchDev</title>
    <dc:date>2026-02-22T20:43:13+00:00</dc:date>
    <link>https://hitchdev.com/strictyaml/why/implicit-typing-removed/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The most tragic aspect of this bug, however, is that it is intended behavior according to the YAML 1.2 specification. The real fix requires explicitly disregarding the spec - which is why most YAML parsers have it.

StrictYAML sidesteps this problem by ignoring key parts of the spec.]]></description>
<dc:subject>yaml standards parsing design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0d26e6255116/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:yaml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:parsing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/ruven/iipsrv">
    <title>GitHub - ruven/iipsrv: iipsrv is an advanced high-performance feature-rich image server for web-based streamed viewing and zooming of ultra high-resolution images.</title>
    <dc:date>2026-02-17T23:50:18+00:00</dc:date>
    <link>https://github.com/ruven/iipsrv</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[IIPImage is an advanced high-performance feature-rich image server system for web-based streamed viewing and zooming of ultra high-resolution images. It is designed to be fast and bandwidth-efficient with low processor and memory requirements. The system can comfortably handle gigapixel size images as well as advanced image features such as 8, 16 and 32 bits per channel, CIELAB colorimetric images and scientific imagery such as multispectral images, image sequences and 3D surface topologies.]]></description>
<dc:subject>IIIF</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5fc46b1262fc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:IIIF"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://uri4uri.is4.site/">
    <title>uri4uri</title>
    <dc:date>2026-02-17T22:42:16+00:00</dc:date>
    <link>https://uri4uri.is4.site/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The URI resolver just parses the URI to get the parts, then uses registries and external queries to retrieve information about MIME types, top-level domains and so forth. This data is taken from IANA and Wikidata and is periodically updated.

It accepts any possible URI, including web addresses, email addresses, ISBNs as well as some more obscure schemes such as Gopher.]]></description>
<dc:subject>inls620 web standards uri</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:78c8a3730815/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://rednegra.net/blog/20260212-virtual-scroll/">
    <title>Virtual Scrolling for Billions of Rows — Techniques from HighTable</title>
    <dc:date>2026-02-17T22:12:17+00:00</dc:date>
    <link>https://rednegra.net/blog/20260212-virtual-scroll/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[No need for a fake scroll bar. No need to render the table in a canvas. We use the Web platform. Thanks to these five techniques that rely on native HTML elements, hightable lets you navigate seamlessly through billions of rows of a remote data file, in the browser.]]></description>
<dc:subject>html css web design architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cf9777ba300f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://datatracker.ietf.org/doc/rfc8820/">
    <title>RFC 8820 - URI Design and Ownership</title>
    <dc:date>2026-02-16T18:39:43+00:00</dc:date>
    <link>https://datatracker.ietf.org/doc/rfc8820/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and
   extensible naming system wherein each scheme's specification may
   further restrict the syntax and semantics of identifiers using that
   scheme."  In other words, the structure of a URI is defined by its
   scheme.  While it is common for schemes to further delegate their
   substructure to the URI's owner, publishing independent standards
   that mandate particular forms of substructure in URIs is often
   problematic.

   This document provides guidance on the specification of URI
   substructure in standards.]]></description>
<dc:subject>uri design structure politics economics standard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8d636d09ed86/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:structure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://datatracker.ietf.org/doc/rfc3227/">
    <title>RFC 3227 - Guidelines for Evidence Collection and Archiving</title>
    <dc:date>2026-02-16T18:32:40+00:00</dc:date>
    <link>https://datatracker.ietf.org/doc/rfc3227/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A "security incident" as defined in the "Internet Security Glossary",
   RFC 2828, is a security-relevant system event in which the system's
   security policy is disobeyed or otherwise breached.  The purpose of
   this document is to provide System Administrators with guidelines on
   the collection and archiving of evidence relevant to such a security
   incident.]]></description>
<dc:subject>security archive evidence standard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7a6110bfc73d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archive"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:evidence"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/International/questions/qa-address-formats">
    <title>Address formats around the world</title>
    <dc:date>2026-02-03T13:22:29+00:00</dc:date>
    <link>https://www.w3.org/International/questions/qa-address-formats</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[How do address formats differ around the world, and what are the implications of those differences on the design of forms, databases, ontologies, etc. for the Web?

Address formats vary widely across the globe, with differences in structure, content, and the level of granularity. For authors and developers designing forms, databases, or systems that handle addresses, understanding these variations is crucial to avoid frustrating users from other countries. This article will introduce some of the key differences in address formats around the world and provide guidance on how to design systems that can handle them effectively.

This is not an exhaustive guide but aims to sensitize you to the complexities of international address formats and the challenges they pose for web design. As with personal names, there is no one specific "perfect" solution, but awareness of these differences is the first step toward building more inclusive systems.]]></description>
<dc:subject>addresses standards i18n</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2c918ab793e6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:addresses"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:i18n"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://w3c-facade-x.github.io/facade-x-metamodel/">
    <title>Façade-X concepts and meta model specification</title>
    <dc:date>2026-01-31T00:26:25+00:00</dc:date>
    <link>https://w3c-facade-x.github.io/facade-x-metamodel/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Façade-X is the (meta-)model resulting from the abstraction of all the basic data structures used to represent source data formats, combined into a unified model. RDF languages can implement it to provide users direct access to external, heterogeneus data formats.]]></description>
<dc:subject>data modeling rdf</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b62876598659/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.wwp.neu.edu/research/publications/documentation/other/dates_and_times_in_DH.xhtml">
    <title>Dates and Times in DH An annotated application profile of ISO 8601:2019 for use with TEI and other DH systems</title>
    <dc:date>2026-01-22T00:21:22+00:00</dc:date>
    <link>https://www.wwp.neu.edu/research/publications/documentation/other/dates_and_times_in_DH.xhtml</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The purpose of this document is to give readers information and guidance on how to write dates, times, intervals, and durations, along with any inherent imprecision or uncertainty, such that the representation conforms to ISO 8601:2019, and thus can be used on the TEI when-iso attribute. This document is not intended to be an exhaustive tutorial on ISO 8601:2019, although in large part it could serve as such for many of the features of the standard.]]></description>
<dc:subject>temporal reference standards howto tei</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0cdb8d76062a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:temporal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tei"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/git/git/blob/master/Documentation/gitdatamodel.adoc">
    <title>git/Documentation/gitdatamodel.adoc at master · git/git</title>
    <dc:date>2026-01-13T13:55:12+00:00</dc:date>
    <link>https://github.com/git/git/blob/master/Documentation/gitdatamodel.adoc</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[It’s not necessary to understand Git’s data model to use Git, but it’s very helpful when reading Git’s documentation so that you know what it means when the documentation says "object", "reference" or "index".]]></description>
<dc:subject>git documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:877a754260f0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://marketplace.visualstudio.com/items?itemName=marimo-team.vscode-marimo">
    <title>marimo - Visual Studio Marketplace</title>
    <dc:date>2026-01-13T13:40:33+00:00</dc:date>
    <link>https://marketplace.visualstudio.com/items?itemName=marimo-team.vscode-marimo</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A marimo notebook extension for VS Code.]]></description>
<dc:subject>inls560</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c2ce003113b1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls560"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://scholarsphere.psu.edu/resources/39688670-949f-4223-a31c-41afbade9135">
    <title>Hollinger's Edge: The Retrieval Object at the Margins of the Archival Ontology</title>
    <dc:date>2025-12-01T19:11:11+00:00</dc:date>
    <link>https://scholarsphere.psu.edu/resources/39688670-949f-4223-a31c-41afbade9135</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Archival resources are frequently described in two parallel representations: as intellectual groupings that facilitate discovery, and as physical inventories that facilitate retrieval and requesting. At the time a researcher requests to use material, it must be possible to map the intellectual grouping to the corresponding retrieval object. In this paper, we analyze three emerging archival linked data standards (BIBFRAME-ARM, Records in Contexts, and Linked.Art) from the perspective of retrieval. We find that only Linked.Art is currently capable of representing retrieval objects natively, and that neither BIBFRAME-ARM nor Records in Contexts are semantically interoperable with archival inventory management or requesting.]]></description>
<dc:subject>archives linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f8cd98bbfbcb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/unum-cloud/usearch">
    <title>unum-cloud/USearch: Fast Open-Source Search &amp; Clustering engine × for Vectors &amp; Arbitrary Objects × in C++, C, Python, JavaScript, Rust, Java, Objective-C, Swift, C#, GoLang, and Wolfram 🔍</title>
    <dc:date>2025-11-13T19:53:54+00:00</dc:date>
    <link>https://github.com/unum-cloud/usearch</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Smaller & Faster Single-File Similarity Search & Clustering Engine for Vectors & 🔜 Texts]]></description>
<dc:subject>clustering search database vectors</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3b2a6b016f20/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:clustering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vectors"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/sdockray/spineless?tab=readme-ov-file">
    <title>sdockray/spineless: Custom PDF viewer based on PDF.JS</title>
    <dc:date>2025-11-10T19:40:49+00:00</dc:date>
    <link>https://github.com/sdockray/spineless?tab=readme-ov-file</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a different way of reading PDFs.]]></description>
<dc:subject>pdf reading software ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cad8fa27c2a3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://journal.digitalmedievalist.org/article/id/8073/">
    <title>Illumination Detection in IIIF Medieval Manuscripts Using Deep Learning | Digital Medievalist</title>
    <dc:date>2025-10-30T15:08:51+00:00</dc:date>
    <link>https://journal.digitalmedievalist.org/article/id/8073/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Illuminated manuscripts are essential iconographic sources for medieval studies. With the massive adoption of IIIF, old and new digital collections of manuscripts are accessible online and provide interoperable image data. However, finding illuminations within the manuscripts’ pages is increasingly time consuming. This article proposes an approach based on machine learning and transfer learning that browses IIIF manuscript pages and detects the illuminated ones. To evaluate our approach, a group of domain experts created a new dataset of manually annotated IIIF manuscripts. The preliminary results show that our algorithm detects the main illuminated pages in a manuscript, thus reducing experts’ search time.]]></description>
<dc:subject>detection</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3772a85bb80d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:detection"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://iscc.io/">
    <title>ISCC - International Standard Content Code |</title>
    <dc:date>2025-10-15T00:39:00+00:00</dc:date>
    <link>https://iscc.io/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The ISCC is an open-source technology that enables the identification, attribution, and management of digital content across various platforms and industries. It provides a unique, decentralized and content-derived identifier for any type of digital media, including text, images, audio, and video.]]></description>
<dc:subject>identifiers media</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ad41392e9b64/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:media"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.britishmuseum.org/collection/object/C_SSB-243-11">
    <title>medal | British Museum</title>
    <dc:date>2025-10-08T20:30:12+00:00</dc:date>
    <link>https://www.britishmuseum.org/collection/object/C_SSB-243-11</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A string of severed heads surrounds a decapitated French aristocrat whose head is falling to the ground. The devil can be seen in the distance. There are two inscriptions one inside the string of severed heads and one outside.]]></description>
<dc:subject>politics history museum</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6a9910e1a56d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:museum"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/typemytype/drawbot">
    <title>typemytype/drawbot</title>
    <dc:date>2025-09-18T18:22:07+00:00</dc:date>
    <link>https://github.com/typemytype/drawbot</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[DrawBot is a powerful, free application for macOS that invites you to write Python scripts to generate two-dimensional graphics. The built-in graphics primitives support rectangles, ovals, (bezier) paths, polygons, text objects, colors, transparency and much more. You can program multi-page documents and stop-motion animations. Export formats include PDF, SVG, PNG, JPEG, TIFF, animated GIF and MP4 video.]]></description>
<dc:subject>python drawing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0ef5612e6477/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:drawing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.sqlite.org/fts5.html">
    <title>SQLite FTS5 Extension</title>
    <dc:date>2025-08-25T16:06:51+00:00</dc:date>
    <link>https://www.sqlite.org/fts5.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[FTS5 is an SQLite virtual table module that provides full-text search functionality to database applications. In their most elementary form, full-text search engines allow the user to efficiently search a large collection of documents for the subset that contain one or more instances of a search term. The search functionality provided to world wide web users by Google is, among other things, a full-text search engine, as it allows users to search for all documents on the web that contain, for example, the term "fts5".

]]></description>
<dc:subject>sqlite database search</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1b1689513688/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sqlite"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:search"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developer.mozilla.org/en-US/docs/Web/API/Media_Session_API">
    <title>Media Session API - Web APIs | MDN</title>
    <dc:date>2025-08-11T16:15:50+00:00</dc:date>
    <link>https://developer.mozilla.org/en-US/docs/Web/API/Media_Session_API</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Media Session API provides a way to customize media notifications. It does this by providing metadata for display by the user agent for the media your web app is playing.

]]></description>
<dc:subject>audio media web api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4c10119a5e1f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:audio"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:media"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/DigiClass/LOD-People/tree/main/sample-data">
    <title>LOD-People/sample-data at main · DigiClass/LOD-People</title>
    <dc:date>2025-08-11T15:51:46+00:00</dc:date>
    <link>https://github.com/DigiClass/LOD-People/tree/main/sample-data</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This directory contains sample person data in a range of (currently unspecified) open formats. Data needs to be open licensed, or a sample published under an open license with permission of the rightsholder.]]></description>
<dc:subject>people modeling linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7dba411e36fd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:people"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/simonw/system-exploration-g/blob/main/src/system_prompt.md">
    <title>system-exploration-g/src/system_prompt.md at main · simonw/system-exploration-g</title>
    <dc:date>2025-08-11T15:47:15+00:00</dc:date>
    <link>https://github.com/simonw/system-exploration-g/blob/main/src/system_prompt.md</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[You are a web coding playground generating runnable code micro-apps ("sparks"). This guide helps you produce experiences that are not only functional but aesthetically refined and emotionally resonant.]]></description>
<dc:subject>web design manifesto</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2eff42c282b6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:manifesto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/NatLibFi/Skosmos/wiki/Data-Model#deprecated-concepts">
    <title>Data Model · NatLibFi/Skosmos Wiki</title>
    <dc:date>2025-08-11T15:45:03+00:00</dc:date>
    <link>https://github.com/NatLibFi/Skosmos/wiki/Data-Model#deprecated-concepts</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Deprecated concepts are concepts that are no longer valid but are kept in the vocabulary for backward compatibility. Skosmos can detect that a concept has been deprecated if the concept data includes:

owl:deprecated true metadata
optionally, dcterms:isReplacedBy relationships pointing to the concepts (one or multiple) that replace this one
Example:

ex:old a skos:Concept ;
  owl:deprecated true ;
  skos:prefLabel "Old concept that has been replaced by a new concept"@en ;
  dct:isReplacedBy ex:new .
Deprecated concepts will not be visible in the alphabetical listing, in the hierarchical view, and cannot be found with the search, unless the option skosmos:showDeprecated is set to true in the vocabularies configuration file. However, deprecated concepts can still be accessed through their URI in both the web user interface and the API.

The concept page of a deprecated concept includes a notification element that informs the user that the concept has been deprecated, and if possible links to the concept that should be used instead (The following link illustrates how Skosmos visualizes deprecated concepts: http://finto.fi/yso/en/page/p3410).]]></description>
<dc:subject>linkeddata deprecation periodo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:de061b319bb2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:deprecation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:periodo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/ULB-Darmstadt/shacl-form">
    <title>ULB-Darmstadt/shacl-form: HTML5 web component for editing/viewing RDF data that conform to SHACL shapes</title>
    <dc:date>2025-08-11T15:44:01+00:00</dc:date>
    <link>https://github.com/ULB-Darmstadt/shacl-form</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[HTML5 web component for editing/viewing RDF data that conform to SHACL shapes.]]></description>
<dc:subject>shacl ui web component</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d3be9124d996/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:shacl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:component"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/rdf-ext/shacl-engine">
    <title>rdf-ext/shacl-engine: A fast RDF/JS SHACL engine</title>
    <dc:date>2025-08-11T15:43:19+00:00</dc:date>
    <link>https://github.com/rdf-ext/shacl-engine</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A fast SHACL engine for data provided as RDF/JS objects.]]></description>
<dc:subject>SHACL javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:bde4eabf2bdf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:SHACL"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://coar-notify.net/">
    <title>COAR Notify: COAR Notify</title>
    <dc:date>2025-08-11T15:21:40+00:00</dc:date>
    <link>https://coar-notify.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The COAR Notify Protocol is a set of profiles, constraints and conventions around the use of W3C Linked Data Notifications (LDN) to integrate repository systems with relevant services in a distributed, resilient and web-native architecture.]]></description>
<dc:subject>notification protocol repository scholarlycommunication infrastructure</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:470c6221f6c4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:notification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:protocol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:repository"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarlycommunication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:infrastructure"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://web.archive.org/web/20241009144707/https://ics.uci.edu/~alspaugh/cls/shr/allen.html">
    <title>Allen’s interval algebra</title>
    <dc:date>2025-08-11T15:17:41+00:00</dc:date>
    <link>https://web.archive.org/web/20241009144707/https://ics.uci.edu/~alspaugh/cls/shr/allen.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In 1983 James F. Allen published a paper [Allen1983-mkti] in which he proposed thirteen basic relations between time intervals that are distinct, exhaustive, and qualitative. 

distinct because no pair of definite intervals can be related by more than one of the relationships
exhaustive because any pair of definite intervals are described by one of the relations
qualitative (rather than quantitative) because no numeric time spans are considered
These relations and the operations on them form Allen's interval algebra.]]></description>
<dc:subject>time temporal reasoning modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5f3c4dc93fc3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:temporal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reasoning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://litestar.dev/">
    <title>Litestar | Effortlessly Build Performant APIs</title>
    <dc:date>2025-08-08T00:06:18+00:00</dc:date>
    <link>https://litestar.dev/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[It’s not trying to be the next Django or the next Flask or whatever; instead, it feels to me like a Pythonic take on the good parts of something like Spring Boot (and the way I like to set it up, doing things like using svcs behind the scenes as a service locator to feed things to both Litestar’s and pytest’s dependency injection, makes it feel even more that way).]]></description>
<dc:subject>python web</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:eb3e897e98a9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.science.org/content/blog-post/stir-bars-can-t-be-ignored">
    <title>Stir Bars Can't Be Ignored | Science | AAAS</title>
    <dc:date>2025-06-20T21:37:06+00:00</dc:date>
    <link>https://www.science.org/content/blog-post/stir-bars-can-t-be-ignored</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[So as painful as it might be, we should be devoting more thought to this sort of thing, at the very least to the level of mentioning the size of the flasks/vials used and the associated stirbars, and (for reproducibility’s sake) trying to insure that these are in a stable non-banging non-hopping regime during the reaction. Details, everything is down there in the details. . .
]]></description>
<dc:subject>science metadata description methods reproducibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:90ad5e6adaef/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:methods"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reproducibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://git.gammaspectra.live/git/go-away">
    <title>git/go-away: Self-hosted abuse detection and rule enforcement against low-effort mass AI scraping and bots. - GammaSpectra.Live Git</title>
    <dc:date>2025-06-02T19:07:52+00:00</dc:date>
    <link>https://git.gammaspectra.live/git/go-away</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Self-hosted abuse detection and rule enforcement against low-effort mass AI scraping and bots. Uses conventional non-nuclear options.

]]></description>
<dc:subject>sysadmin</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e3bbde06fd32/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sysadmin"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://bas.codes/posts/python-slicing">
    <title>A Comprehensive Guide to Slicing in Python - Bas codes</title>
    <dc:date>2025-03-05T15:42:53+00:00</dc:date>
    <link>https://bas.codes/posts/python-slicing</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In Python, some objects like strs or lists can sliced.]]></description>
<dc:subject>python tutorial inls560</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:462a0af9d3fa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls560"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/sparna-git/skos-play">
    <title>sparna-git/skos-play: SKOS-Play allows to print SKOS files in HTML or PDF. It also embeds xls2rdf to generate RDF from Excel.</title>
    <dc:date>2025-02-12T19:20:50+00:00</dc:date>
    <link>https://github.com/sparna-git/skos-play</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[With SKOS Play you can :

Print / visualize thesaurus
Convert Excel tables to SKOS
Validate SKOS files]]></description>
<dc:subject>skos visualization</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:50510a273119/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:skos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/emdonahue/prov">
    <title>emdonahue/prov: Automatic Makefile generation and management for provenance tracking from command line history</title>
    <dc:date>2025-01-24T16:28:11+00:00</dc:date>
    <link>https://github.com/emdonahue/prov</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[prov is a zshell function that contains a collection of subcommands for generating and managing makefiles automatically from your commandline history. Useful for datascience projects that involve extended pipelines of exploratory data processing and file manipulation from the command line.

]]></description>
<dc:subject>make provenance shell</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6acceb4c779c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:make"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:provenance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:shell"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/microsoft/markitdown">
    <title>microsoft/markitdown: Python tool for converting files and office documents to Markdown.</title>
    <dc:date>2025-01-15T15:06:57+00:00</dc:date>
    <link>https://github.com/microsoft/markitdown</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[MarkItDown is a utility for converting various files to Markdown (e.g., for indexing, text analysis, etc).]]></description>
<dc:subject>markdown pdf ocr python text</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b66f4d662cd2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ocr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:text"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://3d.laboratorium.net/2025-01-02-a-quarter-century">
    <title>A Quarter Century of Statutory Interpretation | The Laboratorium (3d ser.)</title>
    <dc:date>2025-01-15T15:00:13+00:00</dc:date>
    <link>https://3d.laboratorium.net/2025-01-02-a-quarter-century</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[By my reckoning, the FCC has treated broadband Internet as an information service, then a telecommunications service, then an information service again, then a telecommunications service again, and is now poised to treat it as an information service for a third time. At various times, federal appellate courts have held that the Telecommunications Act can be read to treat broadband Internet as a telecommunications service, must be read to treat broadband Internet as an telecommunications service, can be read to treat broadband Internet as an information service, and must be read to treat broadband Internet as an information service.

Is this any way to run an information superhighway?]]></description>
<dc:subject>telecom law policy</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c62895d7b4db/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:telecom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:policy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://lists.apache.org/thread/cjwmdkp34mcsn8m4hvt2125mk9nqy3nt">
    <title>Re: &lt;file:/path&gt; is imported as &lt;file:///path&gt;-Apache Mail Archives</title>
    <dc:date>2025-01-07T12:03:54+00:00</dc:date>
    <link>https://lists.apache.org/thread/cjwmdkp34mcsn8m4hvt2125mk9nqy3nt</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In RDF, by definition, all URI are resolved against the base URI and  there is always a base URI of some kind.]]></description>
<dc:subject>rdf uri standard standards semweb inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d69bf7ee762a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/LingDong-/rrpl">
    <title>LingDong-/rrpl: Describing Chinese Characters with Recursive Radical Packing Language (RRPL)</title>
    <dc:date>2025-01-04T02:42:50+00:00</dc:date>
    <link>https://github.com/LingDong-/rrpl</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Recursive Radical Packing Language (RRPL) is a proposal for a method of describing arbitrary Chinese characters concisely while retaining their structural information. Potential fields for usage include font design and machine learning. In RRPL, each Chinese character is described as a short string of numbers, symbols, and references to other characters. Its syntax is inspired by markup languages such as LaTeX, as well as the traditional "米" grids used for calligraphy practice.

]]></description>
<dc:subject>fonts typography visualization language systems</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:adce13655775/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:fonts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:typography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:systems"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://chinese-radical-vis.glitch.me/">
    <title>chinese-radical-vis</title>
    <dc:date>2025-01-04T02:40:01+00:00</dc:date>
    <link>https://chinese-radical-vis.glitch.me/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Visualizations & animations of Chinese ideograms and radicals.]]></description>
<dc:subject>visualization fonts</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d7195f1b729c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:fonts"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://latin.stackexchange.com/questions/16006/why-is-tonos-sometimes-rendered-different-from-oxia">
    <title>typography - Why is tonos (sometimes) rendered different from oxia? - Latin Language Stack Exchange</title>
    <dc:date>2024-12-10T01:07:54+00:00</dc:date>
    <link>https://latin.stackexchange.com/questions/16006/why-is-tonos-sometimes-rendered-different-from-oxia</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The difference between tonos and oxia.

See also <https://lists.apache.org/thread/bry7zdrw2lvgkh9m7r3mzbfhcp46t8sb>.]]></description>
<dc:subject>unicode normalization uri latin</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:197e900a5839/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:unicode"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:normalization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:latin"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/rudof-project/rudof">
    <title>rudof-project/rudof: RDF data shapes implementation in Rust</title>
    <dc:date>2024-12-03T16:23:30+00:00</dc:date>
    <link>https://github.com/rudof-project/rudof</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This repo contains an RDF data shapes library implemented in Rust. The implementation supports ShEx, SHACL, DCTap and conversions between different RDF data modeling formalisms.

]]></description>
<dc:subject>rdf SHACL tools rust</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e711b7d43d71/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:SHACL"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rust"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.minizinc.org/">
    <title>MiniZinc</title>
    <dc:date>2024-12-03T14:29:08+00:00</dc:date>
    <link>https://www.minizinc.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[MiniZinc is a high-level constraint modelling language that allows you to easily express and solve discrete optimisation problems.
]]></description>
<dc:subject>optimization constraints modeling language</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c64f8ce7203c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:optimization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:constraints"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://forms.hypermedia.app/playground/">
    <title>@hydrofoil/shaperone lit-html playground</title>
    <dc:date>2024-11-20T12:16:06+00:00</dc:date>
    <link>https://forms.hypermedia.app/playground/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[SHACL UI playground]]></description>
<dc:subject>SHACL ui inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:fdf961636857/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:SHACL"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>