<?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://uri4uri.is4.site/"/>
	<rdf:li rdf:resource="https://rednegra.net/blog/20260212-virtual-scroll/"/>
	<rdf:li rdf:resource="https://developer.mozilla.org/en-US/docs/Web/API/Media_Session_API"/>
	<rdf:li rdf:resource="https://github.com/simonw/system-exploration-g/blob/main/src/system_prompt.md"/>
	<rdf:li rdf:resource="https://github.com/ULB-Darmstadt/shacl-form"/>
	<rdf:li rdf:resource="https://litestar.dev/"/>
	<rdf:li rdf:resource="https://designsystem.digital.gov/"/>
	<rdf:li rdf:resource="https://developer.mozilla.org/en-US/docs/Web/API/Web_components"/>
	<rdf:li rdf:resource="https://github.com/standard-webhooks/standard-webhooks/blob/main/spec/standard-webhooks.md"/>
	<rdf:li rdf:resource="https://graphorigami.org/"/>
	<rdf:li rdf:resource="https://component.kitchen/elix"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/privacy-principles/"/>
	<rdf:li rdf:resource="https://www.c82.net/euclid/en/"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/dx-prof-conneg/#motivation"/>
	<rdf:li rdf:resource="https://swi-prolog.discourse.group/t/swi-prolog-in-the-browser-using-wasm/5650"/>
	<rdf:li rdf:resource="https://til.simonwillison.net/pytest/playwright-pytest"/>
	<rdf:li rdf:resource="https://dthompson.us/projects/haunt.html"/>
	<rdf:li rdf:resource="https://www.haskellforall.com/2022/05/generate-web-forms-from-pure-functions.html"/>
	<rdf:li rdf:resource="https://www.cogsci.ed.ac.uk/~ht/WhatAreURIs/index.html"/>
	<rdf:li rdf:resource="https://www.cogsci.ed.ac.uk/~ht/justSayHTTP.html"/>
	<rdf:li rdf:resource="https://webflow.com/"/>
	<rdf:li rdf:resource="https://lists.w3.org/Archives/Public/public-whatwg-archive/2009Jan/0213.html"/>
	<rdf:li rdf:resource="https://www.smashingmagazine.com/2021/03/complete-guide-accessible-front-end-components/"/>
	<rdf:li rdf:resource="https://www.w3.org/2020/maps/report"/>
	<rdf:li rdf:resource="https://www.starlette.io/"/>
	<rdf:li rdf:resource="https://wicg.github.io/change-password-url/"/>
	<rdf:li rdf:resource="https://sitejs.org/"/>
	<rdf:li rdf:resource="https://hstspreload.org/"/>
	<rdf:li rdf:resource="https://bitworking.org/news/2019/07/looking-back-on-five-years-of-web-components"/>
	<rdf:li rdf:resource="https://tools.ietf.org/html/draft-yasskin-webpackage-use-cases-01"/>
	<rdf:li rdf:resource="https://webliteracy.pressbooks.com/"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/charmod/"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/charmod-norm/"/>
	<rdf:li rdf:resource="https://www.crossref.org/blog/whats-that-doi/"/>
	<rdf:li rdf:resource="https://w3ctag.github.io/webcomponents-design-guidelines/"/>
	<rdf:li rdf:resource="https://github.com/webcomponents/gold-standard/wiki"/>
	<rdf:li rdf:resource="https://webxray.org/"/>
	<rdf:li rdf:resource="https://mrs.digital/blog/schema-markup-dummies-mrs-guide-2018/"/>
	<rdf:li rdf:resource="https://manu.ninja/webgl-3d-model-viewer-using-three-js/"/>
	<rdf:li rdf:resource="https://hacks.mozilla.org/2017/08/intersection-observer-comes-to-firefox/"/>
	<rdf:li rdf:resource="https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html"/>
	<rdf:li rdf:resource="http://www.dlib.org/dlib/november15/vandesompel/11vandesompel.html"/>
	<rdf:li rdf:resource="http://commoncrawl.org/2016/09/robotstxt-and-404-redirect-data-sets/"/>
	<rdf:li rdf:resource="http://webconcepts.info/"/>
	<rdf:li rdf:resource="http://www.openarchives.org/rs/1.0/resourcesync#Introduction"/>
	<rdf:li rdf:resource="https://commoncrawl.org/"/>
	<rdf:li rdf:resource="http://dret.github.io/webdata/"/>
	<rdf:li rdf:resource="https://www.w3.org/WAI/PF/aria-practices/"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/sdw-bp/"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/webmention/"/>
	<rdf:li rdf:resource="https://github.com/ikreymer/pywb"/>
	<rdf:li rdf:resource="https://github.com/codeforscience/webdata/issues/5"/>
	<rdf:li rdf:resource="https://github.com/substack/omega-projects/issues/8"/>
	<rdf:li rdf:resource="https://web.archive.org/web/20150413151619/https://www.flickr.com/groups/central/discuss/9375/"/>
	<rdf:li rdf:resource="http://3dhop.net/"/>
	<rdf:li rdf:resource="http://linked-research.270a.info/#conceptual-design"/>
	<rdf:li rdf:resource="https://github.com/jbenet/go-ipfs"/>
	<rdf:li rdf:resource="http://ipfs.io/"/>
	<rdf:li rdf:resource="http://netpreserve.org/sites/default/files/resources/OverviewFutureWebWorkshop.pdf"/>
	<rdf:li rdf:resource="http://site.ebrary.com/lib/uncch/detail.action?docID=10494632"/>
	<rdf:li rdf:resource="https://github.com/TryGhost/Ghost/issues/2144"/>
	<rdf:li rdf:resource="http://go-to-hellman.blogspot.com/2014/12/stop-making-web-surveillance-bugs-by.html"/>
	<rdf:li rdf:resource="http://enable-cors.org/"/>
	<rdf:li rdf:resource="http://dashes.com/anil/2012/12/the-web-we-lost.html"/>
	<rdf:li rdf:resource="http://www.theatlantic.com/technology/archive/2014/08/advertising-is-the-internets-original-sin/376041/"/>
	<rdf:li rdf:resource="http://www.wired.co.uk/news/archive/2014-02/06/tim-berners-lee-reclaim-the-web"/>
	<rdf:li rdf:resource="http://tools.ietf.org/html/rfc7252"/>
	<rdf:li rdf:resource="http://www.w3.org/ns/formats/"/>
	<rdf:li rdf:resource="http://tools.ietf.org/html/rfc3986#section-4.4"/>
	<rdf:li rdf:resource="http://tools.ietf.org/html/draft-ietf-urnbis-urns-are-not-uris-00"/>
      </rdf:Seq>
    </items>
  </channel><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://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/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/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://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://designsystem.digital.gov/">
    <title>USWDS: The United States Web Design System | U.S. Web Design System (USWDS)</title>
    <dc:date>2024-07-07T18:38:10+00:00</dc:date>
    <link>https://designsystem.digital.gov/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[USWDS provides principles, guidance, and code to help you design and build accessible, mobile-friendly government websites and digital services.]]></description>
<dc:subject>web design standards government</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:063f2cf6ef70/</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:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:government"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developer.mozilla.org/en-US/docs/Web/API/Web_components">
    <title>Web Components - Web APIs | MDN</title>
    <dc:date>2024-01-16T20:43:49+00:00</dc:date>
    <link>https://developer.mozilla.org/en-US/docs/Web/API/Web_components</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Web Components is a suite of different technologies allowing you to create reusable custom elements — with their functionality encapsulated away from the rest of your code — and utilize them in your web apps.

]]></description>
<dc:subject>web ui components documentation tutorial</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e43d8f152c93/</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:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:components"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tutorial"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/standard-webhooks/standard-webhooks/blob/main/spec/standard-webhooks.md">
    <title>standard-webhooks/spec/standard-webhooks.md at main · standard-webhooks/standard-webhooks · GitHub</title>
    <dc:date>2023-12-08T12:28:52+00:00</dc:date>
    <link>https://github.com/standard-webhooks/standard-webhooks/blob/main/spec/standard-webhooks.md</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Webhooks are a common name for HTTP callbacks, and are a way for services to notify each other of events. Webhooks are part of a service's API, though you can think of them as a sort of a "reverse API". When a client wants to make a request to a service they make an API call, and when the service wants to notify the client of an event the service triggers a webhook ("a user has paid", "task has finished", etc.).

]]></description>
<dc:subject>web distributed networking howto standard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c7d62cfce8f2/</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:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://graphorigami.org/">
    <title>Web Origami</title>
    <dc:date>2023-11-28T02:03:35+00:00</dc:date>
    <link>https://graphorigami.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Web Origami is a research project exploring ideas and tools for building a wide variety of software artifacts and digital content. The system encourages you to view creating such things as an exercise in transformation: you take your starting files, data, etc., and transform them step-by-step into a final result you can use and share.

]]></description>
<dc:subject>web architecture ideas</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:769cbee5436e/</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:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ideas"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://component.kitchen/elix">
    <title>Elix - Component Kitchen</title>
    <dc:date>2023-11-28T02:02:49+00:00</dc:date>
    <link>https://component.kitchen/elix</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Elix is an open collection of high-quality web components for common user interface patterns such as lists, menus, dialogs, carousels, and so on. The modular nature of web components let you easily incorporate them into your web apps, and their standard definition ensures good results across all mainstream browsers.]]></description>
<dc:subject>web components ui library</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:092e3074b55d/</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:components"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:library"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/privacy-principles/">
    <title>Privacy Principles</title>
    <dc:date>2023-03-26T14:47:46+00:00</dc:date>
    <link>https://www.w3.org/TR/privacy-principles/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Privacy is an essential part of the Web. This document provides definitions for privacy and related concepts that are applicable worldwide as well as a set of privacy principles that should guide the development of the Web as a trustworthy platform. People using the Web would benefit from a stronger relationship between technology and policy, and this document is written to work with both.

]]></description>
<dc:subject>web privacy w3c</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:04d8b8cec388/</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:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:w3c"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.c82.net/euclid/en/">
    <title>Byrne’s Euclid</title>
    <dc:date>2023-02-18T00:28:34+00:00</dc:date>
    <link>https://www.c82.net/euclid/en/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A reproduction of Oliver Byrne’s celebrated work from 1847 plus interactive diagrams, cross references, and posters designed by Nicholas Rougeux.]]></description>
<dc:subject>web design geometry diagrams typography</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a9850a2de49d/</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:geometry"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:diagrams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:typography"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/dx-prof-conneg/#motivation">
    <title>Content Negotiation by Profile</title>
    <dc:date>2022-09-01T15:01:42+00:00</dc:date>
    <link>https://www.w3.org/TR/dx-prof-conneg/#motivation</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document describes how Internet clients may negotiate for content provided by servers based on data profiles to which the content conforms. This is distinct from negotiating by Media Type or Language: a profile may specify the content of information returned, which may be a subset of the information the responding server has about the requested resource, and may be structured in a specific way to meet interoperability requirements of a community of practice.]]></description>
<dc:subject>web standards schema data model</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8ea7a68b063c/</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:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:schema"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:model"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://swi-prolog.discourse.group/t/swi-prolog-in-the-browser-using-wasm/5650">
    <title>SWI-Prolog in the browser using WASM - Wiki - SWI-Prolog</title>
    <dc:date>2022-08-11T15:27:57+00:00</dc:date>
    <link>https://swi-prolog.discourse.group/t/swi-prolog-in-the-browser-using-wasm/5650</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This topic discusses running SWI-Prolog in your browser using WASM (Web Assembler).]]></description>
<dc:subject>prolog wasm web inference</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8ac7bda9fc8c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:prolog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wasm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inference"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://til.simonwillison.net/pytest/playwright-pytest">
    <title>Using pytest and Playwright to test a JavaScript web application | Simon Willison’s TILs</title>
    <dc:date>2022-08-10T21:55:25+00:00</dc:date>
    <link>https://til.simonwillison.net/pytest/playwright-pytest</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[playwright-pytest, which lets you write tests in Python using Microsoft's Playwright browser automation library.]]></description>
<dc:subject>python web ui testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c04de05142f3/</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:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://dthompson.us/projects/haunt.html">
    <title>Haunt — dthompson</title>
    <dc:date>2022-08-10T21:47:35+00:00</dc:date>
    <link>https://dthompson.us/projects/haunt.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Haunt is a simple, functional, hackable static site generator that gives authors the ability to treat websites as Scheme programs.]]></description>
<dc:subject>tools web html lisp</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c43f13c7992e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:lisp"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.haskellforall.com/2022/05/generate-web-forms-from-pure-functions.html">
    <title>Haskell for all: Generate web forms from pure functions</title>
    <dc:date>2022-06-01T17:05:26+00:00</dc:date>
    <link>https://www.haskellforall.com/2022/05/generate-web-forms-from-pure-functions.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This project is a web page which can dynamically convert a wide variety of functional programming expressions to their equivalent HTML. This conversion can even auto-generate interactive web forms from functions, which means that people without web programming knowledge can use the Grace browser to create and share simple and interactive web pages.]]></description>
<dc:subject>functional programming web language</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:365c72a90cd8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:functional"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.cogsci.ed.ac.uk/~ht/WhatAreURIs/index.html">
    <title>What's a URI and why does it matter?</title>
    <dc:date>2022-04-22T16:06:26+00:00</dc:date>
    <link>https://www.cogsci.ed.ac.uk/~ht/WhatAreURIs/index.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[It's worth exploring with some care what URIs were meant to be, and how they are being used in practice. In particular, I want to look at what illumination might be contributed from our understanding of how other kinds of identifiers work.]]></description>
<dc:subject>web identifiers uri inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4b9da9c22482/</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:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.cogsci.ed.ac.uk/~ht/justSayHTTP.html">
    <title>Dirk and Nadia design a naming schemeorWeb naming schemes good practices</title>
    <dc:date>2022-04-22T15:57:00+00:00</dc:date>
    <link>https://www.cogsci.ed.ac.uk/~ht/justSayHTTP.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Existing Web technologies and specifications offer a wide range of options to anyone embarking on a project which involves the creation and management of Web-enabled names. As a result, for anyone attempting to follow the above advice, a question immediately arises, namely "What kind of URIs should agents provide?"

This document is intended to supplement AWWW by addressing this question, for which AWWW does not provide much help.]]></description>
<dc:subject>web identifiers inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:52e4dcb0f58b/</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:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://webflow.com/">
    <title>Webflow: Create a custom website | No-code website builder</title>
    <dc:date>2021-12-09T01:58:04+00:00</dc:date>
    <link>https://webflow.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Webflow is used by more than 3,500,000 designers and teams to create, collaborate on, and scale beautiful websites in a completely visual canvas — no coding needed. ]]></description>
<dc:subject>web design tool</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ee7a60cd6728/</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:tool"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://lists.w3.org/Archives/Public/public-whatwg-archive/2009Jan/0213.html">
    <title>[whatwg] RDFa is to structured data, like canvas is to bitmap and SVG is to vector from Dan Brickley on 2009-01-18 (whatwg@whatwg.org from January 2009)</title>
    <dc:date>2021-09-23T19:24:08+00:00</dc:date>
    <link>https://lists.w3.org/Archives/Public/public-whatwg-archive/2009Jan/0213.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Capsule history of RDF from Dan Brickley.]]></description>
<dc:subject>rdf web history</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:db44e4044e16/</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:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.smashingmagazine.com/2021/03/complete-guide-accessible-front-end-components/">
    <title>A Complete Guide To Accessible Front-End Components — Smashing Magazine</title>
    <dc:date>2021-03-22T21:55:57+00:00</dc:date>
    <link>https://www.smashingmagazine.com/2021/03/complete-guide-accessible-front-end-components/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Reliable accessible components: from tabs and tables to toggles and tooltips.]]></description>
<dc:subject>web accessibility reference</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6fca13021ead/</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:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/2020/maps/report">
    <title>Report on the Joint W3C-OGC Workshop on Maps for the Web — W3C/OGC Joint Workshop Series on Maps for the Web</title>
    <dc:date>2021-02-14T17:53:53+00:00</dc:date>
    <link>https://www.w3.org/2020/maps/report</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The workshop organizers want to make map viewers on the web better — more usable, accessible, secure, private, and performant — for website visitors and web app users. At the same time, we want to make it easier for web developers and other creators to build those map-based experiences. And we want to make it more natural for cartographers and geospatial researchers to share their content over the web.]]></description>
<dc:subject>web maps standards cartography</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:30d8830c8d32/</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:maps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cartography"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.starlette.io/">
    <title>Starlette</title>
    <dc:date>2020-11-15T23:50:11+00:00</dc:date>
    <link>https://www.starlette.io/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Starlette is a lightweight ASGI framework/toolkit, which is ideal for building high performance asyncio services.

]]></description>
<dc:subject>python web framework</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:faf9865ca51a/</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:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://wicg.github.io/change-password-url/">
    <title>A Well-Known URL for Changing Passwords</title>
    <dc:date>2020-09-04T23:19:58+00:00</dc:date>
    <link>https://wicg.github.io/change-password-url/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This specification defines a well-known URL that sites can use to make their change password forms discoverable by tools. This simple affordance provides a way for software to help the user find the way to change their password.]]></description>
<dc:subject>web standard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3e2e4d28a3f4/</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:standard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://sitejs.org/">
    <title>Site.js</title>
    <dc:date>2020-01-02T17:48:06+00:00</dc:date>
    <link>https://sitejs.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Develop, test, and deploy your secure static or dynamic personal web site with zero configuration.]]></description>
<dc:subject>web hosting tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7af7fcf4b107/</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:hosting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hstspreload.org/">
    <title>HSTS Preload List Submission</title>
    <dc:date>2019-10-03T16:20:34+00:00</dc:date>
    <link>https://hstspreload.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In order to be accepted to the HSTS preload list through this form, your site must satisfy the following set of requirements:
Serve a valid certificate.
Redirect from HTTP to HTTPS on the same host, if you are listening on port 80.
Serve all subdomains over HTTPS.
In particular, you must support HTTPS for the www subdomain if a DNS record for that subdomain exists.
Serve an HSTS header on the base domain for HTTPS requests:
The max-age must be at least 31536000 seconds (1 year).
The includeSubDomains directive must be specified.
The preload directive must be specified.
If you are serving an additional redirect from your HTTPS site, that redirect must still have the HSTS header (rather than the page it redirects to).]]></description>
<dc:subject>web security https ssl</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5e3eb1c37144/</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:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:https"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ssl"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://bitworking.org/news/2019/07/looking-back-on-five-years-of-web-components">
    <title>Looking back on five years of web components</title>
    <dc:date>2019-08-01T08:20:41+00:00</dc:date>
    <link>https://bitworking.org/news/2019/07/looking-back-on-five-years-of-web-components</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[“A la carte” web development does away with the framework, and says just use the browser for the model, and the rest of the pieces you pick and choose the ones that work for you.]]></description>
<dc:subject>web development architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b47501701ada/</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:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://tools.ietf.org/html/draft-yasskin-webpackage-use-cases-01">
    <title>draft-yasskin-webpackage-use-cases-01 - Use Cases and Requirements for Web Packages</title>
    <dc:date>2019-05-10T01:17:49+00:00</dc:date>
    <link>https://tools.ietf.org/html/draft-yasskin-webpackage-use-cases-01</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[People would like to use content offline and in other situations
   where there isn't a direct connection to the server where the content
   originates.  However, it's difficult to distribute and verify the
   authenticity of applications and content without a connection to the
   network.  The W3C has addressed running applications offline with
   Service Workers ([ServiceWorkers]), but not the problem of
   distribution.

   Previous attempts at packaging web resources (e.g.  Resource Packages
   [3] and the W3C TAG's packaging proposal [4]) were motivated by
   speeding up the download of resources from a single server, which is
   probably better achieved through other mechanisms like HTTP/2 PUSH,
   possibly augmented with a simple manifest of URLs a page plans to use
   [5].  This attempt is instead motivated by avoiding a connection to
   the origin server at all.  It may still be useful for the earlier use
   cases, so they're still listed, but they're not primary.]]></description>
<dc:subject>web standards archives</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1cbe90e02eaf/</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:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://webliteracy.pressbooks.com/">
    <title>Web Literacy for Student Fact-Checkers – Simple Book Production</title>
    <dc:date>2019-02-04T18:11:07+00:00</dc:date>
    <link>https://webliteracy.pressbooks.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is an unabashedly practical guide for the student fact-checker. It supplements generic information literacy with the specific web-based techniques that can get you closer to the truth on the web more quickly.]]></description>
<dc:subject>digital web literacy facts</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:03bb1c7aae26/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digital"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:literacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:facts"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/charmod/">
    <title>Character Model for the World Wide Web 1.0: Fundamentals</title>
    <dc:date>2019-02-04T15:47:47+00:00</dc:date>
    <link>https://www.w3.org/TR/charmod/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The word 'character' is used in many contexts, with different meanings. Human cultures have radically differing writing systems, leading to radically differing concepts of a character. Such wide variation in end user experience can, and often does, result in misunderstanding. This variation is sometimes mistakenly seen as the consequence of imperfect technology. Instead, it derives from the great flexibility and creativity of the human mind and the long tradition of writing as an important part of the human cultural heritage. The alphabetic approach used by scripts such as Latin, Cyrillic and Greek is only one of several possibilities.

EXAMPLE: A character in Japanese hiragana and katakana scripts corresponds to a syllable (usually a combination of consonant plus vowel).

EXAMPLE: Korean Hangul combines symbols for individual sounds of the language into square blocks, each of which represents a syllable. Depending on the user and the application, either the individual symbols or the syllabic clusters can be considered to be characters.

EXAMPLE: In Indic scripts each consonant letter carries an inherent vowel that is eliminated or replaced using semi-regular or irregular ways to combine consonants and vowels into clusters. Depending on the user and the application, either individual consonants or vowels, or the consonant or consonant-vowel clusters can be perceived as characters.

EXAMPLE: In Arabic and Hebrew vowel sounds are typically not written at all. When they are written they are indicated by the use of combining marks placed above and below the consonantal letters.]]></description>
<dc:subject>text writing standards web unicode</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:77806f203275/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:writing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:unicode"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/charmod-norm/">
    <title>Character Model for the World Wide Web: String Matching</title>
    <dc:date>2019-02-04T15:46:03+00:00</dc:date>
    <link>https://www.w3.org/TR/charmod-norm/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This part of the Character Model for the World Wide Web covers string matching—the process by which a specification or implementation defines whether two string values are the same or different from one another. It describes the ways in which texts that are semantically equivalent can be encoded differently and the impact this has on matching operations important to formal languages (such as those used in the formats and protocols that make up the Web).]]></description>
<dc:subject>unicode text web standards semantics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:90893cdd7af6/</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:text"/>
	<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:semantics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.crossref.org/blog/whats-that-doi/">
    <title>What's that DOI? - Crossref</title>
    <dc:date>2019-01-22T18:24:06+00:00</dc:date>
    <link>https://www.crossref.org/blog/whats-that-doi/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[If I understand this correctly, it looks like the infrastructure is becoming available to make it possible to automatically resolve a publisher URL to a DOI. Since publishers increasingly seem to be intentionally hiding DOIs so that people will share the publisher URL instead, that is A Good Thing]]></description>
<dc:subject>doi identifiers web sharing metadata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:29205b80d3ac/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:doi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sharing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://w3ctag.github.io/webcomponents-design-guidelines/">
    <title>Guidelines for creating web platform compatible components</title>
    <dc:date>2019-01-04T15:01:14+00:00</dc:date>
    <link>https://w3ctag.github.io/webcomponents-design-guidelines/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Web components allow you to create encapsulated custom elements on the web platform, but how can you make sure that those elements actually follow common guidelines in such a way that useful elements fit in well with the rest of the platform? The TAG believes this is important so that users don’t feel like they are dealing with mismatched APIs and also a requirement if any of these elements were to end up in the HTML standard.]]></description>
<dc:subject>web component standard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f34ed7df5e02/</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:component"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/webcomponents/gold-standard/wiki">
    <title>Home · webcomponents/gold-standard Wiki</title>
    <dc:date>2019-01-04T14:54:59+00:00</dc:date>
    <link>https://github.com/webcomponents/gold-standard/wiki</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a working draft of a checklist to define a "gold standard" for web components that aspire to be as predictable, flexible, reliable, and useful as the standard HTML elements. The fundamental premise of this list is that it should not only be possible to attain that standard; people creating web components for general consumption should aim to meet that standard. These items are focused on designing good components; there are many other good principles for designing good user interfaces at the page or application level which are not listed here.]]></description>
<dc:subject>web components ui standard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:837a35df6a68/</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:components"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://webxray.org/">
    <title>webxray</title>
    <dc:date>2018-09-06T20:11:54+00:00</dc:date>
    <link>https://webxray.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[webxray is a tool for analyzing third-party content on webpages and identifying the companies which collect user data. A command line user interface makes webxray easy to use for non-programmers, and those with advanced needs may analyze millions of pages with proper configuration. webxray is a professional tool designed for academic research, and may be used by privacy compliance officers, regulators, and those who are generally curious about hidden data flows on the web.]]></description>
<dc:subject>web infrastructure transparency surveillance privacy</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b6c2ab32efdf/</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:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:transparency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:surveillance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:privacy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mrs.digital/blog/schema-markup-dummies-mrs-guide-2018/">
    <title>Schema Markup Guide for Dummies:2018| An MRS Guide</title>
    <dc:date>2018-08-20T13:30:29+00:00</dc:date>
    <link>https://mrs.digital/blog/schema-markup-dummies-mrs-guide-2018/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a pretty good specimen of JSONLD-without-RDF.]]></description>
<dc:subject>jsonld metadata web searchengine howto rdf</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cbaa6f4c6010/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:jsonld"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:searchengine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://manu.ninja/webgl-3d-model-viewer-using-three-js/">
    <title>WebGL 3D Model Viewer Using three.js | manu.ninja</title>
    <dc:date>2018-08-16T18:18:36+00:00</dc:date>
    <link>https://manu.ninja/webgl-3d-model-viewer-using-three-js/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[You can create a WebGL 3D model viewer in just a few lines of code using three.js. This tutorial shows you all you need to get started. ]]></description>
<dc:subject>3d web howto</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:789b185bda5f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:3d"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hacks.mozilla.org/2017/08/intersection-observer-comes-to-firefox/">
    <title>Intersection Observer comes to Firefox</title>
    <dc:date>2017-08-03T05:56:26+00:00</dc:date>
    <link>https://hacks.mozilla.org/2017/08/intersection-observer-comes-to-firefox/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The IntersectionObserver interface of the Intersection Observer API provides a way to asynchronously observe changes in the intersection of a target element with an ancestor element or with a top-level document's viewport. The ancestor element or viewport is referred to as the root.

When an IntersectionObserver is created, it's configured to watch for given ratios of visibility within the root. The configuration cannot be changed once the IntersectionObserver is created, so a given observer object is only useful for watching for specific changes in degree of visibility; however, you can watch multiple target elements with the same observer.]]></description>
<dc:subject>web UI apis</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5a6f23dce58f/</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:UI"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:apis"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html">
    <title>WebID 1.0</title>
    <dc:date>2017-05-04T15:08:04+00:00</dc:date>
    <link>https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A global distributed Social Web requires that each person be able to control their identity, that this identity be linkable across sites - placing each person in a Web of relationships - and that it be possible to authenticate globally with such identities.

This specification outlines a simple universal identification mechanism that is distributed, openly extensible, improves privacy, security and control over how each person can identify themselves in order to allow fine grained access control to their information on the Web. It does this by applying the best practices of Web Architecture whilst building on well established widely deployed protocols and standards including HTML, URIs, HTTP, and RDF Semantics.]]></description>
<dc:subject>web standard identifiers identity inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7007cc3dfc8e/</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:standard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.dlib.org/dlib/november15/vandesompel/11vandesompel.html">
    <title>Reminiscing About 15 Years of Interoperability Efforts</title>
    <dc:date>2016-10-19T12:26:05+00:00</dc:date>
    <link>http://www.dlib.org/dlib/november15/vandesompel/11vandesompel.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Over the past fifteen years, our perspective on tackling information interoperability problems for web-based scholarship has evolved significantly. In this opinion piece, we look back at three efforts that we have been involved in that aptly illustrate this evolution: OAI-PMH, OAI-ORE, and Memento. Understanding that no interoperability specification is neutral, we attempt to characterize the perspectives and technical toolkits that provided the basis for these endeavors. With that regard, we consider repository-centric and web-centric interoperability perspectives, and the use of a Linked Data or a REST/HATEAOS technology stack, respectively. We also lament the lack of interoperability across nodes that play a role in web-based scholarship, but end on a constructive note with some ideas regarding a possible path forward.]]></description>
<dc:subject>web libraries inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f34020eee284/</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:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://commoncrawl.org/2016/09/robotstxt-and-404-redirect-data-sets/">
    <title>Data Sets Containing Robots.txt Files and Non-200 Responses – Common Crawl</title>
    <dc:date>2016-09-21T11:50:47+00:00</dc:date>
    <link>http://commoncrawl.org/2016/09/robotstxt-and-404-redirect-data-sets/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Together with the crawl archive for August 2016 we release two data sets containing

robots.txt files (or what servers return in response to a GET request /robots.txt)
server responses with HTTP status code other than 200 (404s, redirects, etc.)
The data may be useful to anyone interested in web science, with various applications in the field. For instance, redirects are substantial elements of web graphs where they are equivalent to ordinary links. The data may also be useful to people developing crawlers, as it enables testing of robots.txt parsers against a huge data set.]]></description>
<dc:subject>web parsing data crawling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:43f79eeecce7/</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:parsing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:crawling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://webconcepts.info/">
    <title>Web Concepts</title>
    <dc:date>2016-08-20T22:55:39+00:00</dc:date>
    <link>http://webconcepts.info/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Web's Uniform Interface is based on a large and growing set of specifications. These specifications establish the shared concepts that providers and consumers of Web services can rely on. Web Concepts is providing an overview of these concepts and of the specifications defining them.]]></description>
<dc:subject>web standards documentation inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d87b6667d856/</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:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.openarchives.org/rs/1.0/resourcesync#Introduction">
    <title>ResourceSync Framework Specification</title>
    <dc:date>2016-06-18T19:27:10+00:00</dc:date>
    <link>http://www.openarchives.org/rs/1.0/resourcesync#Introduction</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This ResourceSync specification describes a synchronization framework for the web consisting of various capabilities that allow third-party systems to remain synchronized with a server's evolving resources. The capabilities may be combined in a modular manner to meet local or community requirements. This specification also describes how a server should advertise the synchronization capabilities it supports and how third-party systems may discover this information. The specification repurposes the document formats defined by the Sitemap protocol and introduces extensions for them.]]></description>
<dc:subject>web syndication synchronization standard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:bc9e406991e2/</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:syndication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:synchronization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://commoncrawl.org/">
    <title>Common Crawl</title>
    <dc:date>2016-02-18T01:01:29+00:00</dc:date>
    <link>https://commoncrawl.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We build and maintain an open repository of web crawl data that can be accessed and analyzed by anyone.]]></description>
<dc:subject>web data search</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3352316c6e59/</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:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:search"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dret.github.io/webdata/">
    <title>Web Data</title>
    <dc:date>2016-01-27T22:06:47+00:00</dc:date>
    <link>http://dret.github.io/webdata/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Web Data Principles are a simple set of guidelines about how to make structured information more useful on the Web. The main idea of Web Data is that it is a simple set of principles and patterns, and not a specific set of technologies. As such, it is more liberal than the 5-star model of Linked Data, which makes specific statements about required technologies. For a much more detailed set of recommendations, check out the W3C's "Data on the Web Best Practices" document.]]></description>
<dc:subject>web data</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:546ff96226b7/</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:data"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/WAI/PF/aria-practices/">
    <title>WAI-ARIA 1.0 Authoring Practices</title>
    <dc:date>2016-01-20T14:32:57+00:00</dc:date>
    <link>https://www.w3.org/WAI/PF/aria-practices/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document provides readers with an understanding of how to use WAI-ARIA [ARIA] to create accessible rich internet applications. It describes considerations that might not be evident to most authors from the WAI-ARIA specification alone and recommends approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. This document is directed primarily to Web application developers, but the guidance is also useful for user agent and assistive technology developers. ]]></description>
<dc:subject>web interface accessibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9466e3595a74/</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:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/sdw-bp/">
    <title>Spatial Data on the Web Best Practices</title>
    <dc:date>2016-01-20T13:23:58+00:00</dc:date>
    <link>https://www.w3.org/TR/sdw-bp/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document advises on best practices related to the publication and usage of spatial data on the Web; the use of Web technologies as they may be applied to location. The best practices are intended for practitioners, including Web developers and geospatial experts, and are compiled based on evidence of real-world application. These best practices suggest a significant change of emphasis from traditional Spatial Data Infrastructures by adopting a Linked Data approach.]]></description>
<dc:subject>spatial web data linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cffc46171fa5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:spatial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/webmention/">
    <title>Webmention</title>
    <dc:date>2016-01-13T13:46:28+00:00</dc:date>
    <link>https://www.w3.org/TR/webmention/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Webmention is a simple way to notify any URL when you link to it on your site. From the receiver's perspective, it's a way to request notifications when other sites link to it.]]></description>
<dc:subject>web standards notification linkeddata periodo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c9f29563e6a9/</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:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:notification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:periodo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/ikreymer/pywb">
    <title>ikreymer/pywb</title>
    <dc:date>2015-12-11T19:36:43+00:00</dc:date>
    <link>https://github.com/ikreymer/pywb</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[pywb is a python implementation of web archival replay tools, sometimes also known as 'Wayback Machine'.

pywb allows high-quality replay (browsing) of archived web data stored in standardized ARC and WARC, and it can also serve as a customizable rewriting proxy to live web content.

The replay system is designed to accurately replay complex dynamic sites, including video and audio content and sites with complex JavaScript.

Additionally, pywb includes an extensive index query api for querying information about archived content.

The software can run as a traditional web application or an HTTP or HTTPS proxy server, and has been tested on Linux, OS X and Windows platforms.

pywb is fully compliant with the Memento protocol (RFC-7089).]]></description>
<dc:subject>python web archive tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:26eda6502405/</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:li rdf:resource="https://pinboard.in/u:rybesh/t:archive"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/codeforscience/webdata/issues/5">
    <title>Browser file and network I/O</title>
    <dc:date>2015-12-03T01:05:47+00:00</dc:date>
    <link>https://github.com/codeforscience/webdata/issues/5</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A tour of the state of I/O in the browser as it relates to data processing/data science users.]]></description>
<dc:subject>web browser api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:dfca5432d34f/</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:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/substack/omega-projects/issues/8">
    <title>decentralized authentication · Issue #8 · substack/omega-projects</title>
    <dc:date>2015-06-05T13:11:09+00:00</dc:date>
    <link>https://github.com/substack/omega-projects/issues/8</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A decentralized solution to authentication needs many pieces to succeed and many of those pieces are social in nature. Several of these pieces may turn out to be dual-sided, which will make them more difficult to gain adoption but may protect their position once properly established.]]></description>
<dc:subject>authentication decentralize web architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ebd4e2f0e7d8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authentication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:decentralize"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://web.archive.org/web/20150413151619/https://www.flickr.com/groups/central/discuss/9375/">
    <title>Flickr: Discussing Unfound? in FlickrCentral</title>
    <dc:date>2015-04-13T15:17:35+00:00</dc:date>
    <link>https://web.archive.org/web/20150413151619/https://www.flickr.com/groups/central/discuss/9375/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[What is the reason for, or story behind the tag unfound ( www.flickr.com/photos/tags/unfound/)? Lots of people use it and it doesn't seem to be a direct reference to any aspect of the photo. 
6:30AM, 17 December 2004 PDT 
 
*Seuss* says:

In the early days of flickr it apparently meant "I took this picture". That's what I've been told at least.

Like you I really don't see the point now especially seeing most people using it don't have many that they didn't take the picture. 
ages ago 
 
Meer says:

Flickr didn't start out with the exclusive concentration on photo-taking. It was a "social software" which emphasized real-time chatting with images. So a lot of us had our collections of pictures we found on the web ("snagged"), and to denote something that was your own, "unfound" came to be. Now, of course, the chatting is deemphasized and it's all about the photos.]]></description>
<dc:subject>history tagging sharing web images</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:130a28c1f49d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tagging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sharing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:images"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://3dhop.net/">
    <title>3DHOP - Home</title>
    <dc:date>2015-04-02T18:25:56+00:00</dc:date>
    <link>http://3dhop.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[3DHOP (3D Heritage Online Presenter) is a collection of tools and templates for the creation of multimedia interactive Web presentations of digital cultural artifacts.

3DHOP target audience range from the museum curators with some IT experience to the experienced Web designers who want to embed 3D contents in their creations.

It allows easy visualization of 3D models directly inside HTML pages and the streaming of multiresolution 3D meshes over HTTP (using the Nexus format), supporting the exploration of very large models on commodity computers and standard internet connections.]]></description>
<dc:subject>web javascript 3d culturalheritage</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7bcc212816d6/</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:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:3d"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:culturalheritage"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://linked-research.270a.info/#conceptual-design">
    <title>Enabling Accessible Knowledge</title>
    <dc:date>2015-03-16T23:22:26+00:00</dc:date>
    <link>http://linked-research.270a.info/#conceptual-design</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Linked Research [15] is a proposal for Web researchers to use the technologies in the native Web stack to access, share and discover knowledge. The Call for Linked Research [16] aims to encourage the “do it yourself” behaviour for sharing and reusing research knowledge. The workflow template for Linked Research is intended to enable better discovery of research objects, and improved user experience and access to research knowledge.]]></description>
<dc:subject>html publishing web scholarlycommunication</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:75b119a2678e/</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:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarlycommunication"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/jbenet/go-ipfs">
    <title>jbenet/go-ipfs</title>
    <dc:date>2015-02-23T15:40:17+00:00</dc:date>
    <link>https://github.com/jbenet/go-ipfs</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Ipfs is a global, versioned, peer-to-peer filesystem. It combines good ideas from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single bittorrent swarm, exchanging git objects. IPFS provides an interface as simple as the HTTP web, but with permanence built in. You can also mount the world at /ipfs.]]></description>
<dc:subject>p2p distributed web filesystem hypermedia</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d5d5640a8afc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:p2p"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:filesystem"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ipfs.io/">
    <title>The IPFS Project</title>
    <dc:date>2015-02-23T14:58:12+00:00</dc:date>
    <link>http://ipfs.io/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[IPFS is a new hypermedia distribution protocol, addressed by content and identities. IPFS enables the creation of completely distributed applications. It aims to make the web faster, safer, and more open.]]></description>
<dc:subject>p2p hypermedia web filesystem</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ef73b75330a6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:p2p"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:filesystem"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://netpreserve.org/sites/default/files/resources/OverviewFutureWebWorkshop.pdf">
    <title>IIPC Future of the Web Workshop</title>
    <dc:date>2015-02-21T01:07:02+00:00</dc:date>
    <link>http://netpreserve.org/sites/default/files/resources/OverviewFutureWebWorkshop.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[ The problems the evolution of the Web poses for attempts to collect and preserve it. Here is the list of problem areas the workshop identified:

Database driven features & functions
Complex/variable URI formats & inconsistent/variable link implementations
Dynamically generated, ever changing, URIs
Rich Media
Scripted, incremental display & page loading mechanisms
Scripted, HTML forms
Multi-­sourced, embedded material
Dynamic login/auth services: captchas, cross-­site/social authentication, & user-­sensitive embeds
Alternate display based on user agent or other parameters
Exclusions by convention
Exclusions by design
Server side scripts & remote procedure calls
HTML5 "web sockets"
Mobile publishing]]></description>
<dc:subject>web archives preservation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:09516fbcfdc8/</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:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:preservation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://site.ebrary.com/lib/uncch/detail.action?docID=10494632">
    <title>Web Application Hacker's Handbook : Finding and Exploiting Security Flaws (2nd Edition)</title>
    <dc:date>2015-02-20T13:58:50+00:00</dc:date>
    <link>http://site.ebrary.com/lib/uncch/detail.action?docID=10494632</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Web applications are the front door to most organizations, exposing them to attacks that may disclose personal information, execute fraudulent transactions, or compromise ordinary users. This practical book has been completely updated and revised to discuss the latest step-by-step techniques for attacking and defending the range of ever-evolving web applications. You'll explore the various new technologies employed in web applications that have appeared since the first edition and review the new attack techniques that have been developed, particularly in relation to the client side.]]></description>
<dc:subject>web security inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a054c08e5ab8/</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:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/TryGhost/Ghost/issues/2144">
    <title>[Discussion] The future of Ghost's admin UI · Issue #2144 · TryGhost/Ghost</title>
    <dc:date>2014-12-11T18:56:17+00:00</dc:date>
    <link>https://github.com/TryGhost/Ghost/issues/2144</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Discussion point 2: What is the best structure for a complex client side app like this?

This sort of depends on the tool used to build it, but also has implications for choosing a tool.

Is the Ghost admin a single page app, or a collection of single page apps? If you take the dashboard into consideration, I believe that alone is a single page app. The editor is probably the same.

Do you have ideas on how to structure the admin UI, and how to ensure it works as a whole?

Discussion point 3: Is backbone the best framework for the job?

There are many other potential tools we could use, and there are a few main solutions that we consider to be on the table:

Improving the current backbonejs implementation by adding more underlying structure and using additional tools like marionette and rendr
Switching to emberjs
Switching to angular
Something else entirely?]]></description>
<dc:subject>javascript framework web browser client architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d87460816006/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:client"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://go-to-hellman.blogspot.com/2014/12/stop-making-web-surveillance-bugs-by.html">
    <title>Go To Hellman: Stop Making Web Surveillance Bugs by Mistake!</title>
    <dc:date>2014-12-08T02:16:08+00:00</dc:date>
    <link>http://go-to-hellman.blogspot.com/2014/12/stop-making-web-surveillance-bugs-by.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[If you care about user privacy and you have a website, here's what you should do:

Avoid loading images and other assets from 3rd party sites. consider self-hosting these.

When you use 3rd party hosted assets, use HTTPS references only!

Avoid loading static assets from domains that use Google Analytics and set id domain cookies.]]></description>
<dc:subject>privacy http web design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e80e0746f910/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://enable-cors.org/">
    <title>enable cross-origin resource sharing</title>
    <dc:date>2014-09-30T18:07:08+00:00</dc:date>
    <link>http://enable-cors.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Cross-Origin Resource Sharing (CORS) is a specification that enables truly open access across domain-boundaries. If you serve public content, please consider using CORS to open it up for universal JavaScript/browser access.]]></description>
<dc:subject>ajax web javascript linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cea86f546ab7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ajax"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dashes.com/anil/2012/12/the-web-we-lost.html">
    <title>The Web We Lost - Anil Dash</title>
    <dc:date>2014-08-23T14:03:19+00:00</dc:date>
    <link>http://dashes.com/anil/2012/12/the-web-we-lost.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We've lost key features that we used to rely on, and worse, we've abandoned core values that used to be fundamental to the web world.]]></description>
<dc:subject>web architecture culture critique</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:380216f3fb54/</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:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:critique"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.theatlantic.com/technology/archive/2014/08/advertising-is-the-internets-original-sin/376041/">
    <title>The Internet's Original Sin - The Atlantic</title>
    <dc:date>2014-08-23T14:01:25+00:00</dc:date>
    <link>http://www.theatlantic.com/technology/archive/2014/08/advertising-is-the-internets-original-sin/376041/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[What we wanted to do was to build a tool that made it easy for everyone, everywhere to share knowledge, opinions, ideas and photos of cute cats. As everyone knows, we had some problems, primarily business model problems, that prevented us from doing what we wanted to do the way we hoped to do it. What we’re asking for today is a conversation about how we could do this better, since we screwed up pretty badly the first time around.]]></description>
<dc:subject>web architecture privacy critique</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:328c89b1e94c/</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:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:critique"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.wired.co.uk/news/archive/2014-02/06/tim-berners-lee-reclaim-the-web">
    <title>Tim Berners-Lee: we need to re-decentralise the web (Wired UK)</title>
    <dc:date>2014-08-23T14:00:51+00:00</dc:date>
    <link>http://www.wired.co.uk/news/archive/2014-02/06/tim-berners-lee-reclaim-the-web</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Twenty-five years on from the web's inception, its creator has urged the public to re-engage with its original design: a decentralised internet that at its very core, remains open to all.]]></description>
<dc:subject>web architecture decentralize</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:177edbdc2ede/</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:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:decentralize"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tools.ietf.org/html/rfc7252">
    <title>RFC 7252 - The Constrained Application Protocol (CoAP)</title>
    <dc:date>2014-07-24T21:43:31+00:00</dc:date>
    <link>http://tools.ietf.org/html/rfc7252</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks.]]></description>
<dc:subject>web protocols</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:284302b97bd8/</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:protocols"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/ns/formats/">
    <title>Unique URIs for File Formats</title>
    <dc:date>2014-06-20T14:51:18+00:00</dc:date>
    <link>http://www.w3.org/ns/formats/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA['http://www.w3.org/ns/formats/Format' is a unique, top-level Class URI for specific file formats. Media types do not uniquely identify file formats (eg, serialization formats for various abstract concepts), because not all specific cases do have distinct media types, instances in this class can be used instead for proper identification.

Although the URI-s themselves refer to non-informational resources (ie, they are abstract identifiers), they can be dereferenced. Dereferencing leads to informational resources in XHTML, RDF/XML, or Turtle equivalents, depending on content negotiation.]]></description>
<dc:subject>rdf uri web identifiers standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3278dad6edb7/</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:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tools.ietf.org/html/rfc3986#section-4.4">
    <title>RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax</title>
    <dc:date>2014-06-19T03:06:40+00:00</dc:date>
    <link>http://tools.ietf.org/html/rfc3986#section-4.4</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[When a URI reference refers to a URI that is, aside from its fragment
   component (if any), identical to the base URI (Section 5.1), that
   reference is called a "same-document" reference.  The most frequent
   examples of same-document references are relative references that are
   empty or include only the number sign ("#") separator followed by a
   fragment identifier.]]></description>
<dc:subject>web standards uri</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:945721ad0e4b/</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:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tools.ietf.org/html/draft-ietf-urnbis-urns-are-not-uris-00">
    <title>draft-ietf-urnbis-urns-are-not-uris-00 - Names are Not Locators and URNs are Not URIs</title>
    <dc:date>2014-04-25T13:21:09+00:00</dc:date>
    <link>http://tools.ietf.org/html/draft-ietf-urnbis-urns-are-not-uris-00</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Experience has shown that identifiers associated with persistent names are quite different from identifiers associated with the locations of objects.  This is especially true when such names are are expected to be stable for a very long time or when they identify large and complex entities.  In order to allow Uniform Resource Names (URNs) to evolve to meet the needs of the Informational Sciences community and other users, this specification separates the syntax for URNs from the generic syntax for Uniform Resource Identifiers (URIs) specified in RFC 3986, updating the latter specification accordingly.]]></description>
<dc:subject>identifiers names uri web standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:623e587e7e47/</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:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>