<?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://llmstxt.org/"/>
	<rdf:li rdf:resource="https://github.com/git/git/blob/master/Documentation/gitdatamodel.adoc"/>
	<rdf:li rdf:resource="https://developer.apple.com/programs/pathway/"/>
	<rdf:li rdf:resource="https://diataxis.fr/"/>
	<rdf:li rdf:resource="https://docs.github.com/en/education/manage-coursework-with-github-classroom"/>
	<rdf:li rdf:resource="https://developer.mozilla.org/en-US/docs/Web/API/Web_components"/>
	<rdf:li rdf:resource="https://fno.io/spec/"/>
	<rdf:li rdf:resource="https://publi.codes/"/>
	<rdf:li rdf:resource="https://documentation.divio.com/"/>
	<rdf:li rdf:resource="https://github.com/facebookresearch/metaseq/tree/main/projects/OPT/chronicles"/>
	<rdf:li rdf:resource="https://github.com/stedolan/jq/wiki/jq-Language-Description"/>
	<rdf:li rdf:resource="https://github.com/rdflib/pyLODE#what-pylode-understands"/>
	<rdf:li rdf:resource="https://www.publicbooks.org/virtual-roundtable-compression/#hepler-smith"/>
	<rdf:li rdf:resource="https://www.mkdocs.org/"/>
	<rdf:li rdf:resource="https://larvalsubjects.wordpress.com/2019/11/18/zoos/"/>
	<rdf:li rdf:resource="http://www.satori.org/game-programming-gems/"/>
	<rdf:li rdf:resource="https://web.archive.org/web/20120105033527/http://oddbill.com/2007/07/04/programmer-archaeologist/"/>
	<rdf:li rdf:resource="https://github.com/marijnh/builddocs"/>
	<rdf:li rdf:resource="https://cloud.google.com/apis/design/"/>
	<rdf:li rdf:resource="http://webconcepts.info/"/>
	<rdf:li rdf:resource="https://github.com/marijnh/getdocs"/>
	<rdf:li rdf:resource="http://bottlecaps.de/convert/"/>
	<rdf:li rdf:resource="https://github.com/resource-blueprint/resource-blueprint"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/scxml/"/>
	<rdf:li rdf:resource="http://descriptionguy.com/description.html"/>
	<rdf:li rdf:resource="http://descriptionguy.com/images/WEBSITE/Documenting-archives-a-guide-for-dummies.pdf"/>
	<rdf:li rdf:resource="http://sleepycoders.blogspot.hu/2013/03/sharing-travis-ci-generated-files.html"/>
	<rdf:li rdf:resource="http://www.holovaty.com/writing/microvideos/"/>
	<rdf:li rdf:resource="http://dev.w3.org/2004/PythonLib-IH/Doc-pyRdfa/"/>
	<rdf:li rdf:resource="http://docs.webplatform.org/wiki/Main_Page"/>
	<rdf:li rdf:resource="http://ceur-ws.org/Vol-874/paper7.pdf"/>
	<rdf:li rdf:resource="http://jashkenas.github.com/docco/"/>
	<rdf:li rdf:resource="http://en.wikipedia.org/wiki/Telomere"/>
	<rdf:li rdf:resource="http://blog.nodejitsu.com/how-to-write-a-readme"/>
	<rdf:li rdf:resource="http://www.documentcloud.org/opensource"/>
	<rdf:li rdf:resource="http://groups.google.com/group/lod-lam/browse_thread/thread/2f10b9f7b5bf0784"/>
	<rdf:li rdf:resource="http://docs.nodejitsu.com/"/>
	<rdf:li rdf:resource="http://readthedocs.org/"/>
	<rdf:li rdf:resource="http://fitzgen.github.com/pycco/"/>
	<rdf:li rdf:resource="https://developer.mozilla.org/en/NsIAnnotationService"/>
	<rdf:li rdf:resource="http://hurl.it/"/>
	<rdf:li rdf:resource="https://developer.mozilla.org/en/Setting_HTTP_request_headers"/>
	<rdf:li rdf:resource="http://developer.yahoo.com/yui/yuidoc/"/>
	<rdf:li rdf:resource="http://sites.google.com/site/ocropus/documentation/ocr-output-format-links"/>
	<rdf:li rdf:resource="http://www.gbv.de/wikis/cls/Getting_started_with_SeeAlso"/>
	<rdf:li rdf:resource="http://sphinx.pocoo.org/"/>
	<rdf:li rdf:resource="http://www.mediawiki.org/wiki/API:Changing_wiki_content"/>
	<rdf:li rdf:resource="http://developer.yahoo.com/ypatterns/wireframes/"/>
	<rdf:li rdf:resource="http://n2.talis.com/wiki/Main_Page"/>
	<rdf:li rdf:resource="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.1-incubating/docs/html/"/>
	<rdf:li rdf:resource="http://webcitation.org/"/>
	<rdf:li rdf:resource="http://developer.amazonwebservices.com/connect/kbcategory.jspa?categoryID=87"/>
	<rdf:li rdf:resource="http://www.amazon.com/August-Sander-People-20th-Century/dp/0810963981/"/>
	<rdf:li rdf:resource="http://dogasu.bulbagarden.net/comparisons/comparison_links.html"/>
	<rdf:li rdf:resource="http://forums.applenova.com/showpost.php?p=432791&amp;postcount=11"/>
	<rdf:li rdf:resource="http://simile.mit.edu/exhibit/"/>
	<rdf:li rdf:resource="http://www.mnot.net/webdesc/wadl_documentation.xsl"/>
	<rdf:li rdf:resource="http://developers.facebook.com/documentation.php"/>
	<rdf:li rdf:resource="http://www.naturaldocs.org/"/>
      </rdf:Seq>
    </items>
  </channel><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/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://developer.apple.com/programs/pathway/">
    <title>Apple Developer Pathway - Apple Developer Program - Apple Developer</title>
    <dc:date>2024-06-21T21:07:18+00:00</dc:date>
    <link>https://developer.apple.com/programs/pathway/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Pathways are simple and easy-to-navigate collections of the videos, documentation, and resources you’ll need to start building great apps and games. And if you’re new to Apple platforms, you’re in the right place: This Apple Developer Pathway is geared toward beginners and will walk you through the process of starting your Apple developer journey.]]></description>
<dc:subject>apple ios developer documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ba4a6634f060/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:developer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://diataxis.fr/">
    <title>Diátaxis</title>
    <dc:date>2024-01-27T01:37:33+00:00</dc:date>
    <link>https://diataxis.fr/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Diátaxis is a way of thinking about and doing documentation.

It prescribes approaches to content, architecture and form that emerge from a systematic approach to understanding the needs of documentation users.

Diátaxis, from the Ancient Greek δῐᾰ́τᾰξῐς: dia (“across”) and taxis (“arrangement”).

Diátaxis identifies four distinct needs, and four corresponding forms of documentation - tutorials, how-to guides, technical reference and explanation. It places them in a systematic relationship, and proposes that documentation should itself be organised around the structures of those needs.]]></description>
<dc:subject>documentation framework howto reference writing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2e3dd5ae201b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:writing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://docs.github.com/en/education/manage-coursework-with-github-classroom">
    <title>Manage coursework with GitHub Classroom - GitHub Docs</title>
    <dc:date>2024-01-17T22:03:45+00:00</dc:date>
    <link>https://docs.github.com/en/education/manage-coursework-with-github-classroom</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[With GitHub Classroom, you can use GitHub to administer or participate in a course about software development.
]]></description>
<dc:subject>github teaching documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2fee92cc7944/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:teaching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</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://fno.io/spec/">
    <title>The Function Ontology</title>
    <dc:date>2024-01-03T21:42:29+00:00</dc:date>
    <link>https://fno.io/spec/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document discusses the Function Ontology: a way to semantically declare and describe implementation-independent functions, and their relations to related concepts such as parameters, outputs, related problems, algorithms, mappings to concrete implementations, and executions.

]]></description>
<dc:subject>ontology functional programming documentation specification semweb</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cbbdf00f4fd2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<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:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://publi.codes/">
    <title>Publicodes language | Publicodes</title>
    <dc:date>2024-01-02T20:06:31+00:00</dc:date>
    <link>https://publi.codes/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Publicodes is a declarative language for modeling complex business areas by decomposing them into simple elementary rules.

It is used by several administrations to implement calculation rules in a wide variety of areas (pay slip, carbon footprint, retirement notice).

In addition to calculating results from a entered situation, publicodes automatically generates explorable documentation offering an explanation of the calculation, which can be easily integrated into a web application. Publicodes is therefore particularly suitable in an approach to the transparency of public algorithms.]]></description>
<dc:subject>algorithms documentation public</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d6c7b21bc587/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:public"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://documentation.divio.com/">
    <title>Divio Documentation System</title>
    <dc:date>2023-01-30T19:51:43+00:00</dc:date>
    <link>https://documentation.divio.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[There is a secret that needs to be understood in order to write good software documentation: there isn’t one thing called documentation, there are four.

They are: tutorials, how-to guides, technical reference and explanation. They represent four different purposes or functions, and require four different approaches to their creation. Understanding the implications of this will help improve most documentation - often immensely.]]></description>
<dc:subject>documentation howto reference tutorial</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2ed2561c6c46/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tutorial"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/facebookresearch/metaseq/tree/main/projects/OPT/chronicles">
    <title>metaseq/projects/OPT/chronicles at main · facebookresearch/metaseq</title>
    <dc:date>2022-05-10T00:39:56+00:00</dc:date>
    <link>https://github.com/facebookresearch/metaseq/tree/main/projects/OPT/chronicles</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Here we have included our full logbook used while training the OPT-175B model, along with a series of notes written to summarize the process and communicate some of the challenges we faced along the way.]]></description>
<dc:subject>machinelearning documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:fa98d3744f28/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:machinelearning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/stedolan/jq/wiki/jq-Language-Description">
    <title>jq Language Description · stedolan/jq Wiki</title>
    <dc:date>2022-05-10T00:39:23+00:00</dc:date>
    <link>https://github.com/stedolan/jq/wiki/jq-Language-Description</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The jq documentation is written in a style that hides a lot of important detail because the hope is that the language feels intuitive. Some users need documentation that includes such details and more — this page is for them.]]></description>
<dc:subject>json jq documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:17f97b59ca91/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:jq"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/rdflib/pyLODE#what-pylode-understands">
    <title>RDFLib/pyLODE: An OWL ontology documentation tool using Python and templating, based on LODE</title>
    <dc:date>2021-03-25T23:08:37+00:00</dc:date>
    <link>https://github.com/rdflib/pyLODE#what-pylode-understands</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[An OWL ontology documentation tool using Python and templating]]></description>
<dc:subject>semanticweb owl documentation tool</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6f25a1e14994/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semanticweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:owl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tool"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.publicbooks.org/virtual-roundtable-compression/#hepler-smith">
    <title>Virtual Roundtable on “Compression” | Public Books</title>
    <dc:date>2020-02-27T00:07:18+00:00</dc:date>
    <link>https://www.publicbooks.org/virtual-roundtable-compression/#hepler-smith</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The following essays emerge from a conference exploring the transformation of stored objects through the lens of “compression.” Beginning with one of the oldest alleged forms of compression—the alphabet—Stephanie Ann Frampton leads us through a history of consonants and vowels lost, discovered, and invented, complicating any simple notion of alphabets as efficient containers for sounds. Nor have sounds alone posed dilemmas for alphabetic storage: as Evan Hepler-Smith demonstrates, by condensing molecules into alphabetical formulae, chemical information systems flattened our understanding of molecules themselves, with potentially deadly consequences. Finally, Craig Robertson exposes the centrality of compressed storage for the imagination of modern political economy. Examining a once-revolutionary symbol of workplace efficiency—the filing cabinet—he shows how the practice of storing paper “on its edge” emerged alongside that other product of “vertical” capitalism, the skyscraper.]]></description>
<dc:subject>documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:20881eeaf180/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.mkdocs.org/">
    <title>MkDocs</title>
    <dc:date>2020-02-25T21:24:43+00:00</dc:date>
    <link>https://www.mkdocs.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[MkDocs is a fast, simple and downright gorgeous static site generator that's geared towards building project documentation. Documentation source files are written in Markdown, and configured with a single YAML configuration file. Start by reading the introduction below, then check the User Guide for more info.]]></description>
<dc:subject>documentation markdown python tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:85ecee611423/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://larvalsubjects.wordpress.com/2019/11/18/zoos/">
    <title>Zoos | Larval Subjects .</title>
    <dc:date>2019-11-18T20:28:39+00:00</dc:date>
    <link>https://larvalsubjects.wordpress.com/2019/11/18/zoos/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[So, with this in mind, back to the old zoos.  We can approach the way people represent things, the things they build, and the way they pose problems as symptoms of their pre-reflective ontologies.  Just as a very simple dream can be a symptom of a highly complex thought uncovered through the process of free association, a human representation or artifact can be seen as a symptom of a broader set of ontological assumptions or assumptions about the nature of being.  In the old zoos we encounter the animal caged, behind bars, with little to nothing in their cell.  How must one think of beings– not just animals –to construct a zoo such as this?  Is there a more generalized set of ontological assumptions reflected in this zoo construction?]]></description>
<dc:subject>documentation ontology</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:31765163570d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.satori.org/game-programming-gems/">
    <title>Game Programming Gems</title>
    <dc:date>2018-11-15T00:52:40+00:00</dc:date>
    <link>http://www.satori.org/game-programming-gems/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[I launched the Game Programming Gems book series in 2000, and it quickly became a popular source for credible technical information on game programming: written by programmers, for programmers. Each book contained 40-70 short chapters, or “gems”, with each gem tackling a common game programming problem. By encouraging professional game developers to share their hard-earned technology wisdom with others I hoped that it would free all of us up to focus on greater problems. No more re-inventing the wheel! The series grew over time to include 9 books (Gems 1-8 and a “best of” volume), and a number of other great books have spun off from the series over time.]]></description>
<dc:subject>games programming history books documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:42222eb6afdc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://web.archive.org/web/20120105033527/http://oddbill.com/2007/07/04/programmer-archaeologist/">
    <title>oddbill » Blog Archive » Programmer-Archaeologist</title>
    <dc:date>2018-11-12T16:26:55+00:00</dc:date>
    <link>https://web.archive.org/web/20120105033527/http://oddbill.com/2007/07/04/programmer-archaeologist/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In Verner Vinge’s space opera A Deepness in the Sky, he proposes that one of this future’s most valuable professions is that of Programmer-Archaeologist. Essentially, the layers of accreted software in all large systems are so deep, inter-penetrating, idiosyncratic and inter-dependent that it has become impossible to just re-write them for simplicity’s sake – they genuinely can’t be replaced without wrecking the foundations of civilization. The Programmer-Archaeologist churns through this maddening nest of ancient languages and hidden/forgotten tools to repair existing programs or to find odd things that can be turned to unanticipated uses.

“The word for all this is ‘mature programming environment.’ Basically, when hardware performance has been pushed to its final limit, and programmers have had several centuries to code, you reach a point where there is far more significant code than can be rationalized. The best you can do is understand the overall layering, and know how to search for the oddball tool that may come in handy -”
A Deepness in the Sky – Verner Vinge

This is not all that different from what I actually do in my current job.]]></description>
<dc:subject>programming archaeology documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:935fbdcbd6d8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archaeology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/marijnh/builddocs">
    <title>marijnh/builddocs: Convert getdocs-style doc comments into HTML documentation</title>
    <dc:date>2018-05-15T23:16:28+00:00</dc:date>
    <link>https://github.com/marijnh/builddocs</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a utility that transforms code documented with getdocs-style doc comments into HTML.]]></description>
<dc:subject>javascript documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:01c728cc195b/</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:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cloud.google.com/apis/design/">
    <title>API Design Guide  |  Cloud APIs  |  Google Cloud Platform</title>
    <dc:date>2017-03-05T15:43:26+00:00</dc:date>
    <link>https://cloud.google.com/apis/design/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a general design guide for networked APIs. It has been used inside Google since 2014 and is the guide we follow when designing Cloud APIs and other Google APIs. It is shared here to inform outside developers and to make it easier for us all to work together.

External developers may find it particularly useful when designing gRPC APIs for use with Google Cloud Endpoints, and we strongly recommend such developers use these design principles. However, we don't mandate its use for any non-Google developer and you can use Cloud Endpoints and/or gRPC without following the guide.

This guide applies to both REST APIs and RPC APIs, with specific focus on gRPC APIs. gRPC APIs use Protocol Buffers to define their API surface and API Service Configuration to configure their API services, including HTTP mapping, logging, and monitoring. HTTP mapping features are used by Google APIs and gRPC Cloud Endpoints APIs for JSON/HTTP to Protocol Buffers/RPC transcoding.

This guide is a living document and additions to it will be made over time as new style and design patterns are adopted and approved. In that spirit, it is never going to be complete and there will always be ample room for the art and craft of API design.]]></description>
<dc:subject>api design documentation architecture inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cfdd0c9895bd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</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="https://github.com/marijnh/getdocs">
    <title>marijnh/getdocs</title>
    <dc:date>2015-12-17T03:21:28+00:00</dc:date>
    <link>https://github.com/marijnh/getdocs</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Getdocs is like JSDoc or documentation.js, running over ES6 code to extract information and inline documentation in order to generate docs, but without all the @s. It takes source files and outputs JSON.]]></description>
<dc:subject>javascript documentation tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9c34e76267b2/</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:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bottlecaps.de/convert/">
    <title>Grammar Conversion</title>
    <dc:date>2014-10-21T15:39:43+00:00</dc:date>
    <link>http://bottlecaps.de/convert/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Paste grammar into textarea and click button for converting to W3C grammar notation. These grammar notations are supported: ABNF, ANTLR 3, Bison, GOLD, JavaCC, Jison, PEG.js.]]></description>
<dc:subject>syntax documentation visualization parsing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e5a4d10ad0ee/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:syntax"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:parsing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/resource-blueprint/resource-blueprint">
    <title>resource-blueprint/resource-blueprint</title>
    <dc:date>2014-09-30T18:02:15+00:00</dc:date>
    <link>https://github.com/resource-blueprint/resource-blueprint</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The following highlights the API design concepts underlying a Resource Blueprint.

Semantically define data and affordances (link relations).
Define state-machines representing a resource.
Includes transitions in different states (business rules) and the conditions (permissions) for their inclusion in a response.
Ideally, this should ultimately draw the state-machine as part of the design process.
Will be used mock the API to act as a true hypermedia API based on state.
Specify supported media-types.
The API Blueprint parser will generate sample representations based on the semantics, state-machine and known media-types.
Specify the entry point to the resource.
Adding metadata to elements that could be used to define a profile (e.g. ALPS) from the blueprint and other uses in the machine-readable output of the API Blueprint parser.
Enter protocol specific information as an implementation detail well after having designed the actual API.
Initially only supports HTTP protocol.
The only actual URI you will see in the human-readable version is the entry point, even though you can enter URIs in the blueprint.
APIs associated with specific resources can be designed individually as parts of an overall API that may span several resource blueprints to represent the overall API application state-machine.]]></description>
<dc:subject>api documentation hypermedia statemachine inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0d02913967d7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:statemachine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/TR/scxml/">
    <title>State Chart XML (SCXML): State Machine Notation for Control Abstraction</title>
    <dc:date>2014-09-30T17:53:18+00:00</dc:date>
    <link>http://www.w3.org/TR/scxml/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document describes SCXML, or the "State Chart extensible Markup Language". SCXML provides a generic state-machine based execution environment based on CCXML and Harel State Tables.]]></description>
<dc:subject>documentation standards statemachine</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:980d39673850/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:statemachine"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://descriptionguy.com/description.html">
    <title>Chris Hurley (Information Technology)</title>
    <dc:date>2014-04-28T19:37:31+00:00</dc:date>
    <link>http://descriptionguy.com/description.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Look here for writings on archival description and documentation.]]></description>
<dc:subject>archives description documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8d7bc182245e/</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:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://descriptionguy.com/images/WEBSITE/Documenting-archives-a-guide-for-dummies.pdf">
    <title>DOCUMENTING ARCHIVES AND OTHER RECORDS - A GUIDE FOR DUMMIES</title>
    <dc:date>2014-04-28T19:32:47+00:00</dc:date>
    <link>http://descriptionguy.com/images/WEBSITE/Documenting-archives-a-guide-for-dummies.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We can describe only what we understand. There are many ways to understand records. This is one of them.]]></description>
<dc:subject>documentation description archives inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b42bf6562ae3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sleepycoders.blogspot.hu/2013/03/sharing-travis-ci-generated-files.html">
    <title>Sharing Travis-CI generated files</title>
    <dc:date>2014-01-20T19:51:03+00:00</dc:date>
    <link>http://sleepycoders.blogspot.hu/2013/03/sharing-travis-ci-generated-files.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[There are some things that are generated by your project and it will be nice to make available to the broad audience with each successful update. For example code coverage statistics, pdf of your LaTeX publication, maybe some documentation for your library, or even binary of the application itself.]]></description>
<dc:subject>github publishing documentation howto</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0b4ec1b5e081/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.holovaty.com/writing/microvideos/">
    <title>How to make help microvideos for your website | Holovaty.com</title>
    <dc:date>2013-07-01T17:05:58+00:00</dc:date>
    <link>http://www.holovaty.com/writing/microvideos/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[One of the best things we've done at Soundslice is to create help "microvideos" walking people through the site's various features. I've fallen in love with this technique and want more sites to do this, so here's a brain dump on how I make them!]]></description>
<dc:subject>video documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:914d4aefe42d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dev.w3.org/2004/PythonLib-IH/Doc-pyRdfa/">
    <title>pyRdfa API Documentation</title>
    <dc:date>2013-05-08T20:06:02+00:00</dc:date>
    <link>http://dev.w3.org/2004/PythonLib-IH/Doc-pyRdfa/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[RDFa 1.1 parser, also referred to as a “RDFa Distiller”. It is deployed, via a CGI front-end, on the W3C RDFa 1.1 Distiller page.]]></description>
<dc:subject>rdfa python documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2635ca4a67e1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdfa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://docs.webplatform.org/wiki/Main_Page">
    <title>WebPlatform Docs</title>
    <dc:date>2012-10-08T16:12:24+00:00</dc:date>
    <link>http://docs.webplatform.org/wiki/Main_Page</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Web Platform Docs is a new community-driven site that aims to become a comprehensive and authoritative source for web developer documentation. Even though Web Platform Docs is still in alpha, you can already find lots of valuable content on the site, including information on:

How to use features of the open web, with syntax and examples
What platforms and devices you can use various technologies on
What is the current standardization, stability and implementation status of each technology specification
In the future, Web Platform Docs will include even more content for you to explore such as live code examples, resources for educators and much more. ]]></description>
<dc:subject>documentation standards inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d58c56d95544/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ceur-ws.org/Vol-874/paper7.pdf">
    <title>Legal Rules, Text and Ontologies Over Time</title>
    <dc:date>2012-09-03T22:13:22+00:00</dc:date>
    <link>http://ceur-ws.org/Vol-874/paper7.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The current paper presents the “Fill the gap” project that aims to design a set of XML standards for modelling legal documents in the Semantic Web over time. The goal of the project is to design an information system using XML standards able to store in an XML-native database legal resources and legal rules in an integrated way for supporting legal knowledge engineers and end-users (e.g., public administrative officers, judges, citizens).]]></description>
<dc:subject>law ontology documentation time temporality modeling inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:80b5aa7ba3ea/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:temporality"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jashkenas.github.com/docco/">
    <title>docco.coffee</title>
    <dc:date>2012-03-28T14:34:13+00:00</dc:date>
    <link>http://jashkenas.github.com/docco/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Docco is a quick-and-dirty, hundred-line-long, literate-programming-style documentation generator. It produces HTML that displays your comments alongside your code. Comments are passed through Markdown, and code is passed through Pygments syntax highlighting.]]></description>
<dc:subject>coffeescript documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f3e41c34803b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:coffeescript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://en.wikipedia.org/wiki/Telomere">
    <title>Telomere - Wikipedia, the free encyclopedia</title>
    <dc:date>2012-01-27T19:31:44+00:00</dc:date>
    <link>http://en.wikipedia.org/wiki/Telomere</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Telomeres are repetitive nucleotide sequences located at the termini of linear chromosomes. Mons and Velterop refer to concepts linked by a predicate in an RDF triple as "telomeric concepts," an interesting metaphor demonstrating that Otlet's dream of a science of documentation that mirrors the science of natural phenomena is alive and well.]]></description>
<dc:subject>documentation semweb science scholarlycommunication</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:186dbc65d8de/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarlycommunication"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.nodejitsu.com/how-to-write-a-readme">
    <title>How To Write A Readme - blog.nodejitsu.com - scaling node.js applications one callback at a time.</title>
    <dc:date>2011-11-18T14:45:54+00:00</dc:date>
    <link>http://blog.nodejitsu.com/how-to-write-a-readme</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[So you're writing a module. Cool! Are you ready to document it? I'm here to help.
I'm no expert on readmes. I have, however, read a lot of readmes (both good and bad), written my fair share of readmes and documentation, and---most importantly---have formed strong opinions on what I should see in a readme.
This post focuses on the "first pass" for your readme. These PROTIPS are applicable, however, to readmes of all ages.]]></description>
<dc:subject>documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d309459400ca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.documentcloud.org/opensource">
    <title>Open Source - DocumentCloud</title>
    <dc:date>2011-11-09T18:17:08+00:00</dc:date>
    <link>http://www.documentcloud.org/opensource</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[As we work on DocumentCloud, we're constantly building pieces of infrastructure that could be useful for other organizations that work with similar kinds of data. We're releasing as we go by extracting useful components as standalone open source projects. Please follow our work if you're interested in what lies under the hood.]]></description>
<dc:subject>documentation annotation research journalism history tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1eca6b37e35c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:annotation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:journalism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://groups.google.com/group/lod-lam/browse_thread/thread/2f10b9f7b5bf0784">
    <title>Frameworks for publishing vocabularies online - Linked Open Data in Libraries, Archives, &amp; Museums | Google Groups</title>
    <dc:date>2011-10-20T21:10:50+00:00</dc:date>
    <link>http://groups.google.com/group/lod-lam/browse_thread/thread/2f10b9f7b5bf0784</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Survey of frameworks for publishing RDF vocabularies/ontologies online.]]></description>
<dc:subject>semweb linkeddata vocabulary documentation publishing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9aaad2b13274/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabulary"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://docs.nodejitsu.com/">
    <title>node docs</title>
    <dc:date>2011-09-21T02:20:58+00:00</dc:date>
    <link>http://docs.nodejitsu.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We believe in sharing knowledge. So we have assembled this growing collection of node.js how-to articles. These articles range from basic to advanced. They provide relevant code samples and insights into the design and philosophy of node itself.

docs.nodejitsu.com is an open source project and is curated by the Nodejitsu team and friends. If you have articles or ideas that you would like to contribute, we'd very much like to accept your pull request!]]></description>
<dc:subject>nodejs tutorial documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b2e93e4b2304/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://readthedocs.org/">
    <title>Home | Read the Docs</title>
    <dc:date>2011-08-17T21:26:38+00:00</dc:date>
    <link>http://readthedocs.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Read the Docs hosts documentation, making it fully searchable and easy to find. You can import your docs using any major version control system, including Mercurial, Git, Subversion, and Bazaar. It also supports webhooks so your docs get built when you commit code. There's also support for versioning so you can build docs from tagged versions of your code in your repository.]]></description>
<dc:subject>documentation hosting</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:98d0fa56e9ef/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hosting"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://fitzgen.github.com/pycco/">
    <title>main.py</title>
    <dc:date>2011-04-14T03:57:02+00:00</dc:date>
    <link>http://fitzgen.github.com/pycco/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Pycco is a Python port of Docco: the original quick-and-dirty, hundred-line-long, literate-programming-style documentation generator. It produces HTML that displays your comments alongside your code. Comments are passed through Markdown, and code is passed through Pygments syntax highlighting.]]></description>
<dc:subject>python documentation tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:00d2c92fdf72/</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:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developer.mozilla.org/en/NsIAnnotationService">
    <title>NsIAnnotationService</title>
    <dc:date>2009-12-17T23:03:31+00:00</dc:date>
    <link>https://developer.mozilla.org/en/NsIAnnotationService</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The nsIAnnotationService interface is designed to store arbitrary data about a web page in Firefox 3.
]]></description>
<dc:subject>firefox annotation documentation</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:d984befc8890/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:firefox"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:annotation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://hurl.it/">
    <title>hurl</title>
    <dc:date>2009-10-22T17:14:15+00:00</dc:date>
    <link>http://hurl.it/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Hurl makes HTTP requests.]]></description>
<dc:subject>webservices debugging documentation</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:554b8a7f0281/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:debugging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developer.mozilla.org/en/Setting_HTTP_request_headers">
    <title>Setting HTTP request headers - MDC</title>
    <dc:date>2009-07-21T23:49:33+00:00</dc:date>
    <link>https://developer.mozilla.org/en/Setting_HTTP_request_headers</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[To get the nsIHttpChannel just before the HTTP request is made we need to observe the "http-on-modify-request" topic.
]]></description>
<dc:subject>xul api documentation reference javascript firefox extension http</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:1c2fba4f0364/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xul"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:firefox"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:extension"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developer.yahoo.com/yui/yuidoc/">
    <title>Yahoo! UI Library: YUI Doc</title>
    <dc:date>2008-12-09T00:34:37+00:00</dc:date>
    <link>http://developer.yahoo.com/yui/yuidoc/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[YUI Doc is a Python application used at build time to generate API documentation for JavaScript code.
]]></description>
<dc:subject>python tools code javascript documentation yui</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:61eeadb0c01e/</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:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:yui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sites.google.com/site/ocropus/documentation/ocr-output-format-links">
    <title>OCR Output Format Links (OCRopus)</title>
    <dc:date>2008-11-19T17:08:12+00:00</dc:date>
    <link>http://sites.google.com/site/ocropus/documentation/ocr-output-format-links</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Links to documentation for various styles of OCR output.
]]></description>
<dc:subject>ocr xml documentation standards</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:0d7095521465/</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:xml"/>
	<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="http://www.gbv.de/wikis/cls/Getting_started_with_SeeAlso">
    <title>Getting started with SeeAlso</title>
    <dc:date>2008-11-18T00:39:48+00:00</dc:date>
    <link>http://www.gbv.de/wikis/cls/Getting_started_with_SeeAlso</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The SeeAlso Linkserver API documentation is intended for web developers that want to write dynamic web pages that include additional links, or to developers that want to provide links and other information to specific resources that people can include in their web pages.
]]></description>
<dc:subject>library webservices api documentation hypermedia</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:a9ce3b6f2c04/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sphinx.pocoo.org/">
    <title>Overview — Sphinx v0.4.2 documentation</title>
    <dc:date>2008-10-02T15:41:44+00:00</dc:date>
    <link>http://sphinx.pocoo.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Sphinx is a tool that makes it easy to create intelligent and beautiful documentation for Python projects.
]]></description>
<dc:subject>python documentation tools</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:a4ed1adfa7db/</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:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.mediawiki.org/wiki/API:Changing_wiki_content">
    <title>API:Changing wiki content - MediaWiki</title>
    <dc:date>2008-09-26T15:03:54+00:00</dc:date>
    <link>http://www.mediawiki.org/wiki/API:Changing_wiki_content</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Changing wiki content through the API is possible, but must be explicitly enabled by setting $wgEnableWriteAPI = true; in LocalSettings.php (this feature is enabled on Wikimedia wikis).
]]></description>
<dc:subject>wiki documentation api wikipedia reference</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:c789afbe2a1e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wiki"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wikipedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developer.yahoo.com/ypatterns/wireframes/">
    <title>Design Stencils - Yahoo! Design Pattern Library</title>
    <dc:date>2008-06-03T09:40:56+00:00</dc:date>
    <link>http://developer.yahoo.com/ypatterns/wireframes/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A design stencil kit to help designers quickly create mockups for specifications and user testing.
]]></description>
<dc:subject>web design tools documentation</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:b7bb86128948/</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:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://n2.talis.com/wiki/Main_Page">
    <title>n² wiki</title>
    <dc:date>2008-05-02T02:34:09+00:00</dc:date>
    <link>http://n2.talis.com/wiki/Main_Page</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The hub for developers working with the Talis Platform. The Talis Platform is a hosted system which provides an efficient, robust storage infrastructure for documents and metadata.
]]></description>
<dc:subject>semweb tools platform documents metadata reference howto api documentation</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:2bdf36e03743/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:platform"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.1-incubating/docs/html/">
    <title>UIMA Documentation</title>
    <dc:date>2008-02-20T05:51:31+00:00</dc:date>
    <link>http://incubator.apache.org/uima/downloads/releaseDocs/2.2.1-incubating/docs/html/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Documentation for version 2.2.1 of UIMA.
]]></description>
<dc:subject>extraction tools java documentation</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:ee10c699b05c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:extraction"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://webcitation.org/">
    <title>WebCite</title>
    <dc:date>2007-11-15T00:35:11+00:00</dc:date>
    <link>http://webcitation.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[WebCite® is an archiving system for webreferences (cited webpages and websites), which can be used by authors, editors, and publishers of scholarly papers and books, to ensure that cited webmaterial will remain available to readers in the future.
]]></description>
<dc:subject>academia citation infrastructure documentation web</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:aed1d291d3d0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:academia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:citation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developer.amazonwebservices.com/connect/kbcategory.jspa?categoryID=87">
    <title>Amazon EC2 Technical Documentation</title>
    <dc:date>2007-11-02T19:51:15+00:00</dc:date>
    <link>http://developer.amazonwebservices.com/connect/kbcategory.jspa?categoryID=87</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Docs for Amazon's Elastic Computing Cloud.
]]></description>
<dc:subject>distributed computers reference documentation webservices</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:ab9c267cda44/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:computers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.amazon.com/August-Sander-People-20th-Century/dp/0810963981/">
    <title>August Sander: People of the 20th Century (7 Volume Set)</title>
    <dc:date>2007-04-05T04:35:23+00:00</dc:date>
    <link>http://www.amazon.com/August-Sander-People-20th-Century/dp/0810963981/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Sander so refined the art of portraiture that his moving images of his fellow countrymen have been heralded both as an important sociological document and a photographic masterpiece.
]]></description>
<dc:subject>photography documentation sociology books wishlist</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:2fdd5f714cd4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:photography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sociology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wishlist"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dogasu.bulbagarden.net/comparisons/comparison_links.html">
    <title>Anime Comparison Sites</title>
    <dc:date>2007-02-15T18:14:00+00:00</dc:date>
    <link>http://dogasu.bulbagarden.net/comparisons/comparison_links.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Sites documenting the changes made to various anime series when they were exported to the US.
]]></description>
<dc:subject>anime video editing documentation japan usa culture cinema narrative fans</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:364d399b2e17/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:anime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:japan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:usa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cinema"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:narrative"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:fans"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://forums.applenova.com/showpost.php?p=432791&amp;postcount=11">
    <title>R/W NTFS from OSX using MacFUSE</title>
    <dc:date>2007-02-15T16:47:31+00:00</dc:date>
    <link>http://forums.applenova.com/showpost.php?p=432791&amp;postcount=11</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[It's still a little cumbersome and user-unfriendly, but the remaining stuff can be worked out easily.
]]></description>
<dc:subject>osx unix windows code documentation reference</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:04934ae593b9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:osx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:unix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:windows"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://simile.mit.edu/exhibit/">
    <title>SIMILE | Exhibit</title>
    <dc:date>2007-01-23T15:38:37+00:00</dc:date>
    <link>http://simile.mit.edu/exhibit/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The data is stored in JSON files, and the database is implemented in Javascript and running inside the web browser.
]]></description>
<dc:subject>ajax cache database design display documentation information interface javascript mit semweb tools time maps</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:c5028ba9f2bd/</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:cache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:display"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:mit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:maps"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.mnot.net/webdesc/wadl_documentation.xsl">
    <title>wadl_documentation.xsl</title>
    <dc:date>2006-12-13T20:16:04+00:00</dc:date>
    <link>http://www.mnot.net/webdesc/wadl_documentation.xsl</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[WADL to HTML documentation stylesheet.
]]></description>
<dc:subject>webservices api documentation tools xml xslt</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:8c47e32db4e1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xslt"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developers.facebook.com/documentation.php">
    <title>Facebook Developers | Documentation</title>
    <dc:date>2006-08-17T15:31:29+00:00</dc:date>
    <link>http://developers.facebook.com/documentation.php</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Facebook API enables outside applications to make remote procedure calls to Facebook on behalf of a Facebook user.
]]></description>
<dc:subject>api development documentation reference webservices social networking</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:8c0d81b584b9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:social"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:networking"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.naturaldocs.org/">
    <title>Natural Docs</title>
    <dc:date>2006-07-19T20:20:16+00:00</dc:date>
    <link>http://www.naturaldocs.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Natural Docs is an open-source, extensible, multi-language documentation generator. You document your code in a natural syntax that reads like plain English.
]]></description>
<dc:subject>code documentation development tools opensource perl</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:c74f1467c74f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:perl"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>